texmacs
/
doc
mirror of https://github.com/texmacs/doc.git
1
0
Fork 0
Code

doc: fix broken hlinks (en only) and minor changes. Please check new 

internal links are the intended ones.
This commit is contained in:
Philippe Joyez 2022-12-31 12:04:11 +00:00
parent 2a22a39d70
commit 6037f42bc1
25 changed files with 152 additions and 214 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
about/contribute/converters/converters.en.tm
View File

@ -8,12 +8,12 @@
If you are familiar with <TeX>, <LaTeX>, Html, Xml, Sgml, Markdown, Mathml, If you are familiar with <TeX>, <LaTeX>, Html, Xml, Sgml, Markdown, Mathml,
Pdf, Rtf, or any other frequently used data format, please consider Pdf, Rtf, or any other frequently used data format, please consider
contributing to writing good converters for one or more of these formats. contributing to writing good converters for one or more of these formats.
In <hlink|<menu|Help|Source code|Data format>|../../../devel/format/format.en.tm> In <hlink|<menu|Help|Source code|Data format>|../../../devel/format/basics/basics.en.tm>
you will find details about the <TeXmacs> data format and in you will find details about the <TeXmacs> data format and in
<hlink|<menu|Help|Source code|Data conversion>|../../../devel/source/conversions.en.tm> <hlink|<menu|Help|Source code|Data conversion>|../../../devel/source/conversions.en.tm>
we give some suggestions which might be helpful for these projects. we give some suggestions which might be helpful for these projects.
<tmdoc-copyright|1998--2019|Joris van der Hoeven|Darcy Shen> <tmdoc-copyright|1998\U2019|Joris van der Hoeven|Darcy Shen>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1

2
about/contribute/using/using.en.tm
View File

@ -17,7 +17,7 @@
<hlink|contact us|../../authors/contact.en.tm> if you want to contribute to <hlink|contact us|../../authors/contact.en.tm> if you want to contribute to
these or any other issues. In the <menu|Help> menu you can find these or any other issues. In the <menu|Help> menu you can find
documentation about the <hlink|source code|../../../devel/source/source.en.tm> documentation about the <hlink|source code|../../../devel/source/source.en.tm>
of <TeXmacs>, its <hlink|document format|../../../devel/format/format.en.tm>, of <TeXmacs>, its <hlink|document format|../../../devel/format/basics/basics.en.tm>,
how to write <hlink|interfaces|../../../devel/plugin/plugin.en.tm> with how to write <hlink|interfaces|../../../devel/plugin/plugin.en.tm> with
other formats, and so on. other formats, and so on.

41
about/projects/roadmap-external.en.tm
View File

@ -3,35 +3,33 @@
<style|tmdoc> <style|tmdoc>
<\body> <\body>
<tmdoc-title|Ongoing external developments> <tmdoc-title|external developments>
Some people which are not part of the core development team use <TeXmacs> Some people which are not part of the core development team use <TeXmacs>
for other projects. We do our best to support such external developments for other projects. We do our best to support such external developments
and make the necessary changes inside <TeXmacs> when necessary. Here and make the necessary changes inside <TeXmacs> when necessary. Here
follows a list of a few initiatives that we are aware of: follows a list of a few initiatives that we have been aware of:
<\itemize> <\itemize>
<item><hlink|Lionel Mamane|http://www.cs.ru.nl/~lionelm/> is developing a <item>Lionel Mamane has developed a plug-in for the
plug-in for the <hlink|<name|Coq>|http://coq.inria.fr/coq-fra.html> proof <hlink|<name|Coq>|https://coq.inria.fr/> proof assistant, called
assistant, called <name|Tmegg>. A first version of this plug-in is about <name|Tmegg>, but was never released publicly. Similarly, Henri Lesourd
to be released; please check Lionel's homepage. Similarly, Henri Lesourd developed an interface to the \<Omega\>mega mathematical assistant
is developing an interface to the <hlink|Omega system. The use of <TeXmacs> as a front-end for proof assistants and
system|http://www.ags.uni-sb.de/~omega/software/omega/index.html>. The theorem provers raises interesting questions about asynchroneous plug-in
use of <TeXmacs> as a front-end for proof assistants and theorem provers evaluations, keeping track and appropriate rendering of the state of a
raises interesting questions about asynchroneous plug-in evaluations, prover, appropriate mathematical and proof markup, etc.
keeping track and appropriate rendering of the state of a prover,
appropriate mathematical and proof markup, etc.
<item>Saugata Basu, Richard Pollack and Marie-François Roy have written <item>Saugata Basu, Richard Pollack and Marie-Fran<61>ois Roy have written
an interactive book ``<hlink|Algorithms in Real Algebraic an interactive book \P<hlink|Algorithms in Real Algebraic
Geometry|http://perso.univ-rennes1.fr/marie-francoise.roy/bpr-posted1.html>'' Geometry|https://perso.univ-rennes1.fr/marie-francoise.roy/bpr-ed2-posted3.html>\Q
using <TeXmacs>. Any people interested in developing addional interactive using <TeXmacs>. Any people interested in developing addional interactive
features inside <TeXmacs> are invited to contact us. features inside <TeXmacs> are invited to contact us.
<item><hlink|Felix Breuer|http://www.felixbreuer.net/index.html> and <item><hlink|Felix Breuer|http://www.felixbreuer.net/index.html> and
formerly <name|David Mentré> have considered developing a <hlink|literate formerly <name|David Mentr<EFBFBD>> have considered developing a <hlink|literate
programming plug-in|http://david.mentre.free.fr/serendipity/index.php?/archives/8-Literate-programming-as-source-code-comments.html> programming plug-in|http://www.felixbreuer.net/LP4TeXmacs-0.1.tar.gz> for
for <TeXmacs>. Another such initiative is <TeXmacs>. Another such initiative is
<hlink|<name|Fangle>|http://www.nongnu.org/fangle/>, which has recently <hlink|<name|Fangle>|http://www.nongnu.org/fangle/>, which has recently
been started by <name|Sam Liddicott>. Any concrete implementation of been started by <name|Sam Liddicott>. Any concrete implementation of
their proposals would happily find its way into the main distribution. their proposals would happily find its way into the main distribution.
@ -49,8 +47,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|language|english>
</collection>
</initial>

