| Name | lingva JSON |
| Version |
5.0.4
JSON |
| download |
| home_page | None |
| Summary | Translation toolset |
| upload_time | 2024-09-12 16:17:55 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | None |
| license | Copyright (c) 2010-2022, Wichert Akkerman All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the University of Manchester or HITS gGmbH, nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| keywords |
translation
po
gettext
babel
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
What is lingva?
===============
**This is a fork of https://github.com/wichert/lingua**
Lingva is a package with tools to extract translatable texts from
your code, and to check existing translations. It replaces the use
of the ``xgettext`` command from gettext, or ``pybabel`` from Babel.
Message extraction
==================
The simplest way to extract all translatable messages is to point the
``pot-create`` tool at the root of your source tree.
::
$ pot-create src
This will create a ``messages.pot`` file containing all found messages.
Specifying input files
----------------------
There are three ways to tell lingva which files you want it to scan:
1. Specify filenames directly on the command line. For example::
$ pot-create main.py utils.py
2. Specify a directory on the command line. lingva will recursively scan that
directory for all files it knows how to handle.
::
$ pot-create src
3. Use the ``--files-from`` parameter to point to a file with a list of
files to scan. Lines starting with ``#`` and empty lines will be ignored.
::
$ pot-create --files-from=POTFILES.in
You can also use the ``--directory=PATH`` parameter to add the given path to the
list of directories to check for files. This may sound confusing, but can be
useful. For example this command will look for ``main.py`` and ``utils.py`` in
the current directory, and if they are not found there in the ``../src``
directory::
$ pot-create --directory=../src main.py utils.py
Configuration
-------------
In its default configuration lingva will use its python extractor for ``.py``
files, its XML extractor for ``.pt`` and ``.zpt`` files and its ZCML extractor
for ``.zcml`` files. If you use different extensions you setup a configuration
file which tells lingva how to process files. This file uses a simple ini-style
format.
There are two types of configuration that can be set in the configuration file:
which extractor to use for a file extension, and the configuration for a single
extractor.
File extensions are configured in the ``extensions`` section. Each entry in
this section maps a file extension to an extractor name. For example to
tell lingva to use its XML extractor for files with a ``.html`` extension
you can use this configuration::
[extensions]
.html = xml
To find out which extractors are available use the ``-list-extractors`` option.
::
$ bin/pot-create --list-extractors
chameleon Chameleon templates (defaults to Python expressions)
python Python sources
xml Chameleon templates (defaults to Python expressions)
zcml Zope Configuration Markup Language (ZCML)
zope Zope templates (defaults to TALES expressions)
A section named `extractor:<name>` can be used to configure a specific
extractor. For example to tell the XML extractor that the default language
used for expressions is TALES instead of Python::
[extractor:xml]
default-engine = tales
Either place a global configuration file named ``.config/lingva`` to your
home folder or use the ``--config`` option to point lingva to your
configuration file.
::
$ pot-create -c lingva.cfg src
Domain filtering
----------------
When working with large systems you may use multiple translation domains
in a single source tree. lingva can support that by filtering messages by
domain when scanning sources. To enable domain filtering use the ``-d`` option:
::
$ pot-create -d mydomain src
lingva will always include messages for which it can not determine the domain.
For example, take this Python code:
::
print(gettext(u'Hello, World'))
print(dgettext('mydomain', u'Bye bye'))
The first hello-message does not specify its domain and will always be
included. The second line uses `dgettext
<http://docs.python.org/2/library/gettext#gettext.dgettext>`_ to explicitly
specify the domain. lingva will use this information when filtering domains.
Including comments
------------------
You can add comments to messages to help translators, for example to explain
how a text is used, or provide hints on how it should be translated. For
chameleon templates this can be done using the ``i18n:comment`` attribute:
::
<label i18n:comment="This is a form label" i18n:translate="">Password</label>
Comments are inherited, so you can put them on a parent element as well.
::
<form i18n:comment="This is used in the password reset form">
<label i18n:translate="">Password</label>
<button i18n:translate="">Change</button>
</form>
For Python code you can tell lingva to include comments by using the
``--add-comments`` option. This will make Linua include all comments on the
line(s) *immediately preceeding* (there may be no empty line in between) a
translation call.
::
# This text should address the user directly.
return _('Thank you for using our service.')
Alternatively you can also put a comment at the end of the line starting your
translation function call.
::
return _('Thank you for using our service.') # Address the user directly
If you do not want all comments to be included but only specific ones you can
add a keyword to the ``--add-comments`` option, for example ``--add-comments=I18N``.
::
# I18N This text should address the user directly, and use formal addressing.
return _('Thank you for using our service')
Setting message flags in comments
---------------------------------
Messages can have *flags*. These are to indicate what format a message has, and
are typically used by validation tools to check if a translation does not break
variable references or template syntax. lingva does a reasonable job to detect
strings using C and Python formatting, but sometimes you may need to set flags
yourself. This can be done with a ``[flag, flag]`` marker in a comment.
::
# I18N [markdown,c-format]
header = _(u'# Hello *%s*')
Specifying keywords
-------------------
When looking for messages a lingva parser uses a default list of keywords
to identify translation calls. You can add extra keywords via the ``--keyword``
option. If you have your own ``mygettext`` function which takes a string
to translate as its first parameter you can use this:
::
$ pot-create --keyword=mygettext
If your function takes more parameters you will need to tell lingva about them.
This can be done in several ways:
* If the translatable text is not the first parameter you can specify the
parameter number with ``<keyword>:<parameter number>``. For example if
you use ``i18n_log(level, msg)`` the keyword specifier would be ``i18n_log:2``
* If you support plurals you can specify the parameter used for the plural message
by specifying the parameter number for both the singular and plural text. For
example if your function signature is ``show_result(single, plural)`` the
keyword specifier is ``show_result:1,2``
* If you use message contexts you can specify the parameter used for the context
by adding a ``c`` to the parameter number. For example the keyword specifier for
``pgettext`` is ``pgettext:1c,2``.
* If your function takes the domain as a parameter you can specify which parameter
is used for the domain by adding a ``d`` to the parameter number. For example
the keyword specifier for ``dgettext`` is ``dgettext:1d,2``. This is a
lingva-specified extension.
* You can specify the exact number of parameters a function call must have
using the ``t`` postfix. For example if a function *must* have four parameters
to be a valid call, the specifier could be ``myfunc:1,4t``.
Extractors
==========
lingva includes a number of extractors:
* `python`: handles Python source code.
* `chameleon`: handles `Chameleon <http://www.pagetemplates.org/>`_ files,
using the `Zope i18n syntax
<https://chameleon.readthedocs.org/en/latest/reference.html#id51>`_
* `zcml`: handles Zope Configuration Markup Language (ZCML) files.
* `zope`: a variant of the chameleon extractor, which assumes the default
expression language is `TALES
<https://chameleon.readthedocs.org/en/latest/reference.html#expressions-tales>`_
instead of Python.
* `xml`: old name for the `chameleon` extractor. This name should not be used
anymore and is only supported for backwards compatibility.
Babel extractors
----------------
There are several packages with plugins for `Babel
<http://babel.edgewall.org/>`_'s message extraction tool. lingva can use those
plugins as well. The plugin names will be prefixed with ``babel-`` to
distinguish them from lingva extractors.
For example, if you have the `PyBabel-json
<https://pypi.python.org/pypi/PyBabel-json>`_ package installed you can
instruct lingva to use it for .json files by adding this to your configuration
file::
[extensions]
.json = babel-json
Some Babel plugins require you to specify comment tags. This can be set with
the ``comment-tags`` option.
::
[extractor:babel-mako]
comment-tags = TRANSLATOR:
Comparison to other tools
=========================
Differences compared to `GNU gettext <https://www.gnu.org/software/gettext/>`_:
* Support for file formats such as Zope Page Templates (popular in
`Pyramid <http://docs.pylonsproject.org/projects/pyramid/en/latest/>`_,
`Chameleon`_,
`Plone <http://plone.org/>`_ and `Zope <http://www.zope.org>`_).
* Better support for detecting format strings used in Python.
* No direct support for C, C++, Perl, and many other languages. lingva focuses
on languages commonly used in Python projects, although support for other
languages can be added via plugins.
Differences compared to `Babel`_:
* More reliable detection of Python format strings.
* lingva includes plural support.
* Support for only extracting texts for a given translation domain. This is
often useful for extensible software where you use multiple translation
domains in a single application.
Validating translations
=======================
lingva includes a simple ``polint`` tool which performs a few basic checks on
PO files. Currently implemented tests are:
* duplicated message ids (can also be checked with GNU gettext's ``msgfmt``).
These should never happen and are usually a result of a bug in the message
extraction logic.
* identical translations used for multiple canonical texts. This can happen
for valid reasons, for example when the original text is not spelled
consistently.
To check a po file simply run ``polint`` with the po file as argument::
$ polint nl.po
Translation:
${val} ist keine Zeichenkette
Used for 2 canonical texts:
1 ${val} is not a string
2 "${val}" is not a string
Writing custom extractors
=========================
First we need to create the custom extractor::
from lingva.extractors import Extractor
from lingva.extractors import Message
class MyExtractor(Extractor):
'''One-line description for --list-extractors'''
extensions = ['.txt']
def __call__(self, filename, options):
return [Message(None, 'msgid', None, [], u'', u'', (filename, 1))]
Hooking up extractors to lingva is done by ``lingva.extractors`` entry points
in ``setup.py``::
setup(name='mypackage',
...
install_requires=[
'lingva',
],
...
entry_points='''
[lingva.extractors]
my_extractor = mypackage.extractor:MyExtractor
'''
...)
Note - the registered extractor must be a class derived from the ``Extractor``
base class.
After installing ``mypackage`` lingva will automatically detect the new custom
extractor.
Helper Script
=============
There exists a helper shell script for managing translations of packages in
``docs/examples`` named ``i18n.sh``. Copy it to package root where you want to
work on translations, edit the configuration params inside the script and use::
./i18n.sh lang
for initial catalog creation and::
./i18n.sh
for updating translation and compiling the catalog.
Raw data
{
"_id": null,
"home_page": null,
"name": "lingva",
"maintainer": null,
"docs_url": null,
"requires_python": null,
"maintainer_email": "Arkadii Yakovets <ark@cho.red>",
"keywords": "translation, po, gettext, Babel",
"author": null,
"author_email": "Wichert Akkerman <wichert@wiggy.net>",
"download_url": "https://files.pythonhosted.org/packages/fa/57/e21aa369fbcdb68038bdf2313fe5b1004b08d7907fb89922b2024835db94/lingva-5.0.4.tar.gz",
"platform": null,
"description": "What is lingva?\n===============\n\n**This is a fork of https://github.com/wichert/lingua**\n\nLingva is a package with tools to extract translatable texts from\nyour code, and to check existing translations. It replaces the use\nof the ``xgettext`` command from gettext, or ``pybabel`` from Babel.\n\n\nMessage extraction\n==================\n\nThe simplest way to extract all translatable messages is to point the\n``pot-create`` tool at the root of your source tree.\n\n::\n\n $ pot-create src\n\nThis will create a ``messages.pot`` file containing all found messages.\n\n\nSpecifying input files\n----------------------\n\nThere are three ways to tell lingva which files you want it to scan:\n\n1. Specify filenames directly on the command line. For example::\n\n $ pot-create main.py utils.py\n\n2. Specify a directory on the command line. lingva will recursively scan that\n directory for all files it knows how to handle.\n\n ::\n\n $ pot-create src\n\n3. Use the ``--files-from`` parameter to point to a file with a list of\n files to scan. Lines starting with ``#`` and empty lines will be ignored.\n\n ::\n\n $ pot-create --files-from=POTFILES.in\n\nYou can also use the ``--directory=PATH`` parameter to add the given path to the\nlist of directories to check for files. This may sound confusing, but can be\nuseful. For example this command will look for ``main.py`` and ``utils.py`` in\nthe current directory, and if they are not found there in the ``../src``\ndirectory::\n\n\n $ pot-create --directory=../src main.py utils.py\n\n\nConfiguration\n-------------\n\nIn its default configuration lingva will use its python extractor for ``.py``\nfiles, its XML extractor for ``.pt`` and ``.zpt`` files and its ZCML extractor\nfor ``.zcml`` files. If you use different extensions you setup a configuration\nfile which tells lingva how to process files. This file uses a simple ini-style\nformat.\n\nThere are two types of configuration that can be set in the configuration file:\nwhich extractor to use for a file extension, and the configuration for a single\nextractor.\n\nFile extensions are configured in the ``extensions`` section. Each entry in\nthis section maps a file extension to an extractor name. For example to\ntell lingva to use its XML extractor for files with a ``.html`` extension\nyou can use this configuration::\n\n [extensions]\n .html = xml\n\nTo find out which extractors are available use the ``-list-extractors`` option.\n\n::\n\n $ bin/pot-create --list-extractors\n chameleon Chameleon templates (defaults to Python expressions)\n python Python sources\n xml Chameleon templates (defaults to Python expressions)\n zcml Zope Configuration Markup Language (ZCML)\n zope Zope templates (defaults to TALES expressions)\n\nA section named `extractor:<name>` can be used to configure a specific\nextractor. For example to tell the XML extractor that the default language\nused for expressions is TALES instead of Python::\n\n [extractor:xml]\n default-engine = tales\n\nEither place a global configuration file named ``.config/lingva`` to your\nhome folder or use the ``--config`` option to point lingva to your\nconfiguration file.\n\n::\n\n $ pot-create -c lingva.cfg src\n\n\nDomain filtering\n----------------\n\nWhen working with large systems you may use multiple translation domains\nin a single source tree. lingva can support that by filtering messages by\ndomain when scanning sources. To enable domain filtering use the ``-d`` option:\n\n::\n\n $ pot-create -d mydomain src\n\nlingva will always include messages for which it can not determine the domain.\nFor example, take this Python code:\n\n::\n\n print(gettext(u'Hello, World'))\n print(dgettext('mydomain', u'Bye bye'))\n\nThe first hello-message does not specify its domain and will always be\nincluded. The second line uses `dgettext\n<http://docs.python.org/2/library/gettext#gettext.dgettext>`_ to explicitly\nspecify the domain. lingva will use this information when filtering domains.\n\n\nIncluding comments\n------------------\n\nYou can add comments to messages to help translators, for example to explain\nhow a text is used, or provide hints on how it should be translated. For\nchameleon templates this can be done using the ``i18n:comment`` attribute:\n\n::\n\n <label i18n:comment=\"This is a form label\" i18n:translate=\"\">Password</label>\n\nComments are inherited, so you can put them on a parent element as well.\n\n::\n\n <form i18n:comment=\"This is used in the password reset form\">\n <label i18n:translate=\"\">Password</label>\n <button i18n:translate=\"\">Change</button>\n </form>\n\n\nFor Python code you can tell lingva to include comments by using the\n``--add-comments`` option. This will make Linua include all comments on the\nline(s) *immediately preceeding* (there may be no empty line in between) a\ntranslation call.\n\n::\n\n # This text should address the user directly.\n return _('Thank you for using our service.')\n\nAlternatively you can also put a comment at the end of the line starting your\ntranslation function call.\n\n::\n\n return _('Thank you for using our service.') # Address the user directly\n\nIf you do not want all comments to be included but only specific ones you can\nadd a keyword to the ``--add-comments`` option, for example ``--add-comments=I18N``.\n\n::\n\n # I18N This text should address the user directly, and use formal addressing.\n return _('Thank you for using our service')\n\n\nSetting message flags in comments\n---------------------------------\n\nMessages can have *flags*. These are to indicate what format a message has, and\nare typically used by validation tools to check if a translation does not break\nvariable references or template syntax. lingva does a reasonable job to detect\nstrings using C and Python formatting, but sometimes you may need to set flags\nyourself. This can be done with a ``[flag, flag]`` marker in a comment.\n\n::\n\n # I18N [markdown,c-format]\n header = _(u'# Hello *%s*')\n\n\n\nSpecifying keywords\n-------------------\n\nWhen looking for messages a lingva parser uses a default list of keywords\nto identify translation calls. You can add extra keywords via the ``--keyword``\noption. If you have your own ``mygettext`` function which takes a string\nto translate as its first parameter you can use this:\n\n::\n\n $ pot-create --keyword=mygettext\n\nIf your function takes more parameters you will need to tell lingva about them.\nThis can be done in several ways:\n\n* If the translatable text is not the first parameter you can specify the\n parameter number with ``<keyword>:<parameter number>``. For example if\n you use ``i18n_log(level, msg)`` the keyword specifier would be ``i18n_log:2``\n* If you support plurals you can specify the parameter used for the plural message\n by specifying the parameter number for both the singular and plural text. For\n example if your function signature is ``show_result(single, plural)`` the\n keyword specifier is ``show_result:1,2``\n* If you use message contexts you can specify the parameter used for the context\n by adding a ``c`` to the parameter number. For example the keyword specifier for\n ``pgettext`` is ``pgettext:1c,2``.\n* If your function takes the domain as a parameter you can specify which parameter\n is used for the domain by adding a ``d`` to the parameter number. For example\n the keyword specifier for ``dgettext`` is ``dgettext:1d,2``. This is a\n lingva-specified extension.\n* You can specify the exact number of parameters a function call must have\n using the ``t`` postfix. For example if a function *must* have four parameters\n to be a valid call, the specifier could be ``myfunc:1,4t``.\n\n\nExtractors\n==========\n\nlingva includes a number of extractors:\n\n* `python`: handles Python source code.\n* `chameleon`: handles `Chameleon <http://www.pagetemplates.org/>`_ files,\n using the `Zope i18n syntax\n <https://chameleon.readthedocs.org/en/latest/reference.html#id51>`_\n* `zcml`: handles Zope Configuration Markup Language (ZCML) files.\n* `zope`: a variant of the chameleon extractor, which assumes the default\n expression language is `TALES\n <https://chameleon.readthedocs.org/en/latest/reference.html#expressions-tales>`_\n instead of Python.\n* `xml`: old name for the `chameleon` extractor. This name should not be used\n anymore and is only supported for backwards compatibility.\n\nBabel extractors\n----------------\n\nThere are several packages with plugins for `Babel\n<http://babel.edgewall.org/>`_'s message extraction tool. lingva can use those\nplugins as well. The plugin names will be prefixed with ``babel-`` to\ndistinguish them from lingva extractors.\n\nFor example, if you have the `PyBabel-json\n<https://pypi.python.org/pypi/PyBabel-json>`_ package installed you can\ninstruct lingva to use it for .json files by adding this to your configuration\nfile::\n\n [extensions]\n .json = babel-json\n\nSome Babel plugins require you to specify comment tags. This can be set with\nthe ``comment-tags`` option.\n\n::\n\n [extractor:babel-mako]\n comment-tags = TRANSLATOR:\n\n\nComparison to other tools\n=========================\n\nDifferences compared to `GNU gettext <https://www.gnu.org/software/gettext/>`_:\n\n* Support for file formats such as Zope Page Templates (popular in\n `Pyramid <http://docs.pylonsproject.org/projects/pyramid/en/latest/>`_,\n `Chameleon`_,\n `Plone <http://plone.org/>`_ and `Zope <http://www.zope.org>`_).\n* Better support for detecting format strings used in Python.\n* No direct support for C, C++, Perl, and many other languages. lingva focuses\n on languages commonly used in Python projects, although support for other\n languages can be added via plugins.\n\n\nDifferences compared to `Babel`_:\n\n* More reliable detection of Python format strings.\n* lingva includes plural support.\n* Support for only extracting texts for a given translation domain. This is\n often useful for extensible software where you use multiple translation\n domains in a single application.\n\n\nValidating translations\n=======================\n\nlingva includes a simple ``polint`` tool which performs a few basic checks on\nPO files. Currently implemented tests are:\n\n* duplicated message ids (can also be checked with GNU gettext's ``msgfmt``).\n These should never happen and are usually a result of a bug in the message\n extraction logic.\n\n* identical translations used for multiple canonical texts. This can happen\n for valid reasons, for example when the original text is not spelled\n consistently.\n\nTo check a po file simply run ``polint`` with the po file as argument::\n\n $ polint nl.po\n\n Translation:\n ${val} ist keine Zeichenkette\n Used for 2 canonical texts:\n 1 ${val} is not a string\n 2 \"${val}\" is not a string\n\n\nWriting custom extractors\n=========================\n\nFirst we need to create the custom extractor::\n\n from lingva.extractors import Extractor\n from lingva.extractors import Message\n\n class MyExtractor(Extractor):\n '''One-line description for --list-extractors'''\n extensions = ['.txt']\n\n def __call__(self, filename, options):\n return [Message(None, 'msgid', None, [], u'', u'', (filename, 1))]\n\nHooking up extractors to lingva is done by ``lingva.extractors`` entry points\nin ``setup.py``::\n\n setup(name='mypackage',\n ...\n install_requires=[\n 'lingva',\n ],\n ...\n entry_points='''\n [lingva.extractors]\n my_extractor = mypackage.extractor:MyExtractor\n '''\n ...)\n\nNote - the registered extractor must be a class derived from the ``Extractor``\nbase class.\n\nAfter installing ``mypackage`` lingva will automatically detect the new custom\nextractor.\n\n\nHelper Script\n=============\n\nThere exists a helper shell script for managing translations of packages in\n``docs/examples`` named ``i18n.sh``. Copy it to package root where you want to\nwork on translations, edit the configuration params inside the script and use::\n\n ./i18n.sh lang\n\nfor initial catalog creation and::\n\n ./i18n.sh\n\nfor updating translation and compiling the catalog.\n",
"bugtrack_url": null,
"license": "Copyright (c) 2010-2022, Wichert Akkerman All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the University of Manchester or HITS gGmbH, nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ",
"summary": "Translation toolset",
"version": "5.0.4",
"project_urls": {
"homepage": "https://github.com/vacanza/lingva",
"tracker": "https://github.com/vacanza/lingva/issues"
},
"split_keywords": [
"translation",
" po",
" gettext",
" babel"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "ff664d6722d10ff6cfa3f1973eaf4ef083d83d5012bdbfb81d2d0ab3199b9cab",
"md5": "290a4344bfe07bc04734618b3c73eae8",
"sha256": "42910e47ee4fd08b4e3a09e87958a3357979fdac1969616eeb10db27787b8a59"
},
"downloads": -1,
"filename": "lingva-5.0.4-py2.py3-none-any.whl",
"has_sig": false,
"md5_digest": "290a4344bfe07bc04734618b3c73eae8",
"packagetype": "bdist_wheel",
"python_version": "py2.py3",
"requires_python": null,
"size": 25153,
"upload_time": "2024-09-12T16:17:54",
"upload_time_iso_8601": "2024-09-12T16:17:54.507852Z",
"url": "https://files.pythonhosted.org/packages/ff/66/4d6722d10ff6cfa3f1973eaf4ef083d83d5012bdbfb81d2d0ab3199b9cab/lingva-5.0.4-py2.py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "fa57e21aa369fbcdb68038bdf2313fe5b1004b08d7907fb89922b2024835db94",
"md5": "6b3bd99e55e566334c54304d6806e69e",
"sha256": "e6045629ffd2e099328343735762962d7f574026a84a9616c3c196dac4ff9509"
},
"downloads": -1,
"filename": "lingva-5.0.4.tar.gz",
"has_sig": false,
"md5_digest": "6b3bd99e55e566334c54304d6806e69e",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 37971,
"upload_time": "2024-09-12T16:17:55",
"upload_time_iso_8601": "2024-09-12T16:17:55.557180Z",
"url": "https://files.pythonhosted.org/packages/fa/57/e21aa369fbcdb68038bdf2313fe5b1004b08d7907fb89922b2024835db94/lingva-5.0.4.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-09-12 16:17:55",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "vacanza",
"github_project": "lingva",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"tox": true,
"lcname": "lingva"
}
