Hi again,
Thanks for your input. They did push me in the right direction. Fortunately
a direction in which I used to be an expert in the old days.
BTW, sorry for not pointing out that I have seen the problem in Windows.
Fortunately you guessed it.
The problem turned out to be a combination of Lame not being a
Windows-program, but a MS-DOS program, and my controlling it from Windows.
What I actually do is that I write a batch file (.CMD file) with
potentially many calls to Lame.
Now, Windows uses the ANSI character set, whereas MS-DOS (and therefore
Lame) uses the ASCII character set. For English people the difference
between the two is not very visible (I guess). Most of the difference is in
national chars - our local chars are located in different places in ANSI
and ASCII.
In fact, there are really no national chars in ASCII. This is why IBM
and/or MS invented an extension of the ASCII character set, making it
possible to include national chars and to switch between different sets of
them. This mechanism is called code pages.
I realised that the file names I wrote to the batch files were very nice
looking when viewed from Windows, but ugly when viewed in a MS-DOS box.
The solution (well, I would rather call it a woraround...) to the problem
consists of two quite easy steps:
1) When writing the batch file from the Windows program I ensure a proper
translation to ASCII, code page 850 (or 865).
2) I include an extra first line in the batch file in which I set the code
page before Lame starts:
MODE CON CP SELECT=850
(code page 865 is for Denmark/Norway, #850 is for (most of) Western Europe,
as far as I remember)
This has worked very well for several hundred files now!
Thanks again for your help.
I hope the above can be of a little help to others as well.
./Kim
Hanne & Kim Andreasen
Snerlevej 3, DK-3000 Helsingør, Denmark
Tel. +45 49 21 04 17, mobile +45 40 60 82 88
On Tuesday, February 08, 2005 11:25 AM, Takehiro Tominaga
[SMTP:[EMAIL PROTECTED] wrote:
> From: "Kim S. Andreasen" <[EMAIL PROTECTED]>
> Subject: [mp3encoder] Lame & national chars
> Date: Mon, 7 Feb 2005 19:05:11 +0100
>
> > I can't get Lame (3.92 & 3.96) to dance with sound files having
non-English characters in their names. It simply ignores such files.
> > The same goes for ID3 tags. At best they get converted (my guess is
that the MSB gets stripped off).
>
> That is probabry the problem of your shell (like DOS-prompt).
>
> I have no problem with "my" national character (kanji and kana and
hira-gana),
> on my linux box.
> --
> Takehiro TOMINAGA // may the source be with you!
On Tuesday, February 08, 2005 12:05 PM, [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED] wrote:
> Hi Kim,
>
> - concerning the non-European letters in the file-name:
> I wonder whether it's a windows-problem. - I have the same problem when I
> use
> files (which my Asian colleague send me) on a Windows 2000
> operating-system.
>
> - for the ID3:
> did you check the character-byte of the ID3v2 entry?
> Each entry has its own header which contains one of the following
> character-bytes:
> 00 = ISO 8859-1 (= Latin 1)
> 01 = UTF 16, followed by an BOM-entry
> (BOM = byte-order-marker, which indicates whether LE or
> BE is used)
> 02 = UTF 16 BE
> 03 = UTF 8
>
> You can find the details about this ID3-headers at www.id3.org
>
> With regards
> Michael
> An:
"'mp3encoder@minnie.tuhs.org'"
> Kopie:
(Blindkopie: Michi Koch/WET/COMP/PHILIPS)
> Thema:
[mp3encoder] Lame & national chars
> Hi,
>
> I am brand new to this list, but I hope that somebody's able to help me:
>
> I can't get Lame (3.92 & 3.96) to dance with sound files having non-En
glish
> characters in their names. It simply ignores such files.
> The same goes for ID3 tags. At best they get converted (my guess is that
> the MSB gets stripped off).
>
> Does anybody know what to do (other than working with temporarily renamed
> files, which is doable, but cumbersome)?
>
> Thanks,
> ./Kim
___
mp3encoder mailing list
mp3encoder@minnie.tuhs.org
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
