Page 1 of 1

[EN] Cross 1.3.2 Character set?

PostPosted: 17 Jan 2010, 10:09
by Stealthii
It appears a few standard UTF-8/16 characters are not displayed in Mixvibes Cross (all versions are probably affected)

I have not tested this under Windows, only OSX for now.

, the album from Justice, uses a standard character which works as a folder name under Windows and OSX, and is supported by all applications, except Mixvibes.

Additionally, Mixvibes appears to mess up tags it cannot handle. For example, a track by Esmée Denters has had the artist renamed to Esmée Denters, simply by loading the track. (Do not judge me on this track, I need to have charts at all times for my work ;))

Thanks again

Re: [EN] Cross RC 1.3.2 Character set?

PostPosted: 17 Jan 2010, 10:13
by UncleVibes
For example, a track by Esmée Denters has had the artist renamed to Esmée Denters, simply by loading the track.

Strange for a french software we use a lot of special characters...
What do you think sylmv, do Cross use UTF8 ? If yes why this problem?

Re: [EN] Cross 1.3.2 Character set?

PostPosted: 17 Jan 2010, 17:14
by Stealthii
It appears that the tag itself, wasn't changed, but the display of it did. Ie. Esmée was displayed, but Esmée was still in the tag. Right now, upon resaving the tag, and reloading the application, the tag has not inexplicably changed. I am now trying to find out how to reproduce this. Bear with me.

The problem with ✝ still stands.

Re: [EN] Cross 1.3.2 Character set?

PostPosted: 18 Jan 2010, 11:48
by sylMV
Hi there !

Well, Cross internally uses UTF-8.

However, as most of the taggers allow any characters sets, we've tried to detect the encoding for each tag.
Unfortunately, the encoding detection is a pity ! It's quite impossible to be 100% sure of a decision with small text chunk (as in tags). This results in having some japanese characters (e.g) displayed instead of some "é" or "è", etc.

We're aware it's a real problem, and we'll find a solution !

Concerning the "✝", I must admit we never tested it ! I don't know if this char has any particularity. We'll check if it's a decoding issue or just a display issue (the font used might just not have this char ...).