18 May 13:29 2016

### Pre-built format at microtype

Hello,

I just installed TeX Live 2016 pretest and everything seems to be working fine. However, I have a problem with using microtype and a pre-built format. Below I have a minimal test case. Everything works fine if I don't use microtype. LuaLaTeX will give the following error when I uncomment the commented line and try to use microtype:

(/texlive/2016/texmf-dist/tex/latex/microtype/mt-LatinMode
rnRoman.cfg[\directlua]:1: attempt to index global 'microtype' (a nil value)
stack traceback:
[\directlua]:1: in main chunk.
MT <at> ifstreq ...{microtype.if_str_eq([[#1]],[[#2]])}
endcsname
l.105    }

Best regards,
Henrik Mannerström

Command line used to create the format:
lualatex -ini "&lualatex format\dump"

Command line used to (try to) compile document:
lualatex -fmt=format test.tex

Format file 'format.tex':
\documentclass[a4paper]{article}

\usepackage{fontspec}
\setmainfont{Latin Modern Roman}

%\usepackage{microtype}

Document file 'test.tex':
\begin{document}
Hello world!
\end{document}

14 May 17:02 2016

### Removed support of dfont format in luaotfload

With version 2.7, luaotfload has removed support of dfont format. This is mentioned in NEWS

[...]
* Remove support for builtin Fontforge libraries (this includes the PFA,
PFB, DFONT, and feature file readers).

but no explanation is given for why this was removed. Is this given somewhere?

On OS X the usage of dfont format is rapidly receding and apparently replaced by TTC, but still present for
core OS and legacy fonts:

/System/Library/Fonts/Courier.dfont
/System/Library/Fonts/Geneva.dfont
/System/Library/Fonts/Helvetica.dfont
/System/Library/Fonts/HelveticaNeue.dfont
/System/Library/Fonts/Monaco.dfont
/System/Library/Fonts/Times.dfont

Bruno Voisin


2 May 23:10 2016

### luaotfload problem from 4-21 update?

Hello:

I am getting the following error message. It did not appear before today, and immediately appeared after I updated Miktex 2.9 this morning, on a known-good TeX file:

The error appear early, probably as soon as luaotfload reads my font specs. Possibly has something to do with using opentype fonts (such as Adobe Garamond Pro) via fontspec. But as I said, no change other than update of various TeX-related packages.

Robert Allgeyer
California, USA

20 Apr 19:17 2016

### luaotfload requires lowercase filenames, MikTex 2.9 Windows 10

Hi -

Using MikTeX Portable 2.9 on Windows 10. Compiling with LuaLaTeX. This may well be platform-specific.

I have font Cinzel-Regular.otf. This file was obtained from a place other than the TeX distribution, but I assure you that's not the problem. Indeed, if you are going to try the MWE here, it's probably best if you do not have TeX's own Cinzel package installed. I only chose this particular font because you probably have it handy. I first noticed this with proprietary fonts that most others won't have.

I put the font where TeX can find it and update FNDB and formats, also clear prior luatex-cache. Here is a MWE, thanks to Will Robertson (I first raised the issue with him, thinking that the problem was with fontspec):

\documentclass{article}
\begin{document}
{\font\x="[Cinzel-Regular.otf]" at 10pt\x This is Cinzel Regular.}
\end{document}

The above code FAILS. However, if I change
from
"[Cinzel-Regular.otf]"
to
"[cinzel-regular.otf]"
then it WORKS. The only change is font fle name to lowercase. The actual file does have some uppercase in its name, but I did not need to change the font's own file name.

I am a writer (fiction), not mathematics or dissertations. Previously I used pdfLaTeX with otf fonts converted into several PostScript files via LY1 encoding and otftotfm. That's a very long song and dance! Fortunately my font licenses allowed it. Worked great with microtype. Turns out that LuaLaTeX also works well enough with microtype (I do not need the non-working features). Now I can call style sets from within my document, without needing to decompose the fonts. Yaaaaay!

Regards,
Robert Allgeyer
California USA

18 Apr 20:10 2016

### TL2016's luaotfload seemingly unable to access subfonts in either .ttc collections or .dfont suitcases

Hello,

Trying the brand new LuaTeX and luaotfload in TeX Live 2016 on the Mac (using mactex-20160417.pkg from
tlpretest), and after blacklisting LastResort.ttf as documented in various places, it seems
luaotfload-tool cannot analyze properly the various subfonts in .ttc collections or .dfont suitcases,
getting for all these subfonts the data for subfont 0.

For example here is what luaotfload-names.lua.gz in TeX Live 2016 (actually
contains for Times.dfont

{
["basename"]="Times.dfont",
["familyname"]="times",
["fontname"]="timesroman",
["format"]="dfont",
["fullname"]="timesroman",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2020,
["italicangle"]=0,
["location"]="system",
["plainname"]="Times Roman",
["psname"]="timesroman",
["size"]=false,
["splainname"]="timesroman",
["splitstyle"]="roman",
["subfamily"]="regular",
["subfont"]=0,
["version"]="10.0d1e3",
["weight"]=0,
},
{
["basename"]="Times.dfont",
["conflicts"]={
["barename"]=2020,
["basename"]=2020,
},
["familyname"]="times",
["fontname"]="timesroman",
["format"]="dfont",
["fullname"]="timesroman",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2021,
["italicangle"]=0,
["location"]="system",
["plainname"]="Times Roman",
["psname"]="timesroman",
["size"]=false,
["splainname"]="timesroman",
["splitstyle"]="roman",
["subfamily"]="regular",
["subfont"]=1,
["version"]="10.0d1e3",
["weight"]=0,
},
{
["basename"]="Times.dfont",
["conflicts"]={
["barename"]=2020,
["basename"]=2020,
},
["familyname"]="times",
["fontname"]="timesroman",
["format"]="dfont",
["fullname"]="timesroman",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2022,
["italicangle"]=0,
["location"]="system",
["plainname"]="Times Roman",
["psname"]="timesroman",
["size"]=false,
["splainname"]="timesroman",
["splitstyle"]="roman",
["subfamily"]="regular",
["subfont"]=2,
["version"]="10.0d1e3",
["weight"]=0,
},
{
["basename"]="Times.dfont",
["conflicts"]={
["barename"]=2020,
["basename"]=2020,
},
["familyname"]="times",
["fontname"]="timesroman",
["format"]="dfont",
["fullname"]="timesroman",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2023,
["italicangle"]=0,
["location"]="system",
["plainname"]="Times Roman",
["psname"]="timesroman",
["size"]=false,
["splainname"]="timesroman",
["splitstyle"]="roman",
["subfamily"]="regular",
["subfont"]=3,
["version"]="10.0d1e3",
["weight"]=0,
},

and here is what it contained for TeX Live 2015

{
["basename"]="Times.dfont",
["familyname"]="times",
["fontname"]="timesroman",
["format"]="dfont",
["fullname"]="timesroman",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2012,
["italicangle"]=0,
["location"]="system",
["plainname"]="Times Roman",
["psname"]="timesroman",
["size"]=false,
["splainname"]="timesroman",
["splitstyle"]="roman",
["subfamily"]="regular",
["subfont"]=0,
["version"]="10.0d1e3",
["weight"]=0,
},
{
["basename"]="Times.dfont",
["conflicts"]={
["barename"]=2012,
["basename"]=2012,
},
["familyname"]="times",
["fontname"]="timesbold",
["format"]="dfont",
["fullname"]="timesbold",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2013,
["italicangle"]=0,
["location"]="system",
["plainname"]="Times Bold",
["psname"]="timesbold",
["size"]=false,
["splainname"]="timesbold",
["splitstyle"]="bold",
["subfamily"]="bold",
["subfont"]=1,
["version"]="10.0d1e3",
["weight"]=0,
},
{
["basename"]="Times.dfont",
["conflicts"]={
["barename"]=2012,
["basename"]=2012,
},
["familyname"]="times",
["fontname"]="timesitalic",
["format"]="dfont",
["fullname"]="timesitalic",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2014,
["italicangle"]=-15,
["location"]="system",
["plainname"]="Times Italic",
["psname"]="timesitalic",
["size"]=false,
["splainname"]="timesitalic",
["splitstyle"]="italic",
["subfamily"]="italic",
["subfont"]=2,
["version"]="10.0d1e3",
["weight"]=0,
},
{
["basename"]="Times.dfont",
["conflicts"]={
["barename"]=2012,
["basename"]=2012,
},
["familyname"]="times",
["fontname"]="timesbolditalic",
["format"]="dfont",
["fullname"]="timesbolditalic",
["fullpath"]="/System/Library/Fonts/Times.dfont",
["index"]=2015,
["italicangle"]=-15,
["location"]="system",
["plainname"]="Times Bold Italic",
["psname"]="timesbolditalic",
["size"]=false,
["splainname"]="timesbolditalic",
["splitstyle"]="bolditalic",
["subfamily"]="bolditalic",
["subfont"]=3,
["version"]="10.0d1e3",
["weight"]=0,
},

In case that helps, the above was obtained when typesetting a test file calling and displaying samples for
all the built-in fonts of OS X El Capitan (ie 10.11), visible or invisible. The files and output for MacTeX
2015 and 2016 (44 MB zipped) are at

The fonts are loaded directly with the \font primitive in plain LuaTeX (and XeTeX for comparison).

Bruno Voisin
(from the MacTeX technical group)


11 Apr 16:43 2016

### Luatex and multiple pattern files

Dear friends,
I am facing a serious problem with luatex and its policy tho load pattern file only in demand, English excluded.
The synonyms keyword in language.dat.lua contains the list of language names for which a given pattern file is applicable. The analogous hyphennames keyword in polyglossia does more or less the same thing.

But there are language variants that require different hyphenation rules, and therefore different pattern files.

You cannot select the proper hyphenation pattern file with any specific variant of the same language.

The problem is real also in English that has several variant names and pattern files. The gloss-english.ldf is very clear about this: if the variant name involves small changes such as the way of typesetting the current date but does not involve pattern variants, the variant option (english, american, usenglish, US,english) just sets suitable boolean switches (toggles) to do the job; but variants usenglishmax, british, uk, britishmax, australian, newzeland, for example, require different hyphenation pattern files. All these switches are valid for xetex, but are excluded with luatex through such statements as \ifluatex\else...\fi.

Gloss-greek.ldf that does not have any test for checking the luatex engine, has only statements valid for xetex, and if some document containing a specification for the Greek language is typeset with luatex, the various \l <at> *** commands are undefined and the three Greek variants are all equated to nohyphenation.

You know that I am trying to set up Latin to be configured for several variants and I need to use at least three different pattern files for 4 language variants (modern, medieval, classic, liturgical) that do not imply simple typesetting spelling changes. I cannot manage the variant settings for more than modern vs medieval that share the same patterns set, and I cannot select the proper pattern set for classic or liturgical Latin by means of "variant=..." options as it would be natural. I can only specify those variants by means of new individual language names and new gloss-<language>.ldf files. But it is always Latin, simply a different variety. The same would be for English or Greek: it would be the same language with different varieties.

It would be necessary  to have a new keyword for \PolyglosssiaSetup such that specifies one or more different sets of synonyms or hyphen names that allow luatex to load at the beginning of the execution of the .ldf file all the pattern variants, so that the various \l <at> *** language counter values are defined and the same tests valid for xetex produce the same results also with luatex. At least English, Greek, and Latin language description files could be slightly modified  to produce the correct line breaks with any language variety: i recall the language is the same, its spelling, its typographical regulations, its hyphenations rules might be different, bu the language is and remains the same. In TeX jargon these variants are NOT dialects of one mater language.

The luatex policy of not loading pattern file for unused languages remains valid, but at least the same language has available all its own hyphenations variants, even if they are not all used in a given document. There is a little waste of memory, but there is not that huge waste of memory connected to the 80 or so languages handled by xetex and pdftex, that contain all their hashed versions in their format files.

Claudio Beccari
11 Apr 18:32 2015

### Font Names

Howdy,

When typesetting the enclosed demo-document for Lucida OT fonts as distributed by TUG I used to have no
problem. Compiling the document now fails because the fonts Lucida Calligraphy OT' and Lucida
Handwriting OT' are no longer recognized; I've got to use the long names, Lucida Calligraphy OT Italic'
and Lucida Handwriting OT Italic'.

Fully updated TeX Live 2014 under Mac OS X 10.10.3.


Attachment (lucidaot.tex.zip): application/zip, 9 KiB

Good Luck,

Herb Schulz
(herbs2 at mac dot com)


3 Oct 08:43 2014

Hi,

I have two issues concerning some use case using luaotfload package with LuaLaTeX.
The idea is to use TeX system in network multiuser environment with central control.
So, there are no place for using system fonts from different users or different font cache.

Let say (as example):

[db]
scan-system = false

<at>  <at>  -137,6 +137,7  <at>  <at>
db = {
formats     = "otf,ttf,ttc,dfont",
scan_local  = false,
+    scan_system = true,
strip       = true,
update_live = true,
<at>  <at>  -409,6 +410,7  <at>  <at>
end
},
scan_local   = { in_t = boolean_t, },
+    scan_system  = { in_t = boolean_t, },
skip_read    = { in_t = boolean_t, },
strip        = { in_t = boolean_t, },
update_live  = { in_t = boolean_t, },

<at>  <at>  -2851,7 +2851,9  <at>  <at>
local max_fonts = config.luaotfload.db.max_fonts --- XXX revisit for lua 5.3 wrt integers

tableappend (filenames, collect_font_filenames_texmf  ())
-    tableappend (filenames, collect_font_filenames_system ())
+    if config.luaotfload.db.scan_system == true then
+       tableappend (filenames, collect_font_filenames_system ())
+    end
tableappend (filenames, collect_font_filenames_local  ())
end

2. Use only readable font cache (TEXMFCACHE) which can be placed
somewhere on readonly network drive or CD.
Actually we already have configuration possibility in db section "update-live = false",
but the luaotfload package still required writable directory for the cache.
Maybe it it reasonable to drop this requirement then using readonly configuration.

I look forward for any comments or suggestions how to deal with described situation
using current luaotfload package version (v2.5 2014-08-10).

Regards,
Sigitas Tolusis


25 Sep 13:04 2014

### ConTeXt unibidi

Hi List

Has anyone ported ConTeXt unibidi features to plain TeX or LaTeX just
like luaotfload package? About a year ago Philipp Ge­sang gave me some
codes that one could use ConTeXt default method for bidi in LaTeX but
think it would be good to port method two to plain/LaTeX.

Vafa


24 Sep 23:12 2014

### paragraph breaking in lua (node-ltp)

I'm very much interested in playing around with variations of Knuth's
paragraph breaking algorithm.

I recently learned that Taco (I think) did a full reimplementation in
lua that would be perfect for me to do a few experiments.

Unfortunately I'm unable to to make this work e.g., produce a short TeX
file that actually uses the code. Anybody out there who could give a
helping hand?

meteorically I think such code should work with any flavor of TeX (eg
plain) but if there are some reasons that right now it is only possible
to use it with a very specific environment that doesn't matter for what
I'm trying to do ... all I need is something that I can feed paragraph
examples to.

thanks
frank


19 May 14:28 2014

### [luamplib] I can't open file plain.mp'

Hi,
I tried to compile :

\documentclass[a4paper,10pt]{article}

\usepackage{luamplib}

\begin{document}

A%

\begin{mplibcode}

beginfig(1);

fill fullcircle scaled 20;

endfig;

\end{mplibcode}

B\par

\end{document}

but I get :

Module luamplib info: This is MetaPost, Version 1.803

(luamplib)

(luamplib)

(luamplib)

(luamplib) ! I can't open file plain.mp'.

(luamplib) <*> input plain.mp

(luamplib) ;

(luamplib) Please type another input file name

(luamplib) ! Emergency stop.

(luamplib) <*> input plain.mp

(luamplib) ;

(luamplib)

(luamplib)

! LuaTeX error ...texlive/2011/texmf-dist/tex/luatex/luamplib/luamplib.lua:327:

Module luamplib error: unknown, no error, terminal or log messages

stack traceback:

[C]: in function 'error'

...xlive/2011/texmf-dist/tex/luatex/luatexbase/modutils.lua:26: in function 'mo

dule_error_int'

...xlive/2011/texmf-dist/tex/luatex/luatexbase/modutils.lua:49: in function 'er

r'

...texlive/2011/texmf-dist/tex/luatex/luamplib/luamplib.lua:327: in function 'r

eporterror'

...texlive/2011/texmf-dist/tex/luatex/luamplib/luamplib.lua:299: in function 'l

...texlive/2011/texmf-dist/tex/luatex/luamplib/luamplib.lua:661: in function 'm

akeTEXboxes'

[string "\directlua "]:1: in main chunk.

\ltxdomplibcodeindeed ...([===[\reserved <at> a ]===])}

\directlua {luamplib.proce...

l.10 \end{mplibcode}

I didn't find anything on the web.
Can you help me ? Thanks

Gmane