On 5/25/2019 9:46 PM, Herbert Voss wrote:
I had a problem with the fontloader and luatex.
I tried to run my test document with context
(latest minimal) to compare the output, but I failed.
The font LibertinusKeyboard-Regular.otf
https://ctan.org/tex-archive/fonts/libertinus-fonts/
uses
Am Sat, 25 May 2019 21:46:46 +0200 schrieb Herbert Voss:
> The font LibertinusKeyboard-Regular.otf
> https://ctan.org/tex-archive/fonts/libertinus-fonts/
> uses ligatures especially for the keys above 0x
> However, I cannot get it run with latest mkiv.
as was noticed by Zauguin in
I had a problem with the fontloader and luatex.
I tried to run my test document with context
(latest minimal) to compare the output, but I failed.
The font LibertinusKeyboard-Regular.otf
https://ctan.org/tex-archive/fonts/libertinus-fonts/
uses ligatures especially for the keys above 0x
Am Fri, 11 Jan 2019 22:51:30 +0100 schrieb Hans Hagen:
> afaiks it's ok for luatex 1.09+
Oh, good tipp. You are right with luatex 1.09 it compiles fine.
That means that I don't need to debug but should stick to the state
of 2018-12-19 until texlive 2019 comes out.
--
Ulrike Fischer
On 1/11/2019 8:23 PM, Ulrike Fischer wrote:
Am Thu, 10 Jan 2019 17:13:26 +0100 schrieb Pablo Rodriguez:
On 1/7/19 12:40 AM, Ulrike Fischer wrote:
I just tried to import the fontloader from 2019-01-03 into latex,
and get on a simple document the error
(./test-utf8.aux)error:
Am Thu, 10 Jan 2019 17:13:26 +0100 schrieb Pablo Rodriguez:
> On 1/7/19 12:40 AM, Ulrike Fischer wrote:
>> I just tried to import the fontloader from 2019-01-03 into latex,
>> and get on a simple document the error
>>
>> (./test-utf8.aux)error:
>>
On 1/10/2019 5:13 PM, Pablo Rodriguez wrote:
This was the same problem that prevented the compilation of the
following code:
\setupdirections[bidi=on, method=two]
\starttext
\input zapf
\stoptext
this is unlikely as you don't use generic ... probably another fix
On 1/7/19 12:40 AM, Ulrike Fischer wrote:
> I just tried to import the fontloader from 2019-01-03 into latex,
> and get on a simple document the error
>
> (./test-utf8.aux)error:
> ...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868:
> attempt to call upvalue 'getdirection' (a nil
I just tried to import the fontloader from 2019-01-03 into latex,
and get on a simple document the error
(./test-utf8.aux)error:
...ad/texmf/tex/luatex/luaotfload/fontloader-2019-01-03.lua:23868:
attempt to call upvalue 'getdirection' (a nil value)
.
\newpage ...k \@nobreakfalse \everypar {}\fi
Am Sat, 18 Aug 2018 13:47:32 +0200 schrieb Hans Hagen:
>> On the luaotfload tracker was a bug report that the loading of a
>> font failed if too many character variant were requested
>>
>> https://github.com/lualatex/luaotfload/issues/424
>>
>> I wanted to check if the problem still exist with
On 8/18/2018 1:17 PM, Ulrike Fischer wrote:
On the luaotfload tracker was a bug report that the loading of a
font failed if too many character variant were requested
https://github.com/lualatex/luaotfload/issues/424
I wanted to check if the problem still exist with a current
fontloader. Here
On the luaotfload tracker was a bug report that the loading of a
font failed if too many character variant were requested
https://github.com/lualatex/luaotfload/issues/424
I wanted to check if the problem still exist with a current
fontloader. Here (both context and latex) the loading of this
·
> On 12/18/2015 7:34 AM, Philipp Gesang wrote:
> > in the old loader, defining a feature containing mixed ligature /
> > substitution causes a crash. Here’s an example:
> >
> > \enabletrackers [otf.loading]
> > \startluacode
> >fonts.handlers.otf.addfeature ("dunno", {
On 12/18/2015 7:34 AM, Philipp Gesang wrote:
Hi Hans,
in the old loader, defining a feature containing mixed ligature /
substitution causes a crash. Here’s an example:
\enabletrackers [otf.loading]
\startluacode
fonts.handlers.otf.addfeature ("dunno", {
{
Hi Hans,
in the old loader, defining a feature containing mixed ligature /
substitution causes a crash. Here’s an example:
\enabletrackers [otf.loading]
\startluacode
fonts.handlers.otf.addfeature ("dunno", {
{
type = "substitution",
data
···date: 2014-12-14, Sunday···from: Philipp Gesang···
this bug was reported a while ago by user Thérèse on
tex.stackexchange.com [1]. The font “Eadui.ttf” [2] causes the
fontloader to access a nil value because the “Anchor-1” table is
sparse (nil at index 3). Test file for Context:
On 12/15/2014 8:08 AM, Philipp Gesang wrote:
Good morning!
This report by Github user SverreStausland has been lingering on
the Luaotfload tracker for a while: There appears to be a
difference between how certain faces of the Libertine family
handle the placement of diacritics.
With Version
···date: 2014-12-15, Monday···from: Hans Hagen···
On 12/15/2014 8:08 AM, Philipp Gesang wrote:
Good morning!
This report by Github user SverreStausland has been lingering on
the Luaotfload tracker for a while: There appears to be a
difference between how certain faces of the Libertine
Am 15.12.2014 um 21:43 schrieb Philipp Gesang:
\enabletrackers[otf.bugs]
Thanks for the reply and for the pointer. That tracker is indeed
pretty handy!
I attempted to open a bug report on the Libertine tracker but
Sourceforge refuses to cooperate :/ Maybe next time.
As far as I know there
···date: 2014-12-15, Monday···from: Herbert Voss···
Am 15.12.2014 um 21:43 schrieb Philipp Gesang:
\enabletrackers[otf.bugs]
Thanks for the reply and for the pointer. That tracker is indeed
pretty handy!
I attempted to open a bug report on the Libertine tracker but
Sourceforge
···date: 2014-12-14, Sunday···from: Hans Hagen···
On 12/14/2014 2:45 PM, Philipp Gesang wrote:
Hi Hans,
from the huge changeset two weeks ago:
+texio.write_nl(The font code has been brought in sync with the
context version of 2014.12.01 so)
+texio.write_nl(if things
Hi Hans,
from the huge changeset two weeks ago:
+texio.write_nl(The font code has been brought in sync with the context
version of 2014.12.01 so)
+texio.write_nl(if things don't work out as expected the interfacing
needs to be checked. When)
-- Message received ;) First off, thanks
On 12/14/2014 2:45 PM, Philipp Gesang wrote:
Hi Hans,
from the huge changeset two weeks ago:
+texio.write_nl(The font code has been brought in sync with the context
version of 2014.12.01 so)
+texio.write_nl(if things don't work out as expected the interfacing needs to
be checked.
Hi Hans,
this bug was reported a while ago by user Thérèse on
tex.stackexchange.com [1]. The font “Eadui.ttf” [2] causes the
fontloader to access a nil value because the “Anchor-1” table is
sparse (nil at index 3). Test file for Context:
Good morning!
This report by Github user SverreStausland has been lingering on
the Luaotfload tracker for a while: There appears to be a
difference between how certain faces of the Libertine family
handle the placement of diacritics.
With Version 5.1.2 of the family [0], the RZI version
Hi Hans,
when combining e.g. certain number substitutions like onum and
pnum or tnum and lnum, node mode seems to work fine. However,
those do have value in math mode as well which node mode does not
currently support. For comparison, here is a test file:
On 4/5/2014 4:37 PM, Philipp Gesang wrote:
Hi Hans,
when combining e.g. certain number substitutions like onum and
pnum or tnum and lnum, node mode seems to work fine. However,
those do have value in math mode as well which node mode does not
currently support. For comparison, here is a test
···date: 2014-04-05, Saturday···from: Hans Hagen···
On 4/5/2014 4:37 PM, Philipp Gesang wrote:
Hi Hans,
when combining e.g. certain number substitutions like onum and
pnum or tnum and lnum, node mode seems to work fine. However,
those do have value in math mode as well which node mode
On 4/5/2014 9:58 PM, Philipp Gesang wrote:
···date: 2014-04-05, Saturday···from: Hans Hagen···
On 4/5/2014 4:37 PM, Philipp Gesang wrote:
Hi Hans,
when combining e.g. certain number substitutions like onum and
pnum or tnum and lnum, node mode seems to work fine. However,
those do have value
···date: 2013-06-28, Friday···from: Akira Kakuto···
Hi Philipp,
I’ve traced it to luatex-basics-gen.lua.
luaotfload-basics-gen.lua and luaotfload-merged.lua?
The latter is generated from the former, so yes. For a hot fix it
suffices to patch the merged file. Anyways, luaotfload will be
On 6/28/2013 1:12 PM, Philipp Gesang wrote:
···date: 2013-06-28, Friday···from: Akira Kakuto···
Hi Philipp,
I’ve traced it to luatex-basics-gen.lua.
luaotfload-basics-gen.lua and luaotfload-merged.lua?
The latter is generated from the former, so yes. For a hot fix it
suffices to patch
Hi Hans,
this has been reported by Dohyun Kim [1]: the generic fontloader
(not Context) serializes some tounicode values as Lua numbers,
not strings. When re-reading the cache file the values lose all
leading zeros, so they are no longer well-formed UTF-16BE.
...
[tounicode]={
···date: 2013-06-27, Thursday···from: Philipp Gesang···
Hi Hans,
this has been reported by Dohyun Kim [1]: the generic fontloader
(not Context) serializes some tounicode values as Lua numbers,
not strings. When re-reading the cache file the values lose all
leading zeros, so they are no
Hi Philipp,
I’ve traced it to luatex-basics-gen.lua.
luaotfload-basics-gen.lua and luaotfload-merged.lua?
Thank you very much.
Akira
___
If your question is of interest to others as well, please add an entry to
On 5/3/2013 9:04 PM, Philipp Gesang wrote:
Hi,
loading this font:
https://collab.itc.virginia.edu/access/content/group/26a34146-33a6-48ce-001e-f16ce7908a6a/Tibetan%20fonts/Tibetan%20Unicode%20Fonts/TibetanMachineUnicodeFont.zip
causes the fontloader to emit a dozen or so messages of the
Hi,
loading this font:
https://collab.itc.virginia.edu/access/content/group/26a34146-33a6-48ce-001e-f16ce7908a6a/Tibetan%20fonts/Tibetan%20Unicode%20Fonts/TibetanMachineUnicodeFont.zip
causes the fontloader to emit a dozen or so messages of the kind
fontsloading can't
36 matches
Mail list logo
