Jon Stevens wrote:
on 10/14/01 2:17 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Following the threads on i18n for navigations, I'd just like to raise some
points on the subject:
You got it 100% right raphael.
+1
Also, make sure to use Turbine's localization service. DLR just put a bunch
Can both solutions be used at the same time?
As an example, use a string lookup tables for the default navigation.
This implementation would allow for a common navigation bar. Many
languages with similar length text would share the common navigation
bar, and the remaining languages would have
Paul Spencer wrote:
Can both solutions be used at the same time?
Sure. The default template would use string lookups for localized labels
while for some locales it would find some more specific templates and use
them instead...
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks -
Following the threads on i18n for navigations, I'd just like
to raise some
points on the subject:
i18n can typically be achieved in 2 different fashions:
- using different templates per locale (current Jetspeed way)
- using a string lookup table/class to store locale dependant
on 10/14/01 2:17 AM, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Following the threads on i18n for navigations, I'd just like to raise some
points on the subject:
You got it 100% right raphael.
+1
Also, make sure to use Turbine's localization service. DLR just put a bunch
of work into it
Yup it makes sense.
I just tested localizing a navigation, and it did not work.
Looking at the code, we seem to have overlooked navigations in the
TemplateLocatorService.
-Original Message-
From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]]
Sent: Saturday, October 13, 2001 9:07 PM
