On 06/12/07 23:09, [EMAIL PROTECTED] wrote:
> also * ? !
I was wondering already about "Invalid characters *include*",
which to me means that there are probably more than these.
Ok, so far we have
. " / \ [ ] : ; = ,
* ? !
However, '!' is in the list of characters that can be used "as is"
right now, so where do you take it from that this character is also
Also: the '.' is perfectly ok, unless at the end of a directory name.
So, from my point of view the characters to be exchanged to "#XX"
" / \ [ ] : ; = , * ?
. at the end of a directory name
"The day Microsoft invents something that
doesn't suck, it will be a vacuum cleaner."
> -----Original Message-----
> Date: Tue, 12 Jun 2007 18:28:10 +0200
> Subject: Re: [vdr] VDR 1.5.3: UTF-8 vs. ExchangeChars()
> From: Stone
> To: "VDR Mailing List"
> On 6/12/07, KLAUS SCHMIDINGER wrote: 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.
> I use this FAT feature so I can mount my linux drive on windows and
> stream movies with vdradmin to my windows machine. I have noticed
> that VDR might currently be renaming a little more than is required.
> Invalid characters include: . " / [ ] : ; = ,
> http://support.microsoft.com/kb/142982  Regards.
vdr mailing list