5,493 reputation
1630
bio website bitbucket.org/phg
location Golgafrincham
age
visits member for 2 years, 9 months
seen Jan 23 at 22:59

Jan
15
comment Why is \setmainfont case sensitive with XelateX but not with LuaLaTeX?
It is not engine-dependent, just how Luaotfload (and, incidentally, Context) treat things. The rationale is simple: Font names are a horrible mess that will haunt you and your descendants to the fifth generation if you attempt to uncover a system behind them. Since capitalization of identifiers can vary even within a font family, the only sane approach is to eliminate it completely. For info about Luaotfload read texdoc luaotfload and man 1 luaotfload-tool.
Jan
15
comment How to install Luajittex from binary
Also, installing a binary from Context won’t work if in combination with TeX Live since a matching texmf.cnf must be present at compile time. Why don’t you just use the Luajittex binary supplied with your TeX distribution?
Jan
15
comment How to install Luajittex from binary
(tagged luaotfload as its slowness is the main reason why I'm installing this!) -- Have you thought this through? Luaotfload execution time is largely determined by file IO. Font parsing is done by the engine anyways so performance is not going to increase by adding the JIT. Btw. unless you’re from the future I doubt that you already use “Linux 17.1”.
Jan
15
comment Ways to parse JSON in LaTeX?
@Aditya It’s the same code, just not updated as frequently.
Jan
15
comment Why is \setmainfont case sensitive with XelateX but not with LuaLaTeX?
Luaotfload normalizes all names supplied by the font. Apart from lowercasing you can also leave out spaces if you wish.
Dec
27
comment What is “the” LUA root for context packages?
Btw. one of my packages works in Context, Plain, and Latex: bitbucket.org/phg/enigma/src -- I just verified that placing the files in the respective trees under the texmf-local works just fine.
Dec
27
comment What is “the” LUA root for context packages?
Here’s a suggestion for debugging path lookup: First determine where Context stores its file info. Usually this is a directory named luatex-cache/context under the root texmf-cache or texmf-var. Then create a dummy file with a unique name somewhere under your texmf-local/. Now run mtxrun --generate and grep the luatex-cache recursively for the name of the dummy file. If the file was found it will show up in a description of tree contents (luatex-cache/context/<hash>/trees/<hash>.lua). If not, then the location isn’t traversed by Context at all.
Dec
27
comment What is “the” LUA root for context packages?
If the file isn’t found after --generate then perhaps it’s located in the wrong tree? Modules from the Garden usually reside in the texmf-modules, stuff that you install manually goes under texmf-local. That’s assuming you’re using the Minimals, of course. There are certain conventions regarding file locations. Most files of third party modules belong under tex/context/third/${MODULE}/, scripts that are supposed to be called from mtxrun under ./scripts/context/lua/third/${MODULE}, but I don’t think that convention is enforced when doing file lookups.
Dec
25
comment What is “the” LUA root for context packages?
[… continued] Also, Context code rarely calls require() to load packages, usually only for external, non-TeX libs. Instead it’s more idiomatic to use environment.loadluafile() at the Lua end, and \registerctxluafile from TeX.
Dec
25
comment What is “the” LUA root for context packages?
Did you run mtxrun --generate to recreate the filename database? That should make files in the TEXMF available to Context’s lookup routines.
Dec
22
comment Eadui font and luatex
This question appears to be off-topic because it is a bug report. The bug was fixed upstream recently.
Dec
22
comment Eadui font and luatex
There’s an upstream fix now that corrects the sparse table; will be part of next Luaotfload.
Dec
21
comment Using LuaLaTeX and SQLite3
lsqlite3 is a binary module, at least in part. You probably have to set package.cpath as well.
Sep
27
comment Debug log the text returned via tex.sprint() and friends?
Not in all cases. Because of its efficiency, it is idiomatic in Lua to use local references to functions instead of calling them explicitly. Consequently, after a chunk of code (e.g. a .lua file) is loaded those references are fixed and cannot be replaced. Not without resorting to the debug library anyways. You’d have to substitute your wrappers before loading third party code. This should be possible but make sure you get the semantics right. If you intend to use Context it might not work at all because most Lua libraries are loaded before the document gets to execute anything.
Sep
27
comment Debug log the text returned via tex.sprint() and friends?
Why not just use a wrapper that calls print() or io.write() on the strings if some trace flag is set?
Sep
14
comment Replacement(s) for TeX's paragraph builder using LuaTeX
@Aradnix The parbuilder code has been part of Context for quite some time. Just check your TeX distribution for the file node-ltp.lua. Of course, the code is available in the official Git repo as well.
Sep
12
comment Precompiled header with lualatex and unicode-math
@John try updating your Luatex binary. Élie’s fix was applied some time ago. If it still fails afterwards, there might be another bug that should be reported to the devs.
Sep
4
comment Get cell content from a Google doc spreadsheet using LuaTeX
@cjorssen Thanks, fixed. I wonder whether the code still works …
Sep
4
comment About the internals of ConTeXt
@Manuel I don’t know; best ask on meta.tex.stackexchange.com
Sep
3
comment About the internals of ConTeXt
@Manuel The most convenient way to search the list is by downloading the archives at ntg.nl/pipermail/ntg-context and concatenating them into one big mailbox. Then use grep or your MUA at your convenience.