CODEWITHSUNDEEP
localization
criddell
criddell

Reputation: 14599

Localization and Lists of Decimal Numbers

I'm working on localizing some strings in our application and we have text that looks something like:

Factor f (1.0, 1.2, or 1.5)

In a locale that uses a comma for the decimal point, would this be written as:

Factor f (1,0, 1,2, or 1,5)

Maybe it's just not what I'm accustomed to, but that looks crazy hard to read quickly.

I'm also wondering about text like version numbers. Would Firefox 3.5.1 be Firefox 3,5,1?

Upvotes: 2

Views: 1124

Answers (2)

Paweł Dyda
Paweł Dyda

Reputation: 18662

If I understand what you are looking for, there are two things in regards to Internationalization here:

  • Decimal separator
  • List separator

Obviously these separators are quite tightly coupled, so in Locale that uses comma as decimal separator, list separator must be something else. Usually this is a semicolon and there just a few Locales that uses something different than comma or semicolon for list separator.

To summarize:

In Locales that uses dot as a decimal separator, comma is usually used as a list separator, so in some free-form text you might expect something like Factor f (1.0, 1.2, or 1.5).
In Locales that uses comma as a decimal separator, semicolon is typically used as a list separator – Faktor f (1,0; 1,2; oder 1,5) is something you should expect.

I am not sure what you are up to (the technology does matter in the advice) but you can leave the format as well as list separator to the translators to decide. In .Net list separator is given, though (no need to ask translators for input, just use appropriate property of CultureInfo class).

Upvotes: 3

ckittel
ckittel

Reputation: 6646

Sorry to say, but I don't know about your first question. However, as far as version numbers go, they are generally left untranslated. End users typically attribute little meaning to the version's numeric value (they are infact NOT numeric in nature. 3.90 < 3.100). They are simply discrete numbers with a universally-accepted separator, and not natural numbers with natural "grouping/decimal" separators.

In addition to end-user experience with version numbers. Developers are often known to parse version numbers in the standard format of {major}.{minor}.{revision}, using . as the well-known seperator character.

I did find this link that talks about your first question (sort of). I don't know how authoritative or credible it is; but it doesn't look dubious.

Upvotes: 2

Related Questions