fontsize changes not understood

Meer, Hans van der

24 May 2016 24 May '16

3:04 p.m.

Can someone explain to me the changes in fontsize in the following example? Enclosing the fontswitches in a group did not change the behaviour. \setupbodyfont[dejavu,12pt] \def\MarkMasterA{\inmargin[location=left]{\bgroup\switchtobodyfont[9pt]\red Master\egroup}} \def\MarkMasterB{\inmargin[location=left]{\bgroup\usebodyfont[9pt]\red Master\egroup}} \starttext \startsection[title=\MarkMasterA First title] \input hawking \MarkMasterA \input hawking \stopsection \startsection[title=\MarkMasterB First title] \input hawking \MarkMasterB \input hawking \blank contextversion=\contextversion \stopsection \stoptext In the first section the absolute value of 9 pt appears not to be honoured but it looks as if there is a reduction relative to the surrounding font. In the second section the size does not change and looks even bigger than the first one above. I am baffled and do not understand why not all fontsizes are the same absolute 9pt as requested? Hans van der Meer

Attachments:

attachment.html (text/html — 1.4 KB)
marginfontsize.pdf (application/pdf — 30.6 KB)

Show replies by date

Wolfgang Schuster

24 May 24 May

3:57 p.m.

...

Meer, Hans van der mailto:H.vanderMeer@uva.nl 24. Mai 2016 um 15:04

Can someone explain to me the changes in fontsize in the following example? Enclosing the fontswitches in a group did not change the behaviour.

\setupbodyfont[dejavu,12pt] \def\MarkMasterA{\inmargin[location=left]{\bgroup\switchtobodyfont[9pt]\red Master\egroup}} \def\MarkMasterB{\inmargin[location=left]{\bgroup\usebodyfont[9pt]\red Master\egroup}} \starttext \startsection[title=\MarkMasterA First title] \input hawking \MarkMasterA \input hawking \stopsection \startsection[title=\MarkMasterB First title] \input hawking \MarkMasterB \input hawking \blank contextversion=\contextversion \stopsection \stoptext

In the first section the absolute value of 9 pt appears not to be honoured but it looks as if there is a reduction relative to the surrounding font. In the second section the size does not change and looks even bigger than the first one above.

I am baffled and do not understand why not all fontsizes are the same absolute 9pt as requested? When you flush the margin text in the heading its style (e.g. \tfa) is added to your font size for the margin text.

To get rid of the size change from \section in your example you can add the "reset" keyword to \switchtobodyfont. \def\MarkMasterA{\margindata[inleft][style={\switchtobodyfont[reset,9pt]},color=red]{Master}} Wolfgang

Meer, Hans van der

4:28 p.m.

...

On 24 May 2016, at 15:57, Wolfgang Schuster wrote:

...
Meer, Hans van der 24. Mai 2016 um 15:04

Can someone explain to me the changes in fontsize in the following example? Enclosing the fontswitches in a group did not change the behaviour.

\setupbodyfont[dejavu,12pt] \def\MarkMasterA{\inmargin[location=left]{\bgroup\switchtobodyfont[9pt]\red Master\egroup}} \def\MarkMasterB{\inmargin[location=left]{\bgroup\usebodyfont[9pt]\red Master\egroup}} \starttext \startsection[title=\MarkMasterA First title] \input hawking \MarkMasterA \input hawking \stopsection \startsection[title=\MarkMasterB First title] \input hawking \MarkMasterB \input hawking \blank contextversion=\contextversion \stopsection \stoptext

In the first section the absolute value of 9 pt appears not to be honoured but it looks as if there is a reduction relative to the surrounding font. In the second section the size does not change and looks even bigger than the first one above.

I am baffled and do not understand why not all fontsizes are the same absolute 9pt as requested? When you flush the margin text in the heading its style (e.g. \tfa) is added to your font size for the margin text.

To get rid of the size change from \section in your example you can add the "reset" keyword to \switchtobodyfont.

Thanks, I really didn't know that, it could not spot it in my copy of "Fonts in Context". But although reset works for \switchtobodyfont, it is not working in \usebodyfont[reset,9pt] in the second section. There it keeps the size derived from the section title. Both commands however, are reported to inherit from \setupbodyfont (where the reset is named). Should that be correct? Hans van der Meer

Wolfgang Schuster

5 p.m.

...

Meer, Hans van der mailto:H.vanderMeer@uva.nl 24. Mai 2016 um 16:28

Thanks, I really didn't know that, it could not spot it in my copy of "Fonts in Context".

