The issue isn't whether or not there is software available to guess
encodings, but whether we want to assume the burden of integrating
such software and dealing with the inevitable bug reports that will
result when it makes a) the wrong guess, or b) the right but
unexpected guess.
Right now, we have to handle occasional bug reports about unguessed
encodings, but our responses can be simple: they boil down to "change
your locale, change the encoding, or pass --encoding".
If our responses have to get more complex, that's lost time. Since
it's pretty easy for users to do one of the above anyway, I think the
status quo strikes a good balance for this stage of Subversion's
development.
-Karl
"Han The Man" <hantheman12@hotmail.com> writes:
> Really?
>
> Commercial: IntelliScope Retrieval Toolkik
>
> Free:
>
> TextCat:
> http://odur.let.rug.nl/~vannoord/TextCat/
>
> Mozilla universal charset detector:
> http://lxr.mozilla.org/seamonkey/source/extensions/universalchardet/
>
> See also:
> http://www.unicode.org/iuc/iuc19/a322.html
> http://www.i18ngurus.com/docs/998504805.html
>
> _________________________________________________________________
> Hotmail snakker ditt språk!
> http://www.hotmail.msn.com/cgi-bin/sbox?rru=dasp/lang.asp - Få Hotmail
> på norsk i dag
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 29 08:37:52 2003