Reputation
5,713
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
20 32
Newest
 Enlightened
Impact
~170k people reached

Jan
25
comment Per line text gradient (ala beeline reader)
@a-feldman This appears to be a Latex document, so AFAIR you need \input{beegradients.tex}. If that fails too, check the path and post a complete error log.
Dec
16
comment LuaLaTeX font loader picks Regular variant from system font repertory but Bold from texmf-local
@jfbu How does Fontspec request those fonts? What does luaotfload-tool report, if you pass it the exact same requests? Which fonts are returned can vary depending on what names a font advertises. Which is why if you care about a certain font file, you should request that font by the file name.
Dec
16
comment LuaLaTeX font loader picks Regular variant from system font repertory but Bold from texmf-local
@jfbu No that’s not the same. The .lua.gz file isn’t even read except when the bytecode version is missing. The font version is irrelevant too: Those version strings are meaningless and there is no way to request a specific version. You can check what font name resolves to which file using luaotfload-tool(1): If that doesn’t match what ends up in your document, set the variable run.definer to info_patch in the config file and observe which fonts Fontspec actually requests. Since you know the exact file names, the best advice is to use them directly.
Dec
16
comment LuaLaTeX font loader picks Regular variant from system font repertory but Bold from texmf-local
@jfbu There is no defined lookup order for file system traversal, nor does Luaotfload prefer any of the recognized file formats: It will return the first entry found. BTW., it doesn’t matter in the case at hand since OTF and TTF are really the same format. If you wish for consistency at the file level, there is no other solution than using file names directly. You might then place those files somewhere under version control along with the rest of the document to ensure the correct version of the file is loaded independently of the machine it’s built on.
Dec
15
awarded  Enlightened
Dec
15
awarded  Nice Answer
Nov
24
comment using a Postscript Type 1 font with fontspec and LuaLaTex on MacOSX
@cfr AFM files are indexed along with the other registered formats when building the names database but not by default. That behavior can be overridden by passing an appropriate --formats=… option to luaotfload-tool or by setting the configuration option. (The reason for not including them by default is that TeX distros ship with tons of Type1 font files that only slow down the loading and are rarely used with Luatex.)
Nov
24
comment using a Postscript Type 1 font with fontspec and LuaLaTex on MacOSX
@cfr Can LuaTeX also make use of the relevant .afm files? -- Yes, that functionality is exposed by means of the function fontloader.apply_afmfile(). Though AFAIR the Luaotfload fontloader does its own AFM parsing and applies them similar to Opentype features. See the source for the gory details.
Nov
24
comment What is “the” LUA root for context packages?
@Sean Allred I’d probably write an answer but this judgemental site claims I’m a robot and won’t let me disprove that by means of a captcha. That issue persists for half a year or so now and I’m not interested in wasting any more time on it.
Nov
24
comment GNU Readline- like history, for the latex terminal shell?
@erreka: I’d love to, I just can’t seem to get the captcha to work in my browser. How nice of them to tell me I don’t pass the robot filter only after I already composed the answer! Unbelievable how much this site has degenerated … Anyways, here’s my post: gist.github.com/anonymous/608858f78efac2133bf0 -- feel free to post it as your own for some free internet points. =)
Nov
24
comment access all characters in an OpenType font with LuaLaTeX
Is there a way to get this to work for font names with spaces? -- Font names or file names? In font names, the spaces don’t matter: along with capitalization they are dropped when the font index is built. (Remember: you need the name: directive to load a font by a name.) For file names it should work, but avoiding spaces in file names is a good idea in general.
Nov
22
awarded  Enlightened
Nov
22
awarded  Nice Answer
Jun
15
comment Parallel text in ConTeXt
You can track the progress of the implementation on the git mirror. TL;DR: Not much appears to have happened. Anyways, you can always ask on the mailing list.
Apr
29
awarded  Yearling
Apr
21
comment Vertical alignment of fonts of different size on same line in ConTeXt
If you intend to present these elements on a separate page, then a makeup would be the obvious approach.
Apr
21
comment Why is \setmainfont case sensitive with XelateX but not with LuaLaTeX?
@Paul Gessler I’m unable to post answers due to the captcha barrier which fails to load, leaving me without any obvious way to prove my humanity to the robots of stackexchange. I guess that’s what you get for relying on a web forum …
Apr
21
comment Colored mainfont with fontspec in a textblock yields to pdf error with LuaLaTex
@Jean-Sébastien Gosselin leave the question for reference, it’s valid just IMO not appropriate for this site. Regarding colorization perhaps start with the luacolor package. It’s specifically geared toward the Luatex engine so it should be one of the best options. I’d recommend searching around for other suggestions especially by the crowd that actually do use Latex ;)
Apr
20
comment Colored mainfont with fontspec in a textblock yields to pdf error with LuaLaTex
I'm voting to close this question as off-topic because it’s something in between a bug report and a feature request for Luaotfload concerning borderline supported functionality ;) The next release will come with a fix.
Apr
20
comment Colored mainfont with fontspec in a textblock yields to pdf error with LuaLaTex
The issue will be addressed in the upcoming release of Luaotfload. Also, as @Ulrike-Fischer rightfully pointed out, the font-based colorization is little more than a hack for compatibility. Please consider using a proper colorization package instead.