10
about/welcome/welcome.en.tm
View File

@ -28,12 +28,6 @@
documentation about the <TeXmacs> format, its primitives and environment documentation about the <TeXmacs> format, its primitives and environment
variables, and the standard style files. variables, and the standard style files.
<item>In the <hlink|<menu|Help|Tutorial>|../../tutorial/tut-tutorial.en.tm>
menu, we have started a <TeXmacs> tutorial. The tutorial is mainly
intended for beginners, but the later chapters should also be useful for
more experienced users. Unfortunately, the tutorial is not very complete
yet.
<item>The <hlink|<menu|Help|About>|../../about/about.en.tm> menu contains <item>The <hlink|<menu|Help|About>|../../about/about.en.tm> menu contains
more information about <TeXmacs>, like information about its more information about <TeXmacs>, like information about its
<hlink|authors|../../about/authors/authors.en.tm>, how to <hlink|contact <hlink|authors|../../about/authors/authors.en.tm>, how to <hlink|contact
@ -45,6 +39,10 @@
<menu|Help|full manuals>. In fact, you may compile such books yourself <menu|Help|full manuals>. In fact, you may compile such books yourself
from any help page using <menu|Help|full manuals|Compile book>. This may from any help page using <menu|Help|full manuals|Compile book>. This may
take a few minutes though. take a few minutes though.
<item>Finally the <hlink|<TeXmacs> website|https://www.texmacs.org>
provides further material such as videos, tutorials (not necessarily
up-to-date), FAQs, links to user forum and mailing lists, etc.\
</itemize> </itemize>
<section|Contribute to <TeXmacs>> <section|Contribute to <TeXmacs>>

4
devel/format/environment/env-general.en.tm
View File

@ -93,7 +93,7 @@
<src-var|prog-language> variable in order to determine a concrete <src-var|prog-language> variable in order to determine a concrete
implementation as well as a particular instance of the current implementation as well as a particular instance of the current
programming language. For instance, in case of the programming language. For instance, in case of the
<hlink|<name|Maxima>|../../../main/interface/cas/man-maxima.en.tm> <hlink|<name|Maxima>|../../../../plugins/maxima/doc/maxima-abstract.en.tm>
language, different implementation may be used fooor the underlying language, different implementation may be used fooor the underlying
<name|Lisp>. Similarly, one may wish to run two different instances of <name|Lisp>. Similarly, one may wish to run two different instances of
<name|Maxima> in parallel. <name|Maxima> in parallel.
@ -136,7 +136,7 @@
like ``<verbatim|Salmon>'', are supported for different color charts: like ``<verbatim|Salmon>'', are supported for different color charts:
<hlink|<verbatim|dvips>|https://en.wikibooks.org/wiki/LaTeX/Colors#The_68_standard_colors_known_to_dvips>, <hlink|<verbatim|dvips>|https://en.wikibooks.org/wiki/LaTeX/Colors#The_68_standard_colors_known_to_dvips>,
<hlink|<verbatim|x11>|https://en.wikipedia.org/wiki/X11_color_names#Color_name_charts> <hlink|<verbatim|x11>|https://en.wikipedia.org/wiki/X11_color_names#Color_name_charts>
and <hlink|<verbatim|html>|http://www.w3schools.com/html/html_colornames.asp>. and <hlink|<verbatim|html>|https://www.w3schools.com/colors/colors_names.asp>.
</explain> </explain>
<\explain> <\explain>

