May 2008 - ntg-context - NTG Mailing Lists

A question about the node library in luatex
by Jin-Hwan Cho 26 May '08

26 May '08

I am trying a few tests with luatex. 1. Made a format file "luaetex.fmt" by "luatex --ini etex.ini" and a lua file "luaetex.lua" containing just one line "node.types()" 2. Test file "test.tex" is as follows: \directlua0{node.types()} \bye 3. Run "luatex --fmt=luaetex.fmt test". Then there is no problem. 4. Instead, "luatex --lua=luaetex.lua --fmt=luaetex.fmt test" causes an error. Why don't we use the node library in the lua file "luaetex.lua"? Thanks in advance, ChoF.

3 3

Out of office: ntg-context Digest, Vol 47, Issue 55
by rordorf＠mdpi.org 26 May '08

26 May '08

I am out of office and will return on Thursday, 29 May 2008. Kind regards, Dietrich Rordorf -- Mr. Dietrich Rordorf Molecular Diversity Preservation International (MDPI) Matthaeusstrasse 11, CH-4057 Basel, Switzerland E-mail: rordorf(a)mdpi.org Tel. +41 61 683 77 34 (office) Tel. +41 76 561 41 83 (mobile) Fax +41 61 302 89 18

1 0

interim fix for aesc-like macro
by Charles P. Schaum 25 May '08

25 May '08

I found an interim fix for the \ae macro in the schemata: put the word with the macro in an hbox, and the problem goes away. I wonder what the mechanics behind that are. I tend to have weird documents with dead languages. Who knows, maybe I want to cite Aelfric using Old English letters or Sir Gawain or whatever Middle High German with a yogh or similar glyph. Come to think of it, Gothic would be cool, too. So, figuring out the mechanics would be helpful. Thanks, Charles

2 1

Thanks for the boxes with schems
by Charles P. Schaum 24 May '08

24 May '08

Thanks, Hans, for the suggestion. It works quite well, except the \ae{} macro starts producing a lowercase j. My guess is this refers to an encoding issue, since I found that using \sc tends to not do small caps except for using Computer Modern. I did RTFM, but I'm just not making the connection. If someone can point me to a document on fonts that I can work through ... the section in the manual left me a little confused. After using Pagemaker, Quark, and InDesign, I kinda get the approach but it seems to be a culture shock like Metafont was and remains. I copied the examples from the manual when I did a book mock-up for work and that worked real well. Everyone was impressed by what ConTeXt could do, although the official workflow will remain Incopy and InDesign. Still, I uotdid an experienced graphic designer using Adobe CS3 with my little bit of code for schemas. ConTeXt and friends have some unique benefits. So if I could solve the font mystery, I would be grateful. I have some books, for example, that I would like to reproduce with ConTeXt by scanning the Fraktur and OCR'ing with tesseract, then doing the layout with ConTeXt. I have an Ernestine Bible (Das Weimarische Bibelwerk) for which the binding is shot but the pages are good. This way will take much less than scanned images, although some images will remain. Ultimately I would like to make something like yfonts, but with unicode or some standard encoding to allow either umlauts or superscript e. In my own library I have books from the early eighteenth century on, and Google books has more, so there's no lack of subjects to scan into Fontforge. Charles

2 1

luaTeX and on-the-fly MetaPost compilation
by Stephan Hennig 24 May '08

24 May '08

Hi, I didn't have the opportunity to touch luaTeX yet, but let me ask one question in advance: Since luaTeX has a built-in MetaPost interpreter, is it possible to refer to a certain figure in a MetaPost source file for inclusion, instead of a compiled figure? As an example, I would like to say in a TeX document (syntax may differ) \includeMetaPost{foo.2} and this should not refer to the pre-compiled file foo.2 but to section figure(2); ... endfig; in file foo.mp and compile it on-the-fly. Would that be possible? Rationale: I do not want to mix TeX and MetaPost code. Probably, I'll stick with compiling .mp files prior to the TeX run anyway, but I'm curious about this option. Best regards, Stephan Hennig

3 6

Odd Behavior in pdftex/xetex
by Michael.Urban＠jpl.nasa.gov 24 May '08

