On 2010-08-13 11:39:43 +0200, Stefan Sperling wrote:
> Yes, I see the difference. It's a question of where the primary
> configuration knob for the charset is located.
>
> Right now, the source of charset information is always the locale.
>
> You want it to be the locale at checkout time and some
On 2010-08-13 11:18:00 +0200, Stefan Sperling wrote:
> On Fri, Aug 13, 2010 at 09:37:57AM +0200, Vincent Lefevre wrote:
> > On 2010-08-13 08:16:48 +0200, Alexander Skwar wrote:
> > > 2010/8/13 Vincent Lefevre
> > > >
> > > > On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
> > >
> > > > > ~/b
On 2010-08-13 09:47:37 +0200, Alexander Skwar wrote:
> Well, if you want or need to parse the output of a program,
> you'll need to make sure that it's in the "correct" locale. The
> way to do that, is by setting the locale variables to the expected
> values. Thus, it's totally correct to set LC_CT
On Fri, Aug 13, 2010 at 12:27:30AM +0200, Vincent Lefevre wrote:
> On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
> > Using UTF-8 instead of the recorded charset is out of the question.
> > That leaves erroring out as the only option. So how is that
> > different from the current situation?
>
On Fri, Aug 13, 2010 at 09:37:57AM +0200, Vincent Lefevre wrote:
> On 2010-08-13 08:16:48 +0200, Alexander Skwar wrote:
> > 2010/8/13 Vincent Lefevre
> > >
> > > On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
> >
> > > > ~/bin/mysvn:
> > > > #!/bin/sh
> > > > env LC_CTYPE="en_US." svn upd
Hi.
2010/8/13 Vincent Lefevre :
> On 2010-08-13 08:16:48 +0200, Alexander Skwar wrote:
>> 2010/8/13 Vincent Lefevre
>> >
>> > On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
>>
>> > > ~/bin/mysvn:
>> > > #!/bin/sh
>> > > env LC_CTYPE="en_US." svn update
>> >
>> > Wrong, wrong, wrong! Secur
On 2010-08-13 08:16:48 +0200, Alexander Skwar wrote:
> 2010/8/13 Vincent Lefevre
> >
> > On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
>
> > > ~/bin/mysvn:
> > > #!/bin/sh
> > > env LC_CTYPE="en_US." svn update
> >
> > Wrong, wrong, wrong! Security hole!
>
> No, not wrong, but totally c
Hi.
2010/8/13 Vincent Lefevre
>
> On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
> > ~/bin/mysvn:
> > #!/bin/sh
> > env LC_CTYPE="en_US." svn update
>
> Wrong, wrong, wrong! Security hole!
No, not wrong, but totally correct - especially, if you need to parse the
output in some script, y
On 2010-08-12 17:16:37 +0200, Stefan Sperling wrote:
> On Thu, Aug 12, 2010 at 02:30:50AM +0200, Vincent Lefevre wrote:
> > On 2010-08-11 19:56:28 +0200, Stefan Sperling wrote:
> > > On Wed, Aug 11, 2010 at 04:29:56PM +0200, Vincent Lefevre wrote:
> > > > You're forcing the user to use a UTF-8 loca
On Thu, Aug 12, 2010 at 02:30:50AM +0200, Vincent Lefevre wrote:
> On 2010-08-11 19:56:28 +0200, Stefan Sperling wrote:
> > On Wed, Aug 11, 2010 at 04:29:56PM +0200, Vincent Lefevre wrote:
> > > You're forcing the user to use a UTF-8 locale. Unacceptable.
> >
> > No, we leave users a choice.
>
>
Olivier Sannier wrote:
Csaba Raduly wrote:
On Wed, Aug 11, 2010 at 4:49 PM, Michael Pruemm wrote:
But don't forget that different platforms may use different UTF-8
encodings
for the same filename.
Huh? There's only one UTF-8 encoding for each Unicode code point. Are
you thinking of c
On 2010-08-12 09:59:30 +0200, Csaba Raduly wrote:
> On Wed, Aug 11, 2010 at 4:49 PM, Michael Pruemm wrote:
> > Vincent Lefevre wrote:
> (snip)
> >> Under these conditions, the only possibility is
> >> to encode the filenames in UTF-8 anyway. So, why not enforcing
> >> that?
> >>
> >
> > But don't
Csaba Raduly wrote:
On Wed, Aug 11, 2010 at 4:49 PM, Michael Pruemm wrote:
Vincent Lefevre wrote:
(snip)
Under these conditions, the only possibility is
to encode the filenames in UTF-8 anyway. So, why not enforcing
that?
But don't forget that different platforms may u
On Wed, Aug 11, 2010 at 4:49 PM, Michael Pruemm wrote:
> Vincent Lefevre wrote:
(snip)
>> Under these conditions, the only possibility is
>> to encode the filenames in UTF-8 anyway. So, why not enforcing
>> that?
>>
>
> But don't forget that different platforms may use different UTF-8 encodings
>
On 2010-08-11 19:56:28 +0200, Stefan Sperling wrote:
> On Wed, Aug 11, 2010 at 04:29:56PM +0200, Vincent Lefevre wrote:
> > You're forcing the user to use a UTF-8 locale. Unacceptable.
>
> No, we leave users a choice.
The choice doesn't work.
> I consider your idea of forcing UTF-8 filenames on
On 2010-08-11 17:34:19 +0200, Paul Ebermann wrote:
> Vincent Lefevre wrote:
> > That's wrong. GNOME let's me to use any locale in shell sessions.
> > Subversion doesn't.
>
> Yes, but GNOME does not allow using any locale in a file manager
> session (or, it ignores the locale in the filemanager ses
On 2010-08-11 19:55:01 +0200, Stefan Sperling wrote:
> On Wed, Aug 11, 2010 at 05:23:31PM +0200, Vincent Lefevre wrote:
> > On 2010-08-11 16:26:32 +0200, Vincent Lefevre wrote:
> > > Configuring a UTF-8 locale can yield non-portable behavior.
>
> Such as?
Outputting messages in a different langua
On Wed, Aug 11, 2010 at 04:29:56PM +0200, Vincent Lefevre wrote:
> You're forcing the user to use a UTF-8 locale. Unacceptable.
No, we leave users a choice.
I consider your idea of forcing UTF-8 filenames on everybody unacceptable.
Stefan
On Wed, Aug 11, 2010 at 05:23:31PM +0200, Vincent Lefevre wrote:
> On 2010-08-11 16:26:32 +0200, Vincent Lefevre wrote:
> > Configuring a UTF-8 locale can yield non-portable behavior.
Such as?
> > There's a good reason why various scripts do a "LC_ALL=C".
Then those scripts are written for proje
Vincent Lefevre wrote:
> On 2010-08-11 13:51:18 +0200, Stefan Sperling wrote:
>> On Wed, Aug 11, 2010 at 12:35:59PM +0200, Vincent Lefevre wrote:
>>> Yes, and this is another reason why the solution chosen by Subversion
>>> doesn't work well. For instance, GNOME always uses UTF-8 for filename
>>>
On 2010-08-11 16:26:32 +0200, Vincent Lefevre wrote:
> On 2010-08-11 13:42:35 +0200, Stefan Sperling wrote:
> > On Wed, Aug 11, 2010 at 12:31:48AM +0200, Vincent Lefevre wrote:
> > > On 2010-08-10 20:59:00 +0200, Stefan Sperling wrote:
> > > > Right now, if the filename cannot be represented in the
On 2010-08-11 16:49:46 +0200, Michael Pruemm wrote:
> But don't forget that different platforms may use different UTF-8
> encodings for the same filename. Mac OS X encodes accented
> characters in filenames in a different way than Linux.
Yes, but that's another problem, for which I think that the
Vincent Lefevre wrote:
However, I'd expect many will just assume that the user wants filenames
to be encoded according to the current locale.
If everybody follows this convention, there is no problem, apart from
user errors during locale configuration.
You're asking the user, and even all users
On 2010-08-11 16:20:38 +0200, Alexander Skwar wrote:
> 2010/8/11 Vincent Lefevre
> > Yes, and this is another reason why the solution chosen by Subversion
> > doesn't work well. For instance, GNOME always uses UTF-8 for filename
> > encoding. So, if the user uses ISO-8859-* locales (for shell sess
On 2010-08-11 13:51:18 +0200, Stefan Sperling wrote:
> On Wed, Aug 11, 2010 at 12:35:59PM +0200, Vincent Lefevre wrote:
> > On 2010-08-11 11:11:25 +0200, Paul Ebermann wrote:
> > > The thing is, users are using other tools than SVN to work with the
> > > files, too.
> > >
> > > So if I look at my
On 2010-08-11 13:42:35 +0200, Stefan Sperling wrote:
> On Wed, Aug 11, 2010 at 12:31:48AM +0200, Vincent Lefevre wrote:
> > On 2010-08-10 20:59:00 +0200, Stefan Sperling wrote:
> > > Right now, if the filename cannot be represented in the current locale,
> > > you get this error: "svn: Can't conver
Hi.
2010/8/11 Vincent Lefevre
>
> Yes, and this is another reason why the solution chosen by Subversion
> doesn't work well. For instance, GNOME always uses UTF-8 for filename
> encoding. So, if the user uses ISO-8859-* locales (for shell sessions),
> one gets inconsistencies.
>
>
>
Just curious
On Wed, Aug 11, 2010 at 12:35:59PM +0200, Vincent Lefevre wrote:
> On 2010-08-11 11:11:25 +0200, Paul Ebermann wrote:
> > The thing is, users are using other tools than SVN to work with the
> > files, too.
> >
> > So if I look at my directory with a file manager, I want my
> > filenames to be read
On Wed, Aug 11, 2010 at 12:31:48AM +0200, Vincent Lefevre wrote:
> On 2010-08-10 20:59:00 +0200, Stefan Sperling wrote:
> > Right now, if the filename cannot be represented in the current locale,
> > you get this error: "svn: Can't convert string from 'UTF-8' to native
> > encoding"
>
> which is
On 2010-08-11 11:11:25 +0200, Paul Ebermann wrote:
> The thing is, users are using other tools than SVN to work with the
> files, too.
>
> So if I look at my directory with a file manager, I want my
> filenames to be readable (and renameable). The idea is that usually
> the user uses for one worki
Vincent Lefevre wrote:
> On 2010-08-10 20:59:00 +0200, Stefan Sperling wrote:
>
>> The native encoding is determined by the locale, but that does not matter.
>> The point is that, wherever encoding configuration happens to come from,
>> if the configured encoding cannot represent the character stri
On 2010-08-10 20:59:00 +0200, Stefan Sperling wrote:
> On Tue, Aug 10, 2010 at 07:44:35PM +0200, Vincent Lefevre wrote:
> > This is easy (at least from the specification point of view): once the
> > encoding has been determined[*], typically at checkout time, store the
> > encoding in the WC metada
On Tue, Aug 10, 2010 at 07:44:35PM +0200, Vincent Lefevre wrote:
> On 2010-08-10 17:42:57 +0200, Stefan Sperling wrote:
> > There are extensions in some systems like Linux, where filename encoding
> > can be specified at mount time and a process can query this information.
> > But the actual encodi
On 2010-08-10 17:42:57 +0200, Stefan Sperling wrote:
> The locale only matters when data is presented to the user (by the svn
> client, or svnlook, or svnadmin, ...) in which case Subversion uses iconv
> to translate the UTF-8 data into the character set of the current locale.
The svn client also
On Tue, Aug 10, 2010 at 04:59:58PM +0200, Vincent Lefevre wrote:
> On 2010-08-09 19:30:00 +0300, Daniel Shahaf wrote:
> > In the repository filesystem, we use UTF-8 exclusively. APR handles
> > translating that UTF-8 to whatever the local OS supports.
>
> Which is meaningless, since under Unix, t
On 2010-08-09 19:30:00 +0300, Daniel Shahaf wrote:
> In the repository filesystem, we use UTF-8 exclusively. APR handles
> translating that UTF-8 to whatever the local OS supports.
Which is meaningless, since under Unix, the locale is not related
to the OS, but to the process: one can have a shel
To
> Suman MAINAM
> cc
> users
> Subject
> Re: svn checkout - special characters in file name are not encoding
> properly
>
>
>
>
>
>
> (I'm going to handle just the "svn repository" potential cause of the
> pro
characters in file name are not encoding
properly
(I'm going to handle just the "svn repository" potential cause of the
problem. I'll let others handle the "client-side problem, but repository
is
okay" potential cause.)
suman.mai...@asia.bnpparibas.com wr
> -Original Message-
> From: Alexander Skwar [mailto:a.sk...@gmail.com] On Behalf Of Alexander
> Skwar
> Sent: maandag 9 augustus 2010 18:23
> To: Daniel Shahaf
> Cc: suman.mai...@asia.bnpparibas.com; users@subversion.apache.org
> Subject: Re: svn checkout - speci
Alexander Skwar wrote on Mon, Aug 09, 2010 at 18:22:57 +0200:
> Hi.
>
>
> Am 09.08.2010 um 17:31 schrieb Daniel Shahaf :
>
>>
>>
>> suman.mai...@asia.bnpparibas.com wrote on Mon, Aug 09, 2010 at
>> 11:42:04 +0530:
>>> Hi,
>>> I'm working on French project. Very recently we have migrated our
>>>
Hi.
Am 09.08.2010 um 17:31 schrieb Daniel Shahaf :
suman.mai...@asia.bnpparibas.com wrote on Mon, Aug 09, 2010 at
11:42:04 +0530:
Hi,
I'm working on French project. Very recently we have migrated our
project
from CVS to SVN repository. After migration, when checking out the
file
names
(I'm going to handle just the "svn repository" potential cause of the
problem. I'll let others handle the "client-side problem, but repository is
okay" potential cause.)
suman.mai...@asia.bnpparibas.com wrote on Mon, Aug 09, 2010 at 11:42:04 +0530:
> Hi,
> I'm working on French project. Very rece
Hi,
I'm working on French project. Very recently we have migrated our project
from
CVS to SVN repository. After migration, when checking out the file names
which
have special characters like Western-Europe encoding fonts are giving
problem.
e.g.:"modŠle fields-replacements.xsl" is the file name
43 matches
Mail list logo
