5,323 reputation
1528
bio website bitbucket.org/phg
location Golgafrincham
age
visits member for 2 years, 4 months
seen 10 hours ago

1d
comment ConTeXt: hyperlinks with special characters
Did you try defining your URLs inside a \startasciimode ... \stopasciimode environment?
2d
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
@Mico Good! However, I just figured out why it was that no kerns showed up, at least for Cambria anyways: I forgot to explicitly request the “latin” script. Sorry for the noise! Here’s an updated test file. Please run it with Optima and/or Hoefler substituted for Cambria in TL 2013 and 2014. If there’s a difference, then we have a reproducible case.
2d
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
@Mico Have you actually run the test file?
2d
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
@Mico I cannot figure out what programs you ran to create the screenshot you've posted, let alone reproduce it on my system. -- I used the Luatex binary from TL 2013 with the most recent fontloader from the Context distribution (the one that’s also in current Luaotfload). The output is the same as with the TL 2014 binary or more recent ones. That refutes your hypothesis that the problem in on the Luatex side. Your other question is an exact duplicate of this one, btw.
Aug
26
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
@Mico I just reproduced the issue with the engine from TL 2013 (version 0.76.0). That rules out an issue with Luatex, including the removal of AAT support. Try it out. As you say, you still have the binaries.
Aug
26
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
@Mico I’m not following you here. How could the removal of AAT support from the engine affect TTC subfont handling in the fontloader? Was the bug introduced with the branch on which Khaled prepared the removal?
Aug
26
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
@Mico Dropping AAT support is a feature and most likely unrelated to the issue at hand. The test file I posted earlier reproduces the bug 1) without Luaotfload and 2) with a regular non-AAT font (Cambria).
Aug
25
comment LuaLaTeX, fontspec, .ttc fonts and kerning (Optima on Mac OS)
Ack, @egreg seems right; here’s a test file: bitbucket.org/phg/lua-la-tex-tests/src/…
Aug
22
comment Practical use of lua
@cfr neither Biber nor Biblatex work with Context, and Bibtex outside of Latex was always a hack. So, yes, it is in fact the new bibliography system, as far as Context is concerned.
Aug
21
comment Is there any way to do a correct word count of a LaTeX document?
You’d have to store it somewhere between TeX runs. Write the result of packagedata.word_count.current_word_count() to some temporary file and re-read it at the start of the next run.
Aug
20
comment Write unit tests for Lua in ConTeXt
Btw. are you aware of the test suite? You might draw inspiration from their approach.
Aug
20
comment Write unit tests for Lua in ConTeXt
What Lua files might one need to include to get the variables? -- For the context namespace this does make only limited sense because it relies on Luatex builtins from the tex namespace only available during a TeX run. Also, don’t waste your time trying to run Context .lua files on a regular Lua interpreter. They make use of many of the Luatex extensions even outside the TeX run. Basically, in order to use the fundamental Lua libraries you can run your scripts with mtxrun directly, for everything more complicated you’re going to have to run Context itself.
Aug
18
comment \LaTeX macro: “Font shape `OT1/LatinModernSans(0)/m/n' undefined”
@Socob: I thought \setmainfont etc. just select the default font and didn't think of it as a "font definition" -- Well, in order to use the font above all you need to define it. So if you have printed text in your document then the statement will result in font definitions. So there is a difference between just loading fontspec and saying \setsansfont{Latin Modern Sans}? -- Possibly. Fontspec’s definitions for LM (see the the file I cited earlier) may differ from a dynamic definition using the \setfoofont macros.
Aug
17
comment \LaTeX macro: “Font shape `OT1/LatinModernSans(0)/m/n' undefined”
doesn't LuaTeX load Latin Modern as a default anyway? Or is it Computer Modern? -- The latter: by default the Luatex formats behave like Pdftex and load only CM in the Type1 version. Fontspec, however, loads the LM fonts with a set of definitions for different optical sizes. (See e.g. cat $(kpsewhich eu2lmr.fd).) There is really no point in defining the font yourself again after loading Fontspec.
Aug
8
comment Eadui font and luatex
Thérèse, @Herbert: Definitely a bug, I’m on it, but if there’s an official fix unfortunately it will take a while.
Aug
5
comment LuaTeX and polyglossia -> Warnings
None that I know of but I can only support the Luatex version in TeX Live as well as the latest SVN trunk. But it’s not that big of a deal: after all, we’re talking about a harmless warning, not an error.
Aug
5
comment LuaTeX and polyglossia -> Warnings
I would like to get rid of those. -- You can get rid of the first one by updating you Luatex engine.
Jul
29
comment æ ø å giving “Package inputenc Error: Keyboard character used is undefined”
@DoomStone Don’t use luainputenc, it’s a compatiblity package for documents with evil encodings. Instead use UTF-8 natively (run the files through iconv(1) if necessary) and load the fontspec package.
Jul
26
comment Arch Linux: fontspec does not find system fonts
That’s an old one and it had the bug you describe. Unfortunately, the TeX packages in most distros are crap and Arch is no exception. You could install a current TeX live yourself, otherwise you will have to wait for the Arch maintainers to catch up.
Jul
26
comment Arch Linux: fontspec does not find system fonts
What version of Luaotfload do you run? You can find out running luaotfload-tool --version. The current version (2.5) should update the font index automatically if a font couldn’t be found, unless you explicitly disabled the updates in the configuration file. In any case it should work on Arch because that’s the platform it is being developed on. If not then you most likely found a bug.