On Fri, 21 Sep 2007 14:40:33 +0200
Hans Hagen
Wolfgang Schuster wrote:
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.
i dunno what this featurs is but if it has to do with some kind of automatism for switching fonts depending on chars, then it has to wait till i have something in place for luatex (using virtual fonts btw, basics are there actually), and then we can look if we can use the same high level interface to mimick this in xetex; it's ok to have the same high level interface with slightly different behaviour, as with font features
you can use this feature for font switching but this is not hard coded. Version 0.997 of XeTeX introduced a new concept to assign every character a class value. You can define rules what should happen if you switch for example from class 1 to class 2 and another one if you do the same in reverse order. The commands for this action are saved in token register and came into action if this class switch appear in the document. the unicode-letters file from XeTeX define a class for quotation, punctutation ... in CJK and another one for the other CJK characters and define spacing and linebreaking between normal characters and punctuation now by the class number (you did something similiar in your chinese module but used active characters instead). The XeTeX reference manual has a simple example of this concept on page 10 and 11. http://tug.ctan.org/info/xetexref/XeTeX-reference.pdf can't this be done in LuaTeX with nodes (or what you mentioned for your color modell) or something similar.
- 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.
no problem if we need what should go in there
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
sure, but that's why you can have a different formatname and filename that generates it, so you can have blabla.tex being used for generating the format pdftex.fmt (also, since one has to move files anyway, renaming isno big deal either)
but I am too lazy to rename files or create them always by hand with every update ... Wolfgang