question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ttx roundtrip error

See original GitHub issue

fontbakery 0.5.1

   Checking with fontTools.ttx
 * ERROR: Failed with ExpatError: not well-formed (invalid token): line 422637, column 66
           File "/usr/local/lib/python3.6/site-packages/fontbakery/checkrunner.py", line 350, in _exec_check
             for sub_result in result:  # Might raise.
           File "/usr/local/lib/python3.6/site-packages/fontbakery/specifications/general.py", line 718, in com_google_fonts_check_ttx_roundtrip
             f.importXML(font + ".xml")
           File "/usr/local/lib/python3.6/site-packages/fontTools/ttLib/ttFont.py", line 336, in importXML
             reader.read()
           File "/usr/local/lib/python3.6/site-packages/fontTools/misc/xmlReader.py", line 49, in read
             self._parseFile(self.file)
           File "/usr/local/lib/python3.6/site-packages/fontTools/misc/xmlReader.py", line 74, in _parseFile
             parser.Parse(chunk, 0)
         

   Result: ERROR

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
anthrotypecommented, Sep 13, 2018

I was able to reproduce with latest ttx and the ttf file that @laerm0 linked to above. I’ll investigate, thanks.

0reactions
anthrotypecommented, Sep 13, 2018

yeah, for some reason an inline comment in the VTT code contained in one of the TSI tables (TSI3, i think) contains an invalid control character U+000B. This is invalid in XML, so the expat parser chokes. There is an open issue on fonttools about dealing with invalid XML chars: https://github.com/fonttools/fonttools/issues/71

for the time being I would recommend editing the VTT sources and deleting the offending character, which is located at line line 422637, column 66 in my ttx dump (check the expat error message).

Read more comments on GitHub >

github_iconTop Results From Across the Web

Check fonts roundtrip through ttx without any errors/warnings
Given fonttools is used by the GF API, for me anything that doesn't roundtrip through ttx is a major concern, and so in...
Read more >
fontbakery/Lobby
Image above with ttx roundtrip $ mprof run fontbakery check-googlefonts -n -l ERROR ~/Desktop/SourceHanSans-Regular.otf. (ignore the -n -l ERROR args above) ...
Read more >
Amadeus Cryptic Entries Reference Guide
Basic Entries: Round Trip. Round-trip routing, specified dates and times AN11JULMADCPH8A*23AUG2P. Round trip, returning on the same day.
Read more >
python/2113/typefacet/dependencies/FontTools/MetaTools ...
Dump each TT/OT font as a TTX file, compile again to TTF or OTF ... clast Error(Exception): past. def usage(): ... def roundTrip(ttFile1,...
Read more >
Android - Native typeface cannot be made for TTX font
The recommendation on the issue at code.google.com says that you should make your font go through a roundtrip though ttx tools. What that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found