langfingaz/anki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
4908be62ed
anki/rslib/i18n/Cargo.toml

35 lines
760 B
TOML
Raw Normal View History

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
[package]
name = "anki_i18n"
Use workspace package info in more crates; mark private for cargo-deny
2022-11-30 03:19:56 +01:00
version.workspace = true
authors.workspace = true
edition.workspace = true
license.workspace = true
Drop workspace-hack in favor of workspace deps Workspace deps were introduced in Rust 1.64. They don't cover all the cases that Hakari did unfortunately, but they are simpler to maintain, and they avoid a couple of issues that Hakari had: - It sometimes made updating dependencies harder due to the locked versions, so you had to disable Hakari, do the updates, and then re-generate ( e.g. 943dddf28f9a5bfbf49fd9b8501feb3d15fd2b81) - The current Hakari config was breaking AnkiDroid's build, as it was stopping a cross-compile from functioning correctly.
2023-06-23 05:02:23 +02:00
publish = false
Use workspace package info in more crates; mark private for cargo-deny
2022-11-30 03:19:56 +01:00
rust-version.workspace = true
Drop workspace-hack in favor of workspace deps Workspace deps were introduced in Rust 1.64. They don't cover all the cases that Hakari did unfortunately, but they are simpler to maintain, and they avoid a couple of issues that Hakari had: - It sometimes made updating dependencies harder due to the locked versions, so you had to disable Hakari, do the updates, and then re-generate ( e.g. 943dddf28f9a5bfbf49fd9b8501feb3d15fd2b81) - The current Hakari config was breaking AnkiDroid's build, as it was stopping a cross-compile from functioning correctly.
2023-06-23 05:02:23 +02:00
description = "Anki's Rust library i18n code"
Use workspace package info in more crates; mark private for cargo-deny
2022-11-30 03:19:56 +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
[lib]
name = "anki_i18n"
path = "src/lib.rs"
[build-dependencies]
Drop workspace-hack in favor of workspace deps Workspace deps were introduced in Rust 1.64. They don't cover all the cases that Hakari did unfortunately, but they are simpler to maintain, and they avoid a couple of issues that Hakari had: - It sometimes made updating dependencies harder due to the locked versions, so you had to disable Hakari, do the updates, and then re-generate ( e.g. 943dddf28f9a5bfbf49fd9b8501feb3d15fd2b81) - The current Hakari config was breaking AnkiDroid's build, as it was stopping a cross-compile from functioning correctly.
2023-06-23 05:02:23 +02:00
fluent-syntax.workspace = true
fluent.workspace = true
unic-langid.workspace = true
serde.workspace = true
serde_json.workspace = true
inflections.workspace = true
anki_io.workspace = true
anyhow.workspace = true
Move .ts i18n method generation to Rust Based on a similar approach I used for AnkiDroid. The separate modules file has been integrated into ftl.js.
2023-07-03 06:32:57 +02:00
itertools.workspace = true
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
[dependencies]
Drop workspace-hack in favor of workspace deps Workspace deps were introduced in Rust 1.64. They don't cover all the cases that Hakari did unfortunately, but they are simpler to maintain, and they avoid a couple of issues that Hakari had: - It sometimes made updating dependencies harder due to the locked versions, so you had to disable Hakari, do the updates, and then re-generate ( e.g. 943dddf28f9a5bfbf49fd9b8501feb3d15fd2b81) - The current Hakari config was breaking AnkiDroid's build, as it was stopping a cross-compile from functioning correctly.
2023-06-23 05:02:23 +02:00
fluent.workspace = true
fluent-bundle.workspace = true
intl-memoizer.workspace = true
num-format.workspace = true
phf.workspace = true
serde.workspace = true
serde_json.workspace = true
unic-langid.workspace = true
Reference in New Issue Copy Permalink