[Sugar-devel] Unicode strings in translations

[Martin Langhoff]

On Mon, Aug 13, 2012 at 7:15 PM, S. Daniel Francis
<francis at sugarlabs.org> wrote:
> I look some people is needing to know more about Unicode:

Hi danielf,

one thing to keep in mind is that UTF-8 is one of the possible ways to
represent Unicode data. We will, most of the time, use UTF-8 mixed up
with straight old ASCII. Our python code files are one example.

But that is actually a bit of a trick. A very practical, pragmatic
trick -- for example: we mostly didn't need a major rewrite of our
text editors, or script parsers. That's great. But at the same time,
we pay for it with a degree of ambiguity (is it an ASCII encoded file,
or is it a UTF-8 encoded file?).

So what we are out to do here is to reduce the ambiguity, declaring in
all the relevant spots that these are UTF-8.

The BOM header didn't become popular (for good technical reasons). Is
there a way to tell the Python interpreter that assume that our code
(inc strings in our code) should be assumed to be unicode? If so, we
can set that in sugar-session.

cheers,



m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- Software Architect - OLPC
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff