https://bugzilla.redhat.com/show_bug.cgi?id=1398676
--- Comment #5 from Mike FABIAN <mfabian(a)redhat.com> ---
(In reply to Akira TAGOH from comment #4)
Mike, can you file a bug to upstream bugzilla as well?
Done:
https://bugzilla.gnome.org/show_bug.cgi?id=775202
Though that looks to me like a bug in font as well as we saw the
similar
issue in the Indic fonts and fixed it there.
Was a space missing in the Indic fonts? Is there a requirement
in some standard that a font must have a space?
The upstream author of OldHungarian.ttf is reluctant to add
a space, see:
https://github.com/OldHungarian/old-hungarian-font/issues/1
stupy> Meanwhile I saw that adding the space character will most
stupy> likely break web usage for the font, as it will override the
stupy> main space character for the site for normal text as well. I
stupy> might need to create two separate fonts, one with extra glyphs,
stupy> and one without them
He created two different fonts now, one with a space and one without.
This is quite ugly and confusing I think. Therefore, if fonts are not
required to have a space by some standard, this probably should be
fixed in Pango.
A similar problem recently occured for Andreas Schneider
<asn(a)redhat.com> without using OldHungarian.ttf but some other fonts
on a default installation of Fedora. So this may happen in some
circumstances even on a default installation of Fedora.
I'm not sure if the en.orth
file in fontconfig should contains U+0020 to avoid the sort of this
situation. dunno if that really helps. not yet tested.
Is en.orth relevant if a line rendered by pango-view contains only
Old Hungarian for example?
--
You are receiving this mail because:
You are on the CC list for the bug.