21
devel/format/regular/prim-space.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.0.3.10> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|White space primitives> <tmdoc-title|White space primitives>
@ -11,9 +11,9 @@
<explain-macro|vspace|len|min|max><explain-synopsis|vertical space after> <explain-macro|vspace|len|min|max><explain-synopsis|vertical space after>
<|explain> <|explain>
This primitive inserts an elastic vertical space after the current This primitive inserts an elastic vertical space after the current
paragraph. All operands must be <hyper-link|length paragraph. All operands must be <hlink|length
values|../language/lengths.en.tm>. The <src-arg|len> argument specifies values|../basics/lengths.en.tm>. The <src-arg|len> argument specifies the
the default length and the <src-arg|min> and <src-arg|max> arguments the default length and the <src-arg|min> and <src-arg|max> arguments the
bounds to vertical stretching for page breaking and filling. If bounds to vertical stretching for page breaking and filling. If
<src-arg|min> and <src-arg|max> are not specified, then they are <src-arg|min> and <src-arg|max> are not specified, then they are
determined implicitly from the length unit of <src-arg|len>. determined implicitly from the length unit of <src-arg|len>.
@ -57,9 +57,9 @@
<explain-macro|hspace|len|min|max><explain-synopsis|stretchable <explain-macro|hspace|len|min|max><explain-synopsis|stretchable
horizontal space> horizontal space>
<|explain> <|explain>
This primitive inserts a stretchable horizontal space of nominal This primitive inserts a stretchable horizontal space of nominal width
width <src-arg|len>, which must be a <hyper-link|length <src-arg|len>, which must be a <hlink|length
value|../language/lengths.en.tm>. The <src-arg|min> and <src-arg|max> value|../basics/lengths.en.tm>. The <src-arg|min> and <src-arg|max>
arguments specify bounds to horizontal stretching for line breaking and arguments specify bounds to horizontal stretching for line breaking and
filling. If <src-arg|min> and <src-arg|max> are not specified, then they filling. If <src-arg|min> and <src-arg|max> are not specified, then they
are determined implicitly from the length unit of <src-arg|len>. are determined implicitly from the length unit of <src-arg|len>.
@ -88,7 +88,7 @@
<\indent> <\indent>
<explain-macro|htab|min> inserts a strong spring of minimal width <explain-macro|htab|min> inserts a strong spring of minimal width
<src-arg|min> and of weight unity. The <src-arg|min> operand must be a <src-arg|min> and of weight unity. The <src-arg|min> operand must be a
<hyper-link|length value|../language/lengths.en.tm>. <hlink|length value|../basics/lengths.en.tm>.
<explain-macro|htab|min|weight> specifies the weight, which can be a <explain-macro|htab|min|weight> specifies the weight, which can be a
positive decimal number or one of the two special values documented positive decimal number or one of the two special values documented
@ -119,3 +119,6 @@
Texts. A copy of the license is included in the section entitled "GNU Free Texts. A copy of the license is included in the section entitled "GNU Free
Documentation License".> Documentation License".>
</body> </body>
<initial|<\collection>
</collection>>

2
devel/scheme/gui/scheme-gui-dialogs.en.tm
View File

@ -89,7 +89,7 @@
</session> </session>
<scm|resize> is another of the several available container or <scm|resize> is another of the several available container or
<hlink|content management widgets|scheme-gui-container.en.tm>. It accepts <hlink|content management widgets|scheme-gui-advanced.en.tm>. It accepts
two sorts of arguments. Either one sets a fixed size for the widget with two sorts of arguments. Either one sets a fixed size for the widget with
two strings, as in the example above, or one passes two lists, the first two strings, as in the example above, or one passes two lists, the first
for widths, the second for heights, with the minimum, default and maximum for widths, the second for heights, with the minimum, default and maximum

6
devel/scheme/gui/scheme-gui-lists-trees.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.99.8> <TeXmacs|2.1.2>
<style|<tuple|tmdoc|old-spacing>> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Displaying lists and trees> <tmdoc-title|Displaying lists and trees>
@ -215,7 +215,7 @@
<paragraph|Examples>See <scm|widget10> in <paragraph|Examples>See <scm|widget10> in
<hlink|<verbatim|menu-test.scm>|$TEXMACS_PATH/progs/kernel/gui/menu-test.scm> <hlink|<verbatim|menu-test.scm>|$TEXMACS_PATH/progs/kernel/gui/menu-test.scm>
and ``<hlink|Displaying lists and trees|$TEXMACS_PATH/doc/devel/scheme/gui/scheme-gui-lists-trees.scm>''. and ``<hlink|Displaying lists and trees|$TEXMACS_PATH/doc/devel/scheme/gui/scheme-gui-lists-trees.en.tm>''.
</explain> </explain>
<paragraph|An example using data roles> <paragraph|An example using data roles>

58
devel/scheme/overview/scheme-overview.en.tm
View File

