Menu

#443 Alien characters - not possible to set right

Invalid
nobody
Medium
Defect
2018-08-20
2018-08-19
scrutinizer
No

Hello,

What steps will reproduce the problem?

  1. Change your system default locale to Russian one. Open the CUE file from the zipped folder by the link provided below. The CUE opens to the incorrect encoding of the French characters in the album's title.
  2. Click on "Get Metadata". Changes to the correct symbols however part of the title is missing
  3. Click on "Modify Metadata". Make changes appropriate changes in "Album" field for the title to take the structure you need, then click "OK". Result: incorrect encoding returns.

How about the reproducibility (always, sometimes, rarely, ...)? Always

What is the expected output? What do you see instead? Expected: French characters. Instead: Non-French characters.

What version of the product are you using? On what operating system? XLD 20170729 (150.3) on OS X 10.7.5

Please provide any additional information.

My primary encoding is Russian which is the default system locale.
I wrote a script that heavily depends on XLD's ability to map encoding correctly opening a CUE file. However it proved to be a dead end on achieving the desired result since initially upon opening a CUE whose text contains French characters like É, Ë (capital and small) they are subsituted with Asian characters (謗, 部). When I click on Get Metadata then symbols are mapped correctly however parts of the original album title which the very 1st CUE's line beginning with "TITLE" corresponds to are skipped which is not what I want. Me trying to modify the extracted metadata so that it would retain both correct French characters and the needed title results in reverting to the initially incorrect encoding with the Asian letters in words belonging to the album's title.

A few considerations:

  • Opening the CUE file in TextEdit which applies the default UTF8 encoding renders aforementioned French characters yet another unexpected characters. Opening the same file with Windows Latin 1 encoding renders correct characters.
  • To work around the issue and with the previous point in mind I use a shell script command that creates a copy of the CUE file in TXT format with Windows Latin 1 encoding that in turn is read as UTF8 by my script. I get it right now however I need it to match the lines on the Encoding pane it which it fails because of the method with which XLD encodes non-ASCII characters.
  • A link to download the zipped folder containing audio files bundled with the cue and the txt files.
    https://1drv.ms/u/s!Ar7_8hidDIZziFJb21WjjVc2fA3x

  • Here's anoter link - a video capture of the behavior
    https://d.docs.live.net/73860c9d18f2ffbe/Documents/XLD.mov

Please let me know if either of the links doesn't work and thank you for your many years of maintaining this wonderful program.

Discussion

  • tmkk

    tmkk - 2018-08-20

    Well, your cue file is encoded with ISO Latin-1. So You have to choose a proper encoding in XLD preference pane.

     
  • scrutinizer

    scrutinizer - 2018-08-20

    Oh, thank you. A user error.

     
  • tmkk

    tmkk - 2018-08-20
    • status: New --> Invalid
     

Log in to post a comment.

MongoDB Logo MongoDB