Hi all, I have made a first snapshot available, now that it processes torture.tex correctly. This is not a 'release' per se, so please do not be offended by the extreme lack of install instructions and manual. Some hints are at the end of this message. The snapshot is up to par with Aleph-RC4 (from texlive devel) and the latest pdftex beta (even newer than 20060811). However, there are some differences, to summarize: * There is no pool file (all strings are embedded) * -8bit and -translate-file are silently ignored * There is no mltex nor enctex (conflicts with aleph) * The tex functionality is always present and enabled (but see below about TeXXeT), so the asterisk or -etex switch for initex is not needed * "plus 1 filllllllll" does not generate any errors from TeX * TeXXeT (from eTeX) is not present, so the primives \TeXXeTstate \beginR \beginL \endR \endL are missing * The experimental pdftex regex match operations are removed, because that feature does not make much sense when lua is available so the primitives \pdfmatch \pdflastmatch are missing * The input translations from Aleph are not implemented, the 16 related primitives are all missing \DefaultInputMode \noDefaultInputMode \noInputMode \InputMode \DefaultOutputMode \noDefaultOutputMode \noOutputMode \OutputMode \DefaultInputTranslation \noDefaultInputTranslation \noInputTranslation \InputTranslation \DefaultOutputTranslation \noDefaultOutputTranslation \noOutputTranslation \OutputTranslation All file IO assumes UTF-8, except that all the low-ascii controls except TAB, CR en LF are written to the terminal using ^^ notation (even these are binary in the log file). * Input characters can use the full range of Unicode, but it probably only makes sense to use values above the base plane for \mathcode and \catcode assignments, since the fonts as well as the hyphenation patterns are strictly 16-bit still. * The primitives \pdfpagewidth and \pagewidth, \pdfpageheight and \pageheight, \fontcharwd and \charwd, \fontcharht and \charht, \fontchardp and \chardp, \fontcharic and \charic, are all aliases of eachother. * The new primitive \clearmarks<number> clears a marks class completely. * The experimental pdftex primitives \pdfprimitive \ifpdfprimitive \ifpdfabsnum \ifpdfabsdim and provided without the extra 'pdf' prefix, so they are simply called \primitive \ifprimitive \ifabsnum \ifabsdim instead. * I probably forgot to mention some things :-) Have fun, Taco Downloading and installation details: If you go to https://foundry.supelec.fr/frs/?group_id=10&release_id=160 you will see that there are three released files: * luatex-snapshot-20060818.tar.gz This is the source tree. * luatex-snapshot-20060818-win32.zip A cross-compiled (mingw) windows binary. This is a web2c based binary, so it needs a texmf.cnf file (It will NOT work if you have only miktex installed). This executable cannot run dynamically loaded lua dlls. Perhaps that can be fixed but I do not know how. * luatex-snapshot-20060818-linux-i386.tar.gz A linux binary. This needs ld-linux.so.2, so you need a somewhat modern linux for that, but compiling from source for linux should not be a problem. The binaries should go in a 'normal' TeX binary folder like texmf/bin or texmf-win32/bin so that they can find your texmf.cnf automatically. If you put them elsewhere, you have to set the TEXMFCNF environment variable. There is no pool file, so you do not have to worry about that. For meaningful unicode input and hyphenation, you need a file that sets the \lccode etc. values for chars with a value higher than 256. One such file is part of the xetex distribution (unicode-letters.tex). Greetings, Taco
Taco Hoekwater wrote:
* I probably forgot to mention some things :-)
Only the most important remarks: * The pdf writing parts are still 8bit, these do not understand ofm/ovf fonts yet. * Text directions TRT etc. also only work in dvi mode. * Memory consumption is nearly 300MB higher than either pdfTeX or Aleph. The memory and font writing issues are next on my todo list for next week. Greetings, Taco
Taco Hoekwater wrote:
The binaries should go in a 'normal' TeX binary folder like texmf/bin or texmf-win32/bin so that they can find your texmf.cnf automatically. If you put them elsewhere, you have to set the TEXMFCNF environment variable.
There is no pool file, so you do not have to worry about that.
Hopefully this I'm not doing something too obviously wrong here, but I'm getting the following error trying to build a LaTeX format. ./luatex -ini /usr/share/texmf-tetex/tex/latex/base/latex.ltx ... ... ! Text line contains an invalid utf-8 sequence. l.7801 \uccode`\=`\ Ð % d-bar I'm able to build the format for Plain TeX working without any problems though. -- [Geoff Washburn|geoffw@cis.upenn.edu|http://www.cis.upenn.edu/~geoffw/]
Hi Geoffrey, Geoffrey Alan Washburn wrote:
... ! Text line contains an invalid utf-8 sequence. l.7801 \uccode`\=`\ Ð % d-bar
I'll bet this line is coming from a hyphenation patterns file. _all_ file I/O has to be utf-8 encoded, including patterns. Unf., lots of patterns files are using EC font encoding as a file encoding, and are therefore not valid utf-8. I do not normally use LaTeX any more, making it hard for me to give exact advice, but you either need to find a set of patterns for this language that _is_ utf-8 encoded (ConTeXt ships with such pattern files, and I understood that there is a set of similar files that come with XeTeX), or you have to disable the language(s) that is causing you grief by means of some babel configuration file. Greetings, Taco
Hi Taco,
On Fri, 18 Aug 2006 12:55:05 -0600, Taco Hoekwater
Hi Geoffrey,
Geoffrey Alan Washburn wrote:
... ! Text line contains an invalid utf-8 sequence. l.7801 \uccode`\=`\ Ð % d-bar
I'll bet this line is coming from a hyphenation patterns file. _all_ file I/O has to be utf-8 encoded, including patterns. Unf., lots of patterns files are using EC font encoding as a file encoding, and are therefore not valid utf-8.
I do not normally use LaTeX any more, making it hard for me to give exact advice, but you either need to find a set of patterns for this language that _is_ utf-8 encoded (ConTeXt ships with such pattern files, and I understood that there is a set of similar files that come with XeTeX), or you have to disable the language(s) that is causing you grief by means of some babel configuration file.
How do you avoid this problem to run torture.tex, which is a latex/lambda file? Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Taco Hoekwater wrote:
The binaries should go in a 'normal' TeX binary folder like texmf/bin or texmf-win32/bin so that they can find your texmf.cnf automatically. If you put them elsewhere, you have to set the TEXMFCNF environment variable.
There is no pool file, so you do not have to worry about that.
Hopefully this I'm not doing something too obviously wrong here, but I'm getting the following error trying to build a LaTeX format.
./luatex -ini /usr/share/texmf-tetex/tex/latex/base/latex.ltx ... ... ! Text line contains an invalid utf-8 sequence. l.7801 \uccode`\=`\ Ð % d-bar
I'm able to build the format for Plain TeX working without any problems though. i dunno about latex; since luatex is far from production ready you can best comment pattern loading or (since you're 'edu') stick to us
Geoffrey Alan Washburn wrote: patterns only since that is covered by utf (context uses utf patterns so loading there is no problem in generating context formats) 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 Fri, 18 Aug 2006 12:04:20 -0600, Geoffrey Alan Washburn
I'm getting the following error trying to build a LaTeX format.
./luatex -ini /usr/share/texmf-tetex/tex/latex/base/latex.ltx ... ... ! Text line contains an invalid utf-8 sequence. l.7801 \uccode`\=`\ Ð % d-bar
I'm able to build the format for Plain TeX working without any problems though.
Here is what I did: 1. comment out lines 7801 and 7901 in latex.ltx 2. comment out offending languages in \tex\generic\config\language.dat (for me I just commented out everything other than english-) Then I do luatex "&lambda" torture And I can confirm that torture.tex runs fine! BTW: Taco, what dod you do with \nextfakemath (I just did \let\nextfakemath\relax)? Best Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Hi, Idris Samawi Hamid wrote:
Here is what I did:
1. comment out lines 7801 and 7901 in latex.ltx
I do not remember having to do that, but it could be just my memory cells that no longer accept 'hitting enter' as a noticeable event. Or it could be a difference in latex (mine was fetched fresh from CTAN yesterday)
BTW: Taco, what dod you do with \nextfakemath (I just did \let\nextfakemath\relax)?
I had \def\nextfakemath{}, that amounts to roughly the same thing in practice. The strange thing is: the command doesn't appear to be necessary anyway. I googled for what it was supposed to do, but could not quite figure it out. It was not even clear if it was a really old (1.5?) or a really new primitive (1.21?). However, the output does not strike me as 'wrong' in any way. Bizarre. Taco
Taco Hoekwater wrote:
Hi,
Idris Samawi Hamid wrote:
Here is what I did:
1. comment out lines 7801 and 7901 in latex.ltx
I do not remember having to do that, but it could be just my memory cells that no longer accept 'hitting enter' as a noticeable event. Or it could be a difference in latex (mine was fetched fresh from CTAN yesterday)
BTW: Taco, what dod you do with \nextfakemath (I just did \let\nextfakemath\relax)?
I had \def\nextfakemath{}, that amounts to roughly the same thing in practice.
The strange thing is: the command doesn't appear to be necessary anyway. I googled for what it was supposed to do, but could not quite figure it out.
It was not even clear if it was a really old (1.5?) or a really new primitive (1.21?). However, the output does not strike me as 'wrong' in any way. Bizarre.
maybe a left over from this one time tex -> pres mml mess Hans
Taco,
I had \def\nextfakemath{}, that amounts to roughly the same thing in practice.
The strange thing is: the command doesn't appear to be necessary anyway. I googled for what it was supposed to do, but could not quite figure it out.
IIRC, it was a trick for the LaTeX tabular environment, which is typeset in math mode, but there were plans to remove it. I think it ensures the writing direction is that of text. Javier
participants (5)
-
Geoffrey Alan Washburn
-
Hans Hagen
-
Idris Samawi Hamid
-
Javier Bezos
-
Taco Hoekwater