-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Can't get ligatures to work. #19
Comments
Looked at it some more. From the code, I see that tracking != 0 will turn ligatures off. I tried that, but still no go. Then I debugged and found that the "source sans pro" version provided with the project doesn't seem to have ligatures. Actually, if I'm interpreting the font.txt format correctly none of the fonts have ligatures. Ligatures would be at the end of the filed, preceded by '3', right? |
It depends if the characters are exported. Ligatures bloat the font about 3x in some cases so we defaulted to not exporting them. It add them, export the font with /tools/font export/Characters.py uncomment the ligatures you want added. Once the txt font contains then, they will work. Get Outlook for iOS On Wed, May 11, 2016 at 10:55 PM -0700, "casperno" notifications@github.com wrote: Looked at it some more. From the code, I see that tracking != 0 will turn ligatures off. I tried that, but still no go. Then I debugged and found that the "source sans pro" version provided with the project doesn't seem to have ligatures. Actually, if I'm interpreting the font.txt format correctly none of the fonts have ligatures. Ligatures would be at the end of the filed, preceded by '3', right? — |
Got it. Only real issue remaining is that the ligature example (http://txtjs.com/examples/Text/ligatures.html) doesn't have ligatures. So when you created all the font.txt files this repo, you left ligatures commented out? I'm a bit unsure to how ligatures can triple the font size — usually there's just a handful of them. Or maybe 'ligatures' cover more glyphs than the traditional "fi" etc. I associate them with. |
Ah... I updated the export a while back and must have exported without ligatures. The file size factor depends on the source font, some contain hundreds of ligatures and sometimes many duplicates where style was slightly different. Then again we were dealing with fonts for print design so that made the issue worse. Exported font for Bickham Script with ligatures was 370kb, ligatures removed 120kb Get Outlook for iOS
From: casperno notifications@github.com Got it. Only real issue remaining is that the ligature example (http://txtjs.com/examples/Text/ligatures.html) doesn't have ligatures. So when you created all the font.txt files this repo, you left ligatures commented out? I'm a bit unsure to how ligatures can triple the font size — usually there's just a handful of them. Or maybe 'ligatures' cover more glyphs than the traditional "fi" etc. I associate them with. — |
Export Lobster with ligatures See diverted247#19 See ReCreateJS#5
Testing with
source sans pro has ft and ff ligatures, but they don't seem to work with this example.
The font in the samle (http://txtjs.com/examples/Text/ligatures.html) doesn't seem to have ligatures at all.
The text was updated successfully, but these errors were encountered: