Export File List As CSV?

milo1012 · Post by *milo1012 » 2016-05-23, 17:45 UTC

Axxy wrote:All i get is a small black graphic where the letter should be.

Well, what program/editor do you use to view the file?
In most text editors, the rendering depends on the display font.

Anyway, this command will output a UTF-16 file, so to confirm this, open the output file in TC's Lister and switch to Unicode (= UTF-16) view (press "6"), and compare it to default non-Unicode view ("1"), or use some decent text editor, which will show you the detected file encoding.

Axxy · Post by *Axxy » 2016-05-23, 21:15 UTC

milo1012 wrote:
Axxy wrote:All i get is a small black graphic where the letter should be.
Well, what program/editor do you use to view the file?
In most text editors, the rendering depends on the display font.

Anyway, this command will output a UTF-16 file, so to confirm this, open the output file in TC's Lister and switch to Unicode (= UTF-16) view (press "6"), and compare it to default non-Unicode view ("1"), or use some decent text editor, which will show you the detected file encoding.

I've just done some checking. TC internal viewer, notepad and notepad+ all show a graphic or quotes instead of the accented letter. When I change to ASCII DOS charset in viewer, it displays it properly, it defaulted to ANSI Windows charset. It seems it's the audioinfo plugin issue not displaying the meta details properly.

milo1012 · Post by *milo1012 » 2016-05-24, 02:03 UTC

Axxy wrote:When I change to ASCII DOS charset in viewer, it displays it properly, it defaulted to ANSI Windows charset. It seems it's the audioinfo plugin issue not displaying the meta details properly.

Strange, all test I did with different custom columns views and cm_SaveDetailsToFile produced a valid UTF-16 file,
even when I tried AudioInfo with a column view for files with non-ASCII characters in their audio tags.
If there were problems, it was because the original audio file had a bad tag (e.g. a non-standard id3tag with UTF-16 instead of ISO-8859-1).
So yes, audioinfo seems to have problems with certain files, resulting in recoding issues, but this wouldn't explain why you are able to view a valid character in ASCII DOS (= OEM) encoding only.

Axxy · Post by *Axxy » 2016-05-25, 08:25 UTC

milo1012 wrote:
Axxy wrote:When I change to ASCII DOS charset in viewer, it displays it properly, it defaulted to ANSI Windows charset. It seems it's the audioinfo plugin issue not displaying the meta details properly.
Strange, all test I did with different custom columns views and cm_SaveDetailsToFile produced a valid UTF-16 file,
even when I tried AudioInfo with a column view for files with non-ASCII characters in their audio tags.
If there were problems, it was because the original audio file had a bad tag (e.g. a non-standard id3tag with UTF-16 instead of ISO-8859-1).
So yes, audioinfo seems to have problems with certain files, resulting in recoding issues, but this wouldn't explain why you are able to view a valid character in ASCII DOS (= OEM) encoding only.

Windows 10 thing? Tbh, I never noticed anything like this in Win7...