ubuntustudio-bugs team mailing list archive

[Paul Hardy <unifoundry@xxxxxxxxxxxxxx>]

Sworddragon,

Here is some more detail.  The UTF-8 equivalent for the surrogate pair
you entered should be (in octal) \360\237\217\201 in the web page you
were viewing.

The Unifont package is split between a base "Unifont" font, which only
contains Plane 0 glyphs (and the Copyleft glyph as of Unifont 11.0.01),
and a "Unifont Upper" font, which contains glyphs above Plane 0.  The
TrueType format has a hard limit of 64k glyphs in one font, so the split
into two fonts is necessary.

If you were using the "Unifont Upper" font rather than the base
"Unifont" font to try to display that web page, I added a space glyph to
it for the Unifont Upper 11.0.01 release.  That is the only thing that
might have caused that behavior that changing the TrueType font would
influence.  I could not reproduce the issue you saw even before the
Unifont 11.0.01 release though.

As a data point for the font rendering engine, I found out last year
that Harfbuzz uses its own determination for spacing of TrueType glyphs.
It ignores x-axis offset information that the TrueType font contains.
Harfbuzz only uses horizontal offset information in OpenType fonts, not
in TrueType fonts.  You can see the exchange related to that here:

     https://bugzilla.gnome.org/show_bug.cgi?id=787284

The end result of that should be that at least for combining characters,
vertical placement will be improved but horizontal placement could be
less than ideal (even incorrect, as observed in that GNOME bug report).

Adding the space glyph to "Unifont Upper" in version 11.0.01 was the
only change I could make to a TrueType font that I did not already make.
All horizontal offset information was already in all the TrueType fonts
in the Unifont package.  If this is still a problem, I do not see any
way it could be from the TrueType fonts; it would have to be with the
font rendering engine.

Thank you,


Paul Hardy


** Bug watch added: GNOME Bug Tracker #787284
   https://bugzilla.gnome.org/show_bug.cgi?id=787284

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to unifont in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1489360

Title:
  🏁 Spaces after some unicode characters are looking like unicode
  placeholder characters

Status in unifont package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 15.10 dev with unifont 1:8.0.01-1 and adding spaces after some unicode characters will cause them to look like unicode placeholder characters (a square with some characters in it). An example would be the 2 byte unicode character "D83C DFC1" which is drawn as a flag and looks this: 🏁
  If I'm adding a space after the flag it looks this: 🏁
  But it seems some browsers are drawing the space correctly but on system components the unicode placeholder character is shown. For this reason I have also added the flag and a space at the beginning of the summary to cause it to be shown in the title of the window manager.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unifont/+bug/1489360/+subscriptions