Forums / Developer / Localization of values trough l10n() simply doesn't work

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Localization of values trough l10n() simply doesn't work

Previous topic

Developer

Next topic

Author	Message
Sven Ryen	Thursday 10 July 2003 8:22:42 am I was under the impression that the l10n operator would be connected to the current ContentObjectLocale, but I'm incapable of making formatting reflect what language is currently displayed. I.e. if I have a setup like this: Language 0: nor-NO Language 1: eng-GB Language 2: .... and append /language/[0\|1\|whatever] to any links, the content from the database appear translate - as expected, but no matter what I do, I can't make the text in templates reflect the current translation/locale. What am I missing?

Author

Message

Sven Ryen

Thursday 10 July 2003 8:22:42 am

I was under the impression that the l10n operator would be connected to the current ContentObjectLocale, but I'm incapable of making formatting reflect what language is currently displayed.

I.e. if I have a setup like this:
Language 0: nor-NO
Language 1: eng-GB
Language 2: ....

and append /language/[0|1|whatever] to any links, the content from the database appear translate - as expected, but no matter what I do, I can't make the text in templates reflect the current translation/locale.

What am I missing?