uppercase, small caps, numerals and German capital sharp s

uppercase, small caps, numerals and German capital sharp s

[Thomas Fehige]

Hello,

I'm new to ConTeXt and this list. After a long time of using LaTeX and 
xeLaTeX I was finally lured into trying ConTexT by its ability of grid 
typesetting.

Today's problem is a bit complex. In a book project I have several 
points where stuff is capitalized or turned into caps+smallcaps or pure 
smallcaps. My guess is that that should work either with \WORD{Stuff}, 
\Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and 
{\sc\lowercase{Stuff}}. (Not quite, it seems)

I'll use a commercial font called Calluna, but have added Linux Biolinum 
O to the example for those who don't want to download Calluna (the 
"Regular" can be "bought" for free, e.g. at 
https://www.fontspring.com/fonts/exljbris/calluna).

Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER SHARP 
S" at "1E9E. Calluna also has a small caps version at "F727", while 
Biolinum has it at "E092. I'd like to use these glyphs in the 
capitalizations mentioned, but that only works erratically (cf. example).

Secondly, Calluna comes with oldstyle numerals switched on, which is 
nice for normal text, but should change to proportional lining numbers 
in uppercase and to small-cap proportional lining numbers in an 
all-small-cap text. I'm not sure what I'd want in a caps+smallcaps 
context, but certainly not oldstyle numerals with their descenders.

Any hints and ideas? Thanks for reading! -- Thomas

PS: I asked the same question on stackexchange, there's also an image of 
the result of my example: 
http://tex.stackexchange.com/questions/302823/context-uppercase-%C3%9F-customizing-glyph-substitution

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\mainlanguage[de]
\language[de]

