Unifont - Support: sr #108585, WOFF output scripts
You are not allowed to post comments on this tracker with your current authentication level.
sr #108585: WOFF output scripts
Submitter: | None | ||
Submitted: | Wed 28 May 2014 02:32:12 AM UTC | ||
Category: | None | Priority: | 5 - Normal |
Severity: | 1 - Wish | Status: | Postponed |
Privacy: | Public | Assigned to: | unifoundry |
Originator Email: | -email is unavailable- | Open/Closed: | Open |
Operating System: | None |
Thu 29 May 2014 05:30:18 AM UTC, comment #1: |
Paul Hardy <unifoundry>![]() ![]() |
Wed 28 May 2014 02:32:12 AM UTC, original submission:
I don't know much about font formats, but I was able to produce WOFF output files with this patch, which copies the ttf targets and replaces "ttf" with "woff". The resulting font works for me as a web font in Firefox 24, whereas the TTF font doesn't (the TTF gives the POST table error described at https://savannah.gnu.org/projects/unifont under "20 November 2013"). |
Anonymous |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-05-29 | unifoundry | Status | None | ![]() |
Postponed |
Assigned to | None | ![]() |
unifoundry | ||
2014-05-28 | None | Attached File | - | ![]() |
Added 0001-Build-WOFF-files.patch, #31459 |
Powered by Savane 3.12.
Corresponding source code
Thanks for submitting this suggestion! I plan to look at introducing the WOFF and hopefully related formats (EOT, SVG) after the upcoming Stable release of Debian 8.0. I expect there to be some issues with introducing those font formats, and I have to educate myself better on them. For example, I think Fontforge requires a certain PNG library and the Zlib library to be part of the Fontforge build; otherwise the WOFF output won't work. So I have to look at where that conversion might succeed and where it might fail. Hence the anticipated problems. This is on my radar though.
If anyone else reading this has expertise with such TrueType to Web font conversions, please let me know.