@ -1,52 +1,53 @@
<TeXmacs|1.0.5.2> <TeXmacs|2.1.2>
<style|tmdoc> <style|tmdoc>
<\body> <\body>
<tmdoc-title|Overview of the <value|scheme> extension language> <tmdoc-title|Overview of the <scheme> extension language>
One major characteristic of <TeXmacs> is the possibility to extend the One major characteristic of <TeXmacs> is the possibility to extend the
editor using the <name|Guile>-<value|scheme> <em|extension language>. Such editor using the <name|Guile>-<scheme> <em|extension language>. Such
extensions can be simple, like a personal boot file containing frequently extensions can be simple, like a personal boot file containing frequently
used keyboard shortcuts, or more complex, like a plug-in with special used keyboard shortcuts, or more complex, like a plug-in with special
editing routines for a particular type of documents. The <value|scheme> editing routines for a particular type of documents. The <scheme> language
language can also be used interactively from within the editor or invoked can also be used interactively from within the editor or invoked by special
by special markup like ``actions''. markup like \Pactions\Q.
In this chapter, we give an overview of why and how to use <value|scheme> In this chapter, we give an overview of why and how to use <scheme> from
from within <TeXmacs>. The first sections provide sufficient information within <TeXmacs>. The first sections provide sufficient information for
for someone who wants to program some basic customization of the keyboard someone who wants to program some basic customization of the keyboard and
and menus. The latter sections give an introduction to the general menus. The latter sections give an introduction to the general architecture
architecture of the <value|scheme> API and some important features and of the <scheme> API and some important features and particularities of way
particularities of way <value|scheme> is used within <TeXmacs>. The reading <scheme> is used within <TeXmacs>. The reading of the overview is highly
of the overview is highly recommended to anyone who wants to make recommended to anyone who wants to make non-trivial use of <scheme> inside
non-trivial use of <value|scheme> inside <TeXmacs>. <TeXmacs>.
More complete documentation about the <value|scheme> modules provided by More complete documentation about the <scheme> modules provided by
<TeXmacs> is available from the <menu|Help|Scheme extensions> menu. We also <TeXmacs> is available from the <menu|Help|Scheme extensions> menu. We also
recommend the following on-line manuals about <value|scheme> and its recommend the following on-line manuals about <scheme> and its <name|Guile>
<name|Guile> implementation: implementation:
<\itemize-minus> <\itemize-minus>
<item><hlink|The <value|scheme> programming <item><hlink|The <scheme> programming
language|http://www.scheme.com/tspl2d/index.html>. language|http://www.scheme.com/tspl2d/index.html>.
<item><hlink|Guile reference manual|http://latakia.dyndns.org/~ruhl/guile-doc/guile_toc.html>. <item><hlink|Guile reference manual|https://www.gnu.org/software/guile/manual/>.
</itemize-minus> </itemize-minus>
For further information about <value|scheme>, we refer to For further information about <scheme>, we refer to
<hlink|<verbatim|http://www.schemers.org>|http://www.schemers.org>. As a <hlink|<verbatim|www.schemers.org>|http://www.schemers.org> or
<hlink|community.schemewiki.org|http://community.schemewiki.org/>. As a
general rule, we also encourage users to take a look at the <TeXmacs> general rule, we also encourage users to take a look at the <TeXmacs>
source code for concrete examples on how to use <value|scheme> from within source code for concrete examples on how to use <scheme> from within
<TeXmacs>. <TeXmacs>.
<\traverse> <\traverse>
<branch|Why <TeXmacs> uses <value|scheme> as its extension <branch|Why <TeXmacs> uses <scheme> as its extension
language|overview-why.en.tm> language|overview-why.en.tm>
<branch|When and how to use <value|scheme>|overview-start.en.tm> <branch|When and how to use <scheme>|overview-start.en.tm>
<branch|General architecture of the <value|scheme> <branch|General architecture of the <scheme>
API|overview-architecture.en.tm> API|overview-architecture.en.tm>
<branch|The module system and lazy definitions|overview-lazyness.en.tm> <branch|The module system and lazy definitions|overview-lazyness.en.tm>
@ -70,8 +71,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|language|english>
</collection>
</initial>

21
devel/style/customize/customize-theorems.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.0.4> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Customizing numbered textual environments> <tmdoc-title|Customizing numbered textual environments>
@ -30,11 +30,11 @@
<inactive*|<new-theorem|experiment|Experiment>> <inactive*|<new-theorem|experiment|Experiment>>
</tm-fragment> </tm-fragment>
When available in the <TeXmacs> dictionaries, the text ``Experiment'' will When available in the <TeXmacs> dictionaries, the text \PExperiment\Q will
be automatically translated when your document is written in a foreign be automatically translated when your document is written in a foreign
language. In the section about <hyper-link|how to define new language. In the section about <hlink|how to define new
environments|../../../main/styles/std-dtds/env-manage-dtd.en.tm>, it is environments|../../../main/styles/env/env-base-dtd.en.tm>, it is also
also explained how to define other numbered textual environments (besides explained how to define other numbered textual environments (besides
theorems, remarks and exercises). theorems, remarks and exercises).
<paragraph*|Customization of the rendering> <paragraph*|Customization of the rendering>
@ -42,7 +42,7 @@
The principal rendering of the environments can be customized by redefining The principal rendering of the environments can be customized by redefining
the <markup|render-theorem>, <markup|render-remark> and the <markup|render-theorem>, <markup|render-remark> and
<markup|render-exercise> macros. These macros take the <src-arg|name> of <markup|render-exercise> macros. These macros take the <src-arg|name> of
the environment (like ``Theorem <no-break>1.2'') and its <src-arg|body> as the environment (like \PTheorem <no-break>1.2\Q) and its <src-arg|body> as
arguments. For instance, if you want theorems to appear in a slightly arguments. For instance, if you want theorems to appear in a slightly
indented way, with a slanted body, then you may redefine indented way, with a slanted body, then you may redefine
<markup|render-theorem> as follows: <markup|render-theorem> as follows:
@ -94,7 +94,7 @@
<paragraph*|Customization of the numbering> <paragraph*|Customization of the numbering>
In the sections about <hyper-link|counters and counter In the sections about <hlink|counters and counter
groups|../../../main/styles/std/std-counter-dtd.en.tm>, it is explained how groups|../../../main/styles/std/std-counter-dtd.en.tm>, it is explained how
to customize the counters of numbered environments for particular purposes. to customize the counters of numbered environments for particular purposes.
For instance, by redefining <markup|inc-theorem>, you may force theorems to For instance, by redefining <markup|inc-theorem>, you may force theorems to
@ -117,7 +117,7 @@
<inactive*|<assign|display-std-env|<macro|nr|<section-prefix><arg|nr>>>> <inactive*|<assign|display-std-env|<macro|nr|<section-prefix><arg|nr>>>>
</tm-fragment> </tm-fragment>
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -126,3 +126,6 @@
Texts. A copy of the license is included in the section entitled "GNU Free Texts. A copy of the license is included in the section entitled "GNU Free
Documentation License".> Documentation License".>
</body> </body>
<initial|<\collection>
</collection>>