24 May '08

The following specimen was run on live.contextgarden.net with each of the three typesetters: \setupcolors[state=start] \starttext \input knuth \bTABLE \bTR [align=middle]\bTH Range\eTH{}\bTH Value\eTH{}\eTR \bTR \bTD \type{<} 12\eTD{}\bTD 3\eTD{}\eTR \bTR \bTD 12--16\eTD{}\bTD 2\eTD{}\eTR \bTR \bTD \type{>}16\eTD{}\bTD 1\eTD{}\eTR \eTABLE \input knuth \stoptext In the case of pdfTeX and XeTeX, the table is given a width equal to the textwidth; in the caes of LuaTeX, it is typeset correctly with natural widths. When \setupcolors is removed, both pdfTeX and XeTeX also produce the correct result. This sounds like a bug to me (and took me forever to isolate \setupcolors - of all things! - as the culprit).

3 2

Ramistic schemata
by Charles P. Schaum 23 May '08

23 May '08

Greetings, I have been using ConTeXt since April, plain TeX since March, and LaTeX/LyX for about a year. I have been working on multilingual texts and, until the recent permutations of Word, no WYSIWYG product, with the possible exception of Mellel for Hebrew, did any good job. Now I don't like WYSIWYG anymore but use such products for work. I have been able to create near-optimal reproductions of Ramistic schemata using ConTeXt because the \showboxes toggle is most helpful in showing where I need to put whitespace. The following may indeed be crude, i.e., not computing box height and other sophisticated stuff, but I'm a n00b and have not read the TeXbook through, although that and TeX by topic are both a vade mecum. Here's the code, FWIW. Use it as you like. It started out as plain TeX using Kile on Ubuntu, migrated to ConTeXt in TeXshop/MacTeX, and came back to Kile after I found an xml file for katepart that allowed for proper syntax highlighting. Charles -----Cut Here----- \def\schema#1#2#3{\hbox{$\vcenter{#1}\left\{\vbox to #2{\vfil}\right.\vcenter{#3}$}} \def\altschema#1#2#3#4{\hbox{$\vcenter{#1}{\left\lmoustache\vbox to #2{\vfil}\right.\atop\left\rmoustache\vbox to #3{\vfil}\right.}\vcenter{#4}$}} %\showboxes \starttext \tfx {\tfa I. SCHEMA}\par \schema % top level schema { \hbox{Subjectum theolo-} \hbox{gi\ae{} est Notitia} \hbox{Dei. Considerat} \hbox{ergo, Dei, vel} } {13ex} { \blank[big] \schema % first nested schema { \hbox{{\sc Essentiam}, in} } {5ex} { \hbox{Unitate natur\ae{}.} \hbox{Trinitate personarum.} \hbox{Operibus ad intra.} } \blank[medium] \schema % second nested schema { \hbox{{\sc Voluntatem},} \hbox{manifestatam in} \hbox{operibus ad extra;} \hbox{ut in} } {12ex} { \hbox{Creatione.} \hbox{Sustentatione natur\ae{} laps\ae{}.} \hbox{Reparatione.} \hbox{Conversione.} \hbox{Justificatione.} \hbox{Sanctificatione \&} \hbox{Glorificatione ejusdem.} } } \page {\tfa II. SCHEMA}\par \altschema % { \blank[7*big] \hbox{Subjectum \&} \hbox{summa univer-} \hbox{s\ae{} Scriptur\ae{},} \hbox{est {\sc Cogni-}} \hbox{{\sc tio} vel} } {29ex} {10ex} { \altschema % { \hbox{{\sc Dei}, qua-} \hbox{lis sit, aut} } {10ex} {2ex} { \blank[big] \schema % { \hbox{{\sc Per se}:} \hbox{scilicet.} } {3.1ex} { \hbox{Unus in essentia.} \hbox{Trinus in personis.} } \blank[medium] \schema % { \hbox{Ad hominem} \hbox{quem vel} } {13ex} { \hbox{Accusat \& terret, {\sc Per Legem},} \hbox{Consolatur \& erigit, {\sc Per Evangelium}.} \hbox{Salvat, {\sc Per Christum}.} \hbox{Renovat, {\sc Per Spiritum Sanctum}.} \hbox{Sanctificat, {\sc Per Verbum} \& {Sacramenta}.} \hbox{Castigat, tentat \& exercet, {\sc Per Crucem}.} \hbox{Glorificat {\sc Per Resurrectionem Carnis}} \hbox{{\sc Ad Vitam \AE{}ternam}.} } } \altschema % { \blank[6*big] \hbox{{\sc Hominis},} \hbox{qualis sit} } {22ex} {3ex} { \altschema % { \hbox{{\sc Per se}:} } {6ex} {1ex} { \blank[2*big] \hbox{Ante lapsum.} \blank[big] \altschema % { \hbox{Post lapsum:} } {5ex} {2ex} { \hbox{Ante Regenerationem \&} \hbox{Renovationem S. Sancti.} \blank[small] \hbox{Post Regenerationem \&} \hbox{Renovationem S. Sancti.} \blank[2*small] } \blank[big] } \schema % { \hbox{Ad} } {18ex} { \schema % { \hbox{{\sc Deum}} } {14ex} { \hbox{P\oe{}nitentia agens, agnitis peccatis \& ira} \hbox{Dei cognita {\sc Ex Lege}.} \hbox{Erigens se {\sc Voce Evangelii}.} \hbox{Credens {\sc In Christum Salvatorem}.} \hbox{Non repugnans {\sc Spiritui Sancto} impellenti.} \hbox{Audiens {\sc Verbum}: \& utens {\sc Sacramentis}.} \hbox{Patienter \& constanter sufferens {\sc Crucem}.} \hbox{Sperans \& expectans glorificationem {\sc In}} \hbox{{\sc Resurrectione Carnis Ad Vitam \AE{}ternam}.} } \blank[medium] \schema % { \hbox{seipsum ratione} } {3.1ex} { \hbox{Anim\ae{} vel} \hbox{Corporis} } \schema % { \hbox{Proximum,} } {6ex} { \blank[medium] \schema % { \hbox{Amicum ratione vel} } {7ex} { \hbox{Religionis.} \hbox{Politic\ae{} \& Oeconomic\ae {}.} \hbox{Cognationis.} \hbox{Agnationis.} } \hbox{Inimicum.} \blank[3*big] } \blank[big] } } } \stoptext

