-
```
Found in Release:
Detailed description: We are trying to change the internationalization
(i18n) for the "no data" and number formating but it is not working. In
brazil, 1,500 means: 1.500 (or 1.5…
-
```
Found in Release:
Detailed description: We are trying to change the internationalization
(i18n) for the "no data" and number formating but it is not working. In
brazil, 1,500 means: 1.500 (or 1.5…
-
Translate string resources into other languages.
-
For have volunteers from many countries is a good idea add internationalization to our tasks.
-
```
What steps will reproduce the problem?
1. Deploy antisamy e.g. in an application server
2. Set the locale of the application server e.g. to en_US
What is the expected output? What do you see inst…
-
Suggests:
- Make content localizable (Labels, DataAnnotations, ModelStateError, Dates)
- Provide localized resources for the languages and cultures you support (for example: pt-BR, en-US)
- Imple…
-
From internal discussions:
**Problem statement**
Multilang strings appear in TD in things, interactions (and hopefully soon enumeration values) as
```java
"titles": {
"en": "Room Humidit…
-
I don't want to overlap with the i18n discussion (#59). Let's assume the documentation is written in one language only. This should be configurable to replace `en_US` in the SEO tag and other places.
…
-
I propose a simple yaml file with keys for each message
This will help keep the experience consistent and prevent repetition (#5 and #7)
-
The recommended way to translate a JasperReports template is to create a properties file for each language (e.g. `locale.properties`, `locale-fr.properties`), to set the `resourceBundle` property in t…