Internationalization of JavaME (i18n)

Does anyone have knowledge with internationalization using JavaME? I am looking for as much information as possible, for example, examples, experiences, and possibly some best practices. Thanks

+3
source share
4 answers

A few thoughts. J2ME does not support i18n, since there is no api support there (use of resource packages is possible). But we can do this to a limited extent. Here is what I learned.

  • It is difficult, if not impossible, to support English and speak Chinese (typographic characters) for this J2ME application. But it’s easier to maintain English and speak Spanish (I forgot the right nomenclature to talk about i18n support, but you get the point).
  • We can have all the lines in one configuration class, so you can change it to different languages.
  • We can have text / lines loaded from the server when the application is first launched, and therefore be able to change it on the server.
  • Due to the different screen sizes, it is best to work with custom fonts so that the code can be written to calculate the length of the text when it is displayed. This will make it easier to support multiple languages.
  • . , , .

.

+3

omemuhammed - .

EFIGS (, , , ). XML, XML- . XML 5 , , , .

. , . , , , . , .

, , . 20-30% , , .

+1

. JavaME: http://www.jcp.org/en/jsr/detail?id=238

Symbian .

: ( 4 ), - ( 3- "" ). , /-ussr .

ascii, TextBox TextField, .

+1

, RTL ( ), , , ,

  • 1
  • 2
  • 3

but the bullets will be on the other side of the screen in Arabic (try to do it here, but I cannot create an inverted list: P)

Another thing is that it is better to store your lines in a class than the properties of plain text, as this can cause some errors that interpret the unicode of some languages ​​depending on the OS and the text editor that you use.

What I usually do is the I18nManager class, which stores the language in startApp, and through this class I get all the lines that I need.

0
source

Source: https://habr.com/ru/post/1702476/


All Articles