Re: i18n and l10n question

it works now. Or translations aren't really inline, but I couldn't use that
document-thing, because the translations were all in the document I was
transforming. I now use //factory, which is the root of our document and it
works fine.

The reason I'm using _ in stead of -, is because that is the way I get the
current locale from the Java application.

therefore it is necessary that we follow l10n rules.

yes but often  the i18n lookup table with the
language translations is separate from the actual document, which often
makes it easier to add new translations.

If your translations are "inline" then all you need to to is remove the
<xsl:for-each select="//entry"> and </xsl:for-each> lines.

Also I note  that you are splitting the locale on _ rather than - . -
would be more normal for language codes such as en-uk (ISO 639-1 or ISO
639-2).

David