Hello, <br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">However Andrej's "crude user logic" (;-)) has shown the problem with<br>
that strategy.</blockquote><div><br>The end-user is eternally grateful for noticing ;-)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Okay, folks, what do you think? One of these Strategy 2 options, or<br>
yet a different Strategy?</blockquote><div><br>Which one will let me back up my files? That one is the best :-)<br><br>Consider adding different approaches that user can choose as appropriate at run-time using configuration file or command line options.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
By the way, Andrej, the reason that we were earlier proposing to do<br>
Strategy 1, which Francois's patch implemented, and which rejects<br>
yout filename is because Tahoe can't know whether that filename will<br>
come out as gibberish in certain views, such as the ls/nautilus/<br>
konqueror that you mentioned, or if you share the file with a<br>
friend. However, I guess in this case it is better to pass the data<br>
through and let it be Someone Else's Problem.<br>
</blockquote></div><br>That's the one... :-) You can rest assured that 100% of crude end-users will choose to have a first picture of there baby with gibberish file name, instead of not having it at all.<br><br>Is it realistic to hope to be able to back up my files with current state of the file names in the next 7 days or so?<br>
<br>-- <br>Andrej Falout<br>AU: +61 (410) 463 735 NZ: +64 (21) 0256 6825 US: +1 (360) 488 0970<br>