Den tors 22 dec. 2022 kl 23:40 skrev Karl Berry :
> Clearly those UTF-8 code points cannot be "converted" by svn to the
> 7-bit ASCII locale that is "C". Fine; I don't expect it to. Is there a
> way to force svn to complete the checkout anyway? That is, just check
> out the file and let the name
Karl Berry wrote on Thu, 22 Dec 2022 22:40 +00:00:
> A file with a name that has some "eight-bit" UTF-8 bytes (fn...-utf8.tex)
> was committed to one of my repositories. When I try to check it out in
> the C locale, svn complains:
>
> $ echo $LC_ALL
> C
> $ svn update
> svn: E22: Can't convert
Daniel Sahlberg wrote on Fri, 23 Dec 2022 08:58 +00:00:
> Example: Commit a file with ? (questionmark) in the filename on Linux and
> checkout the file on Windows.
Or case-colliding files:
url=`svn info --show-item=url`
svn mkdir -- $url/foo $url/FOO
svn up
> This is a case where a conversion mi
On Fri, Dec 23, 2022 at 3:58 AM Daniel Sahlberg
wrote:
>
> Den tors 22 dec. 2022 kl 23:40 skrev Karl Berry :
>>
>> Clearly those UTF-8 code points cannot be "converted" by svn to the
>> 7-bit ASCII locale that is "C". Fine; I don't expect it to. Is there a
>> way to force svn to complete the chec
Perhaps «export LC_ALL=C.UTF-8», if your platform has that encoding?
Yes, thanks, that is one of the workarounds. But that's not my
question.
My question is, why can't svn just treat the filenames as bytes? I
remain baffled by the need to unconditionally convert to/from UTF-8 (or
any other
