Illia Denysenko

Also to add to this, having it random makes it possible to have a different number of variants in different languages.

@oliver-ni to answer on using "type" in Rust, you can use raw identifiers. https://doc.rust-lang.org/rust-by-example/compatibility/raw_identifiers.html

(not a maintainer here, but I was able to fix my code by passing args outside, your code can be fixed like that) ```rust use fluent_bundle::{FluentArgs, FluentBundle, FluentResource}; use std::borrow::Cow;...

Still an issue even after https://github.com/translate/translate/issues/4649?

Speaking of ron2json cli, not every Ron is a valid Json (which was a surprise to me). I tried using serde_json for this, but as it says in its to_string...

Thanks for the review! I want to continue working on it, just got interrupted somewhat.

meow, bot

> Presently, Weblate requires source language in monolingual translations to have all the strings. The reason behind this is that this is the only way you can define source string...

@nijel I thought about this more, and I'm increasingly leaning toward creating default entries for terms per component. In general, Fluent may define messages in three ways. ```fluent # just...

If that's an acceptable solution, I could try making an MR to translate-toolkit