Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157838 - Character encoding errors in Finnish KDE
Summary: Character encoding errors in Finnish KDE
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-i18n
Version: 4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-16 13:54 UTC by Markku Kolkka
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-21 12:29:41 UTC


Attachments (Terms of Use)
Screen capture from KDE control center demonstrating the problem (deleted)
2005-05-16 13:56 UTC, Markku Kolkka
no flags Details

Description Markku Kolkka 2005-05-16 13:56:33 UTC
Created attachment 114422 [details]
Screen capture from KDE control center demonstrating the problem

Comment 1 Markku Kolkka 2005-05-16 13:59:13 UTC
It looks like some problem in Bugzilla wiped out the content of the original
report. Anyway, in the attached screen capture you can see lots of ','
characters instead of 'ä' characters that should be there. Other KDE programs
have similar errors as well.

Comment 2 Markku Kolkka 2005-06-15 09:56:32 UTC
This bug hasn't been fixed in FC4 final.

Comment 3 Markku Kolkka 2005-06-18 16:53:55 UTC
Updated to kde-i18n-Finnish-3.4.1-0.fc4.1, no improvement.

Comment 4 Ngo Than 2005-06-21 12:29:41 UTC
it seems a bug in kde-i18n upstream and should be fixed in new upstream. Could
you please report this problem to http://bugs.kde.org/. thanks

Comment 5 Markku Kolkka 2005-06-21 12:34:23 UTC
Upstream report exists already: http://bugs.kde.org/show_bug.cgi?id=106866


Note You need to log in before you can comment on or make changes to this bug.