A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-February/012723.html below:

[Python-Dev] Pre-PEP: Python Character Model

[Python-Dev] Pre-PEP: Python Character Model [Python-Dev] Pre-PEP: Python Character ModelM.-A. Lemburg mal@lemburg.com
Wed, 07 Feb 2001 13:23:50 +0100
Fredrik Lundh wrote:
> 
> Neil Hodgson wrote:
> >    Matz: "We don't believe there can be any single characer-encoding that
> > encompasses all the world's languages.  We want to handle multiple encodings
> > at the same time (if you want to)."
> 
> neither does the unicode designers, of course: the point
> is that unicode only deals with glyphs, not languages.
> 
> most existing japanese encodings also include language info,
> and if you don't understand the difference, it's easy to think
> that unicode sucks...
> 
> I'd say we need support for *languages*, not more internal
> encodings.

>>> print "Hello World!".encode('ascii','German')
Hallo Welt!

Nice thought ;-)

Seriously, do you think that these issues are solvable at the
programming language level ? I think that the information needed
to fully support language specific notations is much too complicated
to go into the Python core. This should be left to applications
and add-on packages to figure out.

-- 
Marc-Andre Lemburg
______________________________________________________________________
Company:                                        http://www.egenix.com/
Consulting:                                    http://www.lemburg.com/
Python Pages:                           http://www.lemburg.com/python/



RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4