But although reset works for \switchtobodyfont, it is not working in \usebodyfont[reset,9pt] in the second section. Why do you think \usebodyfont can be used to change the font size in your document, is this mentioned in a manual? There it keeps the size derived from the section title. Both commands however, are reported to inherit from \setupbodyfont (where the reset is named). Should that be correct? IIRC \usebodyfont can be used to preload a typeface at the begin of a document which make switching to it later in the document with \switchtobodyfont or \setupbodyfont faster but this also means settings like the font size have no effect. The reference manual shows "inherits from XXX" in such a case because a) it is true that the command inherits its values from another command b) it’s faster to document (can be changed but one has to check which arguments are valid).

Wolfgang

Meer, Hans van der

5:47 p.m.

On 24 May 2016, at 17:00, Wolfgang Schuster mailto:schuster.wolfgang@gmail.com> wrote: Meer, Hans van dermailto:H.vanderMeer@uva.nl 24. Mai 2016 um 16:28 Thanks, I really didn't know that, it could not spot it in my copy of "Fonts in Context". But although reset works for \switchtobodyfont, it is not working in \usebodyfont[reset,9pt] in the second section. Why do you think \usebodyfont can be used to change the font size in your document, is this mentioned in a manual? There it keeps the size derived from the section title. Both commands however, are reported to inherit from \setupbodyfont (where the reset is named). Should that be correct? IIRC \usebodyfont can be used to preload a typeface at the begin of a document which make switching to it later in the document with \switchtobodyfont or \setupbodyfont faster but this also means settings like the font size have no effect. The reference manual shows "inherits from XXX" in such a case because a) it is true that the command inherits its values from another command b) it’s faster to document (can be changed but one has to check which arguments are valid). Never too old to learn something I didn't fully understood before. Thanks. met vriendelijke groet Hans van der Meer

Jean-Pierre Delange

6:09 p.m.

Hi HansvdMeer, There are many ways to answer your question. Maybe, the first and simple one is that we may want to have some narrow paragraphs in the middle of our work, as quotations, for example, or whatever you want. So, it is a question of method : to put it in the preamble as \setupbodyfont, and \switchbodyfont on demand is probably easier than populate your code with numerous other commands. See here the 3.11.2 paragraph of this Wikibook in French : https://fr.wikibooks.org/wiki/ConTeXt#D.C3.A9finir_une_police_et_changer_de_...) JP ----- Mail original ----- De: "Hans van der Meer" À: "NTG ConTeXt" Envoyé: Mardi 24 Mai 2016 17:47:19 Objet: Re: [NTG-context] fontsize changes not understood On 24 May 2016, at 17:00, Wolfgang Schuster < schuster.wolfgang@gmail.com > wrote: Meer, Hans van der 24. Mai 2016 um 16:28 Thanks, I really didn't know that, it could not spot it in my copy of "Fonts in Context". But although reset works for \switchtobodyfont, it is not working in \usebodyfont[reset,9pt] in the second section. Why do you think \usebodyfont can be used to change the font size in your document, is this mentioned in a manual? There it keeps the size derived from the section title. Both commands however, are reported to inherit from \setupbodyfont (where the reset is named). Should that be correct? IIRC \usebodyfont can be used to preload a typeface at the begin of a document which make switching to it later in the document with \switchtobodyfont or \setupbodyfont faster but this also means settings like the font size have no effect. The reference manual shows "inherits from XXX" in such a case because a) it is true that the command inherits its values from another command b) it’s faster to document (can be changed but one has to check which arguments are valid). Never too old to learn something I didn't fully understood before. Thanks. met vriendelijke groet Hans van der Meer ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Jean-Pierre Delange

5:57 p.m.

New subject: win64 : luatex is not recognize as an internal command

Dear list, I am currently testing and experimenting such things as a brand new installation (Context Process 0.63 2016.05.22 15:18) on a Windows x64 computer. I have made a new installation of ConTeXt Standalone (with TeXWorks), downloading the *.zip file, etc. 1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'. As a result, the compilation after context --generate is 0,988 s. (and much more than 1 sec with 'context --make' command, which needs usually more than 30 sec. to compile) and after context --make I obtain a \dumpdump message with this cryptic sentence (in French) : 'luatex' is not recognized as an internal or external command, an executable program or a command file. And when I try to do this : \ starttext \startsection[title={Testing ConTeXt}] This is my {\em first} ConTeXt document. \stopsection \stoptext Here is the result : mtx-context | fatal error: no return code, message: luatex: No such file or directory I have missed something ... but what is it ? I am deeply sorry to bother you with this question, but I don't clearly see when, where and what I have missed. Maybe I'm tired ... JP

Hans Hagen

6:56 p.m.

New subject: win64 : luatex is not recognize as an internal command

On 5/24/2016 5:57 PM, Jean-Pierre Delange wrote:

...

Dear list,

I am currently testing and experimenting such things as a brand new installation (Context Process 0.63 2016.05.22 15:18) on a Windows x64 computer. I have made a new installation of ConTeXt Standalone (with TeXWorks), downloading the *.zip file, etc.

1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'.

