On 05/03/2013 01:22 AM, Lorenzo Marcantonio wrote:
> On Thu, May 02, 2013 at 11:20:09PM -0500, Dick Hollenbeck wrote:
>> We introduced a patch today which introduces UTF8 encoding into a couple of
>> source files,
>> then made a policy decision to allow UTF8 string constants in 8 bit strings.
>>
We introduced a patch today which introduces UTF8 encoding into a couple of
source files,
then made a policy decision to allow UTF8 string constants in 8 bit strings.
So this is
currently about 3 places only, nothing to worry about yet.
The only time you can be sure you have an 8 bit string is
On Fri, May 03, 2013 at 10:07:30AM +0200, Edwin van den Oetelaar wrote:
> #! /usr/bin/env python
> # -*- coding: utf-8 -*-
That the vim (or emacs or both) magic string, which can set a lot of
stuff (also indentation parameters)
> The encoding should be on first or second line, so the python parse
On May 3, 2013, at 8:26 AM, Lorenzo Marcantonio
wrote:
> On Fri, May 03, 2013 at 09:12:50AM +0200, Edwin van den Oetelaar wrote:
>> I checked the patch with GEdit, Vim, Geany, Notepad and HexEdit.
>> The original text shows as a mu sign ( in html μ )
>> changes the text into an A circumflex (
Thanks for your detailed explanation.
In my other code I put this : ( off topic joke )
(according to http://www.python.org/dev/peps/pep-0263/ )
#! /usr/bin/env python
# -*- coding: utf-8 -*-
The encoding should be on first or second line, so the python parsers
(and editors) can find it.
I found t
On Fri, May 03, 2013 at 09:43:29AM +0200, Edwin van den Oetelaar wrote:
> Flashback : It reminds me of the problems that existed with
> web-browsers, when people pasted stuff from their text-editor (like
> Word) into html textarea boxes to publish articles... oh the old days.
More or less the same
2013/5/3 Lorenzo Marcantonio :
> On Fri, May 03, 2013 at 09:12:50AM +0200, Edwin van den Oetelaar wrote:
>> I checked the patch with GEdit, Vim, Geany, Notepad and HexEdit.
>> The original text shows as a mu sign ( in html μ )
>> changes the text into an A circumflex ( in html  ) followed by
>> a
On Fri, May 03, 2013 at 09:12:50AM +0200, Edwin van den Oetelaar wrote:
> I checked the patch with GEdit, Vim, Geany, Notepad and HexEdit.
> The original text shows as a mu sign ( in html μ )
> changes the text into an A circumflex ( in html  ) followed by
> a mu sign.
>
> In Hex it shows : 0xB5
I checked the patch with GEdit, Vim, Geany, Notepad and HexEdit.
The original text shows as a mu sign ( in html μ )
changes the text into an A circumflex ( in html  ) followed by
a mu sign.
In Hex it shows : 0xB5 0x6D changed into 0xC2 0xB5 0x6D ( where 0xC2
is the A circumflex)
my environment
On Thu, May 02, 2013 at 11:20:09PM -0500, Dick Hollenbeck wrote:
> We introduced a patch today which introduces UTF8 encoding into a couple of
> source files,
> then made a policy decision to allow UTF8 string constants in 8 bit strings.
> So this is
> currently about 3 places only, nothing to w
We introduced a patch today which introduces UTF8 encoding into a couple of
source files,
then made a policy decision to allow UTF8 string constants in 8 bit strings.
So this is
currently about 3 places only, nothing to worry about yet.
The only time you can be sure you have an 8 bit string is
11 matches
Mail list logo
