gmane.comp.tex.lualatex.devel

Re: luaotfload v2.2 cannot load system font

Philipp Gesang — 2013-05-18T07:08:09

Dear Akira, others,

···<date: 2013-05-18, Saturday>···<from: Akira Kakuto>···


Hans agreed to have the fontloader create the cache directory if
it doesn’t exist. The code will be part of today’s upload.

Best regards
Philipp

Re: luaotfload v2.2 cannot load system font

Akira Kakuto — 2013-05-18T02:17:24

Hi,


Please ignore the test.diff, which is apparently wrong.
Sorry for the noise.

Best regards,
Akira KAKUTO

luaotfload v2.2 cannot load system font

Akira Kakuto — 2013-05-18T01:59:36

Try the attached test.diff.
Pardon me if the test.diff is wrong.

Best regards,
Akira KAKUTO

luaotfload v2.2 cannot load system font

Bill Sun — 2013-05-16T21:21:03

Hi,

I updated my texlive 2013 pretest on May 14, and luaotfload was updated
to v2.2 (2013/05/10). After the update, no matter I use fontspec or
luaotfload package in the preamble, lualatex cannot load system font.
Both produce the same error message.

System info:
texlive 2013 pretest, last update on May 16. Archlinux x86_64.

Here's the error message:
    ! LuaTeX error .../texlive/texmf-dist/tex/luatex/luaotfload/luaotfload.lua:85: a
    ttempt to index global 'dir' (a nil value)
    stack traceback:
            .../texlive/texmf-dist/tex/luatex/luaotfload/luaotfload.lua:85: in main chunk
            [C]: in function 'require'
            ...pt/texlive/texmf-dist/tex/luatex/luatexbase/modutils.lua:57: in function 're
    quire_module'
            [string "\directlua "]:1: in main chunk.
    \lltxb< at >requirelua ...xluaescapestring {#2}" \fi )}

    l.41 \fi

Regards.

Re: Conflict with Miktex and the new oberdiek.luatex.lua

Ulrike Fischer — 2013-05-16T13:56:30

Am Thu, 16 May 2013 15:31:20 +0200 schrieb Élie Roux:


Well yes, everyone can easily attach a tree. On the other side
texlive-dist is a very large tree, it will be searched before the
main tree of miktex and miktex will see everything: ini-files,
updmap.cfg etc. So this can affect formats, scripts, documentation,
font maps files ...  

So I don't think it is a good idea to add this tree permantly to
miktex. But for tests it is fine.

But I have other trees with local files which I added to both
systems and use with both systems. This works fine. - But it is much
more confortable to add and remove a tree in miktex then in TeXLive.
I simply call initexmf --register-root=path/to/root and initexmf
--unregister-root=path/to/root.


As polyglossia until now didn't work for luatex at all I would say
that's not so problematic.

Re: Conflict with Miktex and the new oberdiek.luatex.lua

Élie Roux — 2013-05-16T13:31:20

 >

Sure. Actually I thought I did this kind of test, but I didn't (maybe I 
sent Karl the wrong version)... Anyway, the other files shouldn't pose 
problems with old binaries, only this one. Maybe your version should be 
uploaded to MikTeX? Also, I was wondering: is what you're doing (taking 
texlive tree with MikTeX binary) something others might do?

By the way, polyglossia won't work for French with LuaTeX < 0.76 
(because of node.end_of_math()).

Thank you,

Re: Conflict with Miktex and the new oberdiek.luatex.lua

Ulrike Fischer — 2013-05-16T13:14:10

Am Thu, 16 May 2013 12:16:35 +0200 schrieb Élie Roux:


Sure. But on the other side if you patch a file it doesn't do any
harm to patch it in a way that works with more then one version.
After all it is quite possible that some of the developers will need
to run tests with older binaries. 


I have now added temporarly a test to my version of the file

if tex.luatexversion < 76
 then
 table.insert(package.loaders, kpse_module_loader)
 else
 table.insert(package.searchers, kpse_module_loader)