As a result, the compilation after context --generate is 0,988 s. (and much more than 1 sec with 'context --make' command, which needs usually more than 30 sec. to compile) and after context --make I obtain a \dumpdump message with this cryptic sentence (in French) : 'luatex' is not recognized as an internal or external command, an executable program or a command file.

And when I try to do this : \ starttext \startsection[title={Testing ConTeXt}] This is my {\em first} ConTeXt document. \stopsection \stoptext

Here is the result : mtx-context | fatal error: no return code, message: luatex: No such file or directory

I have missed something ... but what is it ?

Alan BRASLAU

7:55 p.m.

New subject: win64 : luatex is not recognize as an internal command

On Tue, 24 May 2016 18:56:44 +0200 Hans Hagen wrote:

...

or is your console slow (if you run a lot from the console it makes sense to use 'conemu' as consoles - on any os - take some runtime due to the way tex flushes)

On any OS?? I believe that conemu is a Windows-specific terminal emulator. Alan

Hans Hagen

25 May 25 May

12:30 a.m.

New subject: win64 : luatex is not recognize as an internal command

On 5/24/2016 7:55 PM, Alan BRASLAU wrote:

...

On Tue, 24 May 2016 18:56:44 +0200 Hans Hagen wrote:

...
or is your console slow (if you run a lot from the console it makes sense to use 'conemu' as consoles - on any os - take some runtime due to the way tex flushes)

On any OS??

I believe that conemu is a Windows-specific terminal emulator.

i meant that writing data to the console (from tex) can be responsible for additional runtime; it depends (sometimes) on the font used on the console (osx), ansi control sequence interception, and buffering (the standard wondows console doesn't buffer, conemu on windows does, on other operating systems it depends) .. tex writes in chunks (no line buffering) because it's often progress info (although context does bit of optimization) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Jean-Pierre Delange

24 May 24 May

8:29 p.m.

New subject: win64 : luatex is not recognize as an internal command

Hi Hans and others, 1) Yes, I have set the PATH to /context/tex/texmf-win64/bin (set PATH=%PATH%). For this ConTeXt installation, I run ConteXt on Windows x64, on an Intel i5Core, with 8Go RAM on a 500Go Barracuda 7200t/mn hard drive. I'll try it on a Mac OS X Mavericks or Yosemite (in virtualization). I use to test ConTeXT on a Intel i3Core Lenovo Laptop, where ConTeXt is installed on Ubuntu and Windows 10 and run without any problem. 2) Each time I do a 'context --generate' on the Intel i5Core, the process is quick (less than 10 s.), but with 'context --make', the proces takes more or less than 35 sec. JP ----- Mail original ----- De: "Hans Hagen" À: "mailing list for ConTeXt users" Envoyé: Mardi 24 Mai 2016 18:56:44 Objet: Re: [NTG-context] win64 : luatex is not recognize as an internal command On 5/24/2016 5:57 PM, Jean-Pierre Delange wrote:

...

Dear list,

I am currently testing and experimenting such things as a brand new installation (Context Process 0.63 2016.05.22 15:18) on a Windows x64 computer. I have made a new installation of ConTeXt Standalone (with TeXWorks), downloading the *.zip file, etc.

1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'.

As a result, the compilation after context --generate is 0,988 s. (and much more than 1 sec with 'context --make' command, which needs usually more than 30 sec. to compile) and after context --make I obtain a \dumpdump message with this cryptic sentence (in French) : 'luatex' is not recognized as an internal or external command, an executable program or a command file.

And when I try to do this : \ starttext \startsection[title={Testing ConTeXt}] This is my {\em first} ConTeXt document. \stopsection \stoptext

Here is the result : mtx-context | fatal error: no return code, message: luatex: No such file or directory

I have missed something ... but what is it ?

is there a texmf-win64 directory someplace? btw, 30 sec for making a format sounds a lot to me (normally it takes me around 4.5 sec for one format including generating the file database, a few year old laptop but with an ssd) ... or is your console slow (if you run a lot from the console it makes sense to use 'conemu' as consoles - on any os - take some runtime due to the way tex flushes) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Jean-Pierre Delange

25 May 25 May

12:10 a.m.

New subject: win64 : luatex is not recognize as an internal command

