Difference between revisions of "Gremlins"
(→50px No Locale Framework) |
(→30px No Locale Framework) |
||
| Line 4: | Line 4: | ||
Those gremlins sneak up in your source code. |
Those gremlins sneak up in your source code. |
||
= [[File:King-gremlin.png|30px]] No Locale Framework = |
= [[File:King-gremlin.png|30px]] No Locale Framework = |
||
| + | * <b> Issues</b>: The king of all Gremlins: If the application does not have a locale framework, the Gremlin King rules and all Gremlins infest the application. |
||
| − | |||
| + | * <b>Remedy</b>: Design a Locale Framework. How to detect, negotiate, persist, assign the locale for the application needs to be designed and implemented. |
||
| − | == Issue == |
||
| − | The king of all Gremlins: If the application does not have a locale framework, the Gremlin King rules and all Gremlins infest the application. |
||
| − | |||
| − | == Remedy: Design a Locale Framework == |
||
| − | How to detect, negotiate, persist, assign the locale for the application needs to be designed and implemented. |
||
= Embedded Strings = |
= Embedded Strings = |
||
Revision as of 17:48, 23 July 2019
I18n Gremlins are sneaky issues that work their way into your code and foul up localization. They can be hard for developers to recognize.
I18n Gremlins
Those gremlins sneak up in your source code.
No Locale Framework
- Issues: The king of all Gremlins: If the application does not have a locale framework, the Gremlin King rules and all Gremlins infest the application.
- Remedy: Design a Locale Framework. How to detect, negotiate, persist, assign the locale for the application needs to be designed and implemented.
