Anki/pylib/anki/_backend
Damien Elmes 9aece2a7b8 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 09:41:32 +10:00
..
__init__.py rework translation handling 2021-03-26 09:41:32 +10:00
backend_pb2.pyi start work on more clearly defining backend/protobuf boundaries 2021-01-31 18:55:45 +10:00
BUILD.bazel rework translation handling 2021-03-26 09:41:32 +10:00
fluent.py rework translation handling 2021-03-26 09:41:32 +10:00
genbackend.py split out remaining rpc methods 2021-03-11 17:04:32 +10:00
generated.py start work on more clearly defining backend/protobuf boundaries 2021-01-31 18:55:45 +10:00
genfluent.py rework translation handling 2021-03-26 09:41:32 +10:00
rsbridge.pyi rework backend codegen to support multiple services; split out sched 2021-03-11 14:51:29 +10:00