anki/qt/tests/test_i18n.py

import anki.lang


def test_no_collection_i18n():
    anki.lang.set_lang("zz")
    tr = anki.lang.tr_legacyglobal
    no_uni = anki.lang.without_unicode_isolation
    assert no_uni(tr.statistics_reviews(reviews=2)) == "2 reviews"

    anki.lang.set_lang("ja")
    assert no_uni(tr.statistics_reviews(reviews=2)) == "2 枚の復習カード"
translations no longer require an open collection 2020-02-23 05:57:02 +01:00			`import anki.lang`


			`def test_no_collection_i18n():`
rework translation handling Instead of generating a fluent.proto file with a giant enum, create a .json file representing the translations that downstream consumers can use for code generation. This enables the generation of a separate method for each translation, with a docstring that shows the actual text, and any required arguments listed in the function signature. The codebase is still using the old enum for now; updating it will need to come in future commits, and the old enum will need to be kept around, as add-ons are referencing it. Other changes: - move translation code into a separate crate - store the translations on a per-file/module basis, which will allow us to avoid sending 1000+ strings on each JS page load in the future - drop the undocumented support for external .ftl files, that we weren't using - duplicate strings in translation files are now checked for at build time - fix i18n test failing when run outside Bazel - drop slog dependency in i18n module 2021-03-26 00:40:41 +01:00			`anki.lang.set_lang("zz")`
update remaining TR references in .py files 2021-03-26 05:49:55 +01:00			`tr = anki.lang.tr_legacyglobal`
translations no longer require an open collection 2020-02-23 05:57:02 +01:00			`no_uni = anki.lang.without_unicode_isolation`
update remaining TR references in .py files 2021-03-26 05:49:55 +01:00			`assert no_uni(tr.statistics_reviews(reviews=2)) == "2 reviews"`
translations no longer require an open collection 2020-02-23 05:57:02 +01:00
rework translation handling Instead of generating a fluent.proto file with a giant enum, create a .json file representing the translations that downstream consumers can use for code generation. This enables the generation of a separate method for each translation, with a docstring that shows the actual text, and any required arguments listed in the function signature. The codebase is still using the old enum for now; updating it will need to come in future commits, and the old enum will need to be kept around, as add-ons are referencing it. Other changes: - move translation code into a separate crate - store the translations on a per-file/module basis, which will allow us to avoid sending 1000+ strings on each JS page load in the future - drop the undocumented support for external .ftl files, that we weren't using - duplicate strings in translation files are now checked for at build time - fix i18n test failing when run outside Bazel - drop slog dependency in i18n module 2021-03-26 00:40:41 +01:00			`anki.lang.set_lang("ja")`
update remaining TR references in .py files 2021-03-26 05:49:55 +01:00			`assert no_uni(tr.statistics_reviews(reviews=2)) == "2 枚の復習カード"`