Stanisław Małolepszy
Stanisław Małolepszy
```properties -wrong-user = (Not {$userName}? Click here.) hello = Hello, {$userName}! {-wrong-user} ``` Or should we require that each variable be passed explicitly as a parameter? Related to #230. ```properties...
Referencing parameterized terms is legal syntax in Fluent 1.0: ```properties -term = {$case -> [lower] value *[upper] Value } ## All three messages format to the same value. hello1 =...
It is sometimes desired to parametrize message references in placeables. In this issue I'd like to propose a new argument type, extending `FluentType` which could be used to programmatically pass...
#### Goal Allow for alternative syntax for nested variants. #### Description Nested variants are currently hard to write and result in some repetition. ICU's experience with MessageFormat also suggests that...
This was originally filed as #188 concerning `VariantExpressions` which was since removed from the Fluent Syntax. However, the same problem remains in named arguments to call expressions. Given a term...
This is a draft PR to discuss the code on the `format` branch. See also the previous attempt in #263.
The `gitbook` CLI tool [has been deprecated](https://github.com/GitbookIO/gitbook/commit/6c6ef7f4af32a2977e44dd23d3feb6ebf28970f4). Let's find an alternative, e.g. [`mdbook`](https://rust-lang-nursery.github.io/mdBook/).
The resolver should be resilient to exponential reference expansion attacks. See https://en.wikipedia.org/wiki/Billion_laughs_attack
Define the mechanism for specifying a transformation function which can modify the result of formatting. This can be used to implement pseudolocalizations. Possibly related to #273.
Should all placeable be wrapped in bidi isolates? Perhaps just `VariableReferences`?