[MPEG-OTSPEC] revised B64K glyf table: new tag "LOCX" and "GLYX"

[Hin-Tak Leung]

 Just a comment on uppercase/lowercase: it isn't mentioned anywhere in the spec I believe, but there was some sort of convention / understanding when Microsoft licensed the truetype font scaler code / tech from Apple, that new tables are to be added in upper-cases, while Apple's older tables were all in lower-cases, and Apple may add new tables in lowercases. Hence the current observed patterns of upper/lowercases. I don't know how legally binding that convention is to either party, or to 3rd parties. Maybe Apple/Microsoft folks can comment on this.
That said, how about LOC2 / GLY2? If they are related to loca and glyf ? And if that's the case, why aren't they done in a new/expanded version of those?
    On Wednesday, 27 September 2023 at 03:09:15 BST, suzuki toshiya <mpsuzuki at hiroshima-u.ac.jp> wrote:  
 
 Dear Liam,

You proposed "LOCX" and "GLYX" as the tags for
the new implementations. The tags "LOCX" and
"GLYX" are natural for the proposed extension.
I appreciate.

But according to a header file of GhostScript/GhostPDL,

https://github.com/ArtifexSoftware/ghostpdl/blob/master/devices/gxfcopy.h

I have a concern that "gdir", "locx," and "glyx"
might have been used in some PostScript documents
to emit the TrueType font for the generation of PDF.

Even if "locx" and "glyx" were once used, the
difference between lowercase/uppercase is
sufficient to avoid confusion?

I wish Adobe experts could check whether old
versions of AdobePS printer drivers used them
for their internal use.

Regards,
mpsuzuki
_______________________________________________
mpeg-otspec mailing list
mpeg-otspec at lists.aau.at
https://lists.aau.at/mailman/listinfo/mpeg-otspec
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20230927/4decf679/attachment.html>