Re: Unexpected font rendering with pango

[Eric Mader <emader bigfoot com>]

You can make the font 'sticky' only for that script. In general, it 
seems to be a good idea to try and display all characters in a given 
script in the same font. It might also make sense to take the language 
into account too; possibly with a notion of what characters are used to 
write a given language in a given script. I haven't thought about that 
enough to say for sure..

Another point: for complex text like Arabic and Hindi, you really, 
really want to try and keep it all in the same font, because that's the 
only way to get the correct contextual behavior.

Regards,
Eric Mader
IBM GCoC - San José
5600 Cottle Rd.  M/S 50-2/B11
San Jose, CA 95193

Keith Packard wrote:
> Around 22 o'clock on Jun 27, Pablo Saratxaga wrote:
>
>
> > I meant, if a char "X" is searched in first font, and not found there
> > then found in the second font; then, when displaying the second char "Y",
> > first look at the last used font (the second) instead of looking again
> > at the first, then second.
>
>
> And if the characters are in the opposite order, you'll still get 'ransom 
> note' typography.
>
> A particular counter example is a document which is largely in English but 
> which happens to start with a Japanese glyph.  With a 'sticky font' 
> mechanism, the whole document will be rendered with a Japanese font.
>
> The current mechanism is also designed to be 'stable' so that the glyphs 
> selected for any particular character don't change as the document is 
> edited; this makes layout significantly easier.
>
> The correct solution is to inform the font system what languages are in use
> so that appropriate fonts can be selected.
>
> -keith
>
>
> _______________________________________________
> gtk-i18n-list mailing list
> gtk-i18n-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-i18n-list