Opened 8 years ago

Closed 7 years ago

#7283 closed (fixed)

Documentation mixes up the terms "internationalization" and "localization"

Reported by: jdetaeye Owned by: mtredinnick
Component: Documentation Version: master
Severity: Keywords: localization internationalization
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Both terms have a distinct meaning (see eg
Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes.
Localization is the process of adapting software for a specific region or language by adding locale-specific components and translating text.

The django documentation on "internationalization" doesn't make such a distinction and mixes both.

Attachments (1)

i18n.patch (3.2 KB) - added by jdetaeye 8 years ago.
Documentation update

Download all attachments as: .zip

Change History (6)

comment:1 Changed 8 years ago by jdetaeye

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

If the ticket is accepted, I am more than willing to submit a documentation patch.

Not sure how that'ld work out with the documentation refactoring, which I understood is ongoing...

comment:2 Changed 8 years ago by Simon Greenhill

  • Triage Stage changed from Unreviewed to Accepted

We're perfectionists (with deadlines), so we should get it right.

Changed 8 years ago by jdetaeye

Documentation update

comment:3 Changed 8 years ago by mtredinnick

  • Owner changed from nobody to mtredinnick
  • Status changed from new to assigned

Although there is some confusion in that document, this patch doesn't make it all that much better unfortunately. For example, the "three step" section is actually internationalisation in the first step and localisation in the next two, not all internationalising or all localising (marking up strings for translation is internationalisation; it requires no translation skills or locale knowledge). Similarly, the i18n.txt does cover internationalisation, since it talks about things like using the ugettext family of functions (again, not part of the localisation step).

However, your greater point is well taken. There is indeed some confusion in there and separating out the internationalisation process (the developer side) from the translator side from the third, user side of things is one of the reasons I'm about to pull that document apart. So I'll take close this ticket when that's merged.

comment:4 Changed 7 years ago by ramiro

See also #10260

comment:5 Changed 7 years ago by ramiro

  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed in r12440 (trunk pre-1.2) and r12449 (1.1.X branch).

Note: See TracTickets for help on using tickets.
Back to Top