I answer to Hans, Alan and me. In order to install Context on Windows 10, don't forget to restart the system when you have installed ConTeXt MK IV (Standalone) and set all the stuff (PATH, etc.). I used to know about restarting the opsys on Windows, but I've forgotten it... To Hans : total runtime for 'context --make' = 13,513 s. Thanks ----- Mail original ----- De: "Jean-Pierre Delange" À: "mailing list for ConTeXt users" Envoyé: Mardi 24 Mai 2016 20:29:04 Objet: Re: [NTG-context] win64 : luatex is not recognize as an internal command Hi Hans and others, 1) Yes, I have set the PATH to /context/tex/texmf-win64/bin (set PATH=%PATH%). For this ConTeXt installation, I run ConteXt on Windows x64, on an Intel i5Core, with 8Go RAM on a 500Go Barracuda 7200t/mn hard drive. I'll try it on a Mac OS X Mavericks or Yosemite (in virtualization). I use to test ConTeXT on a Intel i3Core Lenovo Laptop, where ConTeXt is installed on Ubuntu and Windows 10 and run without any problem. 2) Each time I do a 'context --generate' on the Intel i5Core, the process is quick (less than 10 s.), but with 'context --make', the proces takes more or less than 35 sec. JP ----- Mail original ----- De: "Hans Hagen" À: "mailing list for ConTeXt users" Envoyé: Mardi 24 Mai 2016 18:56:44 Objet: Re: [NTG-context] win64 : luatex is not recognize as an internal command On 5/24/2016 5:57 PM, Jean-Pierre Delange wrote:

...

Dear list,

I am currently testing and experimenting such things as a brand new installation (Context Process 0.63 2016.05.22 15:18) on a Windows x64 computer. I have made a new installation of ConTeXt Standalone (with TeXWorks), downloading the *.zip file, etc.

1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'.

As a result, the compilation after context --generate is 0,988 s. (and much more than 1 sec with 'context --make' command, which needs usually more than 30 sec. to compile) and after context --make I obtain a \dumpdump message with this cryptic sentence (in French) : 'luatex' is not recognized as an internal or external command, an executable program or a command file.

And when I try to do this : \ starttext \startsection[title={Testing ConTeXt}] This is my {\em first} ConTeXt document. \stopsection \stoptext

Here is the result : mtx-context | fatal error: no return code, message: luatex: No such file or directory

I have missed something ... but what is it ?

Hans Hagen

12:42 a.m.

New subject: win64 : luatex is not recognize as an internal command

On 5/25/2016 12:10 AM, Jean-Pierre Delange wrote:

...

I answer to Hans, Alan and me. In order to install Context on Windows 10, don't forget to restart the system when you have installed ConTeXt MK IV (Standalone) and set all the stuff (PATH, etc.). I used to know about restarting the opsys on Windows, but I've forgotten it...

normally you only need to restart the process that needs the adapted path (console or editor)

...

To Hans : total runtime for 'context --make' = 13,513 s.

ok, that's better (still twice the time than an i7 with ssd)

...

Thanks

----- Mail original ----- De: "Jean-Pierre Delange" À: "mailing list for ConTeXt users" Envoyé: Mardi 24 Mai 2016 20:29:04 Objet: Re: [NTG-context] win64 : luatex is not recognize as an internal command

Hi Hans and others,

1) Yes, I have set the PATH to /context/tex/texmf-win64/bin (set PATH=%PATH%). For this ConTeXt installation, I run ConteXt on Windows x64, on an Intel i5Core, with 8Go RAM on a 500Go Barracuda 7200t/mn hard drive. I'll try it on a Mac OS X Mavericks or Yosemite (in virtualization). I use to test ConTeXT on a Intel i3Core Lenovo Laptop, where ConTeXt is installed on Ubuntu and Windows 10 and run without any problem.

2) Each time I do a 'context --generate' on the Intel i5Core, the process is quick (less than 10 s.), but with 'context --make', the proces takes more or less than 35 sec.

JP

----- Mail original ----- De: "Hans Hagen" À: "mailing list for ConTeXt users" Envoyé: Mardi 24 Mai 2016 18:56:44 Objet: Re: [NTG-context] win64 : luatex is not recognize as an internal command

On 5/24/2016 5:57 PM, Jean-Pierre Delange wrote:

...
Dear list,

I am currently testing and experimenting such things as a brand new installation (Context Process 0.63 2016.05.22 15:18) on a Windows x64 computer. I have made a new installation of ConTeXt Standalone (with TeXWorks), downloading the *.zip file, etc.

1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'.

As a result, the compilation after context --generate is 0,988 s. (and much more than 1 sec with 'context --make' command, which needs usually more than 30 sec. to compile) and after context --make I obtain a \dumpdump message with this cryptic sentence (in French) : 'luatex' is not recognized as an internal or external command, an executable program or a command file.

And when I try to do this : \ starttext \startsection[title={Testing ConTeXt}] This is my {\em first} ConTeXt document. \stopsection \stoptext

Here is the result : mtx-context | fatal error: no return code, message: luatex: No such file or directory

I have missed something ... but what is it ?

is there a texmf-win64 directory someplace?

btw, 30 sec for making a format sounds a lot to me (normally it takes me around 4.5 sec for one format including generating the file database, a few year old laptop but with an ssd) ... or is your console slow (if you run a lot from the console it makes sense to use 'conemu' as consoles - on any os - take some runtime due to the way tex flushes)

