Hello,
Tomorrow, after incorporating some fixes from this mailing list. I used Latin Modern Roman. The characters were in the PDF, the font as well, but they were invisible and all at the same position.
Strange, that's not what I have here with a very simple test. If you could send an exact example file some day, I would be very interested, and I'm sure Taco would be as well.
First of all, an apology: While complaining about a missing fontforge table documentation, I completely overlooked section 13. Now, after incorporating the fixes (concerning scaling), everything worked. I attached the PlainTeX source as a UTF-8 document (please remove the BOM at the beginning to prevent LuaTeX from complaining about a missing character 65xxx). However (an excerpt from the attached document, I hope the diacritics are not lost): ---------------------------------------------------------------------- \font\textfont=lmroman10-regular at 10pt % (A) % \font\textfont=lmroman10-bold scaled 1000 % (B) % \font\textfont=lmroman10-bold % (C) \textfont Lûátèx sürė ĩs grēăt! fi ffi AV \bye ---------------------------------------------------------------------- (A) works perfectly. (B) and (C) produce (C most likely because 'scaled 1000' is the default): This is LuaTeX, Version snapshot-0.20.0-2007120515 (Web2C 7.5.6) (OTFTest.texLoading font /usr/local/teTeX/share/texmf.tetex/fonts/opentype/publ ic/lm/lmroman10-bold.otf [1{/usr/local/teTeX/share/texmf.local/fonts/map/pdftex /updmap/pdftex.map} ! pdfTeX error (arithmetic): divided by zero. \plainoutput ...headline \pagebody \makefootline } \advancepageno \ifnum \out... <output> {\plainoutput } \supereject ->\par \penalty -\@MM \bye ->\par \vfill \supereject \end l.91 \bye ! ==> Fatal error occurred, no output PDF file produced Changing the output routine to '\output{}' only changes the "stack trace". (D) creates some strange output: 012345678901234567890123456789 012345678901234567890123456789 0 12345678901234567890123456789 012345678901234567890123456789 It seems that texio.write does not reset its internal line length counter then writing a "\n". Also, there is a leading space for some reason. BTW: Is it possible to add a function which does not wrap after 80 characters? Or maybe the wrapping is completely obsolete (though I am not sure about tracing TeX code). Another weird thing: The Latin Modern font contains ligatures, but they are not put inside a "ligatures" table. Example: "f" (simple output of the fontforge glyph table using code from the Lua wiki): [{boundingbox={33,0,357,705},kerns={{char="quotedblright.cm",off=28,lookup="pp_ l_1_s"},{char="quotedblleft.cm",off=28,lookup="pp_l_1_s"},{char="quotedblright" ,off=28,lookup="pp_l_1_s"},{char="quotedblleft",off=28,lookup="pp_l_1_s"},{char ="quoteright",off=28,lookup="pp_l_1_s"},{char="quoteleft",off=28,lookup="pp_l_1 _s"},{char="bracketright",off=28,lookup="pp_l_1_s"},{char="question",off=28,loo kup="pp_l_1_s"},{char="parenright",off=28,lookup="pp_l_1_s"},{char="exclam",off =28,lookup="pp_l_1_s"}},name="f",unicodeenc=102,width=306}] "f" contains a "fi" ligature: [{lookups={ls_l_10_s={{type="ligature",specification={char="f_i",components="f i"}}}},boundingbox={27,0,527,705},name="f_i",unicodeenc=64257,width=556}] But this ligature is not associated with the "f" letter in any way. Is this a bug in the font? In LuaTeX? In the manual? I installed the font in OS X 10.4 and used it in TextEdit (which supports OpenType ligatures), and fi and other ligatures were inserted correctly. So I would guess that the font is OK. The font's version is 1.010. And finally: "design_size" vs. "designsize" ...
Arthur
Jonathan