end

 

I will keep this in mind in case I run into some error. Until then I
will left them unchanged.

Re: Conflict with Miktex and the new oberdiek.luatex.lua

Élie Roux — 2013-05-16T10:16:35

Dear Ulrike,

Sadly, we are not in charge of the oberdiek bundle. We provided a patch 
for it to work in TeXLive 2013 because Heiko was not responding and it 
was a blocking issue for TeXLive 2013 pretest, but this should 
definitely be reported to the author. I don't think it's our or 
TeXLive's responsibility to provide patches for oberdiek bundle or for 
MikTeX... Anyway, you can ask Karl to commit a patch in TeXLive's svn 
for MikTeX compatibility, though it sounds a bit weird, it's up to him 
to decide.

We also provided other patches that might not work with MikTeX, one was 
in pdftexcmds.lua and another in hologo.sty.

Thank you,

Conflict with Miktex and the new oberdiek.luatex.lua

Ulrike Fischer — 2013-05-16T09:25:57

I'm currently trying to do some tests with miktex and the various
new versions of lua-packages to identify potential problems. 

Do this extend I attached  texmf-dist of a current TL2013 pretest to
my miktex system (I love the easy way to attach and remove roots in
miktex ;-)). 

A small document using fontspec then leads to an error. The older
luatex of miktex stumbles over this line in oberdiek.luatex.lua

table.insert(package.searchers, kpse_module_loader)

There is no problem if I change the line to:

table.insert(package.loaders, kpse_module_loader) 

Could some luatex version check been added to this file?

Re: Problems with fontspec and ligatures

Ulrike Fischer — 2013-05-15T09:57:13

Am Wed, 15 May 2013 11:46:34 +0200 schrieb Philipp Gesang:



 

This work. Now fontspec reports

fontspec: script 'latn' exists in font 'LMRoman10-Regular'
fontspec:
feature '-liga' for language 'DFLT' and script 'latn' exists in font
'
LMRoman10-Regular'

(I tried also to enable Ligatures and also with DejaVu Serif and it
work fine too).

Re: Problems with fontspec and ligatures

Philipp Gesang — 2013-05-15T09:46:34

···<Datum: Wednesday, 15. May 2013>···<Von: Ulrike Fischer>···


Indeed. But we have fallbacks, one of which was disabled because
of an unrelated issue. Can you test this file and report back:

    https://raw.github.com/phi-gamma/luaotfload/master/luaotfload-auxiliary.lua

Thank you
Philipp

Problems with fontspec and ligatures

Ulrike Fischer — 2013-05-15T09:16:45

I downloaded today a new luaotfload from the link mentioned in issue
72 as I had this problem too:
https://github.com/lualatex/luaotfload/issues/72

Now if I run this document in a texlive 2013 pretest updated today:

\documentclass{book}
\usepackage{fontspec}
\usepackage{ifluatex}
\begin{document}
\fontspec[Ligatures=NoCommon]{Latin Modern Roman}
off fit fly office baffle

\ifluatex
\font\test="file:lmroman10-regular.otf:mode=node;script=latn;language=DFLT;+liga;"
\test off fit fly office baffle

\font\test="file:lmroman10-regular.otf:mode=node;script=latn;language=DFLT;-liga;"
\test off fit fly office baffle

\font\test="file:lmroman10-regular.otf:mode=node;-liga;"
\test off fit fly office baffle
\fi
\end{document}

I get