Hans

----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl ----------------------------------------------------------------- ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

-- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

L.S.-Soc&Gam

12:48 a.m.

New subject: win64 : luatex is not recognize as an internal command

There are three things which I don't fully understand either: 1. Why are there three files on " http://standalone.contextgarden.net/setup/ " which is reachable via the " Download ConTeXt " link? There are [ ] context-setup-mswin.zip http://standalone.contextgarden.net/setup/context-setup-mswin.zip 2016-05-23 22:36 21M [ ] context-setup-win32.zip http://standalone.contextgarden.net/setup/context-setup-win32.zip 2016-05-23 22:36 21M [ ] context-setup-win64.zip http://standalone.contextgarden.net/setup/context-setup-win64.zip 2016-05-23 22:36 21M Wouldn't *win32* and *win64* files alone suffice? I am wondering what the *mswin* files is for. It is a little bit confusing. Especially because there is also another folder " [...] contextgarden.net/setup2/ ". Again with [ ] context-setup-win32.zip http://standalone.contextgarden.net/setup2/context-setup-win32.zip 2016-05-23 22:36 21M [ ] context-setup-win64.zip http://standalone.contextgarden.net/setup2/context-setup-win64.zip 2016-05-23 22:37 21M 2. Is the " setup2 " folder really necessary? Last thing is about the problem with finding lua... In your description you don't mention using " first-setup.bat ": 1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'. I mean I see your point that you want to use it standalone. So... 3. Why don't you try it the simple way? I am on Win10 x64, but this should work for every supported Win system: 0. I donwloaded context-setup-win32.zip http://standalone.contextgarden.net/setup/context-setup-win32.zip from " setup " folder. 1. Extracted " context " anywhere. I used short paths: " C:\context " or " D:\context ". Renamed to ConTeXt for readability. 2. Used command (cmd.exe ideally as Admin) and went to my CTX path: " D:\ConTeXt\ " 3. Entered first-setup.bat -> I also added " --modules=all ". CTX is around 400 MB now. I am sure it's fully worth it! 4. After download finished I navigated deeper to: " tex\texmf-win64\bin " like " D:\ConTeXt\tex\texmf-win64\bin " 5. Created a document " test.tex " right inside " bin " folder. 6. Edited it with editor and only enterd: " \starttext Hello world \stoptext " 7. Save the document 8. Entered " context test.tex " 9. And finished was my first PDF. Maybe you could try the same... Greeting, Seba

L.S.-Soc&Gam

12:50 a.m.

New subject: win64 : luatex is not recognize as an internal command

context-setup-win64.zip http://standalone.contextgarden.net/setup/context-setup-win64.zip was what i downloaded of course. Am 25.05.2016 um 00:48 schrieb L.S.-Soc&Gam:

...

3. Why don't you try it the simple way? I am on Win10 x64, but this should work for every supported Win system:

0. I donwloaded context-setup-win32.zip http://standalone.contextgarden.net/setup/context-setup-win32.zip from " setup " folder. 1. Extracted " context " anywhere. I used short paths: " C:\context " or " D:\context ". Renamed to ConTeXt for readability. 2. Used command (cmd.exe ideally as Admin) and went to my CTX path: " D:\ConTeXt\ " 3. Entered first-setup.bat -> I also added " --modules=all ". CTX is around 400 MB now. I am sure it's fully worth it! 4. After download finished I navigated deeper to: " tex\texmf-win64\bin " like " D:\ConTeXt\tex\texmf-win64\bin " 5. Created a document " test.tex " right inside " bin " folder. 6. Edited it with editor and only enterd: " \starttext Hello world \stoptext " 7. Save the document 8. Entered " context test.tex " 9. And finished was my first PDF.

Maybe you could try the same...

Greeting, Seba

Mojca Miklavec

10:46 a.m.

New subject: win64 : luatex is not recognize as an internal command

On 25 May 2016 at 00:48, L.S.-Soc&Gam wrote:

...

There are three things which I don't fully understand either:

1. Why are there three files on " http://standalone.contextgarden.net/setup/ " which is reachable via the " Download ConTeXt " link? There are

context-setup-mswin.zip 2016-05-23 22:36 21M context-setup-win32.zip 2016-05-23 22:36 21M context-setup-win64.zip 2016-05-23 22:36 21M

Wouldn't *win32* and *win64* files alone suffice? I am wondering what the *mswin* files is for. It is a little bit confusing.

I don't like mswin and would like to switch to win32 to make it consistent with win64, but I need the blessing from Hans first.

...

Especially because there is also another folder " [...] contextgarden.net/setup2/ ". Again with

context-setup-win32.zip 2016-05-23 22:36 21M context-setup-win64.zip 2016-05-23 22:37 21M

2. Is the " setup2 " folder really necessary?

