[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#549322: Non friendly kde for internationnal user



On Wed, Sep 8, 2010 at 3:43 PM, Frederik Schwarzer <schwarzerf@gmail.com> wrote:
> [Bastien ROUCARIES - Mittwoch 08 September 2010 14:08:22]
>
> Hi,
>
>> kde does not seems to be friendly with internationnal user.
>>
>> See bugs https://bugs.kde.org/show_bug.cgi?id=165044 and
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549322
>
> The former has an explanation, that a fix would cause too much trouble
> and that KDE had transition code for 5 years. The files you cannot
> rename anymore have brocen file name encodings. There is also a link
> to a more technical explanation:
> http://lists.kde.org/?l=kde-core-devel&m=122025063320264&w=2
>
>
>> description of upstream bug show clearly the problem:
>> >Attached is a tar file with two folders with characters that aren't utf-8 encoded.
>> >
>> >If I open it with ark, it seems to guess the right encoding, and shows the special characters, ("Relatório" and "Código" -- the problem is in the 'ó').
>> >
>> >If I use dolpin tar:/... to navigate inside the file without extracting it, the special character just isn't shown (folders show up as Relatrio and Cdigo), but I can still navigate and see the >files inside the folders.
>> >
>> >Finally, if I extract the file (tar xvf <file>), and try to navigate inside the folders with the wacky names, I get an error saying The file or folder (...) does not exist, and It refuses to >delete them too.
>>
>> Unfortunatly upstream refuse to fix this bug, that is really anoying
>> for internationnal user.
>
> If I understand correctly, only for those with broken file names.
>
> Sure, it's annoying. If the fix was easy, it would likely already be there.
> The risk of breaking many other things seems not worth the risk though.
>
The problem is the actual state is a regression comparing to kde 3,
and I can not fix my cdrom (by renaming)

command line work so it is not a question of broken or not. Every
thing except / and nul are valid filename.

Technical explanation is not satisfactory, (i do not want to show
correct char, ??? will be good)

Bastien



Reply to: