-
Coming back from the Unicode Conference, there was a lot of chatter about pseudo-locales.
Fluent already had a pretty good support for pseudo-locales in the past and due to our client-side mode, we…
-
When developing a new feature in the DApp, it may be helpful to be able to view the component with longer/taller strings to identify inflexible containers and make sure they can handle non-english str…
-
When the Crowdin In-Context tool is enabled, the archive with your project translation will include one additional language. It is required to store operational data about localization strings. Integr…
-
It might be more user and developer friendly in our polyfill to support parsing of the `` `lang` attribute (to the extent that we have internationalized message strings for the language). Currently…
-
**Describe the bug**
#360 removed the conditional inclusion of resw files in the project file, but also completely removed the references to pseudo-loc ressw files as they haven't been getting suppli…
-
Hi :)
Localization behavior is working fine for me, but i don't know if i can use it in a ready function and how.
For exemple, for a login form, i want to show a toast with different informations in …
Naehs updated
6 years ago
-
With the i18n packages upgrade, our current pseudo locale implementation is very limited and has obvious drawbacks:
1. Only `en-xa` is supported from the psuedo locale suite.
2. Runtime check at the…
-
**Description**
I would like to use the pseudo-localization feature released in 1.3.2. However I have some strings that should not be translated. I can see [here](https://github.com/cashapp/paparazzi…
-
Text in languages other than English is often much longer (~Europe) or taller (~Asia), hence once the UI is localized there may be usability issues with users not being able to see the entire text due…
-
### Checks
- [X] I have checked that this enhancement has not already been requested
### How would you categorize this request. You can select multiple if not sure
Performance
### Enhan…