Mailinglist Archive: opensuse-bugs (3349 mails)

< Previous Next >
[Bug 977195] Some Indic fonts have broken bytecode
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 16 May 2016 09:17:02 +0000
  • Message-id: <bug-977195-21960-MX68An7IbK@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=977195
http://bugzilla.suse.com/show_bug.cgi?id=977195#c14

Werner Lemberg <wl@xxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(wl@xxxxxxx) |

--- Comment #14 from Werner Lemberg <wl@xxxxxxx> ---
Looks better, thanks!

Some issues.

. What you currently provide in
http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_42.1/noarch/
is version 20140220-36.1; however, the previous version available from this
repository was 20140220-38.1, which is confusing. You should definitely
provide a more recent version number :-)

. aakar-medium.ttf as distributed in your recent 36.1 package is older! It
identifies itself as 001.100, while 38.1 contains version 0.2 (you can see that
with `ftdump -n'). I suggest that you apply your script to the newer font; it
contains less characters, which is probably better.

. I suggest that you improve your script so that it increases (or modifies) the
version entry in the `name' table, probably also adding a comment that mentions
the openSuSE modifications.

. Rekha.ttf in 38.1 is replaced with Rekha-medium.ttf – note that we have the
same issue as with aakar: you should use the font with the newer version.

. A similar version problem occurs with padmaa-Bold.

. The script doesn't work correctly for padmaa-Bold: I still get `jumping
digits'. I suggest that you remove bytecode from all characters *except* the
Indic ones.

Regarding the newer fonts: I wonder where to get them... Apparently, they
aren't in the github repositories.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >