freetype
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft] rendering problem with soft hyphen


From: Werner LEMBERG
Subject: Re: [ft] rendering problem with soft hyphen
Date: Fri, 14 Feb 2014 06:52:56 +0100 (CET)

> While trying to find out what could be cause of this I've tried
> ftview - is ftview behaviour correct one?

Some issues:

  o ftview's `-m' flag needs input in UTF8, while your attached files
    are in latin2 encoding.

  o you should add the `-e unic' flag to make ftview handle UTF8.

  o The attached images don't correspond to the attached input files.

> txt one looks really weird while html one renders these soft hyphen
> characters as visible.

Again, some issues.

  o The soft hyphen is a *pure input character*.  It is *never*
    intended to be displayed directly!  It's the job of the rendering
    engine (e.g. the HTML browser) to decide whether a real hyphen –
    at a line break, for example – or nothing should be displayed.
    Within a font, it is convenient to put a hyphen-like glyph at the
    position of U+00AD, however, it could be empty too.

  o ftview is a program to display the contents of the font.  It
    contains no logic to manipulate the input.  And yes, Liberation
    Sans Regular does contain a glyph for character U+00AD, and it
    looks like an ordinary hyphen.

ftview behaves correctly.  After the encoding conversion, I properly
see Polish characters, together with hyphens for U+00AD and rectangles
for the line-end characters (`\n') – the font doesn't contain a glyph
for U+000A, thus using the `.notdef' glyph instead.


    Werner

reply via email to

[Prev in Thread] Current Thread [Next in Thread]