2 1

[LUATEX] uname() volunteers needed
by Taco Hoekwater 22 May '08

22 May '08

Hi all, This is a little offtopic (it deals with luatex only) but as Mojca said: there are many more luatex-using people here than on dev-luatex. In a discussion with Yue Wang he convinced me that it would be better to use uname() for finding os.name instead of the current jungle of #ifdefs. Because I do not want to alter the lua return values, that means I will have to interpret the contents of the returned structure a bit. To do that, I would appreciate it if the people on a non-linux32intel platform would compile and run the attached minimalistic C file. Thanks in advance, Taco

13 22

font tables
by Idris Samawi Hamid 22 May '08

22 May '08

Dear gang, Is there an available ConTeXt utility for creating font tables for luatex? \ShowFont does this for 256-char encodings but we need something to create a matrix in pdf through luatex for unicode fonts. Best wishes Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shi`i Studies Department of Philosophy Colorado State University Fort Collins, CO 80523

3 3

bug with hyphenatedurl
by Steffen Wolfrum 21 May '08

21 May '08

Hi, please have a look at the following minimal example (ran with mkii): -> \usetypescript[postscript][\defaultencoding] \setupencoding[default=texnansi] \enableregime[utf] Test text\footnote{{Z4300, Stand: 1.{|DuennRaum|}Januar\;2002, einsehbar unter \hyphenatedurl{http://www.thw.de/thw‑inland/ grundlagen/rechtsgrundlagen/abr\_rili.htm}}} \stoptext <- Just shortly before handing the PDF to the printer I saw that the part "thw‑inland" surprisingly became "thw\dochar␣{45}inland" (at least on my machine)! Is there a fix? Steffen

3 2