Re: Internationalization

There are actually two places for language/translation modules: one
for input (docutils/parsers/rst/languages/) and one for output
(docutils/languages/). For this info and other background &
instructions, please read "Docutils Internationalization":
http://docutils.sourceforge.net/docs/howto/i18n.html

The easiest way to develop new language modules is in-situ. Just put
the new modules in the appropriate directories; edit and test them
from there. You can also inject language modules from your custom
tool::

    # appropriate imports here
    docutils.parsers.rst.languages._languages[language_code] =
input_language_module
    docutils.languages._languages[language_code] = output_language_module

When you have completed the new language modules, please send them in
and we'll add them to Docutils!

David Goodger
<https://david.goodger.org>


On Fri, 3 Aug 2018 at 05:23, george boukeas <[email protected]> wrote:
>
> Hello everyone.
>
> I hope you can help me with a question: I am writing a custom tool
> that parses reST in HTML and I need the output to be in a language
> that is not currently supported, i.e. it is not in docutils/languages.
> As far as I can tell from reading the code, docutils only checks in
> docutils/languages for translation files. There doesn't seem to be a
> way for me to specify that it should also check some local user
> directory for the appropriate <language>.py file.
>
> So, is there any way to accomplish this?
>
> Thank you very much.
>
> -- George Boukeas.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot