You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2009-03-27.09:50:21.617>created_at=<Date2009-02-11.07:03:37.315>labels= ['expert-unicode']
title='Add KOI8-RU as a known encoding'updated_at=<Date2014-10-09.23:00:42.339>user='https://bugs.python.org/dwayne'
I found this file http://ra.dkuug.dk/i18n/charmaps/KOI8-RU. I
converted it to a format compatible with gencodec.py. Here is the
resulting file: copy it into <your python library>/encodings/.
it is currently only a proposed draft which hasn't been updated since 1997.
dwayne commented on Feb 13, 2009
dwaynemannequin
MannequinAuthor
More actions
@Haypo: The encoding works and doesn't throw and error, my guess is that
aliases should be updated to cover the variant namings of -R and -U.
I also found glibc points to this reference http://cad.ntu-kpi.kiev.ua/multiling/koi8-ru/ which seems to have
disappeared. I couldn't find a way to validate that the glibc code
points where the same as the ones you have.
My iconv --version is 2.9
Apart from that I can't vouch for its correctness
@lemburg: I can't comment on the status of the standard. I would assume
that like most 8 bit encodings that these are falling away and being
replaced by Unicode.
Why I'm interested in these issues is that our Python tools are used to
recover translations from installed .mo files on Linux. I look for
encoding issues on a semi-regularly basis and fix any ones that present
issues. This is the first I've found that is missing in Python.
For us its useful in that we present a path for people to move from an
old encoding into Unicode if needed.
@lemburg: I can't comment on the status of the standard.
I would assume that like most 8 bit encodings that these
are falling away and being replaced by Unicode.
Can I close this issue? Or do we have enough KOI8-RU users to include
this charset in Python?
I think that iconv is enough for people who need to convert their old
files to UTF-8 (or anything else).
"This charset wasn't supported by Ukrainian Internet community due to
political reasons; KOI8-U was invented as opposition to KOI8-RU."
Provided that resource is correct, it also appears that its inventor
Yuri Demchenko now switched to KOI8-U as well: http://staff.science.uva.nl/~demch/
So I guess, we can close this request and leave the codec attached to
the ticket for interested parties to download and install if they need it.
Activity
dwayne commentedon Feb 11, 2009
This could be broadened to see that we support all encodings that are
supported by iconv.
vstinner commentedon Feb 12, 2009
I found this file http://ra.dkuug.dk/i18n/charmaps/KOI8-RU. I
converted it to a format compatible with gencodec.py. Here is the
resulting file: copy it into <your python library>/encodings/.
vstinner commentedon Feb 12, 2009
Attach file used as gencodec.py input: koi8-ru.
dwayne: Does the result look correct?
vstinner commentedon Feb 12, 2009
My version of iconv (2.6.1) doesn't support KOI8-RU, only:
Note: python trunk doesn't support KOI8R nor KOI8U (which are just
aliases to KOI8-R and KOI8-U).
malemburg commentedon Feb 12, 2009
Could you please clarify the official status of this encoding. According
to this page:
http://www.terena.org/activities/multiling/koi8-ru/index.html
it is currently only a proposed draft which hasn't been updated since 1997.
dwayne commentedon Feb 13, 2009
@Haypo: The encoding works and doesn't throw and error, my guess is that
aliases should be updated to cover the variant namings of -R and -U.
I also found glibc points to this reference
http://cad.ntu-kpi.kiev.ua/multiling/koi8-ru/ which seems to have
disappeared. I couldn't find a way to validate that the glibc code
points where the same as the ones you have.
My iconv --version is 2.9
Apart from that I can't vouch for its correctness
@lemburg: I can't comment on the status of the standard. I would assume
that like most 8 bit encodings that these are falling away and being
replaced by Unicode.
Why I'm interested in these issues is that our Python tools are used to
recover translations from installed .mo files on Linux. I look for
encoding issues on a semi-regularly basis and fix any ones that present
issues. This is the first I've found that is missing in Python.
For us its useful in that we present a path for people to move from an
old encoding into Unicode if needed.
vstinner commentedon Mar 27, 2009
Can I close this issue? Or do we have enough KOI8-RU users to include
this charset in Python?
I think that iconv is enough for people who need to convert their old
files to UTF-8 (or anything else).
malemburg commentedon Mar 27, 2009
Viktor, I found this reference which has some background information
regarding koi8-ru and other cyrillic encodings:
http://segfault.kiev.ua/cyrillic-encodings/
"This charset wasn't supported by Ukrainian Internet community due to
political reasons; KOI8-U was invented as opposition to KOI8-RU."
Provided that resource is correct, it also appears that its inventor
Yuri Demchenko now switched to KOI8-U as well:
http://staff.science.uva.nl/~demch/
So I guess, we can close this request and leave the codec attached to
the ticket for interested parties to download and install if they need it.
serhiy-storchaka commentedon Jul 9, 2026
For the record:
KOI8-RUis now available through the iconv-based codec engine added in #152997 (PR #153001), on platforms whoseiconv()provides it.