Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 28 users
Status: Fixed
Closed: Dec 2011
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature

  • Only users with EditIssue permission may comment.

Sign in to add a comment
Layout tables in remote fonts (@font-face) are not supported
Project Member Reported by, Nov 9 2009 Back to list
Current version of OTS library ( does not support 
GSUB and GDEF tables of OpenType.

We might have to support these tables if we want to use @font-face for 
complex scripts.

Labels: Mstone-5
We should support GPOS, jstf, base, and mort as well.

Summary: Layout tables in remote fonts (@font-face) are not supported (was: NULL)
Labels: I18N
Comment 4 by, Nov 11 2009
See also  bug 27131  (for kern and gsub tables). GSUB is also required for complex 
Comment 5 by, Nov 11 2009
Yusuke, can you update your design doc ( )? 
Both GSUB and GPOS (as well as other tables) are necessary for complex scripts like 
Indic, Thai and Arabic. Currently, the design doc makes it look like GPOS is only for 
kerning. Thank you !


BTW, I've added you (and agl) to the owner list of the project. Please feel free to 
edit the doc if needed.

Comment 7 by, Nov 24 2009
Thank you, Yusuke. 

W3C has some tests for this.

I'll add this to the OTS design doc somewhere. 

Labels: -Mstone-5 Mstone-6
Discussed with Jungshik about the priority of this issue offline. Let me change the 
Mstone label from 5 to 6.

Labels: -Mstone-6 Mstone-7
Comment 10 by, Jul 23 2010
I created another test case, here:

Another important table to support is morx, as it is present in the Hanuman font:

morx checksum=11beabd4 actual=11beabd4 diff=0 offset=231036 len=77136

Thank you for putting up test cases.  Do you have any idea what to do about "validating" morx tables (if possible)? 
Labels: -Area-Misc Area-WebKit
I don't have specific information about the morx table beyond what's in the documentation. This is a good general resource.

It's also described in fairly good detail in Appendix D.13.2 of Haralambous's book, "Fonts & Encodings".

We're about to launch the first round of international fonts in the Google Font API, and this bug is causing a raft of issues with specific fonts. This will increase the visibility of breakage by quite a bit. Please let us know if there's something we can do to move this bug along.

Labels: -Mstone-7 Mstone-8
Bulk moving to mstone 8, at this point work on m7 should effectively be closed.  If something in this bulk edit is not actively being worked on, please change the mstone to m9.
Labels: -Mstone-8 Mstone-9
Since we are passed the branch, moving all mstone-8 issues to mstone-9 for triage/punting
Comment 16 by, Oct 22 2010
Comment 17 by, Oct 26 2010
 Issue 57111  has been merged into this issue.
Issue 58058 has been merged into this issue.
Labels: -mstone-9 Mstone-10
Given our current velocity, we need to punt 500 bugs from m9.  Moving p2 bugs, that are not started and have an owner, to the next milestone.  If this issue absolutely needs to be fixed in the current milestone please move it back, however, at this time the focus should be on p1 bugs.
Comment 20 by, Dec 9 2010
Labels: -Mstone-10 MovedFrom-10 Mstone-11
P2 bugs with an owner that are not marked as started are being automatically moved to mstone:11.
Comment 21 by Deleted ...@, Dec 14 2010
There are variants of the Latin script that require GSUB for ligatures. German in fraktur (de-Latf) needs the ligatures ch, ck, ſt and tz, as can be verified in the Duden book, the authoritative reference on German orthography.

I have made a small testcase:
Comment 22 by, Dec 15 2010

Can you take over this bug from Yusuke-san?
(The owner must be Hence assigned this to myself for now.)
Comment 23 by, Dec 15 2010

Sure. I'll take this.
ISSUE-9: OpenType feature preservation

"The automatic removal of OpenType features such as GPOS and GSUB information at any stage in the process of deploying a WOFF file is strongly discouraged. Many writing systems around the world rely on these features for very basic display of text in the script that they use."

"I would also add that this issue is related to security, the user agent (Chrome) you're concerned about is not doing this for arbitrary reasons, those tables are removed because of concerns over the possibility of exploits in system libraries on various platforms."

Comment 25 by, Dec 30 2010
Having the same problem with GSUB glyphs that concatenate characters with @font-face Urdu font.  All stand-alone glyphs render OK, but glyph substitution does not happen.  Testing on 8.0.552.224 (68599) Ubuntu 10.10.

 Issue 74537  has been merged into this issue.
Comment 28 by, Mar 9 2011
Labels: -Mstone-11 MovedFrom-11 Mstone-12
rolling non releaseblocker mstone 11 bugs to mstone 12. 
Comment 29 by, Mar 21 2011
This bug is 2 years old. It breaks webfonts for Arabic, Thai and Indic languages. We have open-source fonts for these languages that chromium users cannot use as webfonts. Arabic has been one the top 10 languages on the web for a while now:
Status: Started
Please update this bug as well. If I understand correctly, you've finished implementing most of the layout table parsers for OTS.

Comment 31 by, Mar 23 2011

Thank you pinging me. I forgot to update this bug. I've implemented GDEF/GSUB/GPOS support to OTS.  It's not in Chromium yet but it will be in soon.
Good news :)
can we expect this to be fixed in the next release ? 
I have a test case here for WOFF font with Malayalam script(indic, complex script).
 Issue 78155  has been merged into this issue.
Comment 35 by, Apr 25 2011
Labels: Mstone13 MovedFrom12
Moving out of M12.
Comment 36 by, Apr 25 2011
Labels: -Mstone-12 Mstone-13
Moving out of M12.
Layout tables are supported in r57 or later and r62 is already rolled into latest Chromium. What's left?
Comment 38 by, May 26 2011
 Issue 64735  has been merged into this issue.
Labels: -Mstone-13 Mstone-14 MovedFrom13
Moving !type=meta|regression and !releaseblocker to next mstone
Labels: -MovedFrom12 MovedFrom-12
Comment 41 by, Jul 28 2011
Labels: -Mstone-14 Mstone-15 MovedFrom-14
Punting out non-critical bugs.  Please move back to 14 if you believe this was done in error.
Comment 42 by, Sep 8 2011
Labels: Mstone-16 MovedFrom15 bulkmove
moving non-essential bugs from 15 to 16. Please feel free to move back if this is an error and your bug is a blocker for 15.
Comment 43 by, Oct 24 2011
Labels: -Mstone-16 MovedFrom-16 Mstone-17
Comment 44 by, Dec 19 2011
Labels: -Mstone-17 Mstone-18 MovedFrom-17
Moving bugs marked as Started but not blockers from M17 to M18.  Please move back if you think this is a blocker, and add the ReleaseBlock-Stable label.  If you're able.
Comment 45 by, Dec 19 2011
Status: Fixed
OTS now support OpenType layout tables. 
Project Member Comment 46 by, Oct 13 2012
Labels: Restrict-AddIssueComment-Commit
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 47 by, Mar 10 2013
Labels: -Area-WebKit -Mstone-18 Cr-Content M-18
Project Member Comment 48 by, Mar 13 2013
Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Project Member Comment 49 by, Apr 6 2013
Labels: -Cr-Content Cr-Blink
Sign in to add a comment