Re: [Python-Dev] UTF8 in the PEP branch

2007-10-15 Thread Scott Dial
Facundo Batista wrote: > In the PEP text (example: > > http://svn.python.org/view/peps/trunk/pep-0002.txt?rev=56077&view=auto > > ), it says "Last-Modified: $Date$". That $Date$ is being translated in > the checkout or update by subversion. Maybe there is a $C-locale-Date$ > for subversion to a

Re: [Python-Dev] UTF8 in the PEP branch

2007-10-14 Thread Martin v. Löwis
>>> - Find a way to specify something in the original PEP file so SVN >>> translates always the dates in English. >> Are you sure you are talking about the file that contains the >> PEP itself? Or are you perhaps talking about the source code of >> docutils? > > In the PEP text (example: > > ht

Re: [Python-Dev] UTF8 in the PEP branch

2007-10-14 Thread Facundo Batista
2007/10/12, "Martin v. Löwis" <[EMAIL PROTECTED]>: > > - Find a way to specify something in the original PEP file so SVN > > translates always the dates in English. > > Are you sure you are talking about the file that contains the > PEP itself? Or are you perhaps talking about the source code of >

Re: [Python-Dev] UTF8 in the PEP branch

2007-10-12 Thread Martin v. Löwis
> Looking the file through the web browser, I see: > > Version: $Revision$ > Last-Modified: $Date$ > > So, SVN is touching that. I guess that that is actually the idea, but > is breaking thing for us-non-7bits-speakers, :) Please read about the svn:keywords feature, and yes, that is the idea

Re: [Python-Dev] UTF8 in the PEP branch

2007-10-12 Thread Facundo Batista
2007/10/12, "Martin v. Löwis" <[EMAIL PROTECTED]>: > I believe it's subversion that is doing something wrong. In my copy > of the file, I get > > # Contact: [EMAIL PROTECTED] > # Revision: $Revision: 4152 $ > # Date: $Date: 2005-12-08 00:46:30 +0100 (Do, 08 Dez 2005) $ Looking the file through th

Re: [Python-Dev] UTF8 in the PEP branch

2007-10-12 Thread Martin v. Löwis
> # Date: $Date: 2005-12-07 20:46:30 -0300 (mié, 07 dic 2005) $ > > A *lot* of files failed this way. I started to fix them (-*- coding > -*- line at the start), but then I thought that maybe *I* was doing > something wrong, because it's strange that nobody noticed this > before... > > So, shal