traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
cpython/Lib/test/test_gettext.py

954 lines
41 KiB
Python
Raw Normal View History

Test suite for new gettext.py module.
2000-08-25 16:14:25 -03:00
import os
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
import base64
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
import contextlib
Test suite for new gettext.py module.
2000-08-25 16:14:25 -03:00
import gettext
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
import locale
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
import unittest
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
#2621 rename test.test_support to test.support
2008-05-20 18:35:26 -03:00
from test import support
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
Make reindent.py happy (convert everything to 4-space indents!).
2000-10-23 14:22:08 -03:00
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# TODO:
# - Add new tests, for example for "dgettext"
# - Remove dummy tests, for example testing for single and double quotes
# has no sense, it would have if we were testing a parser (i.e. pygettext)
# - Tests should have only one assert.
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
Changes in anticipation of stricter str vs. bytes enforcement.
2007-08-27 14:23:59 -03:00
GNU_MO_DATA = b'''\
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
3hIElQAAAAAJAAAAHAAAAGQAAAAAAAAArAAAAAAAAACsAAAAFQAAAK0AAAAjAAAAwwAAAKEAAADn
AAAAMAAAAIkBAAAHAAAAugEAABYAAADCAQAAHAAAANkBAAALAAAA9gEAAEIBAAACAgAAFgAAAEUD
AAAeAAAAXAMAAKEAAAB7AwAAMgAAAB0EAAAFAAAAUAQAABsAAABWBAAAIQAAAHIEAAAJAAAAlAQA
AABSYXltb25kIEx1eHVyeSBZYWNoLXQAVGhlcmUgaXMgJXMgZmlsZQBUaGVyZSBhcmUgJXMgZmls
ZXMAVGhpcyBtb2R1bGUgcHJvdmlkZXMgaW50ZXJuYXRpb25hbGl6YXRpb24gYW5kIGxvY2FsaXph
dGlvbgpzdXBwb3J0IGZvciB5b3VyIFB5dGhvbiBwcm9ncmFtcyBieSBwcm92aWRpbmcgYW4gaW50
ZXJmYWNlIHRvIHRoZSBHTlUKZ2V0dGV4dCBtZXNzYWdlIGNhdGFsb2cgbGlicmFyeS4AV2l0aCBj
b250ZXh0BFRoZXJlIGlzICVzIGZpbGUAVGhlcmUgYXJlICVzIGZpbGVzAG11bGx1c2sAbXkgY29u
dGV4dARudWRnZSBudWRnZQBteSBvdGhlciBjb250ZXh0BG51ZGdlIG51ZGdlAG51ZGdlIG51ZGdl
AFByb2plY3QtSWQtVmVyc2lvbjogMi4wClBPLVJldmlzaW9uLURhdGU6IDIwMDMtMDQtMTEgMTQ6
MzItMDQwMApMYXN0LVRyYW5zbGF0b3I6IEouIERhdmlkIEliYW5leiA8ai1kYXZpZEBub29zLmZy
PgpMYW5ndWFnZS1UZWFtOiBYWCA8cHl0aG9uLWRldkBweXRob24ub3JnPgpNSU1FLVZlcnNpb246
IDEuMApDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9aXNvLTg4NTktMQpDb250ZW50
LVRyYW5zZmVyLUVuY29kaW5nOiA4Yml0CkdlbmVyYXRlZC1CeTogcHlnZXR0ZXh0LnB5IDEuMQpQ
bHVyYWwtRm9ybXM6IG5wbHVyYWxzPTI7IHBsdXJhbD1uIT0xOwoAVGhyb2F0d29iYmxlciBNYW5n
cm92ZQBIYXkgJXMgZmljaGVybwBIYXkgJXMgZmljaGVyb3MAR3V2ZiB6YnFoeXIgY2ViaXZxcmYg
dmFncmVhbmd2YmFueXZtbmd2YmEgbmFxIHlicG55dm1uZ3ZiYQpmaGNjYmVnIHNiZSBsYmhlIENs
Z3ViYSBjZWJ0ZW56ZiBvbCBjZWJpdnF2YXQgbmEgdmFncmVzbnByIGdiIGd1ciBUQUgKdHJnZ3Jr
ZyB6cmZmbnRyIHBuZ255YnQgeXZvZW5lbC4ASGF5ICVzIGZpY2hlcm8gKGNvbnRleHQpAEhheSAl
cyBmaWNoZXJvcyAoY29udGV4dCkAYmFjb24Ad2luayB3aW5rIChpbiAibXkgY29udGV4dCIpAHdp
bmsgd2luayAoaW4gIm15IG90aGVyIGNvbnRleHQiKQB3aW5rIHdpbmsA
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
'''
Issue #18216: gettext now raises an error when a .mo file has an unsupported major version number. Patch by Aaron Hill.
2014-10-28 16:17:51 -03:00
# This data contains an invalid major version number (5)
# An unexpected major version number should be treated as an error when
# parsing a .mo file
GNU_MO_DATA_BAD_MAJOR_VERSION = b'''\
3hIElQAABQAGAAAAHAAAAEwAAAALAAAAfAAAAAAAAACoAAAAFQAAAKkAAAAjAAAAvwAAAKEAAADj
AAAABwAAAIUBAAALAAAAjQEAAEUBAACZAQAAFgAAAN8CAAAeAAAA9gIAAKEAAAAVAwAABQAAALcD
AAAJAAAAvQMAAAEAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAABQAAAAYAAAACAAAAAFJh
eW1vbmQgTHV4dXJ5IFlhY2gtdABUaGVyZSBpcyAlcyBmaWxlAFRoZXJlIGFyZSAlcyBmaWxlcwBU
aGlzIG1vZHVsZSBwcm92aWRlcyBpbnRlcm5hdGlvbmFsaXphdGlvbiBhbmQgbG9jYWxpemF0aW9u
CnN1cHBvcnQgZm9yIHlvdXIgUHl0aG9uIHByb2dyYW1zIGJ5IHByb3ZpZGluZyBhbiBpbnRlcmZh
Y2UgdG8gdGhlIEdOVQpnZXR0ZXh0IG1lc3NhZ2UgY2F0YWxvZyBsaWJyYXJ5LgBtdWxsdXNrAG51
ZGdlIG51ZGdlAFByb2plY3QtSWQtVmVyc2lvbjogMi4wClBPLVJldmlzaW9uLURhdGU6IDIwMDAt
MDgtMjkgMTI6MTktMDQ6MDAKTGFzdC1UcmFuc2xhdG9yOiBKLiBEYXZpZCBJYsOhw7FleiA8ai1k
YXZpZEBub29zLmZyPgpMYW5ndWFnZS1UZWFtOiBYWCA8cHl0aG9uLWRldkBweXRob24ub3JnPgpN
SU1FLVZlcnNpb246IDEuMApDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9aXNvLTg4
NTktMQpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiBub25lCkdlbmVyYXRlZC1CeTogcHlnZXR0
ZXh0LnB5IDEuMQpQbHVyYWwtRm9ybXM6IG5wbHVyYWxzPTI7IHBsdXJhbD1uIT0xOwoAVGhyb2F0
d29iYmxlciBNYW5ncm92ZQBIYXkgJXMgZmljaGVybwBIYXkgJXMgZmljaGVyb3MAR3V2ZiB6YnFo
eXIgY2ViaXZxcmYgdmFncmVhbmd2YmFueXZtbmd2YmEgbmFxIHlicG55dm1uZ3ZiYQpmaGNjYmVn
IHNiZSBsYmhlIENsZ3ViYSBjZWJ0ZW56ZiBvbCBjZWJpdnF2YXQgbmEgdmFncmVzbnByIGdiIGd1
ciBUQUgKdHJnZ3JrZyB6cmZmbnRyIHBuZ255YnQgeXZvZW5lbC4AYmFjb24Ad2luayB3aW5rAA==
'''
# This data contains an invalid minor version number (7)
# An unexpected minor version number only indicates that some of the file's
# contents may not be able to be read. It does not indicate an error.
GNU_MO_DATA_BAD_MINOR_VERSION = b'''\
3hIElQcAAAAGAAAAHAAAAEwAAAALAAAAfAAAAAAAAACoAAAAFQAAAKkAAAAjAAAAvwAAAKEAAADj
AAAABwAAAIUBAAALAAAAjQEAAEUBAACZAQAAFgAAAN8CAAAeAAAA9gIAAKEAAAAVAwAABQAAALcD
AAAJAAAAvQMAAAEAAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAABQAAAAYAAAACAAAAAFJh
eW1vbmQgTHV4dXJ5IFlhY2gtdABUaGVyZSBpcyAlcyBmaWxlAFRoZXJlIGFyZSAlcyBmaWxlcwBU
aGlzIG1vZHVsZSBwcm92aWRlcyBpbnRlcm5hdGlvbmFsaXphdGlvbiBhbmQgbG9jYWxpemF0aW9u
CnN1cHBvcnQgZm9yIHlvdXIgUHl0aG9uIHByb2dyYW1zIGJ5IHByb3ZpZGluZyBhbiBpbnRlcmZh
Y2UgdG8gdGhlIEdOVQpnZXR0ZXh0IG1lc3NhZ2UgY2F0YWxvZyBsaWJyYXJ5LgBtdWxsdXNrAG51
ZGdlIG51ZGdlAFByb2plY3QtSWQtVmVyc2lvbjogMi4wClBPLVJldmlzaW9uLURhdGU6IDIwMDAt
MDgtMjkgMTI6MTktMDQ6MDAKTGFzdC1UcmFuc2xhdG9yOiBKLiBEYXZpZCBJYsOhw7FleiA8ai1k
YXZpZEBub29zLmZyPgpMYW5ndWFnZS1UZWFtOiBYWCA8cHl0aG9uLWRldkBweXRob24ub3JnPgpN
SU1FLVZlcnNpb246IDEuMApDb250ZW50LVR5cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9aXNvLTg4
NTktMQpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiBub25lCkdlbmVyYXRlZC1CeTogcHlnZXR0
ZXh0LnB5IDEuMQpQbHVyYWwtRm9ybXM6IG5wbHVyYWxzPTI7IHBsdXJhbD1uIT0xOwoAVGhyb2F0
d29iYmxlciBNYW5ncm92ZQBIYXkgJXMgZmljaGVybwBIYXkgJXMgZmljaGVyb3MAR3V2ZiB6YnFo
eXIgY2ViaXZxcmYgdmFncmVhbmd2YmFueXZtbmd2YmEgbmFxIHlicG55dm1uZ3ZiYQpmaGNjYmVn
IHNiZSBsYmhlIENsZ3ViYSBjZWJ0ZW56ZiBvbCBjZWJpdnF2YXQgbmEgdmFncmVzbnByIGdiIGd1
ciBUQUgKdHJnZ3JrZyB6cmZmbnRyIHBuZ255YnQgeXZvZW5lbC4AYmFjb24Ad2luayB3aW5rAA==
'''
Changes in anticipation of stricter str vs. bytes enforcement.
2007-08-27 14:23:59 -03:00
UMO_DATA = b'''\
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
3hIElQAAAAADAAAAHAAAADQAAAAAAAAAAAAAAAAAAABMAAAABAAAAE0AAAAQAAAAUgAAAA8BAABj
AAAABAAAAHMBAAAWAAAAeAEAAABhYsOeAG15Y29udGV4dMOeBGFiw54AUHJvamVjdC1JZC1WZXJz
aW9uOiAyLjAKUE8tUmV2aXNpb24tRGF0ZTogMjAwMy0wNC0xMSAxMjo0Mi0wNDAwCkxhc3QtVHJh
bnNsYXRvcjogQmFycnkgQS4gV0Fyc2F3IDxiYXJyeUBweXRob24ub3JnPgpMYW5ndWFnZS1UZWFt
OiBYWCA8cHl0aG9uLWRldkBweXRob24ub3JnPgpNSU1FLVZlcnNpb246IDEuMApDb250ZW50LVR5
cGU6IHRleHQvcGxhaW47IGNoYXJzZXQ9dXRmLTgKQ29udGVudC1UcmFuc2Zlci1FbmNvZGluZzog
N2JpdApHZW5lcmF0ZWQtQnk6IG1hbnVhbGx5CgDCpHl6AMKkeXogKGNvbnRleHQgdmVyc2lvbikA
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
'''
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
Changes in anticipation of stricter str vs. bytes enforcement.
2007-08-27 14:23:59 -03:00
MMO_DATA = b'''\
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
3hIElQAAAAABAAAAHAAAACQAAAADAAAALAAAAAAAAAA4AAAAeAEAADkAAAABAAAAAAAAAAAAAAAA
UHJvamVjdC1JZC1WZXJzaW9uOiBObyBQcm9qZWN0IDAuMApQT1QtQ3JlYXRpb24tRGF0ZTogV2Vk
IERlYyAxMSAwNzo0NDoxNSAyMDAyClBPLVJldmlzaW9uLURhdGU6IDIwMDItMDgtMTQgMDE6MTg6
NTgrMDA6MDAKTGFzdC1UcmFuc2xhdG9yOiBKb2huIERvZSA8amRvZUBleGFtcGxlLmNvbT4KSmFu
ZSBGb29iYXIgPGpmb29iYXJAZXhhbXBsZS5jb20+Ckxhbmd1YWdlLVRlYW06IHh4IDx4eEBleGFt
cGxlLmNvbT4KTUlNRS1WZXJzaW9uOiAxLjAKQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFy
c2V0PWlzby04ODU5LTE1CkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IHF1b3RlZC1wcmludGFi
bGUKR2VuZXJhdGVkLUJ5OiBweWdldHRleHQucHkgMS4zCgA=
'''
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
LOCALEDIR = os.path.join('xx', 'LC_MESSAGES')
MOFILE = os.path.join(LOCALEDIR, 'gettext.mo')
Issue #18216: gettext now raises an error when a .mo file has an unsupported major version number. Patch by Aaron Hill.
2014-10-28 16:17:51 -03:00
MOFILE_BAD_MAJOR_VERSION = os.path.join(LOCALEDIR, 'gettext_bad_major_version.mo')
MOFILE_BAD_MINOR_VERSION = os.path.join(LOCALEDIR, 'gettext_bad_minor_version.mo')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
UMOFILE = os.path.join(LOCALEDIR, 'ugettext.mo')
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
MMOFILE = os.path.join(LOCALEDIR, 'metadata.mo')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
class GettextBaseTest(unittest.TestCase):
def setUp(self):
Don't try to create the directory if it already exists, otherwise the test fails
2004-07-18 21:08:59 -03:00
if not os.path.isdir(LOCALEDIR):
os.makedirs(LOCALEDIR)
Prevent ResourceWarnings in test_gettext
2010-11-06 01:11:59 -03:00
with open(MOFILE, 'wb') as fp:
fp.write(base64.decodebytes(GNU_MO_DATA))
Issue #18216: gettext now raises an error when a .mo file has an unsupported major version number. Patch by Aaron Hill.
2014-10-28 16:17:51 -03:00
with open(MOFILE_BAD_MAJOR_VERSION, 'wb') as fp:
fp.write(base64.decodebytes(GNU_MO_DATA_BAD_MAJOR_VERSION))
with open(MOFILE_BAD_MINOR_VERSION, 'wb') as fp:
fp.write(base64.decodebytes(GNU_MO_DATA_BAD_MINOR_VERSION))
Prevent ResourceWarnings in test_gettext
2010-11-06 01:11:59 -03:00
with open(UMOFILE, 'wb') as fp:
fp.write(base64.decodebytes(UMO_DATA))
with open(MMOFILE, 'wb') as fp:
fp.write(base64.decodebytes(MMO_DATA))
Merged revisions 72167 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r72167 | walter.doerwald | 2009-05-01 19:35:37 +0200 (Fr, 01 Mai 2009) | 5 lines Make test.test_support.EnvironmentVarGuard behave like a dictionary. All changes are mirrored to the underlying os.environ dict, but rolled back on exit from the with block. ........
2009-05-01 16:58:58 -03:00
self.env = support.EnvironmentVarGuard()
self.env['LANGUAGE'] = 'xx'
Fix caching error found by regrtest -R (#10229)
2010-11-06 01:09:29 -03:00
gettext._translations.clear()
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
def tearDown(self):
Merged revisions 72167 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ........ r72167 | walter.doerwald | 2009-05-01 19:35:37 +0200 (Fr, 01 Mai 2009) | 5 lines Make test.test_support.EnvironmentVarGuard behave like a dictionary. All changes are mirrored to the underlying os.environ dict, but rolled back on exit from the with block. ........
2009-05-01 16:58:58 -03:00
self.env.__exit__()
del self.env
test_gettext: use support.rmtree() instead of shutil.rmtree()
2014-07-24 07:07:45 -03:00
support.rmtree(os.path.split(LOCALEDIR)[0])
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
#17898: reset k and v so that the loop doesn't use an old value
2015-04-13 11:38:56 -03:00
GNU_MO_DATA_ISSUE_17898 = b'''\
3hIElQAAAAABAAAAHAAAACQAAAAAAAAAAAAAAAAAAAAsAAAAggAAAC0AAAAAUGx1cmFsLUZvcm1z
OiBucGx1cmFscz0yOyBwbHVyYWw9KG4gIT0gMSk7CiMtIy0jLSMtIyAgbWVzc2FnZXMucG8gKEVk
WCBTdHVkaW8pICAjLSMtIy0jLSMKQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFyc2V0PVVU
Ri04CgA=
'''
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
class GettextTestCase1(GettextBaseTest):
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def setUp(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
GettextBaseTest.setUp(self)
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
self.localedir = os.curdir
self.mofile = MOFILE
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
gettext.install('gettext', self.localedir, names=['pgettext'])
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_some_translations(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# test some translations
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_('albatross'), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_('mullusk'), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_(r'Raymond Luxury Yach-t'), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_(r'nudge nudge'), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
def test_some_translations_with_context(self):
eq = self.assertEqual
eq(pgettext('my context', 'nudge nudge'),
'wink wink (in "my context")')
eq(pgettext('my other context', 'nudge nudge'),
'wink wink (in "my other context")')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_double_quotes(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# double quotes
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_("albatross"), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_("mullusk"), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_(r"Raymond Luxury Yach-t"), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_(r"nudge nudge"), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_triple_single_quotes(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# triple single quotes
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_('''albatross'''), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_('''mullusk'''), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_(r'''Raymond Luxury Yach-t'''), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_(r'''nudge nudge'''), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_triple_double_quotes(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# triple double quotes
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_("""albatross"""), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_("""mullusk"""), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_(r"""Raymond Luxury Yach-t"""), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(_(r"""nudge nudge"""), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_multiline_strings(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# multiline strings
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_('''This module provides internationalization and localization
Test suite for new gettext.py module.
2000-08-25 16:14:25 -03:00
support for your Python programs by providing an interface to the GNU
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
gettext message catalog library.'''),
'''Guvf zbqhyr cebivqrf vagreangvbanyvmngvba naq ybpnyvmngvba
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
fhccbeg sbe lbhe Clguba cebtenzf ol cebivqvat na vagresnpr gb gur TAH
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
trggrkg zrffntr pngnybt yvoenel.''')
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_the_alternative_interface(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# test the alternative interface
Prevent ResourceWarnings in test_gettext
2010-11-06 01:11:59 -03:00
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# Install the translation object
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
t.install()
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_('nudge nudge'), 'wink wink')
# Try unicode return type
#2512 implement the 3.0 gettext API All the u* gettext variants were renamed to their none u* variants, since there's no point in translating to byte strings. I also killed off the unicode parameters for install
2008-07-14 11:32:15 -03:00
t.install()
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(_('mullusk'), 'bacon')
Patch #1349274: gettext.install() now optionally installs additional translation functions other than _() in the builtin namespace.
2006-02-19 09:26:36 -04:00
# Test installation of other methods
#1535: rename __builtin__ module to builtins.
2007-12-02 05:40:06 -04:00
import builtins
#2512 implement the 3.0 gettext API All the u* gettext variants were renamed to their none u* variants, since there's no point in translating to byte strings. I also killed off the unicode parameters for install
2008-07-14 11:32:15 -03:00
t.install(names=["gettext", "lgettext"])
eq(_, t.gettext)
eq(builtins.gettext, t.gettext)
Patch #1349274: gettext.install() now optionally installs additional translation functions other than _() in the builtin namespace.
2006-02-19 09:26:36 -04:00
eq(lgettext, t.lgettext)
#1535: rename __builtin__ module to builtins.
2007-12-02 05:40:06 -04:00
del builtins.gettext
del builtins.lgettext
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
class GettextTestCase2(GettextBaseTest):
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def setUp(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
GettextBaseTest.setUp(self)
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
self.localedir = os.curdir
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# Set up the bindings
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
gettext.bindtextdomain('gettext', self.localedir)
gettext.textdomain('gettext')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# For convenience
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
self._ = gettext.gettext
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_bindtextdomain(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
self.assertEqual(gettext.bindtextdomain('gettext'), self.localedir)
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_textdomain(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
self.assertEqual(gettext.textdomain(), 'gettext')
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
Issue #18216: gettext now raises an error when a .mo file has an unsupported major version number. Patch by Aaron Hill.
2014-10-28 16:17:51 -03:00
def test_bad_major_version(self):
with open(MOFILE_BAD_MAJOR_VERSION, 'rb') as fp:
with self.assertRaises(OSError) as cm:
gettext.GNUTranslations(fp)
exception = cm.exception
self.assertEqual(exception.errno, 0)
self.assertEqual(exception.strerror, "Bad version number 5")
self.assertEqual(exception.filename, MOFILE_BAD_MAJOR_VERSION)
def test_bad_minor_version(self):
with open(MOFILE_BAD_MINOR_VERSION, 'rb') as fp:
# Check that no error is thrown with a bad minor version number
gettext.GNUTranslations(fp)
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_some_translations(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# test some translations
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._('albatross'), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._('mullusk'), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._(r'Raymond Luxury Yach-t'), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._(r'nudge nudge'), 'wink wink')
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
def test_some_translations_with_context(self):
eq = self.assertEqual
eq(gettext.pgettext('my context', 'nudge nudge'),
'wink wink (in "my context")')
eq(gettext.pgettext('my other context', 'nudge nudge'),
'wink wink (in "my other context")')
def test_some_translations_with_context_and_domain(self):
eq = self.assertEqual
eq(gettext.dpgettext('gettext', 'my context', 'nudge nudge'),
'wink wink (in "my context")')
eq(gettext.dpgettext('gettext', 'my other context', 'nudge nudge'),
'wink wink (in "my other context")')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_double_quotes(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# double quotes
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._("albatross"), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._("mullusk"), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._(r"Raymond Luxury Yach-t"), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._(r"nudge nudge"), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_triple_single_quotes(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# triple single quotes
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._('''albatross'''), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._('''mullusk'''), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._(r'''Raymond Luxury Yach-t'''), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._(r'''nudge nudge'''), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_triple_double_quotes(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# triple double quotes
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._("""albatross"""), 'albatross')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._("""mullusk"""), 'bacon')
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._(r"""Raymond Luxury Yach-t"""), 'Throatwobbler Mangrove')
Rip out all the u"..." literals and calls to unicode().
2007-05-02 16:09:54 -03:00
eq(self._(r"""nudge nudge"""), 'wink wink')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_multiline_strings(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# multiline strings
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(self._('''This module provides internationalization and localization
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
support for your Python programs by providing an interface to the GNU
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
gettext message catalog library.'''),
'''Guvf zbqhyr cebivqrf vagreangvbanyvmngvba naq ybpnyvmngvba
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
fhccbeg sbe lbhe Clguba cebtenzf ol cebivqvat na vagresnpr gb gur TAH
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
trggrkg zrffntr pngnybt yvoenel.''')
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
class PluralFormsTestCase(GettextBaseTest):
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def setUp(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
GettextBaseTest.setUp(self)
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
self.mofile = MOFILE
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_plural_forms1(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
x = gettext.ngettext('There is %s file', 'There are %s files', 1)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(x, 'Hay %s fichero')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
x = gettext.ngettext('There is %s file', 'There are %s files', 2)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(x, 'Hay %s ficheros')
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
def test_plural_context_forms1(self):
eq = self.assertEqual
x = gettext.npgettext('With context',
'There is %s file', 'There are %s files', 1)
eq(x, 'Hay %s fichero (context)')
x = gettext.npgettext('With context',
'There is %s file', 'There are %s files', 2)
eq(x, 'Hay %s ficheros (context)')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_plural_forms2(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Prevent ResourceWarnings in test_gettext
2010-11-06 01:11:59 -03:00
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
x = t.ngettext('There is %s file', 'There are %s files', 1)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(x, 'Hay %s fichero')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
x = t.ngettext('There is %s file', 'There are %s files', 2)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(x, 'Hay %s ficheros')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
def test_plural_context_forms2(self):
eq = self.assertEqual
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
x = t.npgettext('With context',
'There is %s file', 'There are %s files', 1)
eq(x, 'Hay %s fichero (context)')
x = t.npgettext('With context',
'There is %s file', 'There are %s files', 2)
eq(x, 'Hay %s ficheros (context)')
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
# Examples from http://www.gnu.org/software/gettext/manual/gettext.html
def test_ja(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('0')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_de(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n != 1')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "10111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_fr(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n>1')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "00111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111")
Set this test up so that we don't have to create xx/LC_MESSAGES in the cvs tree. It creates the directory and gettext.mo file on the fly, from the base64 encode binary data.
2000-08-25 16:50:38 -03:00
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
def test_lv(self):
eq = self.assertEqual
f = gettext.c2py('n%10==1 && n%100!=11 ? 0 : n != 0 ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
eq(s, "20111111111111111111101111111110111111111011111111101111111110111111111011111111101111111110111111111011111111111111111110111111111011111111101111111110111111111011111111101111111110111111111011111111")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_gd(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n==1 ? 0 : n==2 ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "20122222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_gd2(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# Tests the combination of parentheses and "?:"
f = gettext.c2py('n==1 ? 0 : (n==2 ? 1 : 2)')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "20122222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
def test_ro(self):
eq = self.assertEqual
f = gettext.c2py('n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
eq(s, "10111111111111111111222222222222222222222222222222222222222222222222222222222222222222222222222222222111111111111111111122222222222222222222222222222222222222222222222222222222222222222222222222222222")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_lt(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n%10==1 && n%100!=11 ? 0 : n%10>=2 && (n%100<10 || n%100>=20) ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "20111111112222222222201111111120111111112011111111201111111120111111112011111111201111111120111111112011111111222222222220111111112011111111201111111120111111112011111111201111111120111111112011111111")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_ru(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "20111222222222222222201112222220111222222011122222201112222220111222222011122222201112222220111222222011122222222222222220111222222011122222201112222220111222222011122222201112222220111222222011122222")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
def test_cs(self):
eq = self.assertEqual
f = gettext.c2py('(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
eq(s, "20111222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_pl(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "20111222222222222222221112222222111222222211122222221112222222111222222211122222221112222222111222222211122222222222222222111222222211122222221112222222111222222211122222221112222222111222222211122222")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_sl(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq = self.assertEqual
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
f = gettext.c2py('n%100==1 ? 0 : n%100==2 ? 1 : n%100==3 || n%100==4 ? 2 : 3')
s = ''.join([ str(f(x)) for x in range(200) ])
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
eq(s, "30122333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333012233333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333333")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
def test_ar(self):
eq = self.assertEqual
f = gettext.c2py('n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 && n%100<=10 ? 3 : n%100>=11 ? 4 : 5')
s = ''.join([ str(f(x)) for x in range(200) ])
eq(s, "01233333333444444444444444444444444444444444444444444444444444444444444444444444444444444444444444445553333333344444444444444444444444444444444444444444444444444444444444444444444444444444444444444444")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
def test_security(self):
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
raises = self.assertRaises
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# Test for a dangerous expression
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
raises(ValueError, gettext.c2py, "os.chmod('/etc/passwd',0777)")
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
# issue28563
raises(ValueError, gettext.c2py, '"(eval(foo) && ""')
raises(ValueError, gettext.c2py, 'f"{os.system(\'sh\')}"')
# Maximum recursion depth exceeded during compilation
raises(ValueError, gettext.c2py, 'n+'*10000 + 'n')
self.assertEqual(gettext.c2py('n+'*100 + 'n')(1), 101)
# MemoryError during compilation
raises(ValueError, gettext.c2py, '('*100 + 'n' + ')'*100)
# Maximum recursion depth exceeded in C to Python translator
raises(ValueError, gettext.c2py, '('*10000 + 'n' + ')'*10000)
self.assertEqual(gettext.c2py('('*20 + 'n' + ')'*20)(1), 1)
def test_chained_comparison(self):
# C doesn't chain comparison as Python so 2 == 2 == 2 gets different results
f = gettext.c2py('n == n == n')
self.assertEqual(''.join(str(f(x)) for x in range(3)), '010')
f = gettext.c2py('1 < n == n')
self.assertEqual(''.join(str(f(x)) for x in range(3)), '100')
f = gettext.c2py('n == n < 2')
self.assertEqual(''.join(str(f(x)) for x in range(3)), '010')
f = gettext.c2py('0 < n < 2')
self.assertEqual(''.join(str(f(x)) for x in range(3)), '111')
def test_decimal_number(self):
self.assertEqual(gettext.c2py('0123')(1), 123)
def test_invalid_syntax(self):
invalid_expressions = [
'x>1', '(n>1', 'n>1)', '42**42**42', '0xa', '1.0', '1e2',
'n>0x1', '+n', '-n', 'n()', 'n(1)', '1+', 'nn', 'n n',
]
for expr in invalid_expressions:
with self.assertRaises(ValueError):
gettext.c2py(expr)
def test_nested_condition_operator(self):
self.assertEqual(gettext.c2py('n?1?2:3:4')(0), 4)
self.assertEqual(gettext.c2py('n?1?2:3:4')(1), 2)
self.assertEqual(gettext.c2py('n?1:3?4:5')(0), 4)
self.assertEqual(gettext.c2py('n?1:3?4:5')(1), 1)
def test_division(self):
f = gettext.c2py('2/n*3')
self.assertEqual(f(1), 6)
self.assertEqual(f(2), 3)
self.assertEqual(f(3), 0)
self.assertEqual(f(-1), -6)
self.assertRaises(ZeroDivisionError, f, 0)
def test_plural_number(self):
Issue #28563: Make plural form selection more lenient and accepting non-integer numbers. Django tests depend on this.
2016-11-14 13:22:12 -04:00
f = gettext.c2py('n != 1')
self.assertEqual(f(1), 0)
self.assertEqual(f(2), 1)
bpo-28692: Deprecate using non-integer value for selecting a plural form in gettext. (#507)
2017-03-12 08:15:01 -03:00
with self.assertWarns(DeprecationWarning):
self.assertEqual(f(1.0), 0)
with self.assertWarns(DeprecationWarning):
self.assertEqual(f(2.0), 1)
with self.assertWarns(DeprecationWarning):
self.assertEqual(f(1.1), 1)
Issue #28563: Make plural form selection more lenient and accepting non-integer numbers. Django tests depend on this.
2016-11-14 13:22:12 -04:00
self.assertRaises(TypeError, f, '2')
self.assertRaises(TypeError, f, b'2')
self.assertRaises(TypeError, f, [])
self.assertRaises(TypeError, f, object())
Issue #28563: Fixed possible DoS and arbitrary code execution when handle plural form selections in the gettext module. The expression parser now supports exact syntax supported by GNU gettext.
2016-11-08 15:17:46 -04:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
class LGettextTestCase(GettextBaseTest):
def setUp(self):
GettextBaseTest.setUp(self)
self.mofile = MOFILE
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
@contextlib.contextmanager
def assertDeprecated(self, name):
with self.assertWarnsRegex(DeprecationWarning,
fr'^{name}\(\) is deprecated'):
yield
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
def test_lgettext(self):
lgettext = gettext.lgettext
ldgettext = gettext.ldgettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('mullusk'), b'bacon')
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('spam'), b'spam')
with self.assertDeprecated('ldgettext'):
self.assertEqual(ldgettext('gettext', 'mullusk'), b'bacon')
with self.assertDeprecated('ldgettext'):
self.assertEqual(ldgettext('gettext', 'spam'), b'spam')
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
def test_lgettext_2(self):
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
lgettext = t.lgettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('mullusk'), b'bacon')
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('spam'), b'spam')
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
def test_lgettext_bind_textdomain_codeset(self):
lgettext = gettext.lgettext
ldgettext = gettext.ldgettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('bind_textdomain_codeset'):
saved_codeset = gettext.bind_textdomain_codeset('gettext')
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
try:
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('bind_textdomain_codeset'):
gettext.bind_textdomain_codeset('gettext', 'utf-16')
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('mullusk'), 'bacon'.encode('utf-16'))
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('spam'), 'spam'.encode('utf-16'))
with self.assertDeprecated('ldgettext'):
self.assertEqual(ldgettext('gettext', 'mullusk'), 'bacon'.encode('utf-16'))
with self.assertDeprecated('ldgettext'):
self.assertEqual(ldgettext('gettext', 'spam'), 'spam'.encode('utf-16'))
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
finally:
del gettext._localecodesets['gettext']
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('bind_textdomain_codeset'):
gettext.bind_textdomain_codeset('gettext', saved_codeset)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
def test_lgettext_output_encoding(self):
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
lgettext = t.lgettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('set_output_charset'):
t.set_output_charset('utf-16')
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('mullusk'), 'bacon'.encode('utf-16'))
with self.assertDeprecated('lgettext'):
self.assertEqual(lgettext('spam'), 'spam'.encode('utf-16'))
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
def test_lngettext(self):
lngettext = gettext.lngettext
ldngettext = gettext.ldngettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'Hay %s fichero')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'Hay %s ficheros')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'There is %s directory')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'There are %s directories')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s file', 'There are %s files', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'Hay %s fichero')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s file', 'There are %s files', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'Hay %s ficheros')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s directory', 'There are %s directories', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'There is %s directory')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s directory', 'There are %s directories', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'There are %s directories')
def test_lngettext_2(self):
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
lngettext = t.lngettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'Hay %s fichero')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'Hay %s ficheros')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'There is %s directory')
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, b'There are %s directories')
def test_lngettext_bind_textdomain_codeset(self):
lngettext = gettext.lngettext
ldngettext = gettext.ldngettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('bind_textdomain_codeset'):
saved_codeset = gettext.bind_textdomain_codeset('gettext')
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
try:
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('bind_textdomain_codeset'):
gettext.bind_textdomain_codeset('gettext', 'utf-16')
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'Hay %s fichero'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'Hay %s ficheros'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'There is %s directory'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'There are %s directories'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s file', 'There are %s files', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'Hay %s fichero'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s file', 'There are %s files', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'Hay %s ficheros'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s directory', 'There are %s directories', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'There is %s directory'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('ldngettext'):
x = ldngettext('gettext', 'There is %s directory', 'There are %s directories', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'There are %s directories'.encode('utf-16'))
finally:
del gettext._localecodesets['gettext']
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('bind_textdomain_codeset'):
gettext.bind_textdomain_codeset('gettext', saved_codeset)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
def test_lngettext_output_encoding(self):
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
lngettext = t.lngettext
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('set_output_charset'):
t.set_output_charset('utf-16')
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'Hay %s fichero'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s file', 'There are %s files', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'Hay %s ficheros'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 1)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'There is %s directory'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
with self.assertDeprecated('lngettext'):
x = lngettext('There is %s directory', 'There are %s directories', 2)
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(x, 'There are %s directories'.encode('utf-16'))
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
def test_output_encoding(self):
with open(self.mofile, 'rb') as fp:
t = gettext.GNUTranslations(fp)
with self.assertDeprecated('set_output_charset'):
t.set_output_charset('utf-16')
with self.assertDeprecated('output_charset'):
self.assertEqual(t.output_charset(), 'utf-16')
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
#17898: reset k and v so that the loop doesn't use an old value
2015-04-13 11:38:56 -03:00
class GNUTranslationParsingTest(GettextBaseTest):
def test_plural_form_error_issue17898(self):
with open(MOFILE, 'wb') as fp:
fp.write(base64.decodebytes(GNU_MO_DATA_ISSUE_17898))
with open(MOFILE, 'rb') as fp:
# If this runs cleanly, the bug is fixed.
t = gettext.GNUTranslations(fp)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
class UnicodeTranslationsTest(GettextBaseTest):
def setUp(self):
GettextBaseTest.setUp(self)
Prevent ResourceWarnings in test_gettext
2010-11-06 01:11:59 -03:00
with open(UMOFILE, 'rb') as fp:
UnicodeTranslationsTest.setUp(): Removed the coerce flag to the GNUTranslations constructor.
2003-04-24 15:08:13 -03:00
self.t = gettext.GNUTranslations(fp)
#2512 implement the 3.0 gettext API All the u* gettext variants were renamed to their none u* variants, since there's no point in translating to byte strings. I also killed off the unicode parameters for install
2008-07-14 11:32:15 -03:00
self._ = self.t.gettext
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
self.pgettext = self.t.pgettext
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
def test_unicode_msgid(self):
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertIsInstance(self._(''), str)
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
def test_unicode_msgstr(self):
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
self.assertEqual(self._('ab\xde'), '\xa4yz')
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
def test_unicode_context_msgstr(self):
t = self.pgettext('mycontext\xde', 'ab\xde')
self.assertTrue(isinstance(t, str))
self.assertEqual(t, '\xa4yz (context version)')
class UnicodeTranslationsPluralTest(GettextBaseTest):
def setUp(self):
GettextBaseTest.setUp(self)
with open(MOFILE, 'rb') as fp:
self.t = gettext.GNUTranslations(fp)
self.ngettext = self.t.ngettext
self.npgettext = self.t.npgettext
def test_unicode_msgid(self):
unless = self.assertTrue
unless(isinstance(self.ngettext('', '', 1), str))
unless(isinstance(self.ngettext('', '', 2), str))
def test_unicode_context_msgid(self):
unless = self.assertTrue
unless(isinstance(self.npgettext('', '', '', 1), str))
unless(isinstance(self.npgettext('', '', '', 2), str))
def test_unicode_msgstr(self):
eq = self.assertEqual
unless = self.assertTrue
t = self.ngettext("There is %s file", "There are %s files", 1)
unless(isinstance(t, str))
eq(t, "Hay %s fichero")
unless(isinstance(t, str))
t = self.ngettext("There is %s file", "There are %s files", 5)
unless(isinstance(t, str))
eq(t, "Hay %s ficheros")
def test_unicode_msgstr_with_context(self):
eq = self.assertEqual
unless = self.assertTrue
t = self.npgettext("With context",
"There is %s file", "There are %s files", 1)
unless(isinstance(t, str))
eq(t, "Hay %s fichero (context)")
t = self.npgettext("With context",
"There is %s file", "There are %s files", 5)
unless(isinstance(t, str))
eq(t, "Hay %s ficheros (context)")
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
class WeirdMetadataTest(GettextBaseTest):
def setUp(self):
GettextBaseTest.setUp(self)
Prevent ResourceWarnings in test_gettext
2010-11-06 01:11:59 -03:00
with open(MMOFILE, 'rb') as fp:
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
try:
self.t = gettext.GNUTranslations(fp)
except:
self.tearDown()
raise
def test_weird_metadata(self):
info = self.t.info()
Fixed gettext module for Windows. The metadata lines always end in \n and not in os.linesep
2007-10-31 15:53:44 -03:00
self.assertEqual(len(info), 9)
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
self.assertEqual(info['last-translator'],
'John Doe <jdoe@example.com>\nJane Foobar <jfoobar@example.com>')
Fix interaction of custom translation classes and caching (#9042)
2010-10-04 20:52:37 -03:00
class DummyGNUTranslations(gettext.GNUTranslations):
def foo(self):
return 'foo'
class GettextCacheTestCase(GettextBaseTest):
def test_cache(self):
self.localedir = os.curdir
self.mofile = MOFILE
self.assertEqual(len(gettext._translations), 0)
t = gettext.translation('gettext', self.localedir)
self.assertEqual(len(gettext._translations), 1)
t = gettext.translation('gettext', self.localedir,
class_=DummyGNUTranslations)
self.assertEqual(len(gettext._translations), 2)
self.assertEqual(t.__class__, DummyGNUTranslations)
# Calling it again doesn't add to the cache
t = gettext.translation('gettext', self.localedir,
class_=DummyGNUTranslations)
self.assertEqual(len(gettext._translations), 2)
self.assertEqual(t.__class__, DummyGNUTranslations)
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
# Test deprecated parameter codeset
with self.assertWarnsRegex(DeprecationWarning, 'parameter codeset'):
t = gettext.translation('gettext', self.localedir,
class_=DummyGNUTranslations,
codeset='utf-16')
self.assertEqual(len(gettext._translations), 2)
self.assertEqual(t.__class__, DummyGNUTranslations)
with self.assertWarns(DeprecationWarning):
self.assertEqual(t.output_charset(), 'utf-16')
Fix interaction of custom translation classes and caching (#9042)
2010-10-04 20:52:37 -03:00
Issue #23883: Add test.support.check__all__() and test gettext.__all__ Patches by Jacek Kołodziej.
2015-11-14 07:47:00 -04:00
class MiscTestCase(unittest.TestCase):
def test__all__(self):
blacklist = {'c2py', 'ENOENT'}
support.check__all__(self, gettext, blacklist=blacklist)
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
if __name__ == '__main__':
bpo-33710: Deprecate l*gettext() and related functions in the gettext module. (GH-10139) They return encoded bytes and are Python 2 artifacts.
2018-10-27 02:00:41 -03:00
unittest.main()
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# For reference, here's the .po file used to created the GNU_MO_DATA above.
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
#
# The original version was automatically generated from the sources with
# pygettext. Later it was manually modified to add plural forms support.
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
b'''
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# Dummy translation for the Python test_gettext.py module.
Quick and dirty fix for test_extcall failures trigged by Guido's recent classobject.c change. When calling an unbound method with no instances as first argument, the error message has changed. The message now contains the class name, but the output text being compared to is too generic, so skip printing it.
2001-08-24 16:11:57 -03:00
# Copyright (C) 2001 Python Software Foundation
# Barry Warsaw <barry@python.org>, 2000.
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
#
msgid ""
msgstr ""
"Project-Id-Version: 2.0\n"
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
"PO-Revision-Date: 2003-04-11 14:32-0400\n"
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
"Last-Translator: J. David Ibanez <j-david@noos.fr>\n"
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
"Language-Team: XX <python-dev@python.org>\n"
"MIME-Version: 1.0\n"
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
"Content-Type: text/plain; charset=iso-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
"Generated-By: pygettext.py 1.1\n"
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
"Plural-Forms: nplurals=2; plural=n!=1;\n"
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
#: test_gettext.py:19 test_gettext.py:25 test_gettext.py:31 test_gettext.py:37
#: test_gettext.py:51 test_gettext.py:80 test_gettext.py:86 test_gettext.py:92
#: test_gettext.py:98
msgid "nudge nudge"
msgstr "wink wink"
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
msgctxt "my context"
msgid "nudge nudge"
msgstr "wink wink (in \"my context\")"
msgctxt "my other context"
msgid "nudge nudge"
msgstr "wink wink (in \"my other context\")"
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
#: test_gettext.py:16 test_gettext.py:22 test_gettext.py:28 test_gettext.py:34
#: test_gettext.py:77 test_gettext.py:83 test_gettext.py:89 test_gettext.py:95
msgid "albatross"
msgstr ""
#: test_gettext.py:18 test_gettext.py:24 test_gettext.py:30 test_gettext.py:36
#: test_gettext.py:79 test_gettext.py:85 test_gettext.py:91 test_gettext.py:97
msgid "Raymond Luxury Yach-t"
msgstr "Throatwobbler Mangrove"
#: test_gettext.py:17 test_gettext.py:23 test_gettext.py:29 test_gettext.py:35
#: test_gettext.py:56 test_gettext.py:78 test_gettext.py:84 test_gettext.py:90
#: test_gettext.py:96
msgid "mullusk"
msgstr "bacon"
#: test_gettext.py:40 test_gettext.py:101
msgid ""
"This module provides internationalization and localization\n"
"support for your Python programs by providing an interface to the GNU\n"
"gettext message catalog library."
msgstr ""
"Guvf zbqhyr cebivqrf vagreangvbanyvmngvba naq ybpnyvmngvba\n"
"fhccbeg sbe lbhe Clguba cebtenzf ol cebivqvat na vagresnpr gb gur TAH\n"
"trggrkg zrffntr pngnybt yvoenel."
Patch #633547: Support plural forms. Do TODOs in test suite.
2002-11-21 17:45:32 -04:00
# Manually added, as neither pygettext nor xgettext support plural forms
# in Python.
msgid "There is %s file"
msgid_plural "There are %s files"
msgstr[0] "Hay %s fichero"
msgstr[1] "Hay %s ficheros"
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
# Manually added, as neither pygettext nor xgettext support plural forms
# and context in Python.
msgctxt "With context"
msgid "There is %s file"
msgid_plural "There are %s files"
msgstr[0] "Hay %s fichero (context)"
msgstr[1] "Hay %s ficheros (context)"
Expand the test suite to test both the GNU gettext and translation class-based APIs.
2000-08-30 00:32:07 -03:00
'''
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# Here's the second example po file example, used to generate the UMO_DATA
# containing utf-8 encoded Unicode strings
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
b'''
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
# Dummy translation for the Python test_gettext.py module.
# Copyright (C) 2001 Python Software Foundation
# Barry Warsaw <barry@python.org>, 2000.
#
msgid ""
msgstr ""
"Project-Id-Version: 2.0\n"
"PO-Revision-Date: 2003-04-11 12:42-0400\n"
"Last-Translator: Barry A. WArsaw <barry@python.org>\n"
"Language-Team: XX <python-dev@python.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 7bit\n"
"Generated-By: manually\n"
#: nofile:0
msgid "ab\xc3\x9e"
msgstr "\xc2\xa4yz"
bpo-2504: Add pgettext() and variants to gettext. (GH-7253)
2018-11-07 10:12:20 -04:00
#: nofile:1
msgctxt "mycontext\xc3\x9e"
msgid "ab\xc3\x9e"
msgstr "\xc2\xa4yz (context version)"
From http://mail.python.org/pipermail/i18n-sig/2003-April/001557.html - Expose NullTranslations and GNUTranslations to __all__ - Set the default charset to iso-8859-1. It used to be None, which would cause problems with .ugettext() if the file had no charset parameter. Arguably, the po/mo file would be broken, but I still think iso-8859-1 is a reasonable default. - Add a "coerce" default argument to GNUTranslations's constructor. The reason for this is that in Zope, we want all msgids and msgstrs to be Unicode. For the latter, we could use .ugettext() but there isn't currently a mechanism for Unicode-ifying msgids. The plan then is that the charset parameter specifies the encoding for both the msgids and msgstrs, and both are decoded to Unicode when read. For example, we might encode po files with utf-8. I think the GNU gettext tools don't care. Since this could potentially break code [*] that wants to use the encoded interface .gettext(), the constructor flag is added, defaulting to False. Most code I suspect will want to set this to True and use .ugettext(). - A few other minor changes from the Zope project, including asserting that a zero-length msgid must have a Project-ID-Version header for it to be counted as the metadata record.
2003-04-11 15:36:43 -03:00
'''
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
# Here's the third example po file, used to generate MMO_DATA
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
b'''
Added a test for the fix of SF bug #658233, where continuation lines in .po metadata caused a crash. Also, removed some unnecessary code. Backport candidate.
2003-05-20 14:28:54 -03:00
msgid ""
msgstr ""
"Project-Id-Version: No Project 0.0\n"
"POT-Creation-Date: Wed Dec 11 07:44:15 2002\n"
"PO-Revision-Date: 2002-08-14 01:18:58+00:00\n"
"Last-Translator: John Doe <jdoe@example.com>\n"
"Jane Foobar <jfoobar@example.com>\n"
"Language-Team: xx <xx@example.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=iso-8859-15\n"
"Content-Transfer-Encoding: quoted-printable\n"
"Generated-By: pygettext.py 1.3\n"
'''
#17898: reset k and v so that the loop doesn't use an old value
2015-04-13 11:38:56 -03:00
#
# messages.po, used for bug 17898
#
bpo-29755: Fixed the lgettext() family of functions in the gettext module. (#2266) They now always return bytes. Updated the gettext documentation.
2017-06-20 11:13:29 -03:00
b'''
#17898: reset k and v so that the loop doesn't use an old value
2015-04-13 11:38:56 -03:00
# test file for http://bugs.python.org/issue17898
msgid ""
msgstr ""
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"#-#-#-#-# messages.po (EdX Studio) #-#-#-#-#\n"
"Content-Type: text/plain; charset=UTF-8\n"
'''