17
devel/style/customize/customize.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.0.4> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Customizing the standard <TeXmacs> styles> <tmdoc-title|Customizing the standard <TeXmacs> styles>
@ -12,8 +12,8 @@
understanding of the global architecture of the standard style files and a understanding of the global architecture of the standard style files and a
more precise understanding of the parts you wish to customize. In this more precise understanding of the parts you wish to customize. In this
section, we will explain the general principles. For more details, we refer section, we will explain the general principles. For more details, we refer
to the chapter on the <hyper-link|principal <TeXmacs> to the chapter on the <hlink|principal <TeXmacs>
tags|../../../main/styles/std-dtds/dtds.en.tm>. tags|../design/style-language.en.tm>.
<\traverse> <\traverse>
<branch|Organization of the style files and <branch|Organization of the style files and
@ -33,7 +33,7 @@
information|customize-title.en.tm> information|customize-title.en.tm>
</traverse> </traverse>
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -43,8 +43,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|language|english>
</collection>
</initial>

26
devel/style/design/style-assign.en.tm
View File

@ -1,12 +1,12 @@
<TeXmacs|1.0.3.5> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Assignments> <tmdoc-title|Assignments>
All user defined <TeXmacs> macros and style variables are stored in the All user defined <TeXmacs> macros and style variables are stored in the
``current typesetting environment''. This environment associates a tree \Pcurrent typesetting environment\Q. This environment associates a tree
value to each string variable. Variables whose values are macros correspond value to each string variable. Variables whose values are macros correspond
to new primitives. The others are ordinary environment variables. The to new primitives. The others are ordinary environment variables. The
primitives for operating on the environment are available from primitives for operating on the environment are available from
@ -36,9 +36,9 @@
Finally, you may associate logical properties to environment variables Finally, you may associate logical properties to environment variables
using the <markup|drd-props> primitive. This is explained in more detail in using the <markup|drd-props> primitive. This is explained in more detail in
the section about <hyper-link|macro primitives|../../format/primitives/prim-macro.en.tm>. the section about <hlink|macro primitives|../../format/stylesheet/prim-macro.en.tm>.
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -48,17 +48,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|page-bot|30mm>
<associate|page-even|30mm>
<associate|page-odd|30mm>
<associate|page-reduce-bot|15mm>
<associate|page-reduce-left|25mm>
<associate|page-reduce-right|25mm>
<associate|page-reduce-top|15mm>
<associate|page-right|30mm>
<associate|page-top|30mm>
<associate|par-width|150mm>
</collection>
</initial>

29
devel/style/design/style-compute.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.0.3.5> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Computational markup> <tmdoc-title|Computational markup>
@ -9,7 +9,7 @@
<menu|Source|Tuple> and <menu|Source|Condition> you will find different <menu|Source|Tuple> and <menu|Source|Condition> you will find different
primitives for computing with integers, strings, tuples and boolean values. primitives for computing with integers, strings, tuples and boolean values.
For instance, in the following code, the <markup|new-important> tag defines For instance, in the following code, the <markup|new-important> tag defines
a new ``important tag'' as well as a variant in red: a new \Pimportant tag\Q as well as a variant in red:
<\tm-fragment> <\tm-fragment>
<inactive*|<assign|new-important|<macro|name|<quasi|<style-with|src-compact|none|<style-with|src-compact|none|<assign|<unquote|<arg|name>>|<macro|x|<with|font-series|bold|<arg|x>>>>><style-with|src-compact|none|<assign|<unquote|<merge|<arg|name>|-red>>|<macro|x|<with|font-series|bold|color|red|<arg|x>>>>>>>>>> <inactive*|<assign|new-important|<macro|name|<quasi|<style-with|src-compact|none|<style-with|src-compact|none|<assign|<unquote|<arg|name>>|<macro|x|<with|font-series|bold|<arg|x>>>>><style-with|src-compact|none|<assign|<unquote|<merge|<arg|name>|-red>>|<macro|x|<with|font-series|bold|color|red|<arg|x>>>>>>>>>>
@ -17,11 +17,10 @@
Here we use the <markup|merge> primitive in order to concatenate two Here we use the <markup|merge> primitive in order to concatenate two
strings. The different computational primitives are described in more strings. The different computational primitives are described in more
detail in the <hyper-link|corresponding detail in the <hlink|corresponding section|../../format/stylesheet/prim-functional.en.tm>
section|../../format/primitives/prim-functional.en.tm> on the on the <hlink|<TeXmacs> primitives|../../format/stylesheet/stylesheet.en.tm>.
<hyper-link|<TeXmacs> primitives|../../format/primitives/primitives.en.tm>.
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -31,17 +30,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|page-bot|30mm>
<associate|page-even|30mm>
<associate|page-odd|30mm>
<associate|page-reduce-bot|15mm>
<associate|page-reduce-left|25mm>
<associate|page-reduce-right|25mm>
<associate|page-reduce-top|15mm>
<associate|page-right|30mm>
<associate|page-top|30mm>
<associate|par-width|150mm>
</collection>
</initial>

