2021-10-07 15:31:49 +02:00
|
|
|
// Copyright: Ankitects Pty Ltd and contributors
|
|
|
|
// License: GNU AGPL, version 3 or later; http://www.gnu.org/licenses/agpl.html
|
|
|
|
|
|
|
|
import "intl-pluralrules";
|
2022-02-04 09:36:34 +01:00
|
|
|
|
2021-10-07 15:31:49 +02:00
|
|
|
import { FluentBundle, FluentResource } from "@fluent/bundle";
|
Migrate to protobuf-es (#2547)
* Fix .no-reduce-motion missing from graphs spinner, and not being honored
* Begin migration from protobuf.js -> protobuf-es
Motivation:
- Protobuf-es has a nicer API: messages are represented as classes, and
fields which should exist are not marked as nullable.
- As it uses modules, only the proto messages we actually use get included
in our bundle output. Protobuf.js put everything in a namespace, which
prevented tree-shaking, and made it awkward to access inner messages.
- ./run after touching a proto file drops from about 8s to 6s on my machine. The tradeoff
is slower decoding/encoding (#2043), but that was mainly a concern for the
graphs page, and was unblocked by
https://github.com/ankitects/anki/commit/37151213cd9d431f449ba4b3bc4c0329a1d9af78
Approach/notes:
- We generate the new protobuf-es interface in addition to existing
protobuf.js interface, so we can migrate a module at a time, starting
with the graphs module.
- rslib:proto now generates RPC methods for TS in addition to the Python
interface. The input-arg-unrolling behaviour of the Python generation is
not required here, as we declare the input arg as a PlainMessage<T>, which
marks it as requiring all fields to be provided.
- i64 is represented as bigint in protobuf-es. We were using a patch to
protobuf.js to get it to output Javascript numbers instead of long.js
types, but now that our supported browser versions support bigint, it's
probably worth biting the bullet and migrating to bigint use. Our IDs
fit comfortably within MAX_SAFE_INTEGER, but that may not hold for future
fields we add.
- Oneofs are handled differently in protobuf-es, and are going to need
some refactoring.
Other notable changes:
- Added a --mkdir arg to our build runner, so we can create a dir easily
during the build on Windows.
- Simplified the preference handling code, by wrapping the preferences
in an outer store, instead of a separate store for each individual
preference. This means a change to one preference will trigger a redraw
of all components that depend on the preference store, but the redrawing
is cheap after moving the data processing to Rust, and it makes the code
easier to follow.
- Drop async(Reactive).ts in favour of more explicit handling with await
blocks/updating.
- Renamed add_inputs_to_group() -> add_dependency(), and fixed it not adding
dependencies to parent groups. Renamed add() -> add_action() for clarity.
* Remove a couple of unused proto imports
* Migrate card info
* Migrate congrats, image occlusion, and tag editor
+ Fix imports for multi-word proto files.
* Migrate change-notetype
* Migrate deck options
* Bump target to es2020; simplify ts lib list
Have used caniuse.com to confirm Chromium 77, iOS 14.5 and the Chrome
on Android support the full es2017-es2020 features.
* Migrate import-csv
* Migrate i18n and fix missing output types in .js
* Migrate custom scheduling, and remove protobuf.js
To mostly maintain our old API contract, we make use of protobuf-es's
ability to convert to JSON, which follows the same format as protobuf.js
did. It doesn't cover all case: users who were previously changing the
variant of a type will need to update their code, as assigning to a new
variant no longer automatically removes the old one, which will cause an
error when we try to convert back from JSON. But I suspect the large majority
of users are adjusting the current variant rather than creating a new one,
and this saves us having to write proxy wrappers, so it seems like a
reasonable compromise.
One other change I made at the same time was to rename value->kind for
the oneofs in our custom study protos, as 'value' was easily confused
with the 'case/value' output that protobuf-es has.
With protobuf.js codegen removed, touching a proto file and invoking
./run drops from about 8s to 6s.
This closes #2043.
* Allow tree-shaking on protobuf types
* Display backend error messages in our ts alert()
* Make sourcemap generation opt-in for ts-run
Considerably slows down build, and not used most of the time.
2023-06-14 14:47:37 +02:00
|
|
|
import { i18nResources } from "@tslib/anki/i18n_service";
|
2021-10-07 15:31:49 +02:00
|
|
|
|
|
|
|
import { firstLanguage, setBundles } from "./bundles";
|
|
|
|
import type { ModuleName } from "./modules";
|
|
|
|
|
|
|
|
export function supportsVerticalText(): boolean {
|
|
|
|
const firstLang = firstLanguage();
|
|
|
|
return (
|
2022-11-28 00:33:04 +01:00
|
|
|
firstLang.startsWith("ja")
|
|
|
|
|| firstLang.startsWith("zh")
|
|
|
|
|| firstLang.startsWith("ko")
|
2021-10-07 15:31:49 +02:00
|
|
|
);
|
|
|
|
}
|
|
|
|
|
|
|
|
export function direction(): string {
|
|
|
|
const firstLang = firstLanguage();
|
|
|
|
if (
|
2022-11-28 00:33:04 +01:00
|
|
|
firstLang.startsWith("ar")
|
|
|
|
|| firstLang.startsWith("he")
|
|
|
|
|| firstLang.startsWith("fa")
|
2021-10-07 15:31:49 +02:00
|
|
|
) {
|
|
|
|
return "rtl";
|
|
|
|
} else {
|
|
|
|
return "ltr";
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
export function weekdayLabel(n: number): string {
|
|
|
|
const firstLang = firstLanguage();
|
|
|
|
const now = new Date();
|
|
|
|
const daysFromToday = -now.getDay() + n;
|
|
|
|
const desiredDay = new Date(now.getTime() + daysFromToday * 86_400_000);
|
|
|
|
return desiredDay.toLocaleDateString(firstLang, {
|
|
|
|
weekday: "narrow",
|
|
|
|
});
|
|
|
|
}
|
|
|
|
|
|
|
|
let langs: string[] = [];
|
|
|
|
|
2021-12-29 06:04:15 +01:00
|
|
|
export function localizedDate(
|
2021-10-07 15:31:49 +02:00
|
|
|
date: Date,
|
2021-10-19 01:06:00 +02:00
|
|
|
options?: Intl.DateTimeFormatOptions,
|
2021-10-07 15:31:49 +02:00
|
|
|
): string {
|
|
|
|
return date.toLocaleDateString(langs, options);
|
|
|
|
}
|
|
|
|
|
2021-12-29 06:04:15 +01:00
|
|
|
export function localizedNumber(n: number, precision = 2): string {
|
|
|
|
const round = Math.pow(10, precision);
|
|
|
|
const rounded = Math.round(n * round) / round;
|
|
|
|
return rounded.toLocaleString(langs);
|
|
|
|
}
|
|
|
|
|
2021-10-07 15:31:49 +02:00
|
|
|
export function localeCompare(
|
|
|
|
first: string,
|
|
|
|
second: string,
|
2021-10-19 01:06:00 +02:00
|
|
|
options?: Intl.CollatorOptions,
|
2021-10-07 15:31:49 +02:00
|
|
|
): number {
|
|
|
|
return first.localeCompare(second, langs, options);
|
|
|
|
}
|
|
|
|
|
2023-05-26 04:49:44 +02:00
|
|
|
/** Treat text like HTML, merging multiple spaces and converting
|
|
|
|
newlines to spaces. */
|
2021-10-07 15:31:49 +02:00
|
|
|
export function withCollapsedWhitespace(s: string): string {
|
|
|
|
return s.replace(/\s+/g, " ");
|
|
|
|
}
|
|
|
|
|
2021-10-26 12:11:25 +02:00
|
|
|
export function withoutUnicodeIsolation(s: string): string {
|
|
|
|
return s.replace(/[\u2068-\u2069]+/g, "");
|
|
|
|
}
|
|
|
|
|
2021-10-07 15:31:49 +02:00
|
|
|
export async function setupI18n(args: { modules: ModuleName[] }): Promise<void> {
|
Migrate to protobuf-es (#2547)
* Fix .no-reduce-motion missing from graphs spinner, and not being honored
* Begin migration from protobuf.js -> protobuf-es
Motivation:
- Protobuf-es has a nicer API: messages are represented as classes, and
fields which should exist are not marked as nullable.
- As it uses modules, only the proto messages we actually use get included
in our bundle output. Protobuf.js put everything in a namespace, which
prevented tree-shaking, and made it awkward to access inner messages.
- ./run after touching a proto file drops from about 8s to 6s on my machine. The tradeoff
is slower decoding/encoding (#2043), but that was mainly a concern for the
graphs page, and was unblocked by
https://github.com/ankitects/anki/commit/37151213cd9d431f449ba4b3bc4c0329a1d9af78
Approach/notes:
- We generate the new protobuf-es interface in addition to existing
protobuf.js interface, so we can migrate a module at a time, starting
with the graphs module.
- rslib:proto now generates RPC methods for TS in addition to the Python
interface. The input-arg-unrolling behaviour of the Python generation is
not required here, as we declare the input arg as a PlainMessage<T>, which
marks it as requiring all fields to be provided.
- i64 is represented as bigint in protobuf-es. We were using a patch to
protobuf.js to get it to output Javascript numbers instead of long.js
types, but now that our supported browser versions support bigint, it's
probably worth biting the bullet and migrating to bigint use. Our IDs
fit comfortably within MAX_SAFE_INTEGER, but that may not hold for future
fields we add.
- Oneofs are handled differently in protobuf-es, and are going to need
some refactoring.
Other notable changes:
- Added a --mkdir arg to our build runner, so we can create a dir easily
during the build on Windows.
- Simplified the preference handling code, by wrapping the preferences
in an outer store, instead of a separate store for each individual
preference. This means a change to one preference will trigger a redraw
of all components that depend on the preference store, but the redrawing
is cheap after moving the data processing to Rust, and it makes the code
easier to follow.
- Drop async(Reactive).ts in favour of more explicit handling with await
blocks/updating.
- Renamed add_inputs_to_group() -> add_dependency(), and fixed it not adding
dependencies to parent groups. Renamed add() -> add_action() for clarity.
* Remove a couple of unused proto imports
* Migrate card info
* Migrate congrats, image occlusion, and tag editor
+ Fix imports for multi-word proto files.
* Migrate change-notetype
* Migrate deck options
* Bump target to es2020; simplify ts lib list
Have used caniuse.com to confirm Chromium 77, iOS 14.5 and the Chrome
on Android support the full es2017-es2020 features.
* Migrate import-csv
* Migrate i18n and fix missing output types in .js
* Migrate custom scheduling, and remove protobuf.js
To mostly maintain our old API contract, we make use of protobuf-es's
ability to convert to JSON, which follows the same format as protobuf.js
did. It doesn't cover all case: users who were previously changing the
variant of a type will need to update their code, as assigning to a new
variant no longer automatically removes the old one, which will cause an
error when we try to convert back from JSON. But I suspect the large majority
of users are adjusting the current variant rather than creating a new one,
and this saves us having to write proxy wrappers, so it seems like a
reasonable compromise.
One other change I made at the same time was to rename value->kind for
the oneofs in our custom study protos, as 'value' was easily confused
with the 'case/value' output that protobuf-es has.
With protobuf.js codegen removed, touching a proto file and invoking
./run drops from about 8s to 6s.
This closes #2043.
* Allow tree-shaking on protobuf types
* Display backend error messages in our ts alert()
* Make sourcemap generation opt-in for ts-run
Considerably slows down build, and not used most of the time.
2023-06-14 14:47:37 +02:00
|
|
|
const resources = await i18nResources(args);
|
2022-02-04 09:25:40 +01:00
|
|
|
const json = JSON.parse(new TextDecoder().decode(resources.json));
|
2021-10-07 15:31:49 +02:00
|
|
|
|
|
|
|
const newBundles: FluentBundle[] = [];
|
2022-01-21 12:32:39 +01:00
|
|
|
for (const res in json.resources) {
|
|
|
|
const text = json.resources[res];
|
|
|
|
const lang = json.langs[res];
|
2021-10-07 15:31:49 +02:00
|
|
|
const bundle = new FluentBundle([lang, "en-US"]);
|
|
|
|
const resource = new FluentResource(text);
|
|
|
|
bundle.addResource(resource);
|
|
|
|
newBundles.push(bundle);
|
|
|
|
}
|
|
|
|
|
|
|
|
setBundles(newBundles);
|
|
|
|
langs = json.langs;
|
2021-12-06 09:40:26 +01:00
|
|
|
|
|
|
|
document.dir = direction();
|
2021-10-07 15:31:49 +02:00
|
|
|
}
|