Bug 255862 - Broken utf8-decompsed display
Summary: Broken utf8-decompsed display
Status: RESOLVED DUPLICATE of bug 96536
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-02 10:14 UTC by sieburgh
Modified: 2011-07-20 14:57 UTC (History)
2 users (show)

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


Attachments
Screenshots + example file (86.29 KB, application/x-zip-compressed)
2010-11-02 10:14 UTC, sieburgh
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sieburgh 2010-11-02 10:14:23 UTC
Created attachment 53066 [details]
Screenshots + example file

Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

Konsole 2.5, shipped with Ubuntu 10.X, kde 4.5.1, does not display accents, if these are decomposed (so a separate charater, say o, e or a, and (mostly two) following bytes to indicate an accent. The characters that include an accent, (the composed form, as used in the unicode latin-1 set) are displayed OK.

Another problem is that if a character is separated from it's combining accent by a combining grapheme joiner, the accent is put on the next, instead of on the previous character.

Mind that it is not caused by the editor or environment setting, using the same environment and same editor (vim), but a different terminal (gnome-terminal or putty), the display is OK.

Reproducible: Didn't try

Steps to Reproduce:
Load the attached file utf8-acc.txt (I think I can only add a single attachment, so it's in the zip file)

Actual Results:  
See attached sceenshots for konsole (broken), gnome terminal (mostly OK) and Putty (mostly OK)
Comment 1 Jekyll Wu 2011-07-19 20:32:37 UTC
can't reproduce it with 2.7.999. Looks like a duplicate of #96536 which is already fixed.
Comment 2 Kurt Hindenburg 2011-07-20 02:55:15 UTC

*** This bug has been marked as a duplicate of bug 96536 ***
Comment 3 Kurt Hindenburg 2011-07-20 14:57:47 UTC
Wouter, thanks for the email.  Jekyll and I can't reproduce bug on the latest version.  We think it is resolved.  I could have marked this bug fixed->resolved.  However, marking as a duplicate of the bug that fixed it is better IMHO.

You can reply w/ further comments on this bug report and everyone can see them.

Thanks.