27
devel/style/design/style-flow.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.0.3.7> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Control flow> <tmdoc-title|Control flow>
@ -50,11 +50,10 @@
can be edited by the user). Therefore, you will have to manually give this can be edited by the user). Therefore, you will have to manually give this
information using the <markup|drd-props> primitive. The <markup|case>, information using the <markup|drd-props> primitive. The <markup|case>,
<markup|while> and <markup|for-each> primitives are explained in more <markup|while> and <markup|for-each> primitives are explained in more
detail in the <hyper-link|corresponding detail in the <hlink|corresponding section|../../format/stylesheet/prim-control.en.tm>
section|../../format/primitives/prim-control.en.tm> on the on the <hlink|<TeXmacs> primitives|../../format/stylesheet/stylesheet.en.tm>.
<hyper-link|<TeXmacs> primitives|../../format/primitives/primitives.en.tm>.
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -64,17 +63,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|page-bot|30mm>
<associate|page-even|30mm>
<associate|page-odd|30mm>
<associate|page-reduce-bot|15mm>
<associate|page-reduce-left|25mm>
<associate|page-reduce-right|25mm>
<associate|page-reduce-top|15mm>
<associate|page-right|30mm>
<associate|page-top|30mm>
<associate|par-width|150mm>
</collection>
</initial>

2
devel/style/design/style-language.en.tm
View File

@ -10,7 +10,7 @@
the style-sheet language of <TeXmacs>. In this section, we will give a more the style-sheet language of <TeXmacs>. In this section, we will give a more
complete survey of the available features. For more detailed descriptions, complete survey of the available features. For more detailed descriptions,
we refer to the chapter about the <hlink|<TeXmacs> we refer to the chapter about the <hlink|<TeXmacs>
primitives|../../format/primitives/primitives.en.tm>. primitives|../../format/stylesheet/stylesheet.en.tm>.
The style-sheet primitives can be obtained from the <menu|Source> menu when The style-sheet primitives can be obtained from the <menu|Source> menu when
you are in source mode. In all other modes, the <menu|Source> menu becomes you are in source mode. In all other modes, the <menu|Source> menu becomes

30
devel/style/design/style-macro.en.tm
View File

@ -1,6 +1,6 @@
<TeXmacs|1.0.3.7> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|Macro expansion> <tmdoc-title|Macro expansion>
@ -11,19 +11,19 @@
expansion is computed by <name|Scheme> or a plug-in. The macro-related expansion is computed by <name|Scheme> or a plug-in. The macro-related
primitives are available from the <menu|Source|Macro> menu. Below, we will primitives are available from the <menu|Source|Macro> menu. Below, we will
only describe the ordinary macros. For more details, we refer to the only describe the ordinary macros. For more details, we refer to the
section about <hyper-link|macro primitives|../../format/primitives/prim-macro.en.tm>. section about <hlink|macro primitives|../../format/stylesheet/prim-macro.en.tm>.
Ordinary macros are usually defined using Ordinary macros are usually defined using
<\tm-fragment> <\tm-fragment>
<inactive*|<assign|my-macro|<macro|<active*|x<rsub|1>>|<active*|<with|mode|math|\<cdots\>>>|<active*|x<rsub|n>>|body>>> <inactive*|<assign|my-macro|<macro|<active*|x<rsub|1>>|<active*|<math|\<cdots\>>>|<active*|x<rsub|n>>|body>>>
</tm-fragment> </tm-fragment>
After such an assignment, <markup|my-macro> becomes a new primitive with After such an assignment, <markup|my-macro> becomes a new primitive with
<with|mode|math|n> arguments, which may be called using <math|n> arguments, which may be called using
<\tm-fragment> <\tm-fragment>
<inactive|<my-macro|<active*|y<rsub|1>>|<active*|<with|mode|math|\<cdots\>>>|<active*|y<rsub|n>>>> <inactive|<my-macro|<active*|y<rsub|1>>|<active*|<math|\<cdots\>>>|<active*|y<rsub|n>>>>
</tm-fragment> </tm-fragment>
Inside the body of the macro, the <markup|arg> primitive may be used to Inside the body of the macro, the <markup|arg> primitive may be used to
@ -59,7 +59,7 @@
<inactive*|<assign|overloaded-hi|<macro|name|<style-with|src-compact|none|<compound|<if|<nice-weather>|<value|happy-hi>|<value|sad-hi>>|<arg|name>>>>>> <inactive*|<assign|overloaded-hi|<macro|name|<style-with|src-compact|none|<compound|<if|<nice-weather>|<value|happy-hi>|<value|sad-hi>>|<arg|name>>>>>>
</tm-fragment> </tm-fragment>
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -69,17 +69,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|page-bot|30mm>
<associate|page-even|30mm>
<associate|page-odd|30mm>
<associate|page-reduce-bot|15mm>
<associate|page-reduce-left|25mm>
<associate|page-reduce-right|25mm>
<associate|page-reduce-top|15mm>
<associate|page-right|30mm>
<associate|page-top|30mm>
<associate|par-width|150mm>
</collection>
</initial>

