cdda2wav lacks utf-8 or unicode support?

Hello,

I have made an audio CD from some music we recorded. The tracks
information contains some unicode text. Vorbiscomment and metaflac
commands display the track's information of ogg and flac files correctly
in konsole (so the locale settings are correct and necessary fonts are
installed). However, after burning the audio CD, the following command
shows question marks instead of non-English characters (but English text
is shown properly):
$> cdda2wav -JH dev=/dev/hdd

This is the same session of konsole in which vorbiscomment and metaflac
commands output the characters properly. Does cdda2wav not support utf-8
or unicode characters? Or am I missing something?

As far as I now, my locale is also set properly:
$> set | grep LANG
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en_US:en_GB:en

Also, this on Debian Testing, fully updated.

thanks,
->HS

--

0

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

cdda2wav lacks utf-8 or unicode support?

H.S. wrote:
>
> Hello,
>
> I have made an audio CD from some music we recorded. The tracks
> information contains some unicode text. Vorbiscomment and metaflac
> commands display the track's information of ogg and flac files correctly
> in konsole (so the locale settings are correct and necessary fonts are
> installed). However, after burning the audio CD, the following command
> shows question marks instead of non-English characters (but English text
> is shown properly):
> $> cdda2wav -JH dev=/dev/hdd
>
> This is the same session of konsole in which vorbiscomment and metaflac
> commands output the characters properly. Does cdda2wav not support utf-8
> or unicode characters? Or am I missing something?
>
> As far as I now, my locale is also set properly:
> $> set | grep LANG
> LANG=en_CA.UTF-8
> LANGUAGE=en_CA:en_US:en_GB:en
>
> Also, this on Debian Testing, fully updated.
>
> thanks,
> ->HS
>
>
>

I forgot to add. The audio CD was burned using k3b. When the flac files
were included in the audio cd project, k3b showed unicode characters
properly.

So something could have gone wrong during burning the data to the cd, or
something is going wrong when cdda2wav reads data from the cd. I have a
hunch k3b is not to be blamed and the latter case is the problem.

->HS

--

cdda2wav lacks utf-8 or unicode support?

On Sat, 2007-03-31 at 20:20 -0400, H.S. wrote:
> I have made an audio CD from some music we recorded. The tracks
> information contains some unicode text. Vorbiscomment and metaflac
> commands display the track's information of ogg and flac files correctly
> in konsole (so the locale settings are correct and necessary fonts are
> installed). However, after burning the audio CD, the following command
> shows question marks instead of non-English characters (but English text
> is shown properly):
> $> cdda2wav -JH dev=/dev/hdd
>
> This is the same session of konsole in which vorbiscomment and metaflac
> commands output the characters properly. Does cdda2wav not support utf-8
> or unicode characters? Or am I missing something?

Hi,

I found this,

"Unfortunately, the CD Text standard supports only two character
encodings (ASCII and ISO Latin Modified 1), which, in practice,
means that it cannot be used for non-Latin languages, such as
Japanese."

http://www.xowave.com/doc/ref/metadata.shtml (The description is from
some Mac app, but I think it's general for CD-Text).

I guess cdda2wav (it's icedax really) expects the data to be ASCII or
Latin 1, maybe k3b should convert the text before burning the cd? Could
be a good idea to discuss this with the k3b developers.

--
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 760BDD22

Syndicate content