Forum OpenACS Development: Localization questions
In particular, I need to use the message 'Delete' on one of my pages.
It seems that defining the key and message in my own package requires the duplication of translating the same phrase multiple times across multiple packages.
Is there a common repository for 'common' phrases -- or should I create new keys for every phrase, even if it is reused?
For example, in my installation the phrase Delete exists in:
I saw some mention on the translation server that there were a lot of keys consolidated, but, is there an effort to combine keys that contain the same message?
Or, should each package maintain its own set of keys?
thanks for the compilation of messages that could save
effort of translators or/and programmers. I think, however,
that it is the wrong approach to focus on the mass of
single words. The most laborious work ist not typing
translations for single words, but
- finding the contexts, and
- consolidating terminology.
You and Joel are right that programmers should not simply
create new message keys without consulting a central
repository. This repository, however, should contain some
hint leading to the .adp page or other UI context that
displays the message in question.
Then, the programmer could decide
- if his intended usage matches the terminology of the keys
already available, or
- if the new terminology diverges and a new key must be
created (ideally after some more deliberation about
the usability and consistency of the terminology).
As Anja already warned here,
much care is needed to merge keys.
I cross-checked your list with our translations, and there
are many differences, although it's also a Germanic language
(so I would suspect there are still more problems with
languages less akin).
Administrative Actions: concatenated in one word, needing
lower case initial letter;
This action cannot be reversed: transcribed by one Word
This action will take...: different Word ("Vorgang")
Action in Curriculum: very preliminary due to broken
sometimes standing not alone (needing upper case) but also
sometimes prefixed by object (needing lower case)
used for very different things:
E-Mail Servers ("genehmigt)
member state ("freigeschaltet")
other cases (mostly "freigegeben")
in more general cases as with filestore, a different word is needed ("Autor") than in more concrete ones as forums and news ("Verfasser").
To confirm: translated as noun (needing upper case)
Different word order (needing upper case) same as with Administer above
only sometimes used for the email letter itself,
often synonymously used like email address, and
sometimes meaning the action of emailing, both requiring
different (more precise) translation
compositions like "database error" or "error message" need
single Word ("Fehlermeldung") and therefore sometimes lower
Static (HTML) Data: needs different composition "HTML-Daten"
very dangerous, see opposite bug description
incidentally all German occurrences are upper case, but English are different (e.g. faq.preview)
sometimes used as verb, sometimes used as noun.
Search forums: needs prefix "Foren DURCHsuchen"; if the same were applied to
Search users ("Benutzer durchsuchen") this would mean a
police personal search (Leibesvisitation).
Compositions needing lower case as Administer or Error above
Just lower case problems due to word composition as above.
critical, see separate discussion
I'll create my own keys and leave it up to someone more educated to make the decision to consolidate.
Being educated in the US Public Schools, I am monolingual. As a result, I am handicapped when it comes to internationalization.
My initial thoughts were, I'm using the phrase Email Address. Certainly someone must have already translated that phrase, so, do I force someone to translate it one more time or are there common phrases. Similarly the words Yes, No, Delete and a few others came up -- and were in a number of different packages. I didn't expect basic words to have different meanings.
With the explanation provided, it makes perfect sense.