34
devel/style/presentation/src-present-intro.en.tm
View File

@ -1,13 +1,13 @@
<TeXmacs|1.0.3.7> <TeXmacs|2.1.2>
<style|tmdoc> <style|<tuple|tmdoc|english>>
<\body> <\body>
<tmdoc-title|ASCII-based or tree-based editing: an intricate choice> <tmdoc-title|ASCII-based or tree-based editing: an intricate choice>
Most users are used to edit source code using a conventional editor like Most users are used to edit source code using a conventional editor like
<name|Emacs>, while presenting the source code in ASCII format. Since all <name|Emacs>, while presenting the source code in ASCII format. Since all
<TeXmacs> documents are stored as <hyper-link|trees|../../format/format.en.tm>, <TeXmacs> documents are stored as <hlink|trees|../../../devel/format/basics/basics.en.tm>,
an interesting but complicated question is which format is most suitable an interesting but complicated question is which format is most suitable
for editing such documents. One option is to represent the tree using an for editing such documents. One option is to represent the tree using an
ASCII-based format, such as XML, Scheme, or the native format for storing ASCII-based format, such as XML, Scheme, or the native format for storing
@ -15,10 +15,10 @@
fundamental distinction between source code and normal documents. fundamental distinction between source code and normal documents.
In <TeXmacs> we have chosen to implement the second option. More precisely, In <TeXmacs> we have chosen to implement the second option. More precisely,
any document can be edited in ``source mode'', which is merely a mode for any document can be edited in \Psource mode\Q, which is merely a mode for
rendering the document in a way which makes its tree structure particularly rendering the document in a way which makes its tree structure particularly
apparent. It may be instructive to take an arbitrary document of yours and apparent. It may be instructive to take an arbitrary document of yours and
to take a look at it in ``source mode'' by enabling to take a look at it in \Psource mode\Q by enabling
<menu|Document|Source|Edit source tree>. <menu|Document|Source|Edit source tree>.
The choice between ASCII-based editing and tree-based editing is The choice between ASCII-based editing and tree-based editing is
@ -38,7 +38,7 @@
highlighting, indentation, <abbr|etc.> highlighting, indentation, <abbr|etc.>
<item><label|structure-constraints>One is not constraint by any <item><label|structure-constraints>One is not constraint by any
``structure'' during the editing phase. \Pstructure\Q during the editing phase.
</enumerate> </enumerate>
Our approach is to reproduce as much of the above advantages in a Our approach is to reproduce as much of the above advantages in a
@ -50,11 +50,11 @@
For instance, consider a piece of manually formatted code like For instance, consider a piece of manually formatted code like
<\cpp-fragment> <\cpp-code>
if (cond) hop \ \ = 2; if (cond) hop \ \ = 2;
else \ \ \ \ \ holala= 3; else \ \ \ \ \ holala= 3;
</cpp-fragment> </cpp-code>
Clearly, the user had a particular formatting policy when writing this Clearly, the user had a particular formatting policy when writing this
code. However, this policy does not appear in the document: manual code. However, this policy does not appear in the document: manual
@ -70,7 +70,7 @@
structured highlighting. Further tools will be developed later and we are structured highlighting. Further tools will be developed later and we are
open for any suggestions from our users. open for any suggestions from our users.
<tmdoc-copyright|1998--2004|Joris van der Hoeven> <tmdoc-copyright|1998\U2004|Joris van der Hoeven>
<tmdoc-license|Permission is granted to copy, distribute and/or modify this <tmdoc-license|Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.1 document under the terms of the GNU Free Documentation License, Version 1.1
@ -80,17 +80,5 @@
Documentation License".> Documentation License".>
</body> </body>
<\initial> <initial|<\collection>
<\collection> </collection>>
<associate|page-bot|30mm>
<associate|page-even|30mm>
<associate|page-odd|30mm>
<associate|page-reduce-bot|15mm>
<associate|page-reduce-left|25mm>
<associate|page-reduce-right|25mm>
<associate|page-reduce-top|15mm>
<associate|page-right|30mm>
<associate|page-top|30mm>
<associate|par-width|150mm>
</collection>
</initial>

2
main/config/man-config-keyboard.en.tm
View File

@ -137,7 +137,7 @@
If, for some reason, the standard <TeXmacs> shortcuts are not sufficient or If, for some reason, the standard <TeXmacs> shortcuts are not sufficient or
suitable for you, then you may <hlink|define your own suitable for you, then you may <hlink|define your own
shortcuts|../scheme/man-keyboard.en.tm>. shortcuts|../scheme/man-custom-keyboard.en.tm>.
<tmdoc-copyright|1998--2002|Joris van der Hoeven> <tmdoc-copyright|1998--2002|Joris van der Hoeven>

6
main/convert/man-convert.en.tm
View File

@ -47,3 +47,9 @@
Texts. A copy of the license is included in the section entitled "GNU Free Texts. A copy of the license is included in the section entitled "GNU Free
Documentation License".> Documentation License".>
</body> </body>
<\initial>
<\collection>
<associate|preamble|false>
</collection>
</initial>

2
main/editing/man-versioning.en.tm
View File

