The FreeType Project - Bugs: bug #34896, Can't read BDF files with ENCODING...
You are not allowed to post comments on this tracker with your current authentication level.
bug #34896: Can't read BDF files with ENCODING values larger than 0xFFFF
Submitter: | None | ||
Submitted: | Fri 25 Nov 2011 03:38:23 PM UTC | ||
Severity: | 3 - Normal | Item Group: | None |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.4.9 |
Sun 27 Nov 2011 03:44:14 PM UTC, comment #4: |
Werner LEMBERG <wl>![]() ![]() |
Fri 25 Nov 2011 05:18:03 PM UTC, comment #3: For reasons unknown to me, I can't attach the xz file directly. Strange. Anyway, I've split the file into two parts; please say
|
Werner LEMBERG <wl>![]() ![]() |
Fri 25 Nov 2011 04:59:41 PM UTC, comment #2: I've compressed with `xz -9' instead of bz2, and now the file is only 2.2MByte large, see attachment :-) |
Werner LEMBERG <wl>![]() ![]() |
Fri 25 Nov 2011 03:42:04 PM UTC, comment #1: The system doesn't seem to want to let me attach the SFD file, which is 5.6M bzipped. For the moment it is available at http://ansuz.sooke.bc.ca/temporary/jieub-bt-ps.sfd.bz2 . I can't promise to keep it online indefinitely. |
Anonymous |
Fri 25 Nov 2011 03:38:23 PM UTC, original submission:
If I load the attached SFD font file in FontForge, generate a 100-pixel bitmap version with FontForge's "use FreeType" option selected, and save it as a BDF file, the BDF file (attached) is corrupted, with many glyphs blank or containing ugly artifacts. The problem does not occur if I don't use FontForge's "use FreeType" option when doing the rasterization, or if I compile FontForge without FreeType. Observed with versions 2.3.9 and 2.4.8 of FreeType. It happens identically (not just corruption on both but the SAME corruption on both) on an x86-32 and an x86-64 system.
|
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 10 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2011-11-27 | wl | Planned Release | None | ![]() |
2.4.9 |
2011-11-27 | wl | Status | None | ![]() |
Fixed |
Assigned to | None | ![]() |
wl | ||
Open/Closed | Open | ![]() |
Closed | ||
Summary | Corruption of a BDF file with high-code-point glyphs | ![]() |
Can't read BDF files with ENCODING values larger than 0xFFFF | ||
2011-11-25 | wl | Attached File | - | ![]() |
Added jieub-bt-ps-aa, #24454 |
Attached File | - | ![]() |
Added jieub-bt-ps-ab, #24455 | ||
2011-11-25 | wl | Attached File | - | ![]() |
Added JieubsidaBatangPS.bdf.xz, #24453 |
2011-11-25 | wl | Attached File | #24452 | ![]() |
Removed |
2011-11-25 | None | Attached File | - | ![]() |
Added JieubsidaBatangPS.bdf.bz2, #24452 |
The ENCODING issue is fixed now in the git repository.
Regarding the FontForge problem I can't help, unfortunately.