"Pawel Jackowski na Onet" writes:

[...]

...

The reason I'm so persistant to solve that (probably not crucial)

...

that I'm still spying another problem -- generating format with proper default font information (as described in details in other threads). I thought that texexec config file(s) may be important at that point. But after copying 'texexec.rme' to 'texexec,ini', changing some defaults,

Subject: [NTG-context] bodyfont plr (default font) problem is like

...

set FmtLanguage to pl set FmtBodyFont to plr

and updating ls-R, the problem still appear, means that format generated with proper command

texexec --make --language=pl,en --bodyfont=plr en

doesn't use the proper default font.... So I'm afraid it's not the

solution.

I just did a quick test:

texexec --make --alone --bodyfont=plr en

and then run a simple tex file (\starttext \input tufte \stoptext)

gave me an error that plr12 could not be found. So I guess it now uses plr as a default. But I am not sure.

When you are using your setup, does plr12 get included in your document?

When I use format generated during first context installation, everything works fine, means that context use plr by default. However this quite old format contains only pl-hyphenation patterns. For a couple of weeks I had been trying hard to generate format with additional hyphenation patterns AND plr as default font. But each attempt gave me a format which use cmr by default. Of course when I included i.e plr10 definition in tex code or input some pl-oriented typescript, everything was ok since I have correclty instaled and configured pl-fonts. But default was still cmr, not plr. I've just tried to generate format with additional option '--alone' (as in your quick test) and that was the solution! Generated format uses the proper default font now. Actually I didn't know that texexec uses 'fmtutil' by default while generating formats (is there any special reason for that?...). My problem shows that texexec (its self) is able to generate format in more reliable way :) Anyway Thank You Very Much For That Hint! Regards, Pawe/l

Am Montag, 06.10.03, um 13:18 Uhr (Europe/Zurich) schrieb Pawel

...

But I still can't get an idea of copying '.rme' to '.ini' since '.rme' file can be read as well. Is that an easy way to save orginal config file untouched?

.rme is overwritten at each update, your manually adapted .ini stays.

So that is the answer! Thanks a lot.

...

and updating ls-R, the problem still appear, means that format generated with proper command texexec --make --language=pl,en --bodyfont=plr en doesn't use the proper default font.... So I'm afraid it's not the solution.

I think you must change that in cont-usr.tex (copy from cont-usr.ori, same reason). This file resides in texmf/tex/context/base.

I have tested a lot of modifiction of 'cont-usr.tex' (without effects)... About two hours ago (following Patrick's hint) I added '--alone' option while generating format and than bad dream disappeared. The conclusion is that (probably) bypassing fmtutil in such special cases makes format generating more reliable. Probably the best (quite advanced) way is to generate 'strange' formats using directly 'tex_engine --ini ...' command, but I'm not sure if I can generate proper context format in this way. I'm afraid it's not my ligue yet :-] Thanks, Pawe/l