anki/rslib/i18n/build/write_json.rs

// Copyright: Ankitects Pty Ltd and contributors
// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html

use std::{env, fs, path::Path};

pub fn main() {
    let args: Vec<_> = env::args().collect();
    let target_file = Path::new(args.get(1).expect("output path not provided"));
    let strings_json = include_str!(concat!(env!("OUT_DIR"), "/strings.json"));

    fs::write(target_file, strings_json).unwrap();
}
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			`// Copyright: Ankitects Pty Ltd and contributors`
			`// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html`

embed strings.json into write_json.rs It appears that including the build script as a dependency is not enough to make the file available at runtime, so the build breaks if ts/ is built first. 2021-03-26 00:54:42 +01:00			`use std::{env, fs, path::Path};`
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
			`pub fn main() {`
			`let args: Vec<_> = env::args().collect();`
			`let target_file = Path::new(args.get(1).expect("output path not provided"));`
embed strings.json into write_json.rs It appears that including the build script as a dependency is not enough to make the file available at runtime, so the build breaks if ts/ is built first. 2021-03-26 00:54:42 +01:00			`let strings_json = include_str!(concat!(env!("OUT_DIR"), "/strings.json"));`
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
embed strings.json into write_json.rs It appears that including the build script as a dependency is not enough to make the file available at runtime, so the build breaks if ts/ is built first. 2021-03-26 00:54:42 +01:00			`fs::write(target_file, strings_json).unwrap();`
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			`}`