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/2002-February/020527.html below:

[Python-Dev] PEP 263 -- Python Source Code Encoding)

Japanese codecs (was Re: [Python-Dev] PEP 263 -- Python Source Code Encoding)Barry A. Warsaw barry@zope.com
Thu, 28 Feb 2002 11:17:01 -0500
[This thread probably ought to be moved to i18n-sig, so I'm CC'ing
them and will remove all future cc's to python-dev.  -BAW]

>>>>> "MAL" == M  <mal@lemburg.com> writes:

    MAL> You could (and probably should) add Tamito's codecs in
    MAL> Python, but the others have licensing problems :-/

I believe I am using Tamito KAJIYAMA's codecs, from:

    http://pseudo.grad.sccs.chukyo-u.ac.jp/~kajiyama/python/

Or were you thinking about some different Japanese codecs?  The ones
at this url are BSD-ish and so should be compatible with the PSF
license, GPL, etc.

    MAL> It shouldn't be hard though for native speakers and
    MAL> programmers to build upon the work of Tamito and get those
    MAL> codecs done as well. Alternatively, the PSF or some company
    MAL> interested in having these codecs available could fund the
    MAL> development.

All good points.  I still think that by giving more visibility to the
codecs (i.e. adding them to the Python distro) would help bring muscle
to the effort.

>>>>> "MvL" == Martin v Loewis <martin@v.loewis.de> writes:

    MvL> I would not recommend to incorporate any of this into Python
    MvL> without asking the author(s). When doing so, it would be
    MvL> appropriate, IMO, to ask them whether they would fill out the
    MvL> contributor agreement. Then, the presumed licensing problems
    MvL> would be gone.

Agreed on both points!

-Barry



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