search

GoogleCodeArchives / xbmc-scripts

Automatically exported from code.google.com/p/xbmc-scripts
0 stars 0 forks source link

Different codepage handling on Windows compared to OSX #11

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hi Alex

I did some scanning om my WinXP machine, and the UTF8 translation is OK. I 
encoded all mu ITPC info in UTF8
This is what I see with SQliteSpy

Doing the same scan from my mac/OSX, it look different. In stead of 
“Jordanië” the countrie name “Jordani?” is shown.

I have been looking all day around to fix the problem. But I didnot succed to 
fix it 

Plz help

(print screens are on the email)

Original issue reported on code.google.com by mdeb...@gmail.com on 25 Jan 2011 at 3:20

GoogleCodeExporter commented 9 years ago 
This may be because sometimes I read/write datas in the db using the system 
encoding, and sometime I forced it to utf8. It is not a good Idea, I know, but 
this is because I find encoding very tricky.

I have to use always the same encoding (system encoding every where OR utf8 
everywhere)

Todo...

Original comment by alexso...@gmail.com on 25 Jan 2011 at 5:28

GoogleCodeExporter commented 9 years ago 
Did some additional analysis

When encoding using GeoSetter on Windows, using default Windows charset Latin 1 
(see attachment '0 aan')
XBMC/MPD add-on show Jordanië on Windows
XBMC/MPD add-on show Jordani? on OSX

When encoding using GeoSetter on Windows, using Unicode UTF8 charset (see 
attachment '1 aan')
XBMC/MPD add-on show Jordani? on Windows
XBMC/MPD add-on show Jordanië on OSX

So you understand

Original comment by mdeb...@gmail.com on 25 Jan 2011 at 7:05

Attachments:

GoogleCodeExporter commented 9 years ago 
and even more testing

using codepage Latin I (ansi), central europe (ansi) and arabic (ansi)
goes OK on Win but NOK on OSX

using codepage UTF8
goes NOK on Win but OK on OSX

Original comment by mdeb...@gmail.com on 25 Jan 2011 at 7:50

GoogleCodeExporter commented 9 years ago 
That is not correct on one of the os doesn't necessary mean that the addon does 
not work.
Did your OSX database works on windows (with the addon) ?

The most important thing is that my addon can read what is in database. 
Whatever the addon use as encoding, it should be able to read it using same 
encoding.

Original comment by alexso...@gmail.com on 25 Jan 2011 at 8:31