Den 2010-08-13 02.28, skrev Pravin Satpute psatp...@redhat.com:
Yes, problem is happening only when these characters come at initial
position.
i.e U+0951 and U+0952 in isolation should render with U+25cc
U+25CC should never be inserted automatically. That some systems do so is a
bug (no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
pango uses Unicode Scripts.txt file via glib2 to get script
information of Unicode character and then process it with the
respective script engine module. U+0951 and U+0952 are not getting
rendered properly with pango, while testing it i found
Pravin Satpute psatpute at redhat dot com wrote:
pango uses Unicode Scripts.txt file via glib2 to get script
information of Unicode character and then process it with the
respective script engine module. U+0951 and U+0952 are not getting
rendered properly with pango, while testing it i found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/13/2010 03:11 AM, Doug Ewell wrote:
Pravin Satpute psatpute at redhat dot com wrote:
pango uses Unicode Scripts.txt file via glib2 to get script
information of Unicode character and then process it with the
respective script engine module.
Please make sure to not just implement Unicode properties according to what
you see in UCD files but to also follow the relevant documentation. For
example, http://www.unicode.org/reports/tr24/
http://www.unicode.org/reports/tr24/Note also that Unicode 6.0 adds a new,
provisional (=draft)
5 matches
Mail list logo