i think we need a list of INVALID CHARACTERS and not inverted
-----Original Message-----
Date: Tue, 12 Jun 2007 17:46:39 +0200
Subject: VDR 1.5.3: UTF-8 vs. ExchangeChars()
From: Klaus Schmidinger <Klaus.Schmidinger@xxxxxxxxxx>
To: vdr@xxxxxxxxxxx
The function ExchangeChars() in VDR/recording.c converts characters
that can't be used in file names on Windows to "#XX", where XX is
the hex code of the character.
This was simple when VDR only worked with single byte character sets,
but now that it can handle UTF-8 this needs to be changed, too.
Currently it has a list of characters that can be used "as is",
and converts everything else to "#XX". I guess it is better
to convert any "disturbing" characters to "#XX" and leave the
rest untouched. However, this requires that we know exactly
which characters can't be used with Windows.
Does anybody have that kind of information?
Or should this be done completely different?
Note that I don't use this feature myself, so unless there
is some input from others, I won't be changing anything here.
Klaus
_______________________________________________
vdr mailing list
vdr@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
_______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr