Details
Improvement
Resolved
Major
Description
In order to allow reliable and consistent support for non-English languages, a consistent encoding needs to be used.
- UTF-8 encoding should be mandated for Java source and textual story files.
- ISO-8859-1 with Unicode escaped characters for locale resource bundles.
The requirements need to be clearly documented, with links to tools that allow conversion of native to ascii based unicode, tools that can allow users to easily and efficiently specify keywords in their locales.
A standard set of locales can then be supported and bundled as core resources, so that users need only specify new LocalizedKeywords(<my Locale>).
We may at a later state a further layer of conversion using some of these tools.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
In order to allow reliable and consistent support for non-English languages, a consistent encoding need to used.
The core needs to become stricter about the expected encoding and fails (or at least flag a warning) if a different encoding is used by any character-based content, be it story content, i18n bundles or Steps patterns. |
In order to allow reliable and consistent support for non-English languages, a consistent encoding needs to be used.
The core needs to become stricter about the expected encoding and fails (or at least flag a warning, behaviour to be configurable) if a different encoding is used by any character-based content, be it story content, i18n bundles or Steps patterns. |
Mauro Talevi
made changes -
| Fix Version/s | 3.1 [ 16511 ] | |
| Fix Version/s | 3.0 [ 16302 ] |
Mauro Talevi
made changes -
| Summary | Ensure UTF-8 charset encoding is used consistently | Ensure consistency of encoding |
| Assignee | Mauro Talevi [ maurotalevi ] | |
| Fix Version/s | 3.0 [ 16302 ] | |
| Fix Version/s | 3.1 [ 16511 ] | |
| Description |
In order to allow reliable and consistent support for non-English languages, a consistent encoding needs to be used.
The core needs to become stricter about the expected encoding and fails (or at least flag a warning, behaviour to be configurable) if a different encoding is used by any character-based content, be it story content, i18n bundles or Steps patterns. |
In order to allow reliable and consistent support for non-English languages, a consistent encoding needs to be used.
- UTF-8 encoding should be mandated for Java source and textual story files. - ISO-8859-1 with Unicode escaped characters for locale resource bundles. |
Mauro Talevi
made changes -
| Description |
In order to allow reliable and consistent support for non-English languages, a consistent encoding needs to be used.
- UTF-8 encoding should be mandated for Java source and textual story files. - ISO-8859-1 with Unicode escaped characters for locale resource bundles. |
In order to allow reliable and consistent support for non-English languages, a consistent encoding needs to be used.
- UTF-8 encoding should be mandated for Java source and textual story files. - ISO-8859-1 with Unicode escaped characters for locale resource bundles. The requirements need to be clearly documented, with links to tools that allow conversion of native to ascii based unicode, tools that can allow users to easily and efficiently specify keywords in their locales. A standard set of locales can then be supported and bundled as core resources, so that users need only specify new LocalizedKeywords(<my Locale>). We may at a later state a further layer of conversion using some of these tools. |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Mauro Talevi
made changes -
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
