|Summary:||Errors in ligatures and more in Regular (Book) and Bold for DejaVu Serif and DejaVu Serif 2.32|
|Component:||General||Assignee:||Deja Vu bugs <dejavu-bugs>|
|Status:||RESOLVED NOTOURBUG||QA Contact:|
|i915 platform:||i915 features:|
|Attachments:||Incorrect ligatures and more in PDF made by XeTeX|
Description Pander 2011-02-07 07:41:24 UTC
Created attachment 43032 [details] Incorrect ligatures and more in PDF made by XeTeX I have found errors in ligatures, punctuation marks and euro sign in Regular (Book) and Bold for both DejaVu Serif and DejaVu Serif 2.32. Apart from all other files in 2.32, these four files have version incorrectly version number 2.31. See attachments how this looks in XeTeX from latest stable TeX Live distribution. In version 2.31, these ligatures, punctuation marks and euro sign in Regular (Book) and Bold for DejaVu Serif and DejaVu Serif work correctly. In version 2.32, these four files have wrong version number and somehow a bug has slipped in. It would be fairly easy to fix this as it worked properly before. Please fix this as soon as possible since (at least) TeX users will not be able to use these 4 font files of version 2.32 correctly.
Comment 1 nocturnaldreamer 2011-02-07 08:10:27 UTC
Hi, please make sure that obsolete font files are removed from your system when you upgrade to another version. If you have different versions of a font, XeTeX has a habit of mixing those up, as evidenced by the wrong version number you are getting. In essence XeTeX looks up the glyph positions in the newer file, but then uses the glyphs from the older file (or vice versa). When characters are added between versions, this results in an offset for every glyph position after the addition. You may want to report this issue to TeX Live. On Windows Vista/7 systems there may be a greater risk of encountering this, as old files are randomly kept in the font folder without the user’s knowledge.
Comment 2 Pander 2011-02-07 13:52:01 UTC
XeTeX with fontspec uses fontconfig. Also ttx from fonttools uses fontconfig to get the (wrong) font file for information. Running fc-cache --force is not enough, one also needs to delete /var/cache/fontconfig/* and reboot. :S Probably because Ubuntu (X.org) is using DejaVu itself, hence does not want to unload it somehow.