Mojca Miklavec wrote:

Note that also three really important fixes have been added to XeTeX recently, so ConTeXt works much better with XeTeX 0.997.

the bottom line is, that we need to make sure that we hav ethe most recent bins for all platforms before we can generate minimals

It's the ConTeXt distribution, not the binaries which are broken.

i'm a bit puzzled ... for pdftex, nothing changed, for luatex, indeed bins and zips need to be in sync (esp because there have been changes in the lua font code that needed adaptions in the mkiv code) and xetex ... well, that's an interplay between engine and macros and trying to adapt i think that luatex and xetex are fast moving targets so in most cases one needs to have updates of them and macro packages in sync; xetexs font syntax has changed over time, currently a feature was added to intercept problems but this is only on the latest bins, font searching is very engine dependent and also to some extend os dependent (upper/lowercase) etc etc anyhow, the dust will probably settle in a few weeks (new bins available everywhere) a tricky area is metapost ... since mp cannot handle open type we need to bend the rules sometimes and do ugly workarounds but we're getting there

But note that there are still some problems: - wrong font size in XeTeX

more a xetex problem

- textext("...") in metapost doesn't work

will never work completely if one uses different fonts in xetex and metapost in one document (well, it can work, but one had to make sure that the map stuff is sorted out then)

- most probably others, not yet discovered

we'll try to keep them hidden -) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

Vyatcheslav Yatskovsky wrote:

Hello Hans,

Could you please answer my questions about recent Windows minimal?

1) Why we need to set almost all in setuptex.bat, while the same vars (except Windows' PATH) are already set in texmf.cnf?

well, this is not recent, but has aways been the case; in setuptex i make sure that no conflicts can arise between different trees; so one can have multiple trees installed, without clashed; you don't wanna know what can happen (and how much time it costs to find out and fix) if some installer has set variables at the outer shell level; i just don't want to take any risk here

2) How can I get rid of LM (and other) fonts completely? I want to use solely luatex and system fonts, but bound to have those monsters too.

just delete them but i would not delete the lm since they're used as fallbacks; if you want to default to something else, you need to tweak the initializations (maybe some day when the gyre math fonts are there i'll provide something for that); keep in mind that many tex users use tex for math and not having set up math will break al lot then

My area of interest is luatex only, since it is progressive, font-tolerant and powerful. :o)

well, the overhead of lm is not that large (maybe someday i'll ship zips and run the fonts from zips); a few cjk fonts in your system font path take more space -) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

On 9/26/07, Hans Hagen wrote:

...

1) Why we need to set almost all in setuptex.bat, while the same vars (except Windows' PATH) are already set in texmf.cnf?

well, this is not recent, but has aways been the case; in setuptex i make sure that no conflicts can arise between different trees; so one can have multiple trees installed, without clashed; you don't wanna know what can happen (and how much time it costs to find out and fix) if some installer has set variables at the outer shell level; i just don't want to take any risk here

So what environment variables can I set globally to avoid the need for running setuptex.bat? My first guess is: OSFONTDIR=%SystemRoot%\fonts SETUPTEX=done CTXMINIMAL=yes TEXPATH=C:\...<whatever the path is>...\context\tex\ TEXMFMAIN=%TEXPATH%\texmf TEXMFOS=%TEXPATH%\texmf-mswin TEXMFPROJECT=%TEXPATH%\texmf-project TEXMFFONTS=%TEXPATH%\texmf-fonts TEXMFLOCAL=%TEXPATH%\texmf-local TEXMFEXTRA=%TEXPATH%\texmf-extra TEXMFCNF=%TEXPATH%\texmf{-local,}\web2c TEXPOOL=%TEXMFOS%/web2c\{$engine,} TEXFORMATS=%TEXMFOS%\web2c\{$engine,} MPMEMS=%TEXMFOS%\web2c\{$engine,} MPPOOL=%TEXMFOS%\web2c\{$engine,} Path=%TEXMFOS%\BIN;%Path% TEXMFCACHE=%TEMP% VARTEXMF=%TEXMFCACHE%\texmf-var TEXMF={$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!$TEXMFMAIN} TEXMFDBS=$TEXMF RUBYLIB=%TEXMFLOCAL%\SCRIPTS\CONTEXT\RUBY;

On 9/30/07, Hans Hagen wrote:

...

So what environment variables can I set globally to avoid the need for running setuptex.bat? My first guess is: <snip> SETUPTEX=done CTXMINIMAL=yes

not if setuptex is not used

CTXMINIMAL is also not needed?

...

TEXPATH=C:\...<whatever the path is>...\context\tex\ TEXMFMAIN=%TEXPATH%\texmf

TEXMFOS=%TEXPATH%\texmf-mswin TEXMFPROJECT=%TEXPATH%\texmf-project TEXMFFONTS=%TEXPATH%\texmf-fonts TEXMFLOCAL=%TEXPATH%\texmf-local TEXMFEXTRA=%TEXPATH%\texmf-extra

depends on your trees

Using the directory tree as stored in mswincontext as my starting point.

...

TEXPOOL=%TEXMFOS%/web2c\{$engine,}

not for luatex/xetex

...

TEXFORMATS=%TEXMFOS%\web2c\{$engine,}

not for luatex

...

MPMEMS=%TEXMFOS%\web2c\{$engine,}

depends

...

MPPOOL=%TEXMFOS%\web2c\{$engine,}

not needed any more

But setuptex still sets these. What does it mean, that TEXPOOL &al. aren't needed for luatex/xetex? Does MKII need them?

...

TEXMF={$TEXMFOS,$TEXMFPROJECT,$TEXMFFONTS,$TEXMFLOCAL,$TEXMFEXTRA,!!$TEXMFMAIN}

yes

...

TEXMFDBS=$TEXMF

dependes on kpse version i think

I've been using %var% notation for parts that Windows expands when the variable is defined, but I see UNIX-style $var here and there. Should these be expanded at define-time also, or are these for the programs that use them to understand? I've got Perl, Python, and Ruby installed, & I'm using mswincontext and upgrades thereto as the only TeX distribution on the machine; I'd like it to work as smoothly as MiKTeX does where it's installed -- i.e., replace setuptex with a machine-global set-up. And I'm willing to jump through some hoops to find the "right way" so installation can be made easier for others --Joel

So, to sum up: The tex engines should be accessible via PATH, OSFONTDIR is really handy; other than that only TEXPATH and TEXMF* are needed, since "pool files" (whatever they are) are on the way out. Seems straightforward enough, if that's complete. Is there any real point to creating an NSIS or Inno Setup install program for mswincontext, or is someone working onthat already? They both handle environment variables nicely, I've heard. --Joel