> no, it probably went wrong when i merged some extra data in the file
> (and in the process hex'd the numbers); nothing to wory about
OK, good to know then.
> (btw, by now table.serialize is pretty stable)
Oh, I didn't mean to despise it; I love it and I use it all the time!
Arthu
Arthur Reutenauer wrote:
> Looks nicer now :-)
>
> By the way, was there a bug in table.serialize or some other
> “public” function? Something to worry about?
no, it probably went wrong when i merged some extra data in the file
(and in the process hex'd the numbers); nothing to wory about
Looks nicer now :-)
By the way, was there a bug in table.serialize or some other
“public” function? Something to worry about?
Arthur
___
dev-context mailing list
dev-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/dev-context
ok, new beta ...
-
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
Arthur Reutenauer wrote:
>> So: ["adobename"]="afii0x2732", "instead of" afii10034.
>>
>> What do you suggest? I guess that adobename might need to have
>> multiple entries anyway.
>
> Obviously, the decimal number 10034 has been abusively transformed
> into its hexadecimal equivalent, I guess
> So: ["adobename"]="afii0x2732", "instead of" afii10034.
>
> What do you suggest? I guess that adobename might need to have
> multiple entries anyway.
Obviously, the decimal number 10034 has been abusively transformed
into its hexadecimal equivalent, I guess by table.serialize or something
s
Hello Hans,
According to AGLFN at
http://partners.adobe.com/public/developer/en/opentype/aglfn13.txt
consider for example the glyph
0420;afii10034;CYRILLIC CAPITAL LETTER ER
in char-def.lua you have
[0x0420]={
["adobename"]="afii0x2732",
["category"]="lu",
["cjkwd"]="a",
["cont
