If I want to deploy my software internationally, what architectural considerations should I consider?

I plan to develop software for the international market.

What architecture decisions should I consider, and not just convert text from one language to another?

+3
source share
9 answers

There are a huge number of problems, depending on how interested you are in the transition.

  • Numbers - both in thousands and in decimal separators. In fact, not all locales use a separator every three digits. And the rules for writing numbers as text, for example, for written checks, vary significantly.
  • Currency and Dimensions - not all currencies have two decimal digits . A sign may be leading or ending. A negation indicator can be a sign, brackets, or leading or ending text (for example, "dr" and "cr" are sometimes used in English). Similar problems for measurements (English and metric versus local).
  • script - , . Unicode . , . , , .
  • - ; , , ( , ). , "abc {1} xyz" "abc% 1 xyz" , , "abc" + n + "xyz", , , .
  • . ; . java.util.Calendar System.Globalization.Calendar.
  • . , , . .

(I18N) , . , . , , .:)

, .

+4

. Microsoft .

"" . : .

+2

, . .

, / / , , , / .

+1
  • . , "" .
  • - - .
+1
  • , -
  • , , , , , - , -.
  • , , , , , , , , .

, , , .

-, , , , , . -, .

+1
  • .
  • , .

, , Mac .

0

, , ...

1) . , , . , .

2) , , , , (, ). , ( ) . , . , , , , ( , ). .

0

, . , , , .

- , . , . , . , , , , . , - , . , Unicode , .

, , , , , ( ), , .

, , , - . , . , , 9 , 2/9/2009 , 2 . , 1,000,000.0, , , 1.000.000,0.

. "1 " "2 ", , , " ". . - " : 2" .

, Celcius. , .

, . Google , , , , , , , " ". , ; , , . , . , , , .

, - - , .

, , .

0

: .

, .

, . , , . , . , . , , " ".

- . , , . :

  • ? (, , ) , (, ).

  • ? (, ) , . , .

  • . , , Facebook Twitter.

, . , .

- . , .

0

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


All Articles