Bug#844162: src:kodi: validation failure with new fontforge

Balint Reczey balint at balintreczey.hu
Fri Jan 13 17:07:24 UTC 2017

Control: severity -1 minor
Control: tags -1 confirmed upstream
Control: forwarded -1 https://github.com/fontforge/fontforge/issues/2920

Hi Adam,

On Sat, 12 Nov 2016 22:08:03 +0100 Adam Borowski <kilobyte at angband.pl>
> Package: src:kodi
> Version: 17.0~beta5+dfsg1-1
> Severity: normal
> Hi!
> The new version of fontforge, just uploaded to unstable, has a more stringent
> validator, which causes:
> fontforge -script /<<BUILDDIR>>/kodi-17.0~beta5+dfsg1/debian/mergefonts.ff \
>         /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf \
>         /usr/share/fonts/truetype/dejavu/DejaVuSans.ttf \
>         /<<BUILDDIR>>/kodi-17.0~beta5+dfsg1/media/Fonts/arial.ttf
> Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors.
>  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
>  with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
>  Based on sources from 20161112-ML-D.
>  Based on source from git with hash:
> Cannot find your hotkey definition file!
> This font contains both a 'kern' table and a 'GPOS' table.
>   The 'kern' table will only be read if there is no 'kern' feature in 'GPOS'.
> Use-my-metrics flag set on at least two components in glyph 685
> The glyph named Omega is mapped to U+03A9.
>   But its name indicates it should be mapped to U+2126.
> I don't know the first two problems, but the last one is caused by a
> confusion between U+03A9 GREEK CAPITAL LETTER OMEGA and U+2126 OHM SIGN;
> in an Adobe name list used by fontforge for some strange reason the name
> "Omega" maps to the latter.  The list was apparently changed by Adobe some
> time ago, between fontforge 20120731 and 20161005.  A workaround is to
> explicitly use "Omega.greek".  There's some discussion at:
> https://github.com/fontforge/fontforge/issues/2920

Thanks for the report!

It luckily does not break the build nor cause visible problems AFAIK in

We will see how it gets resolved at fontforge or at the font upstreams.


More information about the pkg-multimedia-maintainers mailing list