\uccode`ß="1E9E    % This gives the capital ß to \uppercase

\definefontfeature[fcalluna][default][]	% I tried all the font features 
built into Calluna, to no avail.

\definefontfamily [myfamily] [serif][Calluna][features=fcalluna]
\definefontfamily [myfamily] [sans] [Linux Biolinum O][features=fcalluna]
\definefontfamily [myfamily] [mono] [TeX Gyre Cursor]

\setupbodyfont [myfamily]
\startTEXpage[offset=10pt]
     \starttabulate[|l|l|l|]
     	 \NC \it Command \NC \it Calluna \NC \it Linux Biolinum \NC\NR
         \NC\type{\WORD{Gruß134}}: 		\NC\WORD{Gruß134} 			\NC 
{\ss\WORD{Gruß134}} 		\NC\NR
         \NC\type{\uppercase{Gruß134}}:	\NC\uppercase{Gruß134} 
\NC{\ss\uppercase{Gruß134}} 	\NC\NR
         \NC\type{\sc{Gruß134}}: 			\NC{\sc Gruß134} 			\NC{\ss{\sc 
Gruß134}}			\NC\NR
         \NC\type{\Cap{Gruß134}:} 		\NC\Cap{Gruß134} 			\NC{\ss 
\Cap{Gruß134}}		\NC\NR
         \NC\type{\cap{Gruß134}:} 		\NC\cap{Gruß134} 			\NC{\ss 
\cap{Gruß134}}		\NC\NR
         \NC\type{{\sc\lowercase{Gruß134}}:} 	 
\NC{\sc\lowercase{Gruß134}} 			\NC{\ss\sc\lowercase{Gruß134}}	\NC\NR
     \stoptabulate
\stopTEXpage
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: uppercase, small caps, numerals and German capital sharp s

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 1943 bytes --]

> Thomas Fehige <mailto:thomas@fehige.de>
> 19. April 2016 um 09:10
> Hello,
>
> I'm new to ConTeXt and this list. After a long time of using LaTeX and 
> xeLaTeX I was finally lured into trying ConTexT by its ability of grid 
> typesetting.
>
> Today's problem is a bit complex. In a book project I have several 
> points where stuff is capitalized or turned into caps+smallcaps or 
> pure smallcaps. My guess is that that should work either with 
> \WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and 
> {\sc\lowercase{Stuff}}. (Not quite, it seems)
>
> I'll use a commercial font called Calluna, but have added Linux 
> Biolinum O to the example for those who don't want to download Calluna 
> (the "Regular" can be "bought" for free, e.g. at 
> https://www.fontspring.com/fonts/exljbris/calluna).
>
> Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER 
> SHARP S" at "1E9E. Calluna also has a small caps version at "F727", 
> while Biolinum has it at "E092. I'd like to use these glyphs in the 
> capitalizations mentioned, but that only works erratically (cf. example).
>
> Secondly, Calluna comes with oldstyle numerals switched on, which is 
> nice for normal text, but should change to proportional lining numbers 
> in uppercase and to small-cap proportional lining numbers in an 
> all-small-cap text. I'm not sure what I'd want in a caps+smallcaps 
> context, but certainly not oldstyle numerals with their descenders.
Use separate threads for each problem. The uppercase sharp s replacement 
with \WORD can be changed in the next beta.

%% begin example
\usemodule[lingual-de]

\setupbodyfont[libertine]

\starttext

Gruß Straße Buße

\WORD{Gruß Straße Buße}

\enabledirectives[fonts.uppercasesharps]

\WORD{Gruß Straße Buße}

\disabledirectives[fonts.uppercasesharps]

\WORD{Gruß Straße Buße}

\stoptext
%% end example

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 3099 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: uppercase, small caps, numerals and German capital sharp s

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 3451 bytes --]

Wolfgang,
> Use separate threads for each problem. The uppercase sharp s 
> replacement with \WORD can be changed in the next beta.
>
> %% begin example
are you saying, use this example as long as the new beta isn't out yet, 
or are you saying, this example will work as soon as I'll use the new 
beta? It doesn't seem to do anything right now, not even an error message.

I was looking for a general way how to substitute one glyph with another 
depending on context, thus I can't see how there are different problems 
in my post? But it's good to hear that others have thought at least of a 
partial solution.

Is my guess right that normally the author of a font ought to provide 
otf features that can be switched on and off to get one result instead 
of the other? That area seems to be utter chaos in the Calluna fonts.

Cheers -- Thomas

Am 19.04.2016 um 14:05 schrieb Wolfgang Schuster:
>> Thomas Fehige <mailto:thomas@fehige.de>
>> 19. April 2016 um 09:10
>> Hello,
>>
>> I'm new to ConTeXt and this list. After a long time of using LaTeX 
>> and xeLaTeX I was finally lured into trying ConTexT by its ability of 
>> grid typesetting.
>>
>> Today's problem is a bit complex. In a book project I have several 
>> points where stuff is capitalized or turned into caps+smallcaps or 
>> pure smallcaps. My guess is that that should work either with 
>> \WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, 
>> and {\sc\lowercase{Stuff}}. (Not quite, it seems)
>>
>> I'll use a commercial font called Calluna, but have added Linux 
>> Biolinum O to the example for those who don't want to download 
>> Calluna (the "Regular" can be "bought" for free, e.g. at 
>> https://www.fontspring.com/fonts/exljbris/calluna).
>>
>> Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER 
>> SHARP S" at "1E9E. Calluna also has a small caps version at "F727", 
>> while Biolinum has it at "E092. I'd like to use these glyphs in the 
>> capitalizations mentioned, but that only works erratically (cf. 
>> example).
>>
>> Secondly, Calluna comes with oldstyle numerals switched on, which is 
>> nice for normal text, but should change to proportional lining 
>> numbers in uppercase and to small-cap proportional lining numbers in 
>> an all-small-cap text. I'm not sure what I'd want in a caps+smallcaps 
>> context, but certainly not oldstyle numerals with their descenders.
> Use separate threads for each problem. The uppercase sharp s 
> replacement with \WORD can be changed in the next beta.
>
> %% begin example
> \usemodule[lingual-de]
>
> \setupbodyfont[libertine]
>
> \starttext
>
> Gruß Straße Buße
>
> \WORD{Gruß Straße Buße}
>
> \enabledirectives[fonts.uppercasesharps]
>
> \WORD{Gruß Straße Buße}
>
> \disabledirectives[fonts.uppercasesharps]
>
> \WORD{Gruß Straße Buße}
>
> \stoptext
> %% end example
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 6207 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: uppercase, small caps, numerals and German capital sharp s

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 3447 bytes --]

Wolfgang,
> Use separate threads for each problem. The uppercase sharp s 
> replacement with \WORD can be changed in the next beta.
>
> %% begin example
are you saying, use this example as long as the new beta isn't out yet, 
or are you saying, this example will work as soon as I'll use the new 
beta? It doesn't seem to do anything right now, not even an error message.

I was looking for a general way how to substitute one glyph with another 
depending on context, thus I can't see how there are different problems 
in my post? But it's good to hear that others have thought at least of a 
partial solution.

Is my guess right that normally the author of a font ought to provide 
otf features that can be switched on and off to get one result instead 
of the other? That area seems to be utter chaos in the Calluna fonts.

Cheers -- Thomas

Am 19.04.2016 um 14:05 schrieb Wolfgang Schuster:
>> Thomas Fehige <mailto:thomas@fehige.de>
>> 19. April 2016 um 09:10
>> Hello,
>>
>> I'm new to ConTeXt and this list. After a long time of using LaTeX 
>> and xeLaTeX I was finally lured into trying ConTexT by its ability of 
>> grid typesetting.
>>
>> Today's problem is a bit complex. In a book project I have several 
>> points where stuff is capitalized or turned into caps+smallcaps or 
>> pure smallcaps. My guess is that that should work either with 
>> \WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, 
>> and {\sc\lowercase{Stuff}}. (Not quite, it seems)
>>
>> I'll use a commercial font called Calluna, but have added Linux 
>> Biolinum O to the example for those who don't want to download 
>> Calluna (the "Regular" can be "bought" for free, e.g. at 
>> https://www.fontspring.com/fonts/exljbris/calluna).
>>
>> Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER 
>> SHARP S" at "1E9E. Calluna also has a small caps version at "F727", 
>> while Biolinum has it at "E092. I'd like to use these glyphs in the 
>> capitalizations mentioned, but that only works erratically (cf. 
>> example).
>>
>> Secondly, Calluna comes with oldstyle numerals switched on, which is 
>> nice for normal text, but should change to proportional lining 
>> numbers in uppercase and to small-cap proportional lining numbers in 
>> an all-small-cap text. I'm not sure what I'd want in a caps+smallcaps 
>> context, but certainly not oldstyle numerals with their descenders.
> Use separate threads for each problem. The uppercase sharp s 
> replacement with \WORD can be changed in the next beta.
>
> %% begin example
> \usemodule[lingual-de]
>
> \setupbodyfont[libertine]
>
> \starttext
>
> Gruß Straße Buße
>
> \WORD{Gruß Straße Buße}
>
> \enabledirectives[fonts.uppercasesharps]
>
> \WORD{Gruß Straße Buße}
>
> \disabledirectives[fonts.uppercasesharps]
>
> \WORD{Gruß Straße Buße}
>
> \stoptext
> %% end example
>
> Wolfgang
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 6167 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: uppercase, small caps, numerals and German capital sharp s

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 1354 bytes --]

> Thomas Fehige <mailto:thomas@fehige.de>
> 20. April 2016 um 16:03
> Wolfgang,
>> Use separate threads for each problem. The uppercase sharp s 
>> replacement with \WORD can be changed in the next beta.
>>
>> %% begin example
> are you saying, use this example as long as the new beta isn't out 
> yet, or are you saying, this example will work as soon as I'll use the 
> new beta? It doesn't seem to do anything right now, not even an error 
> message.
It’s a new feature which will work with the next beta.

With \enabledirectives[fonts.uppercasesharps] you tell context to 
convert ß to ẞ (instead of SS) when you use \WORD to capitalize a string.
> I was looking for a general way how to substitute one glyph with 
> another depending on context, thus I can't see how there are different 
> problems in my post? But it's good to hear that others have thought at 
> least of a partial solution.
>
> Is my guess right that normally the author of a font ought to provide 
> otf features that can be switched on and off to get one result instead 
> of the other? That area seems to be utter chaos in the Calluna fonts.
The output of \sc to produce small capitals depends on the font and it’s 
the font designers job to provide a small ẞ (he could use stilistic sets 
to let you choose between ß and ẞ).

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2761 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: uppercase, small caps, numerals and German capital sharp s

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]

Thanks for the clarification, Wolfgang.

Am 20.04.2016 um 16:25 schrieb Wolfgang Schuster:
> [...]
>> I was looking for a general way how to substitute one glyph with 
>> another depending on context, thus I can't see how there are 
>> different problems in my post? But it's good to hear that others have 
>> thought at least of a partial solution.
>>
>> Is my guess right that normally the author of a font ought to provide 
>> otf features that can be switched on and off to get one result 
>> instead of the other? That area seems to be utter chaos in the 
>> Calluna fonts.
> The output of \sc to produce small capitals depends on the font and 
> it’s the font designers job to provide a small ẞ (he could use 
> stilistic sets to let you choose between ß and ẞ).

Well, there's the problem, I think. Jos Buivenga, aka exljbris, 
Calluna's font designer, has done a superb job on the graphics (in my 
eyes), but his stylistic sets or otf features seem to be full of holes, 
as far as I understand them, which is perhaps not very far.

What I'm looking for is a way on the TeX, LuaTeX or ConTeXt level to 
define "environments" ('scuse my LaTeX slang) within which certain glyph 
substitutions happen. Then I could kind of redefine a thing like \sc to 
use the smallcaps ß and switch to smallcaps lining figures, if 
available, or, otherwise, scaled-down uppercase lining figures. I have 
still other fish to fry in this context, but a general hint where to 
look for something like this would be helpful.

Thanks a lot so far -- Thomas






[-- Attachment #1.2: Type: text/html, Size: 2388 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: uppercase, small caps, numerals and German capital sharp s

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 1590 bytes --]

Thanks for the clarification, Wolfgang.

Am 20.04.2016 um 16:25 schrieb Wolfgang Schuster:
> [...]
>> I was looking for a general way how to substitute one glyph with 
>> another depending on context, thus I can't see how there are 
>> different problems in my post? But it's good to hear that others have 
>> thought at least of a partial solution.
>>
>> Is my guess right that normally the author of a font ought to provide 
>> otf features that can be switched on and off to get one result 
>> instead of the other? That area seems to be utter chaos in the 
>> Calluna fonts.
> The output of \sc to produce small capitals depends on the font and 
> it’s the font designers job to provide a small ẞ (he could use 
> stilistic sets to let you choose between ß and ẞ).

Well, there's the problem, I think. Jos Buivenga, aka exljbris, 
Calluna's font designer, has done a superb job on the graphics (in my 
eyes), but his stylistic sets or otf features seem to be full of holes, 
as far as I understand them, which is perhaps not very far.

What I'm looking for is a way on the TeX, LuaTeX or ConTeXt level to 
define "environments" ('scuse my LaTeX slang) within which certain glyph 
substitutions happen. Then I could kind of redefine a thing like \sc to 
use the smallcaps ß and switch to smallcaps lining figures, if 
available, or, otherwise, scaled-down uppercase lining figures. I have 
still other fish to fry in this context, but a general hint where to 
look for something like this would be helpful.

Thanks a lot so far -- Thomas






[-- Attachment #1.2: Type: text/html, Size: 2381 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

glyph substitution

[Thomas Fehige]

Is there a way to tell ConTeXt to use one glyph where it would on its 
own use another one? Two examples:

- In the font "Purisa Medium" the hyphen comes out as a line that is two 
or three times fatter and even a little longer than the m-dash. That is 
clearly wrong, and probably the font designer's fault. Other than that, 
the font has its merits as a not-too-sweet or crazy handwriting font. 
I'll need to tell ConTeXt to either scale that monster-hyphen down or to 
use a different glyph altogether, maybe even from another font.

- As mentioned in an earlier post, in an \sc group I need the lowercase 
ß to be replaced with its smallcaps version, which is contained in the 
font but not accessible via any of its otf features.

There are more occasions where I have missed such a feature.

Thank you - Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Hans Hagen]

On 4/22/2016 1:35 PM, Thomas Fehige wrote:
> Is there a way to tell ConTeXt to use one glyph where it would on its
> own use another one? Two examples:
>
> - In the font "Purisa Medium" the hyphen comes out as a line that is two
> or three times fatter and even a little longer than the m-dash. That is
> clearly wrong, and probably the font designer's fault. Other than that,
> the font has its merits as a not-too-sweet or crazy handwriting font.
> I'll need to tell ConTeXt to either scale that monster-hyphen down or to
> use a different glyph altogether, maybe even from another font.

you can define your own font .. search in the test suite for 
fallbacks*.tex etc as well as extensions-*.tex

> - As mentioned in an earlier post, in an \sc group I need the lowercase
> ß to be replaced with its smallcaps version, which is contained in the
> font but not accessible via any of its otf features.

see s-lingual-de.mkiv

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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

Sorry, all of ConTeXt is still very new to me, and the documentation 
often confuses me.

Am 22.04.2016 um 22:28 schrieb Hans Hagen:
> you can define your own font .. search in the test suite for 
> fallbacks*.tex etc as well as extensions-*.tex

For both searches the test suite answers "No matches found".

> see s-lingual-de.mkiv

I'd do that, if I knew what that is and where I can find it.

Googling these brought up some interesting stuff though, which I am 
trying to read and understand.

Cheers -- Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

Sorry, all of ConTeXt is still very new to me, and the documentation 
often confuses me.

Am 22.04.2016 um 22:28 schrieb Hans Hagen:
> you can define your own font .. search in the test suite for
> fallbacks*.tex etc as well as extensions-*.tex

For both searches the test suite answers "No matches found".

> see s-lingual-de.mkiv

I'd do that, if I knew what that is and where I can find it.

Googling these brought up some interesting stuff though, which I am 
trying to read and understand.

Cheers -- Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

Am 25.04.2016 um 14:48 schrieb Thomas Fehige:
> Sorry, all of ConTeXt is still very new to me, and the documentation 
> often confuses me.
>
> Am 22.04.2016 um 22:28 schrieb Hans Hagen:
>> you can define your own font .. search in the test suite for
>> fallbacks*.tex etc as well as extensions-*.tex
>
> For both searches the test suite answers "No matches found".

Possibly the test suite you mean is not the same as the one that's 
described on this page: http://wiki.contextgarden.net/Test_suite ??? 
That's where I "searched".

Thomas


___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

Am 25.04.2016 um 14:48 schrieb Thomas Fehige:
> Sorry, all of ConTeXt is still very new to me, and the documentation
> often confuses me.
>
> Am 22.04.2016 um 22:28 schrieb Hans Hagen:
>> you can define your own font .. search in the test suite for
>> fallbacks*.tex etc as well as extensions-*.tex
>
> For both searches the test suite answers "No matches found".

Possibly the test suite you mean is not the same as the one that's 
described on this page: http://wiki.contextgarden.net/Test_suite ??? 
That's where I "searched".

Thomas


___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 305 bytes --]

> Thomas Fehige <mailto:thomas@fehige.de>
> 25. April 2016 um 20:12
>
>
> Possibly the test suite you mean is not the same as the one that's 
> described on this page: http://wiki.contextgarden.net/Test_suite ??? 
> That's where I "searched".
http://pragma-ade.com/download-1.htm -> cont-tst.7z

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1426 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]

Am 25.04.2016 um 22:44 schrieb Wolfgang Schuster:
>> Thomas Fehige <mailto:thomas@fehige.de>
>> 25. April 2016 um 20:12
>>
>>
>> Possibly the test suite you mean is not the same as the one that's 
>> described on this page: http://wiki.contextgarden.net/Test_suite ??? 
>> That's where I "searched".
> http://pragma-ade.com/download-1.htm -> cont-tst.7z
>
Hans, Wolfgang, are you serious? That's just lots of uncommented code 
snippets, many of them don't do nothing or crash in compilation! I 
believe  I mentioned before that I am very new to ConTeXt.

Isn't there any documentation of any of this? Like: "How to make my own 
otf feature at home" -- the script "extensions-001.tex" seems to try 
something like that, but it shows no effect on my machine. Or a bit of 
text that explains the properties and functionalities of 
\definefontfallback in whole sentences? Pointers like that would be very 
welcome.

Cheers -- Thomas



[-- Attachment #1.2: Type: text/html, Size: 2689 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]

Am 25.04.2016 um 22:44 schrieb Wolfgang Schuster:
>> Thomas Fehige <mailto:thomas@fehige.de>
>> 25. April 2016 um 20:12
>>
>>
>> Possibly the test suite you mean is not the same as the one that's 
>> described on this page: http://wiki.contextgarden.net/Test_suite ??? 
>> That's where I "searched".
> http://pragma-ade.com/download-1.htm -> cont-tst.7z
>
Hans, Wolfgang, are you serious? That's just lots of uncommented code 
snippets, many of them don't do nothing or crash in compilation! I 
believe  I mentioned before that I am very new to ConTeXt.

Isn't there any documentation of any of this? Like: "How to make my own 
otf feature at home" -- the script "extensions-001.tex" seems to try 
something like that, but it shows no effect on my machine. Or a bit of 
text that explains the properties and functionalities of 
\definefontfallback in whole sentences? Pointers like that would be very 
welcome.

Cheers -- Thomas



[-- Attachment #1.2: Type: text/html, Size: 2691 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Hans Hagen]

On 4/27/2016 4:27 PM, Thomas Fehige wrote:
> Am 25.04.2016 um 22:44 schrieb Wolfgang Schuster:
>>> Thomas Fehige <mailto:thomas@fehige.de>
>>> 25. April 2016 um 20:12
>>>
>>>
>>> Possibly the test suite you mean is not the same as the one that's
>>> described on this page: http://wiki.contextgarden.net/Test_suite ???
>>> That's where I "searched".
>> http://pragma-ade.com/download-1.htm -> cont-tst.7z
>>
> Hans, Wolfgang, are you serious? That's just lots of uncommented code
> snippets, many of them don't do nothing or crash in compilation! I
> believe  I mentioned before that I am very new to ConTeXt.

indeed they are lots of small examples (taken from the list or 
experiments) but they show what can be done

if they crash (no sure what you mean there) it's most likely due to 
fonts you don't have on your machine

> Isn't there any documentation of any of this? Like: "How to make my own
> otf feature at home" -- the script "extensions-001.tex" seems to try
> something like that, but it shows no effect on my machine. Or a bit of
> text that explains the properties and functionalities of
> \definefontfallback in whole sentences? Pointers like that would be very
> welcome.

a lot has been published in articles in user group journals or for 
meetings, there is a font manual that you can buy for nominal costs, 
there are some manuals on the website and an extended version of the 
more technical one that hardly anyone needs will end up in the 
distribution some day soon, there are examples on stack exchange, in the 
mail archive an don the wiki ... a lot of this depends on voluntary work 
so you can hardly complain about it .. anyone is free to provide more 
documentation and share experiences

Hans

btw, if you want to roll out your own features as in extensions-001 then 
you also need to know what the font provides (or lacks) .. open type 
fonts can be pretty complex and there is no consistency in how certain 
features are implemented

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 1827 bytes --]

Am 27.04.2016 um 17:10 schrieb Hans Hagen:
> indeed they are lots of small examples (taken from the list or 
> experiments) but they show what can be done
>
> if they crash (no sure what you mean there) it's most likely due to 
> fonts you don't have on your machine

Yes, many of the blank pages or obscure (to me) error messages seem to 
be font-related. I'll have to see to that.

> a lot has been published in articles in user group journals or for 
> meetings, there is a font manual that you can buy for nominal costs, 
> there are some manuals on the website and an extended version of the 
> more technical one that hardly anyone needs will end up in the 
> distribution some day soon, there are examples on stack exchange, in 
> the mail archive an don the wiki ... a lot of this depends on 
> voluntary work so you can hardly complain about it .. anyone is free 
> to provide more documentation and share experiences

Yes, I know, I'm sorry I let my exasperation run free. When I started 
out with LaTeX /and/ typesetting more than two decades ago, I had one 
basic book on LaTeX. Over the years my knowledge of LaTeX, typography, 
layout design and typesetting grew side by side, if somewhat organically 
and unsystematic. Nowadays there's about a metre and a half of bookshelf 
occupied by books on LaTeX, TeX and Typography.

As I make books myself, I'm obviously not averse to buying them. I guess 
the ConTeXt books on fonts and layout will do me good.

> btw, if you want to roll out your own features as in extensions-001 
> then you also need to know what the font provides (or lacks) .. open 
> type fonts can be pretty complex and there is no consistency in how 
> certain features are implemented

Yes, I learned that already. Will these home-made features only work on 
open type fonts?

Cheers -- Thomas

[-- Attachment #1.2: Type: text/html, Size: 2537 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Hans Hagen]

On 4/29/2016 9:44 AM, Thomas Fehige wrote:

> Yes, I learned that already. Will these home-made features only work on
> open type fonts?

yes, because type 1 has no such feature processing (i suppose i can make 
them into fake opentypes ... shouldn't be to hard ... it depends a bit 
on how long we keep using type 1)

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
___________________________________________________________________________________

Test Suite Fonts "extensions-001"

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]

Below is a minimal not-working example extracted from 
"extensions-001.tex" in the fonts section of the test suite. From what I 
understand of the code, the second line should read "XPrXcXdXPrX" 
instead of "abracadabra". But it doesn't, it is still "abracadabra". 
Compiling the original extensions-001 gives me seven lines of 
"abracadabra". What am I doing wrong? I'm running ConTeXt version 
2015.05.18 12:26 MKIV current fmt: 2016.4.28 from the debian/ubuntu 
texlive packets.

\startluacode

fonts.handlers.otf.addfeature {

name = "stest",

type = "substitution",

data = {

a = "X",

b = "P",

}

}

\stopluacode

\definefontfeature[stest][stest=yes]

\starttext

\startTEXpage

\definedfont[file:DejaVuSerif.ttf*default]%

abracadabra\par

{\addff{stest}abracadabra\par}

\stopTEXpage

\stoptext


[-- Attachment #1.2: Type: text/html, Size: 4399 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Test Suite Fonts "extensions-001"

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]

> Thomas Fehige <mailto:thomas@fehige.de>
> 29. April 2016 um 10:38
>
> Below is a minimal not-working example extracted from 
> "extensions-001.tex" in the fonts section of the test suite. From what 
> I understand of the code, the second line should read "XPrXcXdXPrX" 
> instead of "abracadabra". But it doesn't, it is still "abracadabra". 
> Compiling the original extensions-001 gives me seven lines of 
> "abracadabra". What am I doing wrong? I'm running ConTeXt version 
> 2015.05.18 12:26 MKIV current fmt: 2016.4.28 from the debian/ubuntu 
> texlive packets.
>
You need a newer context version.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1821 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Setting up TeXworks

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 535 bytes --]

Am 29.04.2016 um 11:05 schrieb Wolfgang Schuster:
> You need a newer context version.

OK, that helps. Everything is fine from the command line. I seem to be 
overlooking something as to the setup of TeXworks, though. I copied the 
programme calls from the _tools.ini_ that came with the ConTeXt 
standalone version into the present _tools.ini_ that lives in my 
personal TeXworks config folder. Now TW starts _mtxrun_ allright, but 
the run crashes with

mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

Cheers -- Thomas



[-- Attachment #1.2: Type: text/html, Size: 1424 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Mojca Miklavec]

On 3 May 2016 at 11:22, Thomas Fehige wrote:
>
> OK, that helps. Everything is fine from the command line. I seem to be
> overlooking something as to the setup of TeXworks, though. I copied the
> programme calls from the tools.ini that came with the ConTeXt standalone
> version into the present tools.ini that lives in my personal TeXworks config
> folder. Now TW starts mtxrun allright, but the run crashes with
>
> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

Can you check the paths in the fourth tab (= Typesetting) of
Preferences/Settings?

It is possible that you have more than one version of ConTeXt
installed and that you see different paths in the Terminal than in the
GUI.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[L.S.-Soc&Gam]

[-- Attachment #1.1: Type: text/plain, Size: 4100 bytes --]



Am 06.05.2016 um 10:04 schrieb Mojca Miklavec:
> On 3 May 2016 at 11:22, Thomas Fehige wrote:
>> OK, that helps. Everything is fine from the command line. I seem to be
>> overlooking something as to the setup of TeXworks, though. I copied the
>> programme calls from the tools.ini that came with the ConTeXt standalone
>> version into the present tools.ini that lives in my personal TeXworks config
>> folder. Now TW starts mtxrun allright, but the run crashes with
>>
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
> Can you check the paths in the fourth tab (= Typesetting) of
> Preferences/Settings?
>
> It is possible that you have more than one version of ConTeXt
> installed and that you see different paths in the Terminal than in the
> GUI.
>
> Mojca
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

I've searched through the mailing list, what the initial post to this 
topic was, but i couldn't find it. If you're having trouble to make 
context compile a document, try this:

- TeXworks tools.ini doesn't need to be edited manually. It's the file 
where TW saves the settings from " Edit -> Preferences -> Typesetting ".
- First of all make sure, that you downloaded ConTeXt by using 
"first-setup.exe"

- Then, you should add the folder where context.exe (and all 
executables) are stored to your system paths: Use your browser to 
navigate to the said folder, click on the address bar and copy the full 
path. For me it looks like this: " F:\Sandbox\ConTeXt\tex\texmf-win64\bin "
- Then add this path to your windows system paths: go to your windows 
control panel, double click " System "-> advanced settings -> 
environment variables (or something like this), in the lower halfth 
there is a window with a point " Path ". Double click it and paste your 
CTX folder pretty much at the top of the section or if there is only one 
line, add it at the beginning, and use semikolon ( ; ) to seperate it 
from the rest. Save your settings and you should be good to go.
- to test if you did it correctly open your command line and simply 
enter " context.exe --version ". If command line tells you, that no 
context.exe was found, then you might try to add the context \bin folder 
to your system paths again
- if command line tells you the version of context, then you can proceed:

- start TW, " Edit -> Preferences -> Typesetting ". There check the 
upper halfth for the context folder you added to your system paths. If 
you've added it at the beginning, it should be at the top here as well. 
Alternatively use the arrows to push context\bin it to the very top

NOTE: this is important. if you have MikTeX installed for example and if 
its folder is listed above your context folder, TW will try to use exe 
files from the MikTeX folder. so make sure that context\bin is above 
anything related to tex, context or lua.

- then in the lower halfth create a new processing tool by clikcking on 
the plus:

- call it CTX mkiv or something
- in the program field either search for your context.exe, or if added 
to the system paths correctly, simply enter context.exe in the Program field
- for arguments add:        $fullname                (this parses the 
filename to context compiler)
- if you want to use the sync code <-> pdf feature, also add another 
argument:        --synctex=-1

that's it. there is the option to make this the default profile at the 
bottom of the Typesetting window.

Now you can test it: paste

\starttext
Hello World!
\stoptext

into a new file and save it somewhere. then use your freshly set up 
processing tool. after compilation the pdf viewer should pop up.


I hope that helps, Seba

[-- Attachment #1.2: Type: text/html, Size: 6090 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 12071 bytes --]

Am 06.05.2016 um 13:39 schrieb L.S.-Soc&Gam:
>
> I've searched through the mailing list, what the initial post to this 
> topic was, but i couldn't find it. If you're having trouble to make 
> context compile a document, try this:
>
> - TeXworks tools.ini doesn't need to be edited manually. It's the file 
> where TW saves the settings from " Edit -> Preferences -> Typesetting ".
> - First of all make sure, that you downloaded ConTeXt by using 
> "first-setup.exe"

That I did. Not *.exe though, being on a Linux OS, Xubuntu to be precise.

> - Then, you should add the folder where context.exe (and all 
> executables) are stored to your system paths: Use your browser to 
> navigate to the said folder, click on the address bar and copy the 
> full path. For me it looks like this: " 
> F:\Sandbox\ConTeXt\tex\texmf-win64\bin "
> - Then add this path to your windows system paths: go to your windows 
> control panel, double click " System "-> advanced settings -> 
> environment variables (or something like this), in the lower halfth 
> there is a window with a point " Path ". Double click it and paste 
> your CTX folder pretty much at the top of the section or if there is 
> only one line, add it at the beginning, and use semikolon ( ; ) to 
> seperate it from the rest. Save your settings and you should be good 
> to go.
> - to test if you did it correctly open your command line and simply 
> enter " context.exe --version ". If command line tells you, that no 
> context.exe was found, then you might try to add the context \bin 
> folder to your system paths again

Translating this into Linux, all this works fine.

> - if command line tells you the version of context, then you can proceed:
>
> - start TW, " Edit -> Preferences -> Typesetting ". There check the 
> upper halfth for the context folder you added to your system paths. If 
> you've added it at the beginning, it should be at the top here as 
> well. Alternatively use the arrows to push context\bin it to the very top
>
> NOTE: this is important. if you have MikTeX installed for example and 
> if its folder is listed above your context folder, TW will try to use 
> exe files from the MikTeX folder. so make sure that context\bin is 
> above anything related to tex, context or lua.

Thanks for your detailed description, but I'm afraid that's not it. 
Meanwhile I uninstalled all my texlive packets and reinstalled TeXworks 
without any of the texlive components, and reinstalled ConTeXt 
standalone strictly according to this: 
http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions 
-- and the problem persists. mtxrun is found and started allright, but 
it complains that it can't find some files, that a database is outdated, 
and that it can't find some other files and stops without a pdf. Below 
is the complete console output as shown in TeXworks. Calling "context 
test" in a terminal window works fine, though.

Cheers -- Thomas

---------------------------------------------------------------------------------- 


mtxrun | forcing cache reload

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context/bin' from specification 'selfautoloc:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-local/web2c' from specification 
'selfautoloc:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-dist/web2c' from specification 
'selfautoloc:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf/web2c' from specification 
'selfautoloc:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-local/web2c' from specification 
'selfautoloc:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-dist/web2c' from specification 
'selfautoloc:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf/web2c' from specification 
'selfautoloc:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context' from specification 'selfautodir:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-local/web2c' from specification 
'selfautodir:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-dist/web2c' from specification 
'selfautodir:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf/web2c' from specification 
'selfautodir:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-local/web2c' from specification 
'selfautodir:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-dist/web2c' from specification 
'selfautodir:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf/web2c' from specification 
'selfautodir:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
'$SELFAUTOGRANDPARENT/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local' from specification 'selfautoparent:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-local/web2c' from specification 
'selfautoparent:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-dist/web2c' from specification 
'selfautoparent:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf/web2c' from specification 
'selfautoparent:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-local/web2c' from specification 
'selfautoparent:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-dist/web2c' from specification 
'selfautoparent:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'

resolvers | resolving |

resolvers | resolving | warning: no lua configuration files found

resolvers | resolving | no texmf paths are defined (using TEXMF)

resolvers | resolving |

mtxrun | the resolver databases are not present or outdated

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-context.lua' using hash 
'lua::mtx-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-contexts.lua' using hash 
'lua::mtx-contexts.lua'

resolvers | resolving | remembered file 'mtx-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-t-context.lua' using hash 
'lua::mtx-t-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-t-contexts.lua' using hash 
'lua::mtx-t-contexts.lua'

resolvers | resolving | remembered file 'mtx-t-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'context.lua' using hash 
'lua::context.lua'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context/bin' from specification 'selfautoloc:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-local/web2c' from specification 
'selfautoloc:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-dist/web2c' from specification 
'selfautoloc:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf/web2c' from specification 
'selfautoloc:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-local/web2c' from specification 
'selfautoloc:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-dist/web2c' from specification 
'selfautoloc:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf/web2c' from specification 
'selfautoloc:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context' from specification 'selfautodir:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-local/web2c' from specification 
'selfautodir:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-dist/web2c' from specification 
'selfautodir:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf/web2c' from specification 
'selfautodir:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-local/web2c' from specification 
'selfautodir:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-dist/web2c' from specification 
'selfautodir:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf/web2c' from specification 
'selfautodir:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
'$SELFAUTOGRANDPARENT/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local' from specification 'selfautoparent:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-local/web2c' from specification 
'selfautoparent:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-dist/web2c' from specification 
'selfautoparent:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf/web2c' from specification 
'selfautoparent:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-local/web2c' from specification 
'selfautoparent:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-dist/web2c' from specification 
'selfautoparent:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'

resolvers | resolving |

resolvers | resolving | warning: no lua configuration files found

resolvers | resolving | no texmf paths are defined (using TEXMF)

resolvers | resolving |

resolvers | resolving | remembered file 'mtx-context.lua'

resolvers | resolving | remembered file 'mtx-contexts.lua'

resolvers | resolving | remembered file 'mtx-context.lua'

resolvers | resolving | remembered file 'mtx-t-context.lua'

resolvers | resolving | remembered file 'mtx-t-contexts.lua'

resolvers | resolving | remembered file 'mtx-t-context.lua'

resolvers | resolving | remembered file 'context.lua'

mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

----------------------------------------------------------------------------------




[-- Attachment #1.2: Type: text/html, Size: 24090 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Jean-Pierre Delange]

At the end of this website page http://lesfichesabebert.fr/index.php/Context/Instalation, there are some explanations about the TeXWorks typesetting setting. There are some screen prints which may help.

----- Mail original -----
De: "Thomas Fehige" <thomas@fehige.de>
À: ntg-context@ntg.nl
Envoyé: Lundi 16 Mai 2016 17:46:13
Objet: Re: [NTG-context] Setting up TeXworks


Am 06.05.2016 um 13:39 schrieb L.S.-Soc&Gam: 



I've searched through the mailing list, what the initial post to this topic was, but i couldn't find it. If you're having trouble to make context compile a document, try this: 

- TeXworks tools.ini doesn't need to be edited manually. It's the file where TW saves the settings from " Edit -> Preferences -> Typesetting ". 
- First of all make sure, that you downloaded ConTeXt by using "first-setup.exe" 

That I did. Not *.exe though, being on a Linux OS, Xubuntu to be precise. 



- Then, you should add the folder where context.exe (and all executables) are stored to your system paths: Use your browser to navigate to the said folder, click on the address bar and copy the full path. For me it looks like this: " F:\Sandbox\ConTeXt\tex\texmf-win64\bin " 
- Then add this path to your windows system paths: go to your windows control panel, double click " System "-> advanced settings -> environment variables (or something like this), in the lower halfth there is a window with a point " Path " . Double click it and paste your CTX folder pretty much at the top of the section or if there is only one line, add it at the beginning, and use semikolon ( ; ) to seperate it from the rest. Save your settings and you should be good to go. 
- to test if you did it correctly open your command line and simply enter " context.exe --version ". If command line tells you, that no context.exe was found, then you might try to add the context \bin folder to your system paths again 

Translating this into Linux, all this works fine. 



- if command line tells you the version of context, then you can proceed: 

- start TW, " Edit -> Preferences -> Typesetting ". There check the upper halfth for the context folder you added to your system paths. If you've added it at the beginning, it should be at the top here as well. Alternatively use the arrows to push context\bin it to the very top 

NOTE: this is important. if you have MikTeX installed for example and if its folder is listed above your context folder, TW will try to use exe files from the MikTeX folder. so make sure that context\bin is above anything related to tex, context or lua. 

Thanks for your detailed description, but I'm afraid that's not it. Meanwhile I uninstalled all my texlive packets and reinstalled TeXworks without any of the texlive components, and reinstalled ConTeXt standalone strictly according to this: http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions -- and the problem persists. mtxrun is found and started allright, but it complains that it can't find some files, that a database is outdated, and that it can't find some other files and stops without a pdf. Below is the complete console output as shown in TeXworks. Calling "context test" in a terminal window works fine, though. 

Cheers -- Thomas 



---------------------------------------------------------------------------------- 

mtxrun | forcing cache reload 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context/bin' from specification 'selfautoloc:' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context' from specification 'selfautodir:' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf/web2c' from specification 'selfautodir:/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification '$SELFAUTOGRANDPARENT/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local' from specification 'selfautoparent:' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' 

resolvers | resolving | 

resolvers | resolving | warning: no lua configuration files found 

resolvers | resolving | no texmf paths are defined (using TEXMF) 

resolvers | resolving | 

mtxrun | the resolver databases are not present or outdated 

resolvers | resolving | using suffix based filetype 'lua' 

resolvers | resolving | remembering file 'mtx-context.lua' using hash 'lua::mtx-context.lua' 

resolvers | resolving | using suffix based filetype 'lua' 

resolvers | resolving | remembering file 'mtx-contexts.lua' using hash 'lua::mtx-contexts.lua' 

resolvers | resolving | remembered file 'mtx-context.lua' 

resolvers | resolving | using suffix based filetype 'lua' 

resolvers | resolving | remembering file 'mtx-t-context.lua' using hash 'lua::mtx-t-context.lua' 

resolvers | resolving | using suffix based filetype 'lua' 

resolvers | resolving | remembering file 'mtx-t-contexts.lua' using hash 'lua::mtx-t-contexts.lua' 

resolvers | resolving | remembered file 'mtx-t-context.lua' 

resolvers | resolving | using suffix based filetype 'lua' 

resolvers | resolving | remembering file 'context.lua' using hash 'lua::context.lua' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context/bin' from specification 'selfautoloc:' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context' from specification 'selfautodir:' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf/web2c' from specification 'selfautodir:/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification '$SELFAUTOGRANDPARENT/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local' from specification 'selfautoparent:' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c' 

resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c' 

resolvers | resolving | 

resolvers | resolving | warning: no lua configuration files found 

resolvers | resolving | no texmf paths are defined (using TEXMF) 

resolvers | resolving | 

resolvers | resolving | remembered file 'mtx-context.lua' 

resolvers | resolving | remembered file 'mtx-contexts.lua' 

resolvers | resolving | remembered file 'mtx-context.lua' 

resolvers | resolving | remembered file 'mtx-t-context.lua' 

resolvers | resolving | remembered file 'mtx-t-contexts.lua' 

resolvers | resolving | remembered file 'mtx-t-context.lua' 

resolvers | resolving | remembered file 'context.lua' 

mtxrun | unknown script 'context.lua' or 'mtx-context.lua' 

---------------------------------------------------------------------------------- 




___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

I tried that, no success (not very different from what I did before 
either). Are there other tests that I could do? Can't anybody interpret 
the messages, error and otherwise?

Cheers -- Thomas

Am 16.05.2016 um 17:55 schrieb Jean-Pierre Delange:
> At the end of this website page http://lesfichesabebert.fr/index.php/Context/Instalation, there are some explanations about the TeXWorks typesetting setting. There are some screen prints which may help.
>
> ----- Mail original -----
> De: "Thomas Fehige" <thomas@fehige.de>
> À: ntg-context@ntg.nl
> Envoyé: Lundi 16 Mai 2016 17:46:13
> Objet: Re: [NTG-context] Setting up TeXworks
>
>
> Am 06.05.2016 um 13:39 schrieb L.S.-Soc&Gam:
>
>
>
> I've searched through the mailing list, what the initial post to this topic was, but i couldn't find it. If you're having trouble to make context compile a document, try this:
>
> - TeXworks tools.ini doesn't need to be edited manually. It's the file where TW saves the settings from " Edit -> Preferences -> Typesetting ".
> - First of all make sure, that you downloaded ConTeXt by using "first-setup.exe"
>
> That I did. Not *.exe though, being on a Linux OS, Xubuntu to be precise.
>
>
>
> - Then, you should add the folder where context.exe (and all executables) are stored to your system paths: Use your browser to navigate to the said folder, click on the address bar and copy the full path. For me it looks like this: " F:\Sandbox\ConTeXt\tex\texmf-win64\bin "
> - Then add this path to your windows system paths: go to your windows control panel, double click " System "-> advanced settings -> environment variables (or something like this), in the lower halfth there is a window with a point " Path " . Double click it and paste your CTX folder pretty much at the top of the section or if there is only one line, add it at the beginning, and use semikolon ( ; ) to seperate it from the rest. Save your settings and you should be good to go.
> - to test if you did it correctly open your command line and simply enter " context.exe --version ". If command line tells you, that no context.exe was found, then you might try to add the context \bin folder to your system paths again
>
> Translating this into Linux, all this works fine.
>
>
>
> - if command line tells you the version of context, then you can proceed:
>
> - start TW, " Edit -> Preferences -> Typesetting ". There check the upper halfth for the context folder you added to your system paths. If you've added it at the beginning, it should be at the top here as well. Alternatively use the arrows to push context\bin it to the very top
>
> NOTE: this is important. if you have MikTeX installed for example and if its folder is listed above your context folder, TW will try to use exe files from the MikTeX folder. so make sure that context\bin is above anything related to tex, context or lua.
>
> Thanks for your detailed description, but I'm afraid that's not it. Meanwhile I uninstalled all my texlive packets and reinstalled TeXworks without any of the texlive components, and reinstalled ConTeXt standalone strictly according to this: http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions -- and the problem persists. mtxrun is found and started allright, but it complains that it can't find some files, that a database is outdated, and that it can't find some other files and stops without a pdf. Below is the complete console output as shown in TeXworks. Calling "context test" in a terminal window works fine, though.
>
> Cheers -- Thomas
>
>
>
> ----------------------------------------------------------------------------------
>
> mtxrun | forcing cache reload
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context/bin' from specification 'selfautoloc:'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context' from specification 'selfautodir:'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf/web2c' from specification 'selfautodir:/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local' from specification 'selfautoparent:'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'
>
> resolvers | resolving |
>
> resolvers | resolving | warning: no lua configuration files found
>
> resolvers | resolving | no texmf paths are defined (using TEXMF)
>
> resolvers | resolving |
>
> mtxrun | the resolver databases are not present or outdated
>
> resolvers | resolving | using suffix based filetype 'lua'
>
> resolvers | resolving | remembering file 'mtx-context.lua' using hash 'lua::mtx-context.lua'
>
> resolvers | resolving | using suffix based filetype 'lua'
>
> resolvers | resolving | remembering file 'mtx-contexts.lua' using hash 'lua::mtx-contexts.lua'
>
> resolvers | resolving | remembered file 'mtx-context.lua'
>
> resolvers | resolving | using suffix based filetype 'lua'
>
> resolvers | resolving | remembering file 'mtx-t-context.lua' using hash 'lua::mtx-t-context.lua'
>
> resolvers | resolving | using suffix based filetype 'lua'
>
> resolvers | resolving | remembering file 'mtx-t-contexts.lua' using hash 'lua::mtx-t-contexts.lua'
>
> resolvers | resolving | remembered file 'mtx-t-context.lua'
>
> resolvers | resolving | using suffix based filetype 'lua'
>
> resolvers | resolving | remembering file 'context.lua' using hash 'lua::context.lua'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context/bin' from specification 'selfautoloc:'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-local/web2c' from specification 'selfautoloc:/share/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf-dist/web2c' from specification 'selfautoloc:/share/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/share/texmf/web2c' from specification 'selfautoloc:/share/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-local/web2c' from specification 'selfautoloc:/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf-dist/web2c' from specification 'selfautoloc:/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/bin/texmf/web2c' from specification 'selfautoloc:/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local/context' from specification 'selfautodir:'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-local/web2c' from specification 'selfautodir:/share/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf-dist/web2c' from specification 'selfautodir:/share/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/share/texmf/web2c' from specification 'selfautodir:/share/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-local/web2c' from specification 'selfautodir:/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf-dist/web2c' from specification 'selfautodir:/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/context/texmf/web2c' from specification 'selfautodir:/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on weird path '/usr/local' from specification 'selfautoparent:'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-local/web2c' from specification 'selfautoparent:/share/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf-dist/web2c' from specification 'selfautoparent:/share/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/share/texmf/web2c' from specification 'selfautoparent:/share/texmf/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-local/web2c' from specification 'selfautoparent:/texmf-local/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf-dist/web2c' from specification 'selfautoparent:/texmf-dist/web2c'
>
> resolvers | resolving | looking for 'texmfcnf.lua' on given path '/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'
>
> resolvers | resolving |
>
> resolvers | resolving | warning: no lua configuration files found
>
> resolvers | resolving | no texmf paths are definedDid (using TEXMF)
>
> resolvers | resolving |
>
> resolvers | resolving | remembered file 'mtx-context.lua'
>
> resolvers | resolving | remembered file 'mtx-contexts.lua'
>
> resolvers | resolving | remembered file 'mtx-context.lua'
>
> resolvers | resolving | remembered file 'mtx-t-context.lua'
>
> resolvers | resolving | remembered file 'mtx-t-contexts.lua'
>
> resolvers | resolving | remembered file 'mtx-t-context.lua'
>
> resolvers | resolving | remembered file 'context.lua'
>
> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
>
> ----------------------------------------------------------------------------------
>
>
>
>
> ___________________________________________________________________________________
> 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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

Whew, I've got it running, finally.

For some reason, TeXworks needs to tell mtxrun explicitly where its 
texmf-tree is located. Meaning, an additional argument is required in 
TeXworks's starter setup, which now looks like this:

name: ConTeXt MkIV
command: mtxrun
arguments:
     --tree=/usr/local/context/tex        <-- this is the one!
     --autogenerate
     --script
     context
     $fullname

In the "Paths to TeX and friends" list I have

     /usr/local/context/texmf-linux-64
     /usr/local/context/bin

as the top two entries.

I don't know what exactly is going on here, so I don't feel confident to 
add this to the wiki, but maybe someone else does and will.

Thanks for listening -- Thomas

Am 17.05.2016 um 13:16 schrieb Thomas Fehige:
> I tried that, no success (not very different from what I did before 
> either). Are there other tests that I could do? Can't anybody 
> interpret the messages, error and otherwise?
>
> Cheers -- Thomas
>
> Am 16.05.2016 um 17:55 schrieb Jean-Pierre Delange:
>> At the end of this website page 
>> http://lesfichesabebert.fr/index.php/Context/Instalation, there are 
>> some explanations about the TeXWorks typesetting setting. There are 
>> some screen prints which may help.
>>
>> ----- Mail original -----
>> De: "Thomas Fehige" <thomas@fehige.de>
>> À: ntg-context@ntg.nl
>> Envoyé: Lundi 16 Mai 2016 17:46:13
>> Objet: Re: [NTG-context] Setting up TeXworks
>>
>>
>> Am 06.05.2016 um 13:39 schrieb L.S.-Soc&Gam:
>>
>>
>>
>> I've searched through the mailing list, what the initial post to this 
>> topic was, but i couldn't find it. If you're having trouble to make 
>> context compile a document, try this:
>>
>> - TeXworks tools.ini doesn't need to be edited manually. It's the 
>> file where TW saves the settings from " Edit -> Preferences -> 
>> Typesetting ".
>> - First of all make sure, that you downloaded ConTeXt by using 
>> "first-setup.exe"
>>
>> That I did. Not *.exe though, being on a Linux OS, Xubuntu to be 
>> precise.
>>
>>
>>
>> - Then, you should add the folder where context.exe (and all 
>> executables) are stored to your system paths: Use your browser to 
>> navigate to the said folder, click on the address bar and copy the 
>> full path. For me it looks like this: " 
>> F:\Sandbox\ConTeXt\tex\texmf-win64\bin "
>> - Then add this path to your windows system paths: go to your windows 
>> control panel, double click " System "-> advanced settings -> 
>> environment variables (or something like this), in the lower halfth 
>> there is a window with a point " Path " . Double click it and paste 
>> your CTX folder pretty much at the top of the section or if there is 
>> only one line, add it at the beginning, and use semikolon ( ; ) to 
>> seperate it from the rest. Save your settings and you should be good 
>> to go.
>> - to test if you did it correctly open your command line and simply 
>> enter " context.exe --version ". If command line tells you, that no 
>> context.exe was found, then you might try to add the context \bin 
>> folder to your system paths again
>>
>> Translating this into Linux, all this works fine.
>>
>>
>>
>> - if command line tells you the version of context, then you can 
>> proceed:
>>
>> - start TW, " Edit -> Preferences -> Typesetting ". There check the 
>> upper halfth for the context folder you added to your system paths. 
>> If you've added it at the beginning, it should be at the top here as 
>> well. Alternatively use the arrows to push context\bin it to the very 
>> top
>>
>> NOTE: this is important. if you have MikTeX installed for example and 
>> if its folder is listed above your context folder, TW will try to use 
>> exe files from the MikTeX folder. so make sure that context\bin is 
>> above anything related to tex, context or lua.
>>
>> Thanks for your detailed description, but I'm afraid that's not it. 
>> Meanwhile I uninstalled all my texlive packets and reinstalled 
>> TeXworks without any of the texlive components, and reinstalled 
>> ConTeXt standalone strictly according to this: 
>> http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions 
>> -- and the problem persists. mtxrun is found and started allright, 
>> but it complains that it can't find some files, that a database is 
>> outdated, and that it can't find some other files and stops without a 
>> pdf. Below is the complete console output as shown in TeXworks. 
>> Calling "context test" in a terminal window works fine, though.
>>
>> Cheers -- Thomas
>>
>>
>>
>> ---------------------------------------------------------------------------------- 
>>
>>
>> mtxrun | forcing cache reload
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context/bin' from specification 'selfautoloc:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-local/web2c' from specification 
>> 'selfautoloc:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-dist/web2c' from specification 
>> 'selfautoloc:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf/web2c' from specification 
>> 'selfautoloc:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-local/web2c' from specification 
>> 'selfautoloc:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-dist/web2c' from specification 
>> 'selfautoloc:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf/web2c' from specification 
>> 'selfautoloc:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context' from specification 'selfautodir:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-local/web2c' from specification 
>> 'selfautodir:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-dist/web2c' from specification 
>> 'selfautodir:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf/web2c' from specification 
>> 'selfautodir:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-local/web2c' from specification 
>> 'selfautodir:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-dist/web2c' from specification 
>> 'selfautodir:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf/web2c' from specification 
>> 'selfautodir:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local' from specification 'selfautoparent:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-local/web2c' from specification 
>> 'selfautoparent:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-dist/web2c' from specification 
>> 'selfautoparent:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf/web2c' from specification 
>> 'selfautoparent:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-local/web2c' from specification 
>> 'selfautoparent:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-dist/web2c' from specification 
>> 'selfautoparent:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf/web2c' from specification 
>> 'selfautoparent:/texmf/web2c'
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | warning: no lua configuration files found
>>
>> resolvers | resolving | no texmf paths are defined (using TEXMF)
>>
>> resolvers | resolving |
>>
>> mtxrun | the resolver databases are not present or outdated
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-context.lua' using hash 
>> 'lua::mtx-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-contexts.lua' using 
>> hash 'lua::mtx-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-t-context.lua' using 
>> hash 'lua::mtx-t-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-t-contexts.lua' using 
>> hash 'lua::mtx-t-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'context.lua' using hash 
>> 'lua::context.lua'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context/bin' from specification 'selfautoloc:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-local/web2c' from specification 
>> 'selfautoloc:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-dist/web2c' from specification 
>> 'selfautoloc:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf/web2c' from specification 
>> 'selfautoloc:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-local/web2c' from specification 
>> 'selfautoloc:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-dist/web2c' from specification 
>> 'selfautoloc:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf/web2c' from specification 
>> 'selfautoloc:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context' from specification 'selfautodir:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-local/web2c' from specification 
>> 'selfautodir:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-dist/web2c' from specification 
>> 'selfautodir:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf/web2c' from specification 
>> 'selfautodir:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-local/web2c' from specification 
>> 'selfautodir:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-dist/web2c' from specification 
>> 'selfautodir:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf/web2c' from specification 
>> 'selfautodir:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local' from specification 'selfautoparent:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-local/web2c' from specification 
>> 'selfautoparent:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-dist/web2c' from specification 
>> 'selfautoparent:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf/web2c' from specification 
>> 'selfautoparent:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-local/web2c' from specification 
>> 'selfautoparent:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-dist/web2c' from specification 
>> 'selfautoparent:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf/web2c' from specification 
>> 'selfautoparent:/texmf/web2c'
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | warning: no lua configuration files found
>>
>> resolvers | resolving | no texmf paths are definedDid (using TEXMF)
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | remembered file 'context.lua'
>>
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
>>
>> ---------------------------------------------------------------------------------- 
>>
>>
>>
>>
>>
>> ___________________________________________________________________________________ 
>>
>> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Hans Hagen]

On 5/17/2016 2:39 PM, Thomas Fehige wrote:
> Whew, I've got it running, finally.
>
> For some reason, TeXworks needs to tell mtxrun explicitly where its
> texmf-tree is located. Meaning, an additional argument is required in
> TeXworks's starter setup, which now looks like this:
>
> name: ConTeXt MkIV
> command: mtxrun
> arguments:
>     --tree=/usr/local/context/tex        <-- this is the one!
>     --autogenerate
>     --script
>     context
>     $fullname
>
> In the "Paths to TeX and friends" list I have
>
>     /usr/local/context/texmf-linux-64
>     /usr/local/context/bin
>
> as the top two entries.
>
> I don't know what exactly is going on here, so I don't feel confident to
> add this to the wiki, but maybe someone else does and will.

Using --tree is quite ok for this. Maybe TeXworks sets some environment 
variable that interferes otherwise. Normally using the full path should 
also work, so

/usr/local/context/texmf-linux-64/mtxrun

don't add /usr/local/context/bin to the path as it's only used when updating

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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

Am 17.05.2016 um 14:59 schrieb Hans Hagen:
> Using --tree is quite ok for this. Maybe TeXworks sets some 
> environment variable that interferes otherwise. Normally using the 
> full path should also work, so
>
> /usr/local/context/texmf-linux-64/mtxrun

Well, it isn't normal, apparently. I remember I tried that at some 
stage, but it didn't work. The problem was not finding mtxrun and 
starting it, but rather that mtxrun, once started, couldn't find some of 
its config files.

Cheers -- Thomas

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Jean-Pierre Delange]

And don't forget to do this before coding :
1) cd /home/[...]/context/tex/. setuptex
This command answers this : "Setting "/home/JohnDoe/context/tex" as ConTeXt root."
2) Then : cd .../context/tex/texmf-win64 (or linux64) with a x64 computer
3) Then type : 
context --generate 
and type : context --make

4) Finally, if you add fonts (in /usr/share/fonts, or $HOME/.fonts), don't forget to reload the font database (in the same depositery as 3)); the command is as follow :
mtxrun --script fonts --reload
In order to see which fonts are installed on your system:
mtxrun --script fonts --list --all
To search a font (like didot) :
mtxrun --script fonts --list --pattern=*didot* --all

All these commands are the same on windows/linux/OS X

More information in French here :
https://fr.wikibooks.org/wiki/ConTeXt

Hope that ich sende nicht Eulen nach Athens !
JP

----- Mail original -----
De: "Thomas Fehige" <thomas@fehige.de>
À: ntg-context@ntg.nl
Envoyé: Mardi 17 Mai 2016 14:39:27
Objet: Re: [NTG-context] Setting up TeXworks

Whew, I've got it running, finally.

For some reason, TeXworks needs to tell mtxrun explicitly where its 
texmf-tree is located. Meaning, an additional argument is required in 
TeXworks's starter setup, which now looks like this:

name: ConTeXt MkIV
command: mtxrun
arguments:
     --tree=/usr/local/context/tex        <-- this is the one!
     --autogenerate
     --script
     context
     $fullname

In the "Paths to TeX and friends" list I have

     /usr/local/context/texmf-linux-64
     /usr/local/context/bin

as the top two entries.

I don't know what exactly is going on here, so I don't feel confident to 
add this to the wiki, but maybe someone else does and will.

Thanks for listening -- Thomas

Am 17.05.2016 um 13:16 schrieb Thomas Fehige:
> I tried that, no success (not very different from what I did before 
> either). Are there other tests that I could do? Can't anybody 
> interpret the messages, error and otherwise?
>
> Cheers -- Thomas
>
> Am 16.05.2016 um 17:55 schrieb Jean-Pierre Delange:
>> At the end of this website page 
>> http://lesfichesabebert.fr/index.php/Context/Instalation, there are 
>> some explanations about the TeXWorks typesetting setting. There are 
>> some screen prints which may help.
>>
>> ----- Mail original -----
>> De: "Thomas Fehige" <thomas@fehige.de>
>> À: ntg-context@ntg.nl
>> Envoyé: Lundi 16 Mai 2016 17:46:13
>> Objet: Re: [NTG-context] Setting up TeXworks
>>
>>
>> Am 06.05.2016 um 13:39 schrieb L.S.-Soc&Gam:
>>
>>
>>
>> I've searched through the mailing list, what the initial post to this 
>> topic was, but i couldn't find it. If you're having trouble to make 
>> context compile a document, try this:
>>
>> - TeXworks tools.ini doesn't need to be edited manually. It's the 
>> file where TW saves the settings from " Edit -> Preferences -> 
>> Typesetting ".
>> - First of all make sure, that you downloaded ConTeXt by using 
>> "first-setup.exe"
>>
>> That I did. Not *.exe though, being on a Linux OS, Xubuntu to be 
>> precise.
>>
>>
>>
>> - Then, you should add the folder where context.exe (and all 
>> executables) are stored to your system paths: Use your browser to 
>> navigate to the said folder, click on the address bar and copy the 
>> full path. For me it looks like this: " 
>> F:\Sandbox\ConTeXt\tex\texmf-win64\bin "
>> - Then add this path to your windows system paths: go to your windows 
>> control panel, double click " System "-> advanced settings -> 
>> environment variables (or something like this), in the lower halfth 
>> there is a window with a point " Path " . Double click it and paste 
>> your CTX folder pretty much at the top of the section or if there is 
>> only one line, add it at the beginning, and use semikolon ( ; ) to 
>> seperate it from the rest. Save your settings and you should be good 
>> to go.
>> - to test if you did it correctly open your command line and simply 
>> enter " context.exe --version ". If command line tells you, that no 
>> context.exe was found, then you might try to add the context \bin 
>> folder to your system paths again
>>
>> Translating this into Linux, all this works fine.
>>
>>
>>
>> - if command line tells you the version of context, then you can 
>> proceed:
>>
>> - start TW, " Edit -> Preferences -> Typesetting ". There check the 
>> upper halfth for the context folder you added to your system paths. 
>> If you've added it at the beginning, it should be at the top here as 
>> well. Alternatively use the arrows to push context\bin it to the very 
>> top
>>
>> NOTE: this is important. if you have MikTeX installed for example and 
>> if its folder is listed above your context folder, TW will try to use 
>> exe files from the MikTeX folder. so make sure that context\bin is 
>> above anything related to tex, context or lua.
>>
>> Thanks for your detailed description, but I'm afraid that's not it. 
>> Meanwhile I uninstalled all my texlive packets and reinstalled 
>> TeXworks without any of the texlive components, and reinstalled 
>> ConTeXt standalone strictly according to this: 
>> http://wiki.contextgarden.net/Ubuntu#With_ConTeXt_Standalone_.E2.80.93_should_work_with_all_Ubuntu_versions 
>> -- and the problem persists. mtxrun is found and started allright, 
>> but it complains that it can't find some files, that a database is 
>> outdated, and that it can't find some other files and stops without a 
>> pdf. Below is the complete console output as shown in TeXworks. 
>> Calling "context test" in a terminal window works fine, though.
>>
>> Cheers -- Thomas
>>
>>
>>
>> ---------------------------------------------------------------------------------- 
>>
>>
>> mtxrun | forcing cache reload
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context/bin' from specification 'selfautoloc:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-local/web2c' from specification 
>> 'selfautoloc:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-dist/web2c' from specification 
>> 'selfautoloc:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf/web2c' from specification 
>> 'selfautoloc:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-local/web2c' from specification 
>> 'selfautoloc:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-dist/web2c' from specification 
>> 'selfautoloc:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf/web2c' from specification 
>> 'selfautoloc:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context' from specification 'selfautodir:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-local/web2c' from specification 
>> 'selfautodir:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-dist/web2c' from specification 
>> 'selfautodir:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf/web2c' from specification 
>> 'selfautodir:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-local/web2c' from specification 
>> 'selfautodir:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-dist/web2c' from specification 
>> 'selfautodir:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf/web2c' from specification 
>> 'selfautodir:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local' from specification 'selfautoparent:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-local/web2c' from specification 
>> 'selfautoparent:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-dist/web2c' from specification 
>> 'selfautoparent:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf/web2c' from specification 
>> 'selfautoparent:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-local/web2c' from specification 
>> 'selfautoparent:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-dist/web2c' from specification 
>> 'selfautoparent:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf/web2c' from specification 
>> 'selfautoparent:/texmf/web2c'
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | warning: no lua configuration files found
>>
>> resolvers | resolving | no texmf paths are defined (using TEXMF)
>>
>> resolvers | resolving |
>>
>> mtxrun | the resolver databases are not present or outdated
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-context.lua' using hash 
>> 'lua::mtx-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-contexts.lua' using 
>> hash 'lua::mtx-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-t-context.lua' using 
>> hash 'lua::mtx-t-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'mtx-t-contexts.lua' using 
>> hash 'lua::mtx-t-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | using suffix based filetype 'lua'
>>
>> resolvers | resolving | remembering file 'context.lua' using hash 
>> 'lua::context.lua'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context/bin' from specification 'selfautoloc:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-local/web2c' from specification 
>> 'selfautoloc:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf-dist/web2c' from specification 
>> 'selfautoloc:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/share/texmf/web2c' from specification 
>> 'selfautoloc:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-local/web2c' from specification 
>> 'selfautoloc:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf-dist/web2c' from specification 
>> 'selfautoloc:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/bin/texmf/web2c' from specification 
>> 'selfautoloc:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local/context' from specification 'selfautodir:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-local/web2c' from specification 
>> 'selfautodir:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf-dist/web2c' from specification 
>> 'selfautodir:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/share/texmf/web2c' from specification 
>> 'selfautodir:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-local/web2c' from specification 
>> 'selfautodir:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf-dist/web2c' from specification 
>> 'selfautodir:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/context/texmf/web2c' from specification 
>> 'selfautodir:/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
>> '$SELFAUTOGRANDPARENT/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
>> '/usr/local' from specification 'selfautoparent:'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-local/web2c' from specification 
>> 'selfautoparent:/share/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf-dist/web2c' from specification 
>> 'selfautoparent:/share/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/share/texmf/web2c' from specification 
>> 'selfautoparent:/share/texmf/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-local/web2c' from specification 
>> 'selfautoparent:/texmf-local/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf-dist/web2c' from specification 
>> 'selfautoparent:/texmf-dist/web2c'
>>
>> resolvers | resolving | looking for 'texmfcnf.lua' on given path 
>> '/usr/local/texmf/web2c' from specification 
>> 'selfautoparent:/texmf/web2c'
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | warning: no lua configuration files found
>>
>> resolvers | resolving | no texmf paths are definedDid (using TEXMF)
>>
>> resolvers | resolving |
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-contexts.lua'
>>
>> resolvers | resolving | remembered file 'mtx-t-context.lua'
>>
>> resolvers | resolving | remembered file 'context.lua'
>>
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
>>
>> ---------------------------------------------------------------------------------- 
>>
>>
>>
>>
>>
>> ___________________________________________________________________________________ 
>>
>> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

Thanks Jean-Pierre, and no, you're not carrying owls to Athens, in 
whatever language. ;) I'm very new to ConTeXt and not all that 
experienced in the Linux world either. My French is honed on cooking 
recipes rather than computing and coding, but I was able to follow your 
page allright.

1. I don't have my standalone ConTeXt tree anywhere under /home/... but 
in /usr/local/context/..., as suggested on the wiki. Would that make a 
difference?

2. What do "--generate" and "--make" do? I remember having run them at 
one occasion or other, but to no avail as to the TeXworks problem. 
Shouldn't they be run by the installation script anyway?

I had managed the fonts database stuff, thanks to the wiki and some 
trial and error. It was time I learned about environment variables in 
Linux and Xfce anyway.

Cheers -- Thomas

Am 17.05.2016 um 15:22 schrieb Jean-Pierre Delange:
> And don't forget to do this before coding :
> 1) cd /home/[...]/context/tex/. setuptex
> This command answers this : "Setting "/home/JohnDoe/context/tex" as ConTeXt root."
> 2) Then : cd .../context/tex/texmf-win64 (or linux64) with a x64 computer
> 3) Then type :
> context --generate
> and type : context --make
>
> 4) Finally, if you add fonts (in /usr/share/fonts, or $HOME/.fonts), don't forget to reload the font database (in the same depositery as 3)); the command is as follow :
> mtxrun --script fonts --reload
> In order to see which fonts are installed on your system:
> mtxrun --script fonts --list --all
> To search a font (like didot) :
> mtxrun --script fonts --list --pattern=*didot* --all
>
> All these commands are the same on windows/linux/OS X
>
> More information in French here :
> https://fr.wikibooks.org/wiki/ConTeXt
>
> Hope that ich sende nicht Eulen nach Athens !
> JP
>
> ----- Mail original -----
> De: "Thomas Fehige" <thomas@fehige.de>
> À: ntg-context@ntg.nl
> Envoyé: Mardi 17 Mai 2016 14:39:27
> Objet: Re: [NTG-context] Setting up TeXworks
>
> Whew, I've got it running, finally.
>
> For some reason, TeXworks needs to tell mtxrun explicitly where its
> texmf-tree is located. Meaning, an additional argument is required in
> TeXworks's starter setup, which now looks like this:
>
> name: ConTeXt MkIV
> command: mtxrun
> arguments:
>       --tree=/usr/local/context/tex        <-- this is the one!
>       --autogenerate
>       --script
>       context
>       $fullname
>
> In the "Paths to TeX and friends" list I have
>
>       /usr/local/context/texmf-linux-64
>       /usr/local/context/bin
>
> as the top two entries.
>
> I don't know what exactly is going on here, so I don't feel confident to
> add this to the wiki, but maybe someone else does and will.
>
> Thanks for listening -- Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Jean-Pierre Delange]

Hi Thomas,

1. There is no great issue to install ConTeXt Standalone in /usr/local/context; it's only a simple advice that I gave to put context in such a directory as /home/Document (e.g. : on Linux Ubuntu) in order to make things clear for beginners; and you can install it in /opt/context if you want it. I have installed CTX in /home/MyComputer/context
, because the whole documentation and files I want to use are near. Under Windows, ConTeXt is installed in C:\users\MyComputer\Documents\context. 
As you know, ConTeXt Standalone is a bundle which is self-sufficient (it doesn't need any extra-package, except some more fonts). I don't have tried yet to work with ConTeXt and Perl/Python, because my goal is to understand ConTeXt step by step in order to write a documentation in French (and I am starting from the beginning), starting by the easiest way to code a document and ending by some project structures.

2. commands like 'context --generate' and 'context --make' , typed after this previous one: '. setuptex', allow to build all the trees that you need thereafter, including databases. After that, you have to set your environment variables (in PATH). If you don't do that, you'll see your Linux system complain with such enigmatic formulas as 'ConTeXt is not installed', or 'mtxrun is not installed. You can installed it with apt-get install mtxrun', etc. 

JP


-----Mail Original -----
> De: "Thomas Fehige" <thomas@fehige.de>
> À: ntg-context@ntg.nl

>experienced in the Linux world either. My French is honed on cooking 
>recipes rather than computing and coding, but I was able to follow your 
>page allright.
>
>1. I don't have my standalone ConTeXt tree anywhere under /home/... but 
>in /usr/local/context/..., as suggested on the wiki. Would that make a 
>difference?
>
>2. What do "--generate" and "--make" do? I remember having run them at 
>one occasion or other, but to no avail as to the TeXworks problem. 
>Shouldn't they be run by the installation script anyway?
>
>I had managed the fonts database stuff, thanks to the wiki and some 
>trial and error. It was time I learned about environment variables in 
>Linux and Xfce anyway.

>Cheers -- Thomas

Am 17.05.2016 um 15:22 schrieb Jean-Pierre Delange:
> And don't forget to do this before coding :
> 1) cd /home/[...]/context/tex/. setuptex
> This command answers this : "Setting "/home/JohnDoe/context/tex" as ConTeXt root."
> 2) Then : cd .../context/tex/texmf-win64 (or linux64) with a x64 computer
> 3) Then type :
> context --generate
> and type : context --make
>
> 4) Finally, if you add fonts (in /usr/share/fonts, or $HOME/.fonts), don't forget to reload the font database (in the same depositery as 3)); the command is as follow :
> mtxrun --script fonts --reload
> In order to see which fonts are installed on your system:
> mtxrun --script fonts --list --all
> To search a font (like didot) :
> mtxrun --script fonts --list --pattern=*didot* --all
>
> All these commands are the same on windows/linux/OS X
>
> More information in French here :
> https://fr.wikibooks.org/wiki/ConTeXt
>
> Hope that ich sende nicht Eulen nach Athens !
> JP
>
> ----- Mail original -----
> De: "Thomas Fehige" <thomas@fehige.de>
> À: ntg-context@ntg.nl
> Envoyé: Mardi 17 Mai 2016 14:39:27
> Objet: Re: [NTG-context] Setting up TeXworks
>
> Whew, I've got it running, finally.
>
> For some reason, TeXworks needs to tell mtxrun explicitly where its
> texmf-tree is located. Meaning, an additional argument is required in
> TeXworks's starter setup, which now looks like this:
>
> name: ConTeXt MkIV
> command: mtxrun
> arguments:
>       --tree=/usr/local/context/tex        <-- this is the one!
>       --autogenerate
>       --script
>       context
>       $fullname
>
> In the "Paths to TeX and friends" list I have
>
>       /usr/local/context/texmf-linux-64
>       /usr/local/context/bin
>
> as the top two entries.
>
> I don't know what exactly is going on here, so I don't feel confident to
> add this to the wiki, but maybe someone else does and will.
>
> Thanks for listening -- Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

Am 06.05.2016 um 10:04 schrieb Mojca Miklavec:
> Can you check the paths in the fourth tab (= Typesetting) of 
> Preferences/Settings? It is possible that you have more than one 
> version of ConTeXt installed and that you see different paths in the 
> Terminal than in the GUI. Mojca

Yes I have two versions of ConTeXt. I have TeXlive from the Ubuntu 
repository and now the newer version as standalone. I added the paths to 
the new version at the top of that list in TeXwoks' preferences. And it 
does find and run the new version of mtxrun.

Cheers -- Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 1446 bytes --]

To prevent misunderstandings: This is /not/ the solution, the problem 
remains that the newly installed standalone mtxrun doesn't find certain 
configuration files and complains about an outdated something or other, 
/when started from within TeXworks/, while everything works fine from 
the command line.

Am 07.05.2016 um 12:49 schrieb Thomas Fehige:
> Am 06.05.2016 um 10:04 schrieb Mojca Miklavec:
>> Can you check the paths in the fourth tab (= Typesetting) of 
>> Preferences/Settings? It is possible that you have more than one 
>> version of ConTeXt installed and that you see different paths in the 
>> Terminal than in the GUI. Mojca
>
> Yes I have two versions of ConTeXt. I have TeXlive from the Ubuntu 
> repository and now the newer version as standalone. I added the paths 
> to the new version at the top of that list in TeXwoks' preferences. 
> And it does find and run the new version of mtxrun.
>
> Cheers -- Thomas
> ___________________________________________________________________________________ 
>
> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 2725 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 3281 bytes --]

Now I uninstalled the texlive version of ConTeXt and did a total new 
install of the standalone version. That did not help at all. There's 
something wrong happening within the mtxrun.

I added a new "compiler" to TeXworks that only executes the command 
printenv and it lists the following environment settings:

TEXROOT=/usr/local/context/tex

PATH=/usr/local/context/texmf-linux-64:/usr/local/context/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/context/texmf-linux-64/bin 


OSFONTDIR=/usr/local/share/fonts;/usr/share/fonts;/home/thomas/.local/share/fonts 


They look pretty correct to me. But still mtxrun complains:

----------------------------------------------

... resolvers | resolving | warning: no lua configuration files found

resolvers | resolving | no texmf paths are defined (using TEXMF)

resolvers | resolving |

mtxrun | the resolver databases are not present or outdated

...

resolvers | resolving | warning: no lua configuration files found

resolvers | resolving | no texmf paths are defined (using TEXMF)

...

mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

----------------------------------------------

Clueless greetings -- Thomas

Am 09.05.2016 um 13:02 schrieb Thomas Fehige:
> To prevent misunderstandings: This is /not/ the solution, the problem 
> remains that the newly installed standalone mtxrun doesn't find 
> certain configuration files and complains about an outdated something 
> or other, /when started from within TeXworks/, while everything works 
> fine from the command line.
>
> Am 07.05.2016 um 12:49 schrieb Thomas Fehige:
>> Am 06.05.2016 um 10:04 schrieb Mojca Miklavec:
>>> Can you check the paths in the fourth tab (= Typesetting) of 
>>> Preferences/Settings? It is possible that you have more than one 
>>> version of ConTeXt installed and that you see different paths in the 
>>> Terminal than in the GUI. Mojca
>>
>> Yes I have two versions of ConTeXt. I have TeXlive from the Ubuntu 
>> repository and now the newer version as standalone. I added the paths 
>> to the new version at the top of that list in TeXwoks' preferences. 
>> And it does find and run the new version of mtxrun.
>>
>> Cheers -- Thomas
>> ___________________________________________________________________________________ 
>>
>> 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
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 7895 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

ConTeXt and Scite

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 802 bytes --]

For the time being, I think I'm giving up on pairing ConTeXt standalone 
and TeXworks on my Xubuntu machine and try to try out SciTE.

In the manual it says that

    If you want to use ConTEXt, you need to copy the relevant files from
    <texroot>/tex/texmf-context/context/data/scite
    to the path were SciTE keeps its property files (*.properties)

Is that the only way? SciTE seems to keep its user-specific properties 
files in my home directory! I don't want to clutter that up with 16 
unhidden files and two directories. At least SciTE's original files are 
hidden ones.

A much more polite way would be if SciTE used a hidden directory named 
"~/.scite", or, better still, "~/.config/scite", to keep its config 
stuff in. Can I reconfigure it to use some place like that?

Cheers -- Thomas

[-- Attachment #1.2: Type: text/html, Size: 1124 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Setting up TeXworks

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 690 bytes --]

Am 29.04.2016 um 11:05 schrieb Wolfgang Schuster:
> You need a newer context version.

OK, thank you, that helped. Everything is fine from the command line.

I seem to be overlooking something as to the setup of TeXworks, though. 
I copied the programme calls from the _tools.ini_ that came with the 
ConTeXt standalone version into the present _tools.ini_ that lives in my 
personal TeXworks config folder. I also added _/usr/local/context/bin_ 
to the "paths for TeX and friends" in the TW preferences window.

Now TW starts the correct _mtxrun_, but the run crashes with, after a 
lot of file searching:

mtxrun | unknown script 'context.lua' or 'mtx-context.lua'


  Cheers -- Thomas



[-- Attachment #1.2: Type: text/html, Size: 1792 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Mojca Miklavec]

On 3 May 2016 at 11:51, Thomas Fehige <thomas@fehige.de> wrote:
> Am 29.04.2016 um 11:05 schrieb Wolfgang Schuster:
>
> You need a newer context version.
>
>
> OK, thank you, that helped. Everything is fine from the command line.
>
> I seem to be overlooking something as to the setup of TeXworks, though. I
> copied the programme calls from the tools.ini that came with the ConTeXt
> standalone version into the present tools.ini that lives in my personal
> TeXworks config folder. I also added /usr/local/context/bin to the "paths
> for TeX and friends" in the TW preferences window.
>
> Now TW starts the correct mtxrun, but the run crashes with, after a lot of
> file searching:
>
> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

Try to run (the correct) "mtxrun --generate" either from the command
line (or from TW just before you start ConTeXt if the command line
doesn't help).

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: Setting up TeXworks

[Thomas Fehige]

Am 03.05.2016 um 12:21 schrieb Mojca Miklavec:
> On 3 May 2016 at 11:51, Thomas Fehige <thomas@fehige.de> wrote:
>> Am 29.04.2016 um 11:05 schrieb Wolfgang Schuster:
>>
>> You need a newer context version.
>>
>>
>> OK, thank you, that helped. Everything is fine from the command line.
>>
>> I seem to be overlooking something as to the setup of TeXworks, though. I
>> copied the programme calls from the tools.ini that came with the ConTeXt
>> standalone version into the present tools.ini that lives in my personal
>> TeXworks config folder. I also added /usr/local/context/bin to the "paths
>> for TeX and friends" in the TW preferences window.
>>
>> Now TW starts the correct mtxrun, but the run crashes with, after a lot of
>> file searching:
>>
>> mtxrun | unknown script 'context.lua' or 'mtx-context.lua'
> Try to run (the correct) "mtxrun --generate" either from the command
> line (or from TW just before you start ConTeXt if the command line
> doesn't help).
>
That wasn't it. Below is the logfile. The command issued by TeXworks 
should be

     mtxrun --autogenerate --script context my_extensions001.tex

A file "texmfcnf.lua" is found at three places:

     /usr/share/texlive/texmf-dist/web2c/texmfcnf.lua (last modified: 
25/03/2016)
     /usr/share/texmf/web2c/texmfcnf.lua (last modified: 25/03/2016)
     /usr/local/context/tex/texmf/web2c/texmfcnf.lua (last modified: 
28.11.2012)

The last one is the one I installed this morning.

Cheers -- Thomas

------------ logfile ----------------------

mtxrun | forcing cache reload

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context/bin' from specification 'selfautoloc:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-local/web2c' from specification 
'selfautoloc:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-dist/web2c' from specification 
'selfautoloc:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf/web2c' from specification 
'selfautoloc:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-local/web2c' from specification 
'selfautoloc:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-dist/web2c' from specification 
'selfautoloc:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf/web2c' from specification 
'selfautoloc:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context' from specification 'selfautodir:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-local/web2c' from specification 
'selfautodir:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-dist/web2c' from specification 
'selfautodir:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf/web2c' from specification 
'selfautodir:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-local/web2c' from specification 
'selfautodir:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-dist/web2c' from specification 
'selfautodir:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf/web2c' from specification 
'selfautodir:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
'$SELFAUTOGRANDPARENT/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local' from specification 'selfautoparent:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-local/web2c' from specification 
'selfautoparent:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-dist/web2c' from specification 
'selfautoparent:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf/web2c' from specification 
'selfautoparent:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-local/web2c' from specification 
'selfautoparent:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-dist/web2c' from specification 
'selfautoparent:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'

resolvers | resolving |

resolvers | resolving | warning: no lua configuration files found

resolvers | resolving | no texmf paths are defined (using TEXMF)

resolvers | resolving |

mtxrun | the resolver databases are not present or outdated

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-context.lua' using hash 
'lua::mtx-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-contexts.lua' using hash 
'lua::mtx-contexts.lua'

resolvers | resolving | remembered file 'mtx-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-t-context.lua' using hash 
'lua::mtx-t-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'mtx-t-contexts.lua' using hash 
'lua::mtx-t-contexts.lua'

resolvers | resolving | remembered file 'mtx-t-context.lua'

resolvers | resolving | using suffix based filetype 'lua'

resolvers | resolving | remembering file 'context.lua' using hash 
'lua::context.lua'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/home/thomas/texmf/web2c' from specification 'home:texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context/bin' from specification 'selfautoloc:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-local/web2c' from specification 
'selfautoloc:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf-dist/web2c' from specification 
'selfautoloc:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/share/texmf/web2c' from specification 
'selfautoloc:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-local/web2c' from specification 
'selfautoloc:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf-dist/web2c' from specification 
'selfautoloc:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/bin/texmf/web2c' from specification 
'selfautoloc:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local/context' from specification 'selfautodir:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-local/web2c' from specification 
'selfautodir:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf-dist/web2c' from specification 
'selfautodir:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/share/texmf/web2c' from specification 
'selfautodir:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-local/web2c' from specification 
'selfautodir:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf-dist/web2c' from specification 
'selfautodir:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/context/texmf/web2c' from specification 
'selfautodir:/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'$SELFAUTOGRANDPARENT/texmf-local/web2c' from specification 
'$SELFAUTOGRANDPARENT/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on weird path 
'/usr/local' from specification 'selfautoparent:'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-local/web2c' from specification 
'selfautoparent:/share/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf-dist/web2c' from specification 
'selfautoparent:/share/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/share/texmf/web2c' from specification 
'selfautoparent:/share/texmf/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-local/web2c' from specification 
'selfautoparent:/texmf-local/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf-dist/web2c' from specification 
'selfautoparent:/texmf-dist/web2c'

resolvers | resolving | looking for 'texmfcnf.lua' on given path 
'/usr/local/texmf/web2c' from specification 'selfautoparent:/texmf/web2c'

resolvers | resolving |

resolvers | resolving | warning: no lua configuration files found

resolvers | resolving | no texmf paths are defined (using TEXMF)

resolvers | resolving |

resolvers | resolving | remembered file 'mtx-context.lua'

resolvers | resolving | remembered file 'mtx-contexts.lua'

resolvers | resolving | remembered file 'mtx-context.lua'

resolvers | resolving | remembered file 'mtx-t-context.lua'

resolvers | resolving | remembered file 'mtx-t-contexts.lua'

resolvers | resolving | remembered file 'mtx-t-context.lua'

resolvers | resolving | remembered file 'context.lua'

mtxrun | unknown script 'context.lua' or 'mtx-context.lua'

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Wolfgang Schuster]

[-- Attachment #1.1: Type: text/plain, Size: 551 bytes --]

> Thomas Fehige <mailto:thomas@fehige.de>
> 25. April 2016 um 14:48
> Sorry, all of ConTeXt is still very new to me, and the documentation 
> often confuses me.
>
> Am 22.04.2016 um 22:28 schrieb Hans Hagen:
>> you can define your own font .. search in the test suite for
>> fallbacks*.tex etc as well as extensions-*.tex
>
> For both searches the test suite answers "No matches found".
>
>> see s-lingual-de.mkiv
>
> I'd do that, if I knew what that is and where I can find it.
There should be a file with this name in your ConTeXt folder.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 1599 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: glyph substitution

[Thomas Fehige]

[-- Attachment #1.1: Type: text/plain, Size: 801 bytes --]

Am 25.04.2016 um 22:47 schrieb Wolfgang Schuster:
>
>>> see s-lingual-de.mkiv
>>
>> I'd do that, if I knew what that is and where I can find it.
> There should be a file with this name in your ConTeXt folder.
>
But there isn't. After seraching the whole file system, these are all 
the files with remotely similar names:

----------------------
/usr/share/texmf/tex/context/base$ ls s-l*.mkiv
s-languages-counters.mkiv
s-languages-frequencies.mkiv
s-languages-hyphenation.mkiv
s-languages-sorting.mkiv
s-languages-system.mkiv
s-languages-words.mkiv
---------------------

I have the debian/ubuntu texlive distro that comes with ubuntu 15.10. 
ConTeXt says:

---------------------ConTeXt ver: 2015.05.18 12:26 MKIV current fmt: 
2016.3.18 int: english/english

---------------------


Cheers -- Thomas

[-- Attachment #1.2: Type: text/html, Size: 2336 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 1552 bytes --]

I'm trying to get the SciTE lexers that come with the ConTeXt 
distribution working but I'm not having much luck. SciTE certainly 
processes the ConTeXt start-up script but never does any highlighting.

I always get the warning that lpeg is not loaded but I cannot find any 
separate lpeg.properties file or lpeg.lua file so I don't know how to 
get it imported and active to run the lexers. Any suggestions?

Interestingly, the lexers work just fine in Textadept but I haven't 
quite figured out how to get them to load automatically. I have to 
manually select the lexer but it works fine once I do.

I'm inclined to go the Textadept route and build a nice snippets file 
and Adeptsense support but I'd like to see things running in SciTE, too.

Right now I'm using Emacs to do my editing but AUCTeX does a poor job of 
supporting ConTeXt and when I asked about future plans on the AUCTeX 
mailing list, I got a snarky, sarcastic reply that "code doesn't change 
itself." Typical FSF attitude, I see. If I'm going to have to write my 
own support, Lua is much closer to the languages I've used before than 
elisp so it should be considerably easier.

Of course, I'll pass on anything I come up with to the ConTeXt community.


-- 
Bill Meahan K8QN

"The pessimist complains about the wind;
  the optimist expects it to change;
  the realist adjusts the sails."

-- William Arthur Ward

This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 19-6-2012 06:54, Bill Meahan wrote:
> I'm trying to get the SciTE lexers that come with the ConTeXt
> distribution working but I'm not having much luck. SciTE certainly
> processes the ConTeXt start-up script but never does any highlighting.
>
> I always get the warning that lpeg is not loaded but I cannot find any
> separate lpeg.properties file or lpeg.lua file so I don't know how to
> get it imported and active to run the lexers. Any suggestions?
>
> Interestingly, the lexers work just fine in Textadept but I haven't
> quite figured out how to get them to load automatically. I have to
> manually select the lexer but it works fine once I do.
>
> I'm inclined to go the Textadept route and build a nice snippets file
> and Adeptsense support but I'd like to see things running in SciTE, too.

You have to change some configuration files but as that situation seems 
to change every now and then I wait with providing extra files for 
textadept till it's more stable.

(Textadept has no realtime log pane so I cannot use it here without 
sacrificing too much convenience.)

> Right now I'm using Emacs to do my editing but AUCTeX does a poor job of
> supporting ConTeXt and when I asked about future plans on the AUCTeX
> mailing list, I got a snarky, sarcastic reply that "code doesn't change
> itself." Typical FSF attitude, I see. If I'm going to have to write my
> own support, Lua is much closer to the languages I've used before than
> elisp so it should be considerably easier.
>
> Of course, I'll pass on anything I come up with to the ConTeXt community.

concerning scite ... on windows it boils down to

- installing scite
- copying the scintillua lexer dir to the wscite path
- copying the context/data/scite directory to teh wscite dir

on linux it's a bit more complex as you need to figure out where scite 
keeps its properties files and that's sort of hard coded in the binary

(but it does work on linux)

on osx it's not working as there is no lpeg support provided there 
(unfortunately)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 1520 bytes --]

On 06/19/2012 04:58, Hans Hagen wrote:
> On 19-6-2012 06:54, Bill Meahan wrote:

>
> (Textadept has no realtime log pane so I cannot use it here without
> sacrificing too much convenience.)
>

Might be fixable, at least on *nix system. Textadept 5.4 does allow 
running processes in a subshell. I'll have to investigate a bit.


> on linux it's a bit more complex as you need to figure out where scite
> keeps its properties files and that's sort of hard coded in the binary
>
> (but it does work on linux)

Finding the properties files is pretty easy (/usr/local/share/scite/), 
Not sure where to put the lexers directory, though. I changed 
ScITEGlobal.properties per the instructions. There is no lpeg.properties 
file, nothing I've found (so far) in the global file to enable lpeg 
support. Took a scan of the source code and didn't see anything 
blindingly obvious. I'll keep searching.

>
> on osx it's not working as there is no lpeg support provided there
> (unfortunately)

I'm on a FreeBSD-9.0 system. Since OSX is based on FreeBSD perhaps it is 
really there but it will take whatever I find out to make it active.

I'll let everyone know what I find. Thanks for the response.

-- 
Bill Meahan K8QN

"The pessimist complains about the wind;
  the optimist expects it to change;
  the realist adjusts the sails."

-- William Arthur Ward

This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 19-6-2012 18:48, Bill Meahan wrote:

> Finding the properties files is pretty easy (/usr/local/share/scite/),
> Not sure where to put the lexers directory, though. I changed
> ScITEGlobal.properties per the instructions. There is no lpeg.properties
> file, nothing I've found (so far) in the global file to enable lpeg
> support. Took a scan of the source code and didn't see anything
> blindingly obvious. I'll keep searching.

you need to fetch it from

http://foicica.com/scintillua/

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]

On 06/19/2012 13:28, Hans Hagen wrote:

> you need to fetch it from
>
> http://foicica.com/scintillua/
>

I ended up installing the complete scintillua package and now everything 
works just fine. Had to modify the scintillua Makefile every place where 
there was a bare scintilla/<something> or scite/<something> to 
/usr/ports/editors/scite/work/scintilla/<something> or 
/usr/ports/editors/scite/work/scite/<something> but that was all.

If you wish, you can add FreeBSD-9.0 as a platform it works on.

Thanks for the suggestion. Now on to configuring Textadept to have 
Emacs-style keybindings, starting the ConTeXt lexers automatically, 
creating a snippets file and seeing if I can get a real-time output 
buffer going.


-- 
Bill Meahan K8QN

"The pessimist complains about the wind;
  the optimist expects it to change;
  the realist adjusts the sails."

-- William Arthur Ward

This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 19-6-2012 22:17, Bill Meahan wrote:
> On 06/19/2012 13:28, Hans Hagen wrote:
>
>> you need to fetch it from
>>
>> http://foicica.com/scintillua/
>>
>
> I ended up installing the complete scintillua package and now everything
> works just fine. Had to modify the scintillua Makefile every place where
> there was a bare scintilla/<something> or scite/<something> to
> /usr/ports/editors/scite/work/scintilla/<something> or
> /usr/ports/editors/scite/work/scite/<something> but that was all.
>
> If you wish, you can add FreeBSD-9.0 as a platform it works on.

maybe we should have a repository in the garden

anyhow, you can edit some info to the scit epage on the wiki

> Thanks for the suggestion. Now on to configuring Textadept to have
> Emacs-style keybindings, starting the ConTeXt lexers automatically,
> creating a snippets file and seeing if I can get a real-time output
> buffer going.

and you can give spell checking a try (you can use mtxrun --script 
--scite to convert a list with words into one suitable for the context 
lexers)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]

On 06/19/2012 16:43, Hans Hagen wrote:

>
> and you can give spell checking a try (you can use mtxrun --script
> --scite to convert a list with words into one suitable for the context
> lexers)
>
> Hans

There is a little module in "Brian's ~/.textadept file" on the Textadept 
wiki that uses aspell to do spell-checking. I'm going to give that a 
try. I can also try using SCOWL plus the method you describe, SCOWL is 
the word-list from which aspell, ispell and hunspell dictionaries are built.

-- 
Bill Meahan K8QN

"The pessimist complains about the wind;
  the optimist expects it to change;
  the realist adjusts the sails."

-- William Arthur Ward

This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 19-6-2012 23:27, Bill Meahan wrote:
> On 06/19/2012 16:43, Hans Hagen wrote:
>
>>
>> and you can give spell checking a try (you can use mtxrun --script
>> --scite to convert a list with words into one suitable for the context
>> lexers)
>>
>> Hans
>
> There is a little module in "Brian's ~/.textadept file" on the Textadept
> wiki that uses aspell to do spell-checking. I'm going to give that a
> try. I can also try using SCOWL plus the method you describe, SCOWL is
> the word-list from which aspell, ispell and hunspell dictionaries are
> built.

fyi: the context lexers do realtime checking in combination with regular 
lexing

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 2403 bytes --]

On 06/19/2012 17:57, Hans Hagen wrote:
> On 19-6-2012 23:27, Bill Meahan wrote:
>> On 06/19/2012 16:43, Hans Hagen wrote:
>>
>>>
>>> and you can give spell checking a try (you can use mtxrun --script
>>> --scite to convert a list with words into one suitable for the context
>>> lexers)
>>>
>>> Hans

> fyi: the context lexers do realtime checking in combination with regular
> lexing
>
> Hans
>

Tried this, ran into problems.

1. Running the command as shown generates a spell-xx.lua file but 
complains about a spell-xx.lucluac file not being present.

2. The lexer does not load the spell-xx.lua file but will find the 
spell-xx.txt file and try to use that.

3. English words are only found if the 'xx' is 'uk' while 'en' or 'us' 
or 'ca' (Canadian) are not found no matter if % language={en | us | ca} 
(one choice only, I'm just using shorthand here). uk is one particular 
form of English with particular spelling rules (e.g. 'our' instead of 
'or' in words like 'honour' &al. There are also some terms proper in UK 
English that are not considered proper in US English and vice versa.) If 
all variants are not allowed, the generic 'en' ought to be used instead 
of 'uk' as it could be confusing to non-UK users. Ozzies and Kiwis may 
not mind but Yanks and Canucks do. :-)

4. Every 3-letter word is indicated as misspelled. This may be a 
side-effect of using the SCOWL word lists as they only deal with words > 
3-letters (except for some acronyms). Hence common words like 'was' or 
'who' or 'and' are marked as misspelled.

5. Only the first screen-full of text was color-coded. The rest of my 
document did not even have keyword highlighting. Turning off the 
spell-checking by removing the 'language=uk' line restored keyword 
highlighting throughout the whole file.

SciTE 3.1.0 on FreeBSD-9.0-i386

The wordlist(s) tried were from SCOWL 7.1 at http://wordlist.sourceforge.net
formed by cat en*80 | sort | uniq >spell-uk.txt

Yes, that is a big wordlist but decades of doing crosswords has left me 
with a large vocabulary. ;-)


-- 
Bill Meahan, Westland, Michigan USA

“Writing is a combination of intangible
   creative fantasy and appallingly
   hard work.”

           —Anthony Powell


This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 20-6-2012 18:37, Bill Meahan wrote:

> 1. Running the command as shown generates a spell-xx.lua file but
> complains about a spell-xx.lucluac file not being present.

luac compiles the lau file into bytecode (luac comes with lua and needs 
to match the lua version in scite)

> 2. The lexer does not load the spell-xx.lua file but will find the
> spell-xx.txt file and try to use that.
>
> 3. English words are only found if the 'xx' is 'uk' while 'en' or 'us'
> or 'ca' (Canadian) are not found no matter if % language={en | us | ca}
> (one choice only, I'm just using shorthand here). uk is one particular
> form of English with particular spelling rules (e.g. 'our' instead of
> 'or' in words like 'honour' &al. There are also some terms proper in UK
> English that are not considered proper in US English and vice versa.) If
> all variants are not allowed, the generic 'en' ought to be used instead
> of 'uk' as it could be confusing to non-UK users. Ozzies and Kiwis may
> not mind but Yanks and Canucks do. :-)

hm, do you have spell-ca and spell-en etc files? there is no hard coded 
uk check

> 4. Every 3-letter word is indicated as misspelled. This may be a
> side-effect of using the SCOWL word lists as they only deal with words >
> 3-letters (except for some acronyms). Hence common words like 'was' or
> 'who' or 'and' are marked as misspelled.

indeed, internally there is a limit of length 2

i can probably do a check for length i.e. if no 3 character words then 
also no checking

> 5. Only the first screen-full of text was color-coded. The rest of my
> document did not even have keyword highlighting. Turning off the
> spell-checking by removing the 'language=uk' line restored keyword
> highlighting throughout the whole file.

weird

> Yes, that is a big wordlist but decades of doing crosswords has left me
> with a large vocabulary. ;-)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 20-6-2012 20:02, Hans Hagen wrote:

> indeed, internally there is a limit of length 2
>
> i can probably do a check for length i.e. if no 3 character words then
> also no checking

the next version has

return {
  ["max"]=40,
  ["min"]=3,
  ["n"]=151493,
  ["words"]={
   ["aardvark"]="aardvark",
   ["aardvarks"]="aardvarks",

so in your case the 3 would be a 4 and that value is checked when coloring

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 817 bytes --]

On 06/20/2012 14:44, Hans Hagen wrote:
> On 20-6-2012 20:02, Hans Hagen wrote:
>
>> indeed, internally there is a limit of length 2
>>
>> i can probably do a check for length i.e. if no 3 character words then
>> also no checking
>
> the next version has
>
> return {
> ["max"]=40,
> ["min"]=3,
> ["n"]=151493,
> ["words"]={
> ["aardvark"]="aardvark",
> ["aardvarks"]="aardvarks",
>
> so in your case the 3 would be a 4 and that value is checked when coloring
>
> Hans

Cool! Many thanks.


-- 
Bill Meahan, Westland, Michigan USA

“Writing is a combination of intangible
   creative fantasy and appallingly
   hard work.”

           —Anthony Powell


This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]

On 06/20/2012 14:02, Hans Hagen wrote:
> On 20-6-2012 18:37, Bill Meahan wrote:
>
>> 1. Running the command as shown generates a spell-xx.lua file but
>> complains about a spell-xx.lucluac file not being present.
>
> luac compiles the lau file into bytecode (luac comes with lua and needs
> to match the lua version in scite)

I'll have to check the version in scite. I tried manually compiling with 
lua 5.1 with no success.

>

>
> hm, do you have spell-ca and spell-en etc files? there is no hard coded
> uk check

I only tried it with spell-en.{txt | lua} - error message said no valid 
word list loaded. Made a hard link from spell-en.txt to spell-uk.txt and 
it found that. I manipulated the line 1 from %  language=en to
%  language=uk to see the difference.




-- 
Bill Meahan, Westland, Michigan USA

“Writing is a combination of intangible
   creative fantasy and appallingly
   hard work.”

           —Anthony Powell


This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 20-6-2012 21:05, Bill Meahan wrote:
> On 06/20/2012 14:02, Hans Hagen wrote:
>> On 20-6-2012 18:37, Bill Meahan wrote:
>>
>>> 1. Running the command as shown generates a spell-xx.lua file but
>>> complains about a spell-xx.lucluac file not being present.
>>
>> luac compiles the lau file into bytecode (luac comes with lua and needs
>> to match the lua version in scite)
>
> I'll have to check the version in scite. I tried manually compiling with
> lua 5.1 with no success.
>
>>
>
>>
>> hm, do you have spell-ca and spell-en etc files? there is no hard coded
>> uk check
>
> I only tried it with spell-en.{txt | lua} - error message said no valid
> word list loaded. Made a hard link from spell-en.txt to spell-uk.txt and
> it found that. I manipulated the line 1 from %  language=en to
> %  language=uk to see the difference.

Forget about the txt file .. just the lua file will do (the luc file 
loads faster but it's neglectable on an edit session). I uploaded new 
scripts that generate a lua fiel with a bit more info and take care of 
the 4 char length (hopefully).

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 1434 bytes --]

On 06/19/2012 04:58, Hans Hagen wrote:

>> Interestingly, the lexers work just fine in Textadept but I haven't
>> quite figured out how to get them to load automatically. I have to
>> manually select the lexer but it works fine once I do.
>>

Turns out they don't work as well as I thought they did. To start the 
context lexers automatically, it is only necessary to configure the 
mime_types.conf file to associate the .tex extension with the desired 
lexer. When I do that, however, Textadept suddenly stops displaying 
anything in the buffer! Even if you load something other than a .tex 
file. :-(

> You have to change some configuration files but as that situation seems
> to change every now and then I wait with providing extra files for
> textadept till it's more stable.
>
> (Textadept has no realtime log pane so I cannot use it here without
> sacrificing too much convenience.)
>

Have you looked at the "run" documentation? It appears from that output 
from whatever command is run is directed to a new buffer in real-time. 
That's what emacs does.

Anybody got a ctags file for ConTeXt?  :-)

-- 
Bill Meahan K8QN

"The pessimist complains about the wind;
  the optimist expects it to change;
  the realist adjusts the sails."

-- William Arthur Ward

This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Hans Hagen]

On 20-6-2012 05:04, Bill Meahan wrote:

> Anybody got a ctags file for ConTeXt?  :-)

what are ctags

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | 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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[luigi scarso]

On Wed, Jun 20, 2012 at 4:24 PM, Hans Hagen <pragma@wxs.nl> wrote:
> On 20-6-2012 05:04, Bill Meahan wrote:
>
>> Anybody got a ctags file for ConTeXt?  :-)
>
>
> what are ctags



CTAGS(1)
                                     Exuberant Ctags

          CTAGS(1)

NAME
       ctags - Generate tag files for source code

SYNOPSIS
       ctags [options] [file(s)]

       etags [options] [file(s)]

DESCRIPTION
       The ctags and etags programs (hereinafter collectively referred
to as ctags, except where distinguished) generate an index (or "tag")
file for a variety of language objects found in file(s).  This tag
file allows these items
       to be quickly and easily located by a text editor or other
utility. A "tag" signifies a language object for which an index entry
is available (or, alternatively, the index entry created for that
object).

       Alternatively, ctags can generate a cross reference file which
lists, in human readable form, information about the various source
objects found in a set of language files.

       Tag index files are supported by numerous editors, which allow
the user to locate the object associated with a name appearing in a
source file and jump to the file and line which defines the name.
Those known  about  at  the
       time of this release are:

           Vi(1) and its derivatives (e.g. Elvis, Vim, Vile, Lemmy),
CRiSP, Emacs, FTE (Folding Text Editor), JED, jEdit, Mined, NEdit
(Nirvana Edit), TSE (The SemWare Editor), UltraEdit, WorkSpace, X2,
Zeus

       Ctags  is  capable of generating different kinds of tags for
each of many different languages. For a complete list of supported
languages, the names by which they are recognized, and the kinds of
tags which are generated for
       each, see the --list-languages and --list-kinds options.

-- 
luigi
___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Aditya Mahajan]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 909 bytes --]

On Wed, 20 Jun 2012, Hans Hagen wrote:

> On 20-6-2012 05:04, Bill Meahan wrote:
>
>> Anybody got a ctags file for ConTeXt?  :-)
>
> what are ctags

They allow you to jump around to specific locations in a file.

For example, in vim, pressing CTRL+] on "\in[sec:first]"  will jump to the 
location where sec:first is defined. Basically, a ctags file contains tag 
and the file name and line number where those tags are defined. The editor 
then reads the ctags file and jumps to the appropriate location.

A few years back, I had written a MkII module that generated ctags file 
when a tex file was compiled (attached). It was a hack that redefined a 
few low level macros.

To provide proper support for ctags, we also need to store the current 
filename and line number for each reference in the tuc file. Then a module 
can read the tuc file and write the ctags file in an appropriate format.

Aditya






[-- Attachment #2: Type: APPLICATION/x-tex, Size: 5969 bytes --]

[-- Attachment #3: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

Re: ConTeXt and SciTE

[Bill Meahan]

[-- Attachment #1.1: Type: text/plain, Size: 719 bytes --]

On 06/20/2012 11:24, Aditya Mahajan wrote:
> On Wed, 20 Jun 2012, Hans Hagen wrote:
>
>> On 20-6-2012 05:04, Bill Meahan wrote:
>>
>>> Anybody got a ctags file for ConTeXt? :-)
>>
>> what are ctags
>
> They allow you to jump around to specific locations in a file.
>

SciTE also uses them to generate auto-completion/insertion of language 
commands so a ctags file for ConTeXt itself would be useful.

-- 
Bill Meahan, Westland, Michigan USA

“Writing is a combination of intangible
   creative fantasy and appallingly
   hard work.”

           —Anthony Powell


This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4920 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________