<br><br>
<div><span class="gmail_quote">On 6/12/07, <b class="gmail_sendername">Klaus Schmidinger</b> <<a href="mailto:Klaus.Schmidinger@cadsoft.de">Klaus.Schmidinger@cadsoft.de</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">The function ExchangeChars() in VDR/recording.c converts characters<br>that can't be used in file names on Windows to "#XX", where XX is
<br>the hex code of the character.<br><br>This was simple when VDR only worked with single byte character sets,<br>but now that it can handle UTF-8 this needs to be changed, too.<br><br>Currently it has a list of characters that can be used "as is",
<br>and converts everything else to "#XX". I guess it is better<br>to convert any "disturbing" characters to "#XX" and leave the<br>rest untouched. However, this requires that we know exactly
<br>which characters can't be used with Windows.<br><br>Does anybody have that kind of information?<br>Or should this be done completely different?<br><br>Note that I don't use this feature myself, so unless there
<br>is some input from others, I won't be changing anything here.</blockquote>
<div> </div>
<div> </div>
<div>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:
</div>
<div> </div>
<div>
<div class="indent">. " / \ [ ] : ; = , </div>
<div class="indent"> </div>
<div class="indent"><a href="http://support.microsoft.com/kb/142982">http://support.microsoft.com/kb/142982</a></div>
<div class="indent"> </div>
<div class="indent">Regards.</div></div><br> </div><br>