No. Long time ago Hans asked me if we could switch to rsync from the MinGW project rather than the one based on cygwin's dll. (Then we probably both forgot about this.) The "setup2" is experimental setup bundling rsync from MinGW, the idea was to provide testing setup that would replace the old one. As soon as I get a green light, I could remove "setup", rename "setup2" to "setup" and only leave the new binaries there. (I can also remove "setup2" in principle.) Mojca

Hans Hagen

11:18 a.m.

New subject: win64 : luatex is not recognize as an internal command

On 5/25/2016 10:46 AM, Mojca Miklavec wrote:

...

Long time ago Hans asked me if we could switch to rsync from the MinGW project rather than the one based on cygwin's dll. (Then we probably both forgot about this.)

it's more that we never decided on a moment of switching ... the updater should work with --mingw and hen we default to it we only need to change local rsync_variant = "cygwin" into local rsync_variant = "mingw" in mtx-update.lua we could just try that (in the worst case we need to have a few attempts) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

L.S.-Soc&Gam

26 May 26 May

3 a.m.

New subject: win64 : luatex is not recognize as an internal command

Thanks a lot for clarifying this. Well I think it's great to keep CTX open for devs or experimental purposes. Imho the point is that the download section could use a slight tune up. In fact, to make the installation as easy as possible for new users, the main structure might be divided by operating system. Win, Lin, Mac and Experimental or Developer. Right now Wiki looks like: Installation * download ConTeXt http://standalone.contextgarden.net/ * download area http://dl.contextgarden.net/ Me as a new user didn't know which one to take at first. This might be merged. one single donwload button to the ftp and then Win, Lin, Mac, Developer, Experimental. I would love to help with contextgarden wiki, but I am student and it took a long time learning CTX so far. But some day... Only a few words for usability ;-) Thanks for this great piece of idea and greetings from germany to the whole CTX team. Seba Am 25.05.2016 um 10:46 schrieb Mojca Miklavec:

...

I don't like mswin and would like to switch to win32 to make it consistent with win64, but I need the blessing from Hans first.

...

...
2. Is the " setup2 " folder really necessary? No.

Long time ago Hans asked me if we could switch to rsync from the MinGW project rather than the one based on cygwin's dll. (Then we probably both forgot about this.)

The "setup2" is experimental setup bundling rsync from MinGW, the idea was to provide testing setup that would replace the old one.

As soon as I get a green light, I could remove "setup", rename "setup2" to "setup" and only leave the new binaries there. (I can also remove "setup2" in principle.)

Mojca

Jean-Pierre Delange

25 May 25 May

11:36 a.m.

New subject: win64 : luatex is not recognize as an internal command

Hi Seba, 1) On Windows, I unzip context-setup-win64 in C:\[Users]/MyName/Documents/ConTeXt (or something alike, anywhere in C: or D:); 2) cd context/tex; then : context-setup.bat 3) There is no need to get Admin rights to launch context commands, but one has to be carefull before launching the approriate first-setup.bat --modules=all --fonts=all --goodies=all --engine=luatex (which I do in order to use some modules, or fonts) : one has to go to /context/tex/texmf-win/bin or /context/tex/texmf-win64/bin before launching 'context --generate' and 'context --make' to build the trees (including fonts trees). 4) I have not forget to set the PATH; But it seems (only in this peculiar installation, because I run ContExt daily on others machines ) that ConTeXt refuses 'context --generate' and 'context --make', and therefore to parse *.tex files. JP ----- Mail original ----- De: "L.S.-Soc&Gam" À: "mailing list for ConTeXt users" Envoyé: Mercredi 25 Mai 2016 00:48:48 Objet: Re: [NTG-context] win64 : luatex is not recognize as an internal command There are three things which I don't fully understand either: 1. Why are there three files on " http://standalone.contextgarden.net/setup/ " which is reachable via the " Download ConTeXt " link? There are [ ] context-setup-mswin.zip 2016-05-23 22:36 21M [ ] context-setup-win32.zip 2016-05-23 22:36 21M [ ] context-setup-win64.zip 2016-05-23 22:36 21M Wouldn't *win32* and *win64* files alone suffice? I am wondering what the *mswin* files is for. It is a little bit confusing. Especially because there is also another folder " [...] contextgarden.net/setup2/ ". Again with [ ] context-setup-win32.zip 2016-05-23 22:36 21M [ ] context-setup-win64.zip 2016-05-23 22:37 21M 2. Is the " setup2 " folder really necessary? Last thing is about the problem with finding lua... In your description you don't mention using " first-setup.bat ": 1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'. I mean I see your point that you want to use it standalone. So... 3. Why don't you try it the simple way? I am on Win10 x64, but this should work for every supported Win system: 0. I donwloaded context-setup-win32.zip from " setup " folder. 1. Extracted " context " anywhere. I used short paths: " C:\context " or " D:\context ". Renamed to ConTeXt for readability. 2. Used command (cmd.exe ideally as Admin) and went to my CTX path: " D:\ConTeXt\ " 3. Entered first-setup.bat -> I also added " --modules=all ". CTX is around 400 MB now. I am sure it's fully worth it! 4. After download finished I navigated deeper to: " tex\texmf-win64\bin " like " D:\ConTeXt\tex\texmf-win64\bin " 5. Created a document " test.tex " right inside " bin " folder. 6. Edited it with editor and only enterd: " \starttext Hello world \stoptext " 7. Save the document 8. Entered " context test.tex " 9. And finished was my first PDF. Maybe you could try the same... Greeting, Seba ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Jean-Pierre Delange

