Comment 3 for bug 488519

<poolie> 1- in most cases, the filename is valid but the filename encoding is not set properly
<poolie> eg on unix filenames are normally going to be utf-8 but in this case we seem to be detecting it as ascii
<poolie> so that could be about better detection or better defaults or perhaps (last resort) having a configuration for it
<poolie> 2- in some cases the user really may have a file that does not fit with the encoding of their tree
<poolie> and then i guess we should...
<poolie> i wonder
<poolie> i think ideally we would just tolerate it if it was an ignored file

<parthm> poolie: i saw another ticket by you saying we need a config option for bazaar.conf. maybe that should be fixed first?
<parthm> poolie: bug #538925
<ubot5> Launchpad bug 538925 in Bazaar "want configuration option for filesystem encoding (affected: 1, heat: 6)" [Medium,Confirmed] https://launchpad.net/bugs/538925
<poolie> i would do #1 then bug 538925 then #2