Font LatinModernRoman does not contain any OpenType `Script'
information.
...............................................

fontspec warning: "icu-feature-not-exist-in-font"
* 
* OpenType
feature 'Ligatures=NoCommon' (-liga) not available for font
*
'LatinModernRoman' with script '' and l

Re: luaotfload refuses to load bold font of some font family

Stephan Hennig — 2013-05-13T20:45:14

Am 13.05.2013 20:06, schrieb Philipp Gesang:


Works fine with the patch.  Thanks!

Best regards,
Stephan Hennig

Re: luaotfload refuses to load bold font of some font family

Philipp Gesang — 2013-05-13T18:06:40

Hi Stephan,

thanks for the report.

···<Datum: Monday, 13. May 2013>···<Von: Stephan Hennig>···

 
<snip />


Something defines a font by an absolute path, but uses the wrong
lookup for this. As absolute paths contain a “:” on Windows, this
confuses the parser which in turn tries to load the font “d”.

Could you apply below patch to luaotfload-features.lua and report
back?

Thanks
Philipp




diff --git a/luaotfload-features.lua b/luaotfload-features.lua
index e732ed9..af4ef67 100644
--- a/luaotfload-features.lua
+++ b/luaotfload-features.lua
< at >< at > -980,9 +980,8 < at >< at > local subfont           = P"(" * Cg((1 - S"()")^1, "sub") * P")"
 --- top-level rules ---------------------------------------------------
 --- \font\foo=<specification>:<features>
 local features          = Cg(feature_list, "features")
-local specification     = (prefixed + unprefixed)
-                        * subfont^-1
-                        * modifier_list^-1
+local specification     = prefixed * subfont^-1 * modifier_list^-1

Re: luaotfload refuses to load bold font of some font family

Stephan Hennig — 2013-05-13T16:29:43

Am 10.05.2013 10:35, schrieb Stephan Hennig:


The problem is still present after today's update of luaotfload.  New
log file attached.

Best regards,
Stephan Hennig


> luaotfload:  reported to the ConTeXt mailing list.â€

Re: luatexbase and module version

Stephan Hennig — 2013-05-11T18:23:53

Dear Élie,

Am 11.05.2013 18:56, schrieb Élie Roux:


Yes, thanks for the prompt action!

Best regards,
Stephan Hennig

Re: luatexbase and module version

Élie Roux — 2013-05-11T16:56:53

Dear Stephan,

Is https://github.com/lualatex/luatexbase/ ok for you? It should appear 
soon on CTAN.

Thank you,

Re: luatexbase and module version

Élie Roux — 2013-05-11T07:31:59

Dear Stephan,


It's true, the luatexbase modules don't use the module functions. I will 
change it very soon.


There is no valid reason...


No, this is clearly wrong, my bad...

I'll upload a new version today or tomorrow...

Thank you!

Re: luatexbase and module version

Stephan Hennig — 2013-05-10T22:12:12

Am 10.05.2013 20:16, schrieb Philipp Gesang:


Will that change in a future version?



Thanks!

Best regards,
Stephan Hennig

Re: luatexbase and module version

Philipp Gesang — 2013-05-10T18:16:18

···<Datum: Friday, 10. May 2013>···<Von: Stephan Hennig>···


nil signals that there is no entry of this name.


attr doesn’t currently use the interface since it is loaded
before modutils. But you are correct, the version info of
luatexbase should be accessible; I’ll make a tracker item.


Not all version strings have been updated so far.

Best
Philipp

luatexbase and module version

Stephan Hennig — 2013-05-10T16:40:18

Hi,

luatexbase-modutils provides means to test if and what version of a
module is loaded.  I want to test if a certain version of package
luatexbase-attr is loaded, but the attached code returns nil.

Alternatively, I could check if a particular feature foo is present via

  if luatexbase.foo then

instead, but I wonder why applying the interface provided in
luatexbase-modutils to package luatexbase shouldn't work.

BTW, as you can see from the log file, package luatexbase-attr from
luatexbase v0.6 identifies itself as 2011/05/24 v0.4.  I know, there
have indeed been recent changes to luatexbase-attr.  Is that package
version and date intentional?

Best regards,
Stephan Hennig


\listfiles
\documentclass{article}
\usepackage{luatexbase}
\begin{document}
\directlua{
  local v = luatexbase.get_module_version('luatexbase')
  texio.write_nl(tostring(v))
}
\end{document}