@CCRDude wrote:
Hey, you seem to know more about what I tested than I did, how about coming over and fixing all the remains? 😛
Please, don’t be upset. You working on this, and that is great. I only read what you write and comment on that information.
Yes, the locale I set by hand was UTF-8, but there was no explicit locale before I generated one, so how do you know both I “tested” where UTF-8?
Actually, the problem was (or may have been) that the OS image was partly Japanese at some point.
Japanese system/locale? Did you get strange output from ‘ls -l’? You should have been using locale “C” if not specified using any other locale. But that doesn’t mean I know that, it’s just an obeservation from information in your posts and my knowled about this subjekt.
You wrote (or did I missunderstood you) you used two other locales with UTF-8 scripting. But locales has influence on more stuff than what script the computer is using.
So my comments was more to clear that locales and scripts is not the same. And that the two locales you said you use has same script, UTF-8. And that should not give any differences in this case. Locales “C” on the other hand, would have given differences compared to the other locales mentioned here.
Also I don’t quite understand what you mean by “there are not lots of Unicode”, there’s a noun missing, lots of what? If you feel insulted by my statement that there are lots of Unicode versions, keep in mind that we’ve reached Unicode version 5.0.0 by now, with I think nearly 20 versions of Unicode so far. For a standard, that’s actually quite a lot in my opinion.
I’m not insulted? Sorry if I have given you that impression, or if I insulted you.
You are right that there is different Unicode standards, but on same computer system there is only one. So that shouldn’t give any problems for programs running on same system.
And about all that locale changes you mention – there are only two “things” involved here, which are ID3 tags, which use UTF-8 or UTF-16 LE or BE, but the locace is only used to determine the language of comments, sync and unsync lyric fields, so the “change lots of things” won’t hit here (I wrote my own tagging application to be able to properly tag polish files, so I think I encountered all ID3v2 special cases 😉 ). The other thing are filenames, which are quite useless here since they’re just stored the way they’re read and that’s it.
So I strongly disagree with your disagreement 😉
I don’t disagree on possible effects on programs, just the using of terms.
Locales (like sv_SE.ISO-8859-1 or sv_SE.UTF-8 ) are not same thing as scripts (like ISO-8859-1 or UTF-8 ). Scrips are part of locales. Lots of people (and by that I don’t mean anyone special) get confused by that.
So using locale en_GB.UTF-8, de_DE.UTF-8 or sv_SE.UTF-8 should give same results when it comes to character encoding. But not comparing those three with en_GB.ISO-8859-1 or C shouldn’t nessesarily do that.
So my intent with my comments on this was meant to clear that possible confussion. I might have failed on that 😉
So, keep up the good work. I do appresiate that.
“Well, just pass by folks, nothing interesting here.”