Polish national chars not properly displayed

Bug #587018 reported by Badkonis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Time Drive
Confirmed
Medium
Rob Oakes

Bug Description

Hello,
the problem is: all Polish national characters are not properly displayed. Polish chars are replaced by some symbols (look like incorect font encoding) - for some expamples please see attached print screen (main program window and settings window)
There are some replacing rules (I'm not sure if it's important):
- for some chars: at least 2 Polish chars are replaced by one and the same symbol ("ą" and "ę" by one symbol, "ł" and "ń" by other - if you can see my chars proprely);
- for some chars: one pcs of Polish chars is replaced by two symbols ("ł" and also "ń" by A with dot above and next to A - rectangle), some others by only one symbol

The problem is visible in Gnome and KDE either
I'm using Timedrive version: 0.4-2karmic1 on Ubuntu 10.04 LTS "Linux cave 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux".
I've checked the time-drive.mo file (/usr/share/locale/pl/LC_MESSAGES/) and all Polish national chars are displayed (in kedit, but also cat command in konsole) correctly.

Pls apologize for my English, I hope all above is clear.

Revision history for this message
Badkonis (badkonis) wrote :
Revision history for this message
Philippe Delodder (lodder) wrote :

@Rob could it be possible that you rebuild the complete build to fix this issue?

Changed in time-drive:
importance: Undecided → Medium
status: New → Confirmed
assignee: nobody → Rob Oakes (robertsoakes)
Revision history for this message
Rob Oakes (robertsoakes) wrote : Re: [Bug 587018] Re: Polish national chars not properly displayed

Hi Philippe,

I don't know what is causing this bug. The only thing I can think of is some kind of weirdness in the Qt framework. It only appears to affect certain characters and punctuation marks. (One of the offenders I had problems with on my system was the upside down question mark commonly used in Spanish.)

By default, Qt makes use of a different system for translations (Qt Translator). If I understand our translation system correctly (and, frankly, I don't), we make use of the gettext python module. Do you know if the strange characters are appearing only in the GUI, or both in the GUI and in the error messages? If it's the former, the problem likely lies with Qt/PyQt, and I can try and solicit those mailing lists for ideas.

If it's the latter, it may be something we are doing wrong in the interface between translator and gettext. The PyQt website has some information about translations that might be of help in tracking down the problem.

Anything else turned up on your end of things?

Cheers,

Rob

Revision history for this message
Philippe Delodder (lodder) wrote :

Hi Rob,

I believe It has something to do with the UTF-8 encoding I remember we had
about the same issues with French. maybe you could recompile it?

Kind Regards,
--
Philippe Delodder
<email address hidden>
http://www.delodder.be

2010/6/4 Rob Oakes <email address hidden>

> Hi Philippe,
>
> I don't know what is causing this bug. The only thing I can think of is
> some kind of weirdness in the Qt framework. It only appears to affect
> certain characters and punctuation marks. (One of the offenders I had
> problems with on my system was the upside down question mark commonly
> used in Spanish.)
>
> By default, Qt makes use of a different system for translations (Qt
> Translator). If I understand our translation system correctly (and,
> frankly, I don't), we make use of the gettext python module. Do you
> know if the strange characters are appearing only in the GUI, or both in
> the GUI and in the error messages? If it's the former, the problem
> likely lies with Qt/PyQt, and I can try and solicit those mailing lists
> for ideas.
>
> If it's the latter, it may be something we are doing wrong in the
> interface between translator and gettext. The PyQt website has some
> information about translations that might be of help in tracking down
> the problem.
>
> Anything else turned up on your end of things?
>
> Cheers,
>
> Rob
>
> --
> Polish national chars not properly displayed
> https://bugs.launchpad.net/bugs/587018
> You received this bug notification because you are a member of Time
> Drive - Devel, which is subscribed to Time Drive.
>
> Status in Time Drive: Confirmed
>
> Bug description:
> Hello,
> the problem is: all Polish national characters are not properly displayed.
> Polish chars are replaced by some symbols (look like incorect font encoding)
> - for some expamples please see attached print screen (main program window
> and settings window)
> There are some replacing rules (I'm not sure if it's important):
> - for some chars: at least 2 Polish chars are replaced by one and the same
> symbol ("ą" and "ę" by one symbol, "ł" and "ń" by other - if you can see my
> chars proprely);
> - for some chars: one pcs of Polish chars is replaced by two symbols ("ł"
> and also "ń" by A with dot above and next to A - rectangle), some others by
> only one symbol
>
> The problem is visible in Gnome and KDE either
> I'm using Timedrive version: 0.4-2karmic1 on Ubuntu 10.04 LTS "Linux cave
> 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686
> GNU/Linux".
> I've checked the time-drive.mo file (/usr/share/locale/pl/LC_MESSAGES/) and
> all Polish national chars are displayed (in kedit, but also cat command in
> konsole) correctly.
>
> Pls apologize for my English, I hope all above is clear.
>
>
>

Revision history for this message
Badkonis (badkonis) wrote :

Hi Developers,
my light suggestion is to add a simple language switcher of user interface, for switching between English and system-default language.
I guess that it's a simpler solution, which could be temporary used in Time Drive, before solving this bug.
--
Best regards
Bernard Adkonis

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.