Bug 217684 - Indic - hindi, telugu unicode characters are not rendered properly
Summary: Indic - hindi, telugu unicode characters are not rendered properly
Status: RESOLVED DUPLICATE of bug 96536
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.3.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-07 08:36 UTC by Mohd Asif Ali Rizwaan
Modified: 2011-08-16 05:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
rendender in konsole-2.7.999 (85.72 KB, image/png)
2011-08-16 05:04 UTC, Jekyll Wu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mohd Asif Ali Rizwaan 2009-12-07 08:36:04 UTC
Version:           2.3.3 (using KDE 4.3.4)
OS:                Linux
Installed from:    Ubuntu Packages

Unicode Indic rendering bug. matras are not rendered. this might also affect all other indic languages like bengali, punjabi, marathi, etc.

्ािीुूेैोौंॆ <- hindi matras
్ాిీుూేైోౌంె <- telugu matras
The above characters are not displayed at all, except these - "ािीोौ" in hindi and these "ుూం" in telugu. 

example consonent with vowels -> कु कृ के कै is also not rendered in konsole, it is just rendered as  क क क क

How to reproduce:

1. copy the above ्ािीुूेैोौंॆ and ్ాిీుూేైోౌంె and paste it in konsole.
2. observe that the unicode characters simply disappears and get lost.

Expected behavior:

1. characters (matras - vowels) which are place above and below a consonents, should also be rendered.


thank you.
Comment 1 Jekyll Wu 2011-08-16 05:04:25 UTC
Created attachment 62860 [details]
rendender in konsole-2.7.999

The fix of #bug 96536 should have also fixed this one. At least this part :

"example consonent with vowels -> कु कृ के कै is also not rendered in konsole, 
it is just rendered as  क क क क "

is rendered as expected in 2.7.999(devel version).
Comment 2 Jekyll Wu 2011-08-16 05:05:37 UTC

*** This bug has been marked as a duplicate of bug 96536 ***