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 ___________________________________________________________________________________

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.

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

With \enabledirectives[fonts.uppercasesharps] you tell context to convert ß to ẞ (instead of SS) when you use \WORD to capitalize a string. the font designers job to provide a small ẞ (he could use stilistic sets to let you choose between ß and ẞ). Wolfgang

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

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

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

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

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

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

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

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

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

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_shoul... -- 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' ----------------------------------------------------------------------------------

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" À: 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_shoul... -- 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 ___________________________________________________________________________________

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

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" À: 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" À: 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_shoul... -- 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 ___________________________________________________________________________________

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" À: 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" À: 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 ___________________________________________________________________________________

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 ___________________________________________________________________________________

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

On 3 May 2016 at 11:51, Thomas Fehige 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

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