Bug 147054

Summary:	fails to show utf-8 encoded track information (international characters)
Product:	kscd	Reporter:	Olivier Vitrat <ovit.debian>
Component:	general	Assignee:	Alex Kern <alex.kern>
Status:	CONFIRMED ---
Severity:	normal	CC:	joerg.schilling
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:

Description Olivier Vitrat 2007-06-21 19:40:58 UTC

Version:            (using KDE KDE 3.5.5)
Installed from:    Debian stable Packages

Reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416549

If I play a CD which has CD-Text in UTF-8 format, the utf-8 encoded
information is shown as question marks in the Kscd
track information.

However, if I output that cd's track information using cdda2wav with "-J"
option, then the information is shown properly
in Konsole output, proving the data in the audio cd is okay.

I made a CD (output from a mixer was recorded in wav format) and put some
international characters in the title of the
tracks using easytag. That particular information (titles) is shown with
question makes in kscd, but the rest of the
information (artist, album, etc.) was put in English and is displayed
properly in kscd.

Hopefully, this is just a little problem and easily solved.

Comment 1 Alex Kern 2007-12-11 23:57:57 UTC

Can You please submit information about how this disk was created? I cannot found any hints in Internet, that CD-text standart defines any Language-ID for UTF-8 encoding, today as some years ago, as I first wrote support for it. Some burners applications can define some numbers at his own risk, but it will work so long they define the same ;-) And even this case: "it's not a standart".

Greetings
Alex

Comment 2 joerg.schilling 2013-12-19 14:46:41 UTC

Note that CD-Text cannot use UTF-8, it was defined to be based on ISO-8859-1

Comment 3 Justin Zobel 2021-03-10 00:32:20 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.