4:14 p.m.

New subject: ConTeXt on Mac OS X installation

Hi dear fellows, Trying to install ConTeXt on a virtual OS X Mavericks (with VMWare Workstation 12 Pro on Windows 10). 1. Downloading and install ConteXt Minimals simply in /Documents/context 2. In a Terminal : chmod +x first-setup.sh 3. Then : . first-setup.sh 4. After a while, downloading and setting stuff achieved, I type : cd tex, then: . setuptex. Here is the answer : "/Users/adeimantos/Documents/context/tex" is not a valid TEXROOT path. (There is no file "/Users/adeimantos/Documents/context/tex/texmf/tex/plain/base/plain.tex") provide a proper tex root (like '. setuptex /something/tex') What do you think about it ? Many thanks for your help. JP

Jean-Pierre Delange

6:32 p.m.

New subject: ConTeXt on Mac OS X installation

I answer to myself, looking to 2008 mail-post here (it seems to be a recurring issue) : https://www.mail-archive.com/ntg-context@ntg.nl/msg32419.html ----- Mail original ----- De: "Jean-Pierre Delange" À: "mailing list for ConTeXt users" Envoyé: Mercredi 25 Mai 2016 07:14:14 Objet: Re: [NTG-context] ConTeXt on Mac OS X installation Hi dear fellows, Trying to install ConTeXt on a virtual OS X Mavericks (with VMWare Workstation 12 Pro on Windows 10). 1. Downloading and install ConteXt Minimals simply in /Documents/context 2. In a Terminal : chmod +x first-setup.sh 3. Then : . first-setup.sh 4. After a while, downloading and setting stuff achieved, I type : cd tex, then: . setuptex. Here is the answer : "/Users/adeimantos/Documents/context/tex" is not a valid TEXROOT path. (There is no file "/Users/adeimantos/Documents/context/tex/texmf/tex/plain/base/plain.tex") provide a proper tex root (like '. setuptex /something/tex') What do you think about it ? Many thanks for your help. JP ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Jean-Pierre Delange

7:28 p.m.

New subject: ConTeXt on Mac OS X installation

There are a few subtleties to manage in order to install ConTeXt on Mac OS X. The 'setuptex' config is not the same as a Linux one. But documentation does exist on the Net. Just for information, the 'context --make' command process is as follow : system | total runtime: 7.429 seconds ----- Mail original ----- De: "Jean-Pierre Delange" À: "mailing list for ConTeXt users" Envoyé: Mercredi 25 Mai 2016 09:32:27 Objet: Re: [NTG-context] ConTeXt on Mac OS X installation I answer to myself, looking to 2008 mail-post here (it seems to be a recurring issue) : https://www.mail-archive.com/ntg-context@ntg.nl/msg32419.html ----- Mail original ----- De: "Jean-Pierre Delange" À: "mailing list for ConTeXt users" Envoyé: Mercredi 25 Mai 2016 07:14:14 Objet: Re: [NTG-context] ConTeXt on Mac OS X installation Hi dear fellows, Trying to install ConTeXt on a virtual OS X Mavericks (with VMWare Workstation 12 Pro on Windows 10). 1. Downloading and install ConteXt Minimals simply in /Documents/context 2. In a Terminal : chmod +x first-setup.sh 3. Then : . first-setup.sh 4. After a while, downloading and setting stuff achieved, I type : cd tex, then: . setuptex. Here is the answer : "/Users/adeimantos/Documents/context/tex" is not a valid TEXROOT path. (There is no file "/Users/adeimantos/Documents/context/tex/texmf/tex/plain/base/plain.tex") provide a proper tex root (like '. setuptex /something/tex') What do you think about it ? Many thanks for your help. JP ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

josephcanedo＠gmail.com

24 May 24 May

6:59 p.m.

New subject: win64 : luatex is not recognize as an internal command

