On 6/11/05, Michael Wechner <[EMAIL PROTECTED]> wrote: > I still receive from time to time "untranslated" on i18n stuff and it's not > clear to me what the reason for this is. Any other people experiencing this?
[No research, just experience] "untranslated" appears when key is the within the tag rather than a property, and the key does not exist in the appropriate language file. These return blanks: <18n:text key="willNotBeFound"></18n:text> <18n:text key="willNotBeFound"/> This returns "untranslated": <18n:text>willNotBeFound</18n:text> "untranslated" also when i18n is used for a property, such as Value of a Button. I guess the i18n tags are added around the label before it passes through i18n. "untranslated" is very useful for debugging. It should be easy to change i18n if that is desirable. If it is changed, it would be better to keep the original text than set it to blank, possible adding a mark to show it was supposed to be translated. I prefer the current method. It allows writing everything in the default language, adding the i18n tags around phrases needing translation, and seeing "untranslated" during testing. The <i18n:text key="some-key"/> is useful for when you want a phrase to appear only if a translation exists. It allows language-specific help, such as "Click here to return to the default language", and satisfies customer requests like "Can you add this option only to the German version of the layout?" solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
