Update to lxgw-fonts

This is just to thank the TeX Live team for the update of lxgw-fonts a few hours ago.

Earlier yesterday LuaLaTeX could no longer build its font database: the database started to be built in the console, nothing happened for minutes, and then suddenly the process was killed. Running "luaotfload --update --force" on the command line got the same result.

Switching to "luaotfload-tool --update --force --verbose=4" revealed what was happening: luaotfload-tool halted when processing the lxgw fonts, spent minutes (about 5 or 6, maybe) on the first, moved on to the second, then the process was killed:

luaotfload | db : Loading font /usr/local/texlive/2026/texmf-dist/fonts/truetype/public/ektype-tanka/Mukta-Regular.ttf
luaotfload | db : Loading font /usr/local/texlive/2026/texmf-dist/fonts/truetype/public/ektype-tanka/Baloo2-ExtraBold.ttf
luaotfload | db : Loading font /usr/local/texlive/2026/texmf-dist/fonts/truetype/public/lxgw-fonts/LXGWNeoXiHeiScreen.ttf
luaotfload | db : Loading font /usr/local/texlive/2026/texmf-dist/fonts/truetype/public/lxgw-fonts/LXGWNeoXiHei.ttf
zsh: killed     luaotfload-tool --update --force --verbose=4

Indeed, the lxgw fonts couldn't be displayed in the macOS Finder nor opened in Font Book. FontForge couldn't open them either, reporting several faulty tables and ending up with

Couldn't find a font file named/usr/local/texlive/2026/texmf-dist/fonts/truetype/public/Ixgw-fonts/LXGWNeoXiHeiScreen.ttf

Whatever the problem was (introduced by a font update on March 23), the new update a few hours ago corrects it:

https://svn.tug.org:8369/texlive?revision=78500&view=revision

So thanks Karl for solving the problem!

Bruno Voisin