Hello Jean Pierre, Have you added C:\context\tex\texmf-win64\bin (or whatever dir you installed ConTeXt) directory to PATH env variable ? Best regards Joseph Canedo From: Jean-Pierre Delange Sent: ‎Tuesday‎, ‎May‎ ‎24‎, ‎2016 ‎5‎:‎57‎ ‎PM To: ntg-context@ntg.nl Dear list, I am currently testing and experimenting such things as a brand new installation (Context Process 0.63 2016.05.22 15:18) on a Windows x64 computer. I have made a new installation of ConTeXt Standalone (with TeXWorks), downloading the *.zip file, etc. 1) Download the context-mswin.zip in C:\[...]\Documents; 2) mkdir 'context' => cd 'context' 3) Unzip it and launch context-setup.bat in the new C:\[...]Documents\context 4) Then, go to \context\tex and launch 'setuptex'; 5) Then again, cd \context\tex\texmf-win64\bin and do : 'context --generate', and 'context --make'. As a result, the compilation after context --generate is 0,988 s. (and much more than 1 sec with 'context --make' command, which needs usually more than 30 sec. to compile) and after context --make I obtain a \dumpdump message with this cryptic sentence (in French) : 'luatex' is not recognized as an internal or external command, an executable program or a command file. And when I try to do this : \ starttext \startsection[title={Testing ConTeXt}] This is my {\em first} ConTeXt document. \stopsection \stoptext Here is the result : mtx-context | fatal error: no return code, message: luatex: No such file or directory I have missed something ... but what is it ? I am deeply sorry to bother you with this question, but I don't clearly see when, where and what I have missed. Maybe I'm tired ... JP ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________

Hans Hagen

4:04 p.m.

On 5/24/2016 3:04 PM, Meer, Hans van der wrote:

...

Can someone explain to me the changes in fontsize in the following example? Enclosing the fontswitches in a group did not change the behaviour.

\setupbodyfont[dejavu,12pt] \def\MarkMasterA{\inmargin[location=left]{\bgroup\switchtobodyfont[9pt]\red Master\egroup}} \def\MarkMasterB{\inmargin[location=left]{\bgroup\usebodyfont[9pt]\red Master\egroup}} \starttext \startsection[title=\MarkMasterA First title] \input hawking \MarkMasterA \input hawking \stopsection \startsection[title=\MarkMasterB First title] \input hawking \MarkMasterB \input hawking \blank contextversion=\contextversion \stopsection \stoptext

In the first section the absolute value of 9 pt appears not to be honoured but it looks as if there is a reduction relative to the surrounding font. In the second section the size does not change and looks even bigger than the first one above.

I am baffled and do not understand why not all fontsizes are the same absolute 9pt as requested?

inmargin also has a style parameter that can be set (and maybe it is) \setupbodyfont is a global font switch that should be used local (as it affects the headers footers, spacing etc ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Manuel Conzelmann

4:10 p.m.

New subject: Sorting index register

How can i sort the register alphabetically, so that all indexes are sorted under max. 26 entries (a-z) instead of the default behaviour: sorted alphabetically per page order? At the moment it looks like GATKABF instead of ABFGKT Thx! Am 24.05.2016 15:08 schrieb "Meer, Hans van der" : Can someone explain to me the changes in fontsize in the following example? Enclosing the fontswitches in a group did not change the behaviour. \setupbodyfont[dejavu,12pt] \def\MarkMasterA{\inmargin[location=left]{\bgroup\switchtobodyfont[9pt]\red Master\egroup}} \def\MarkMasterB{\inmargin[location=left]{\bgroup\usebodyfont[9pt]\red Master\egroup}} \starttext \startsection[title=\MarkMasterA First title] \input hawking \MarkMasterA \input hawking \stopsection \startsection[title=\MarkMasterB First title] \input hawking \MarkMasterB \input hawking \blank contextversion=\contextversion \stopsection \stoptext In the first section the absolute value of 9 pt appears not to be honoured but it looks as if there is a reduction relative to the surrounding font. In the second section the size does not change and looks even bigger than the first one above. I am baffled and do not understand why not all fontsizes are the same absolute 9pt as requested? Hans van der Meer

Wolfgang Schuster

4:13 p.m.

New subject: Sorting index register

...

Manuel Conzelmann mailto:conzelma@hs-pforzheim.de 24. Mai 2016 um 16:10 How can i sort the register alphabetically, so that all indexes are sorted under max. 26 entries (a-z) instead of the default behaviour: sorted alphabetically per page order? At the moment it looks like

GATKABF instead of ABFGKT

1. Create a new thread for your problem. 2. Provide a minimal working example. Wolfgang

3131

Age (days ago)

3133

Last active (days ago)

List overview

Download

25 comments

9 participants

participants (9)

Alan BRASLAU
Hans Hagen
Jean-Pierre Delange
josephcanedo＠gmail.com
L.S.-Soc&Gam
Manuel Conzelmann
Meer, Hans van der
Mojca Miklavec
Wolfgang Schuster