@ -13,7 +13,7 @@
automatic. Below, we will describe in more detail how this tool works. automatic. Below, we will describe in more detail how this tool works.
In addition, there exist many stand-alone programs for maintaining several In addition, there exist many stand-alone programs for maintaining several
versions of a same file, such as <hlink|<name|Subversion>|http://subversion.tigris.org/>, versions of a same file, such as <hlink|<name|Subversion>|https://en.wikipedia.org/wiki/Apache_Subversion>,
<hlink|<name|Git>|http://git-scm.com/>, <hlink|<name|Git>|http://git-scm.com/>,
<hlink|<name|Darcs>|http://darcs.net/>, <hlink|<name|GNU <hlink|<name|Darcs>|http://darcs.net/>, <hlink|<name|GNU
Arch>|http://www.gnu.org/software/gnu-arch/>, just to mention a few of Arch>|http://www.gnu.org/software/gnu-arch/>, just to mention a few of

2
main/faq/faq.en.tm
View File

@ -251,7 +251,7 @@
<item>Try reinstalling <TeXmacs>, preferably the latest version that <item>Try reinstalling <TeXmacs>, preferably the latest version that
used to work for you. Old versions can be found at used to work for you. Old versions can be found at
<slink|ftp://ftp.texmacs.org/pub/TeXmacs/tmftp/> \ <slink|http://ftp.texmacs.org/pub/TeXmacs/tmftp/>
<item>Submit a bug report, report the issue to one of our mailing <item>Submit a bug report, report the issue to one of our mailing
lists, or contact the authors. lists, or contact the authors.

4
main/math/keyboard/man-enter-math.en.tm
View File

@ -38,8 +38,8 @@
This entry allows you to create an <markup|eqnarray*>, a three columns This entry allows you to create an <markup|eqnarray*>, a three columns
wide table-like environment (see <hlink|creating wide table-like environment (see <hlink|creating
tables|../table/man-create-table.en.tm>). This environment is typically tables|../../table/man-create-table.en.tm>). This environment is
used for lists of multiple relations like typically used for lists of multiple relations like
<\eqnarray*> <\eqnarray*>
<tformat|<table|<row|<cell|x+0>|<cell|=>|<cell|x>>|<row|<cell|x+<around|(|\<um\>x|)>>|<cell|=>|<cell|0>>|<row|<cell|x+y>|<cell|=>|<cell|y+x>>|<row|<cell|<around|(|x+y|)>+z>|<cell|=>|<cell|x+<around|(|y+z|)>>>>> <tformat|<table|<row|<cell|x+0>|<cell|=>|<cell|x>>|<row|<cell|x+<around|(|\<um\>x|)>>|<cell|=>|<cell|0>>|<row|<cell|x+y>|<cell|=>|<cell|y+x>>|<row|<cell|<around|(|x+y|)>+z>|<cell|=>|<cell|x+<around|(|y+z|)>>>>>

4
main/math/semantics/man-syntax-correction.en.tm
View File

@ -15,8 +15,8 @@
instance, the formulas might contain some text or meaningful whitespace. instance, the formulas might contain some text or meaningful whitespace.
Another example of an <em|ad hoc> notation is the sign sequence Another example of an <em|ad hoc> notation is the sign sequence
<math|++-+-+>. In such cases, the user should <hlink|explicitly <math|++-+-+>. In such cases, the user should <hlink|explicitly
annotate|man-semantic-annotation.en.tm> the appropriate parts of the annotate|man-semantics.en.tm> the appropriate parts of the formula in
formula in order to make them semantically meaningful. order to make them semantically meaningful.
<item>The <TeXmacs> grammar used for the interpretation of mathematical <item>The <TeXmacs> grammar used for the interpretation of mathematical
formulas may be incomplete or inadequate for certain situations. It is formulas may be incomplete or inadequate for certain situations. It is

2
main/text/keyboard/man-keyboard.en.tm
View File

@ -6,7 +6,7 @@
<tmdoc-title|Mastering the keyboard> <tmdoc-title|Mastering the keyboard>
We recall that the section on <hlink|general We recall that the section on <hlink|general
conventions|../start/man-conventions.en.tm> contains explanations on the conventions|../../start/man-conventions.en.tm> contains explanations on the
way keyboard shortcuts are printed in this manual. It may also be useful to way keyboard shortcuts are printed in this manual. It may also be useful to
take a look at the section on <hlink|keyboard take a look at the section on <hlink|keyboard
configuration|../../config/man-config-keyboard.en.tm>. configuration|../../config/man-config-keyboard.en.tm>.

4
main/text/keyboard/man-keyboard.fr.tm
View File

@ -6,8 +6,8 @@
<tmdoc-title|Maîtrise du clavier> <tmdoc-title|Maîtrise du clavier>
Nous rappelons que la section sur \ les <hlink|conventions Nous rappelons que la section sur \ les <hlink|conventions
générales|../start/man-conventions.fr.tm> contiens des explications sur la générales|../../start/man-conventions.fr.tm> contient des explications sur la
manière dont les raccourcis clavier sont afficher dans ce manuel. Il peut manière dont les raccourcis clavier sont affichés dans ce manuel. Il peut
aussi être utile de consulter la section sur <hlink|configuration aussi être utile de consulter la section sur <hlink|configuration
clavier|../../config/man-config-keyboard.fr.tm>. clavier|../../config/man-config-keyboard.fr.tm>.