Re: waiting for mswincontext

[Wolfgang Schuster <schuster.wolfgang@googlemail.com>]

On Thu, 20 Sep 2007 22:41:08 +0200
Hans Hagen <pragma@wxs.nl> wrote:

> Mojca Miklavec wrote:
> >>> So one additionally needs:
> >>> - (possibly modified) xetex.ini itself
> >>> - unicode-letters.tex (could be replaced by enco-utf.tex, though I
> 
> context does not use that file (plain may use it) we can indeed use 
> enco-utf for plain as well (also defines some named chars)
> 
> context does not depend on any tex file outside the base path
> 
> >>> just figured out that there's more in unicode-letters than in
> >>> enco-utf, but in that case enco-utf is that one which should be fixed)
> 
> depends on the kind of error -)
> 
> enco-utf uses info from unicode tables (character categories)
> 
> >> this is not possible with the 0.997dev version because it presets
> >> charclasses (a new feature in XeTeX) for a few CJK characters
> > 
> > I saw some new additions when I took a look.
> > 
> > This means that enco-utf needs to be updated once hans gets the new
> > binaries from Akira :)
> 
> depends, if we don't use these new features .. (yet)

THis is a nice feature for our own simple plain documents but nothing
for ConTeXt because there is no replacement in pdfTeX/luaTeX but it
would be nice to have also something to use different fonts for latin,
greek, CJK without using environments and switch to them with only the
right characters.

I want such a feature because CJK fonts have sometimes ugly latin
characters and I want to use another font for them, I know this did
happen in the current ConTeXt version but there should be no
difference in fonts for CJK and the rest. Both should be defined with
typescripts, one can use one fonts for both or select one for CJK and
another one for the rest.

> >>> - etex.src (btw: why is that one only used in xetex, but not in pdfTeX?)
> >> this is also used for the pdftex format in w32tex
> 
> because i cannot imagine a macro package to use the content of that file
> 
> > I will take a look at w32tex then.
> > 
> > It would be really handy to have those three plain formats.
> 
> well, only is if it is not adding too much to the minimals, (and formats 
> to be generated by users)

I have nothing against to make another archive cont-pln with all the
file we need for the plain formats.

> if you want such formats, we need dedicated files to make them, like 
> pdftex-plain.tex and such (after all, we want predictable stuff) for 
> initializing them
> 
> Hans

the file name for the format should math the engine name because it
will be loaded with engine by default if you call it, e.g. pdftex myfile
with process the file myfile with the format file pdftex.fmt

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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________