10 May
2016
10 May
'16
12:28 p.m.
Hi,
in the course of vcard and the encoding issue I ask herewith for help to
solve another annoying utf8 encoding issue.
Problem:
Attached images show that My_Documents when language set to bg gets mangled.
Unfortunately looking into this I found out it is mangled in
/opt/trinity/share/apps/kdesktop/Desktop/My_Documents
I tested in fresh install of TDE, but after first logout/login it changed
I workaround it by fixing the file and removing the write permissions.
I don't know where to look for the system:/ entry.
regards
20 Jun
20 Jun
10:24 p.m.
New subject: [trinity-devel] My_Documents mangled UTF8
2016-05-10 15:28 GMT+03:00 deloptes <deloptes(a)gmail.com>om>:
Hi,
in the course of vcard and the encoding issue I ask herewith for help to
solve another annoying utf8 encoding issue.
Problem:
Attached images show that My_Documents when language set to bg gets mangled.
Unfortunately looking into this I found out it is mangled in
/opt/trinity/share/apps/kdesktop/Desktop/My_Documents
I tested in fresh install of TDE, but after first logout/login it changed
I workaround it by fixing the file and removing the write permissions.
I don't know where to look for the system:/ entry.
regards
Have you fixed the encoding in the system-wide file
(/opt/trinity/share/apps/kdesktop/Desktop/My_Documents)?
It should be enough. The same is required to be done in the kdebase repository.
Also note if you are able to demangle it with some {i,en}conv you, may
want to do the same for bn/be locales, they supposed to be mangled
same way...
10:38 p.m.
New subject: [trinity-devel] My_Documents mangled UTF8
On Tuesday 21 of June 2016 00:24:56 Fat-Zer wrote:
2016-05-10 15:28 GMT+03:00 deloptes
<deloptes(a)gmail.com>om>:
As far as I know, this was fixed sometime in year 2011...
--
Slávek
Hi,
in the course of vcard and the encoding issue I ask herewith for help to
solve another annoying utf8 encoding issue.
Problem:
Attached images show that My_Documents when language set to bg gets
mangled.
Unfortunately looking into this I found out it is mangled in
/opt/trinity/share/apps/kdesktop/Desktop/My_Documents
I tested in fresh install of TDE, but after first logout/login it changed
I workaround it by fixing the file and removing the write permissions.
I don't know where to look for the system:/ entry.
regards
Have you fixed the encoding in the system-wide file
(/opt/trinity/share/apps/kdesktop/Desktop/My_Documents)?
It should be enough. The same is required to be done in the kdebase
repository.
Also note if you are able to demangle it with some {i,en}conv you, may
want to do the same for bn/be locales, they supposed to be mangled
same way...
11:31 p.m.
New subject: [trinity-devel] My_Documents mangled UTF8
2016-06-21 1:38 GMT+03:00 Slávek Banko <slavek.banko(a)axis.cz>cz>:
On Tuesday 21 of June 2016 00:24:56 Fat-Zer wrote:
As far as I know, this was fixed sometime in year 2011...
Seems somebody missed a spot ;)
Best results I've got:
cat My_Documents | grep '\[b[egn]\]' | iconv -t cp1252 -c
Name[be]=Т�чка дл� дакументаў
Name[bg]=Директори� � документи
Name[bn]=ডক��মেন��ট ফোল��ডার
So they all should be removed or fixed by native speakers (I suppose
we have a Bulgarian one here).
For Belarussian I suspect it should be "Точка для дакументаў" (not
100% positive)...
Got no damn clue, how it should looks on Bengali...
21 Jun
21 Jun
6:31 a.m.
Fat-Zer wrote:
2016-06-21 1:38 GMT+03:00 Slávek Banko
<slavek.banko(a)axis.cz>cz>:
Haha, thanks yes. This is exactly what I mean. According my experience after
correcting it, it looks fine until it gets reloaded. Something I noticed
about KSaveFile - it does not set the encoding to the stream.
I think the original files should be OK and when they get read for first
time it also looks OK, but after this they get mangled.
In my case it does not look like latin1 but utf8 mangling. This might be,
because you run it via iconv -t cp1252
cat /opt/trinity/share/apps/kdesktop/Desktop/Printers | grep '\[b[egn]\]'
Name[be]=Друкаркі
Name[bg]=Принтери
Name[bn]=মদরণ
Anyway, thank you for looking into it. As I wrote before the workaround for
me was to remove the write permissions on the file after changing it.
regards
On Tuesday 21 of June 2016 00:24:56 Fat-Zer
wrote:
As far as I know, this was fixed sometime in year 2011...
Seems somebody missed a spot ;)
Best results I've got:
cat My_Documents | grep '\[b[egn]\]' | iconv -t cp1252 -c
Name[be]=Т�чка дл� дакументаў
Name[bg]=Директори� � документи
Name[bn]=ডক��মেন��ট ফোল��ডার
So they all should be removed or fixed by native speakers (I suppose
we have a Bulgarian one here).
For Belarussian I suspect it should be "Точка для дакументаў" (not
100% positive)...
Got no damn clue, how it should looks on Bengali...
8:14 p.m.
New subject: [trinity-devel] Re: My_Documents mangled UTF8
2016-06-21 9:31 GMT+03:00 deloptes <deloptes(a)gmail.com>om>:
Fat-Zer wrote:
Are you positive, that the fixes reverts with the logins — that sounds
mostly impossible... You are likely just reinstalled the kdesktop
package.
And what's the correct Bulgarian variant, if you may provide such?
2016-06-21 1:38 GMT+03:00 Slávek Banko
<slavek.banko(a)axis.cz>cz>:
Haha, thanks yes. This is exactly what I mean. According my experience after
correcting it, it looks fine until it gets reloaded. Something I noticed
about KSaveFile - it does not set the encoding to the stream.
I think the original files should be OK and when they get read for first
time it also looks OK, but after this they get mangled.
In my case it does not look like latin1 but utf8 mangling. This might be,
because you run it via iconv -t cp1252
cat /opt/trinity/share/apps/kdesktop/Desktop/Printers | grep '\[b[egn]\]'
Name[be]=Друкаркі
Name[bg]=Принтери
Name[bn]=মদরণ
Anyway, thank you for looking into it. As I wrote before the workaround for
me was to remove the write permissions on the file after changing it.
regards
On Tuesday 21 of June 2016 00:24:56 Fat-Zer
wrote:
As far as I know, this was fixed sometime in year 2011...
Seems somebody missed a spot ;)
Best results I've got:
cat My_Documents | grep '\[b[egn]\]' | iconv -t cp1252 -c
Name[be]=Т�чка дл� дакументаў
Name[bg]=Директори� � документи
Name[bn]=ডক��মেন��ট ফোল��ডার
So they all should be removed or fixed by native speakers (I suppose
we have a Bulgarian one here).
For Belarussian I suspect it should be "Точка для дакументаў" (not
100% positive)...
Got no damn clue, how it should looks on Bengali...
10:06 p.m.
Fat-Zer wrote:
2016-06-21 9:31 GMT+03:00 deloptes
<deloptes(a)gmail.com>om>:
I updated the My_Documents file and saved. It appears correct on the screen,
but after some time or login - don't recall exactly it appears mangled on
the screen. I check the file and the mangled is there - definitely UTF.
I observed the same with the KSaveFile as stated above.
The correct one is
مستنداتي
Name[bg]=Документи
Oh, I just see here (from git):
tdebase/kdesktop/init/My_Documents
[Desktop Entry]
Encoding=UTF-8
Icon=folder_wordprocessing
Name=My Documents
Name[af]=Dokument Gids
Name[ar]=مستنداتي
Name[be]=ТÑчка Ð´Ð»Ñ Ð´Ð°ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñž
Name[bg]=Ð”Ð¸Ñ€ÐµÐºÑ‚Ð¾Ñ€Ð¸Ñ Ñ Ð´Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð¸
Name[bn]=ডকà§à¦®à§‡à¦¨à§à¦Ÿ ফোলà§à¦¡à¦¾à¦°
So it's broken in git - perhaps one could find the original file and it is
correct there - what a mess - I always hated this encoding stuff. Each time
you have to write some code dealing with text ... it was such a pain ... it
will last another 10-20y before its gone.
regards
Fat-Zer wrote:
Are you positive, that the fixes reverts with the logins — that sounds
mostly impossible... You are likely just reinstalled the kdesktop
package.
And what's the correct Bulgarian variant, if you may provide such? 2016-06-21 1:38 GMT+03:00 Slávek Banko
<slavek.banko(a)axis.cz>cz>:
Haha, thanks yes. This is exactly what I mean. According my experience
after correcting it, it looks fine until it gets reloaded. Something I
noticed about KSaveFile - it does not set the encoding to the stream.
I think the original files should be OK and when they get read for first
time it also looks OK, but after this they get mangled.
In my case it does not look like latin1 but utf8 mangling. This might be,
because you run it via iconv -t cp1252
cat /opt/trinity/share/apps/kdesktop/Desktop/Printers | grep '\[b[egn]\]'
Name[be]=Друкаркі
Name[bg]=Принтери
Name[bn]=মদরণ
Anyway, thank you for looking into it. As I wrote before the workaround
for me was to remove the write permissions on the file after changing it.
regards
On Tuesday 21 of June 2016 00:24:56 Fat-Zer
wrote:
As far as I know, this was fixed sometime in year 2011...
Seems somebody missed a spot ;)
Best results I've got:
cat My_Documents | grep '\[b[egn]\]' | iconv -t cp1252 -c
Name[be]=Т�чка дл� дакументаў
Name[bg]=Директори� � документи
Name[bn]=ডক��মেন��ট ফোল��ডার
So they all should be removed or fixed by native speakers (I suppose
we have a Bulgarian one here).
For Belarussian I suspect it should be "Точка для дакументаў" (not
100% positive)...
Got no damn clue, how it should looks on Bengali...
22 Jun
22 Jun
2:26 p.m.
New subject: [trinity-devel] Re: Re: My_Documents mangled UTF8
2016-06-22 1:06 GMT+03:00 deloptes <deloptes(a)gmail.com>om>:
Fat-Zer wrote:
Ok, I've found a way to demangle those locales completely. The reason
the iconv failed on some chars is that the encoding is mess of cp1252
and latin1 (the first one got non-leter symbols in place of some
control sequences)
Here is the patch.
2016-06-21 9:31 GMT+03:00 deloptes
<deloptes(a)gmail.com>om>:
I updated the My_Documents file and saved. It appears correct on the screen,
but after some time or login - don't recall exactly it appears mangled on
the screen. I check the file and the mangled is there - definitely UTF.
I observed the same with the KSaveFile as stated above.
The correct one is
مستنداتي
Name[bg]=Документи
Oh, I just see here (from git):
tdebase/kdesktop/init/My_Documents
[Desktop Entry]
Encoding=UTF-8
Icon=folder_wordprocessing
Name=My Documents
Name[af]=Dokument Gids
Name[ar]=مستنداتي
Name[be]=ТÑчка Ð´Ð»Ñ Ð´Ð°ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð°Ñž
Name[bg]=Ð”Ð¸Ñ€ÐµÐºÑ‚Ð¾Ñ€Ð¸Ñ Ñ Ð´Ð¾ÐºÑƒÐ¼ÐµÐ½Ñ‚Ð¸
Name[bn]=ডকà§à¦®à§‡à¦¨à§à¦Ÿ ফোলà§à¦¡à¦¾à¦°
So it's broken in git - perhaps one could find the original file and it is
correct there - what a mess - I always hated this encoding stuff. Each time
you have to write some code dealing with text ... it was such a pain ... it
will last another 10-20y before its gone.
regards
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Fat-Zer wrote:
Are you positive, that the fixes reverts with the logins — that sounds
mostly impossible... You are likely just reinstalled the kdesktop
package.
And what's the correct Bulgarian variant, if you may provide such? 2016-06-21 1:38 GMT+03:00 Slávek Banko
<slavek.banko(a)axis.cz>cz>:
> On Tuesday 21 of June 2016 00:24:56 Fat-Zer wrote:
>
> As far as I know, this was fixed sometime in year 2011...
>
Seems somebody missed a spot ;)
Best results I've got:
cat My_Documents | grep '\[b[egn]\]' | iconv -t cp1252 -c
Name[be]=Т�чка дл� дакументаў
Name[bg]=Директори� � документи
Name[bn]=ডক��মেন��ট ফোল��ডার
So they all should be removed or fixed by native speakers (I suppose
we have a Bulgarian one here).
For Belarussian I suspect it should be "Точка для дакументаў" (not
100% positive)...
Got no damn clue, how it should looks on Bengali...
Haha, thanks yes. This is exactly what I mean. According my experience
after correcting it, it looks fine until it gets reloaded. Something I
noticed about KSaveFile - it does not set the encoding to the stream.
I think the original files should be OK and when they get read for first
time it also looks OK, but after this they get mangled.
In my case it does not look like latin1 but utf8 mangling. This might be,
because you run it via iconv -t cp1252
cat /opt/trinity/share/apps/kdesktop/Desktop/Printers | grep '\[b[egn]\]'
Name[be]=Друкаркі
Name[bg]=Принтери
Name[bn]=মদরণ
Anyway, thank you for looking into it. As I wrote before the workaround
for me was to remove the write permissions on the file after changing it.
regards
7:53 p.m.
Fat-Zer wrote:
Ok, I've found a way to demangle those locales
completely. The reason
the iconv failed on some chars is that the encoding is mess of cp1252
and latin1 (the first one got non-leter symbols in place of some
control sequences)
you are a magician :)
thanks
PS: BG has been always cp1251 btw - but it looks it worked pretty well with
what you did
23 Jun
23 Jun
6:27 a.m.
Fat-Zer wrote:
Ok, I've found a way to demangle those locales
completely. The reason
the iconv failed on some chars is that the encoding is mess of cp1252
and latin1 (the first one got non-leter symbols in place of some
control sequences)
I forgot to ask 2 things
1. did you upload the patch, or should I do the paper work.
2. Can you help me solving the second problem "system:/documents" - see
screenshot. I don't even know where it is coming from. If its tdebase
again - I think it is "System.desktop", both could go in a patch together.
In fact if I change this with right mouse click it gets mangled again just
after I press OK.
Thanks
8:18 a.m.
New subject: [trinity-devel] Re: Re: Re: My_Documents mangled UTF8
On Thursday 23 of June 2016 08:27:26 deloptes wrote:
Fat-Zer wrote:
I'll do commit early. Fat-Zer, thank you for the patch!
Ok, I've found a way to demangle those
locales completely. The reason
the iconv failed on some chars is that the encoding is mess of cp1252
and latin1 (the first one got non-leter symbols in place of some
control sequences)
I forgot to ask 2 things
1. did you upload the patch, or should I do the paper work. 2. Can you help me solving the second problem
"system:/documents" - see
screenshot. I don't even know where it is coming from. If its tdebase
again - I think it is "System.desktop", both could go in a patch together.
In fact if I change this with right mouse click it gets mangled again just
after I press OK.
Yes, I know about it. A second file with the same problem is in
tdeioslave/system/entries/documents.desktop. I'll apply the same patch also
to this file.
Thanks
--
Slávek
24 Jun
24 Jun
5:06 p.m.
Slávek Banko wrote:
On Thursday 23 of June 2016 08:27:26 deloptes wrote:
Indeed it worked
thanks
Fat-Zer wrote:
I'll do commit early. Fat-Zer, thank you for the patch!
Ok, I've found a way to demangle those
locales completely. The reason
the iconv failed on some chars is that the encoding is mess of cp1252
and latin1 (the first one got non-leter symbols in place of some
control sequences)
I forgot to ask 2 things
1. did you upload the patch, or should I do the paper work. 2. Can you help me solving the second problem
"system:/documents" - see
screenshot. I don't even know where it is coming from. If its tdebase
again - I think it is "System.desktop", both could go in a patch
together.
In fact if I change this with right mouse click it gets mangled again
just after I press OK.
Yes, I know about it. A second file with the same problem is in
tdeioslave/system/entries/documents.desktop. I'll apply the same patch
also to this file.
Thanks
5 Jul
5 Jul
1:05 p.m.
New subject: [trinity-devel] Re: Re: Re: Re: My_Documents mangled UTF8
On Friday 24 of June 2016 19:06:36 deloptes wrote:
Slávek Banko wrote:
Thank you both.
Patch was pushed.
--
Slávek
On Thursday 23 of June 2016 08:27:26 deloptes
wrote:
Indeed it worked
thanks
Fat-Zer wrote:
I'll do commit early. Fat-Zer, thank you for the patch!
Ok, I've found a way to demangle those
locales completely. The reason
the iconv failed on some chars is that the encoding is mess of cp1252
and latin1 (the first one got non-leter symbols in place of some
control sequences)
I forgot to ask 2 things
1. did you upload the patch, or should I do the paper work. 2. Can you help me solving the second problem
"system:/documents" - see
screenshot. I don't even know where it is coming from. If its tdebase
again - I think it is "System.desktop", both could go in a patch
together.
In fact if I change this with right mouse click it gets mangled again
just after I press OK.
Yes, I know about it. A second file with the same problem is in
tdeioslave/system/entries/documents.desktop. I'll apply the same patch
also to this file.
> Thanks
3061
days inactive
3117
days old
12 comments
3 participants
participants (3)
-
deloptes -
Fat-Zer -
Slávek Banko