This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal

eZ Community » Forums » Developer » i18n with an other language than...

i18n with an other language than siteaccess

i18n with an other language than siteaccess

Wednesday 18 April 2012 6:08:23 pm - 6 replies

Hi eZCommunity,

So, i'm on an eZ Community Project 2011.9
On a module and i've a GET variable to select the language.
I can fetch all the node and all the node's content in this language no problem

I've a select attribute and i need to i18n its value but it's translated in the siteaccess language and i want it to be in the language retrieved in the GET variable

I tried to change my site.ini > RegionalSettings > Locale in my module but no it doesn't work, i18n still in my default siteaccess language


So huge thanks if you have any idea...

Thursday 19 April 2012 9:35:44 am


i think there is no solution with standard i18n... then you could perhaps write an operator to do what you want..

be careful : the cache can "cache" what you wnat to do.


See you


Thursday 19 April 2012 10:00:37 am

Problem is.. how can i retrieve the translation from the correction translation.ts file...

As i see it right now, it's a huge process :

browse the translation folders
find the correct one
create an associative array

and for each string :

check if translation exists
display it or the original one


It will be so great if i could just override the i18n loading file process!


Thank you, and if you see it differently i'm interested

Thursday 19 April 2012 11:40:52 am


I think you can simply write a template operateur that's based on 'ezpI18n::translateText'

something like that:

{$my_text|myi18n( $my_context, $my_language)}

Modified on Thursday 19 April 2012 12:19:45 pm by Ousmane KANTE

Thursday 19 April 2012 1:54:11 pm

Yeah! i'm on it, i will post the template operator i've created if it works happy.gif Emoticon


Thank you

Thursday 19 April 2012 2:28:07 pm

Quote from Côme EDELINE :

Yeah! i'm on it, i will post the template operator i've created if it works happy.gif Emoticon


Thank you

Yes, that can be usefull for others blunk.gif Emoticon

you can also imagine your language parameters optional (default Language should be use)

Thursday 19 April 2012 3:22:42 pm

As for every tricky things i do on eZ or i can't remember, i save it :

Here is a resume of the code i've produced:


$eZTemplateOperatorArray = array();
$eZTemplateOperatorArray[] = array( 'script' => ''extension/extension_name/autoloads/myautoloads_operators.php',
                                    'class' => 'myAutoloads',
                                    'operator_names' => array( 'i18n_custom' ) );
class myAutoloads
    public $Operators;
    function operatorList()
        return array( 'i18n_custom' );
    function namedParameterPerOperator()
        return true;
    function namedParameterList()
        return array( 'i18n_custom' => array( 'context' => array( 'type' => 'string',
                                                                  'required' => true,
                                                                  'default' => 'my_default_context' ),
                                              'language' => array( 'type' => 'string',
                                                                   'required' => false,
                                                                   'default' => 'eng-GB' ) ) );
    function modify( $tpl, $operatorName, $operatorParameters, $rootNamespace, $currentNamespace, &$operatorValue, $namedParameters )
        $ret = '';
        switch ( $operatorName )
            case 'i18n_custom':
                $operatorValue = self::i18n_custom( $namedParameters['context'], $operatorValue, $namedParameters['language'] );
     * Retrieve translation in specific language
     * @params context STRING
     * @params source STRING
     * @params language STRING
     * @return trans STRING
    function i18n_custom( $context, $source, $language)
        $comment = null;
        $localeCode = eZLocale::instance($language)->localeFullCode();
        $ini = eZINI::instance();
        eZTSTranslator::initialize( $context, $localeCode, 'translation.ts', false );
        $man = eZTranslatorManager::instance();
        $trans = $man->translate( $context, $source, $comment );
        if ( $trans !== null ) {
            return $trans;
        eZDebug::writeDebug( "Missing translation for message in context: '$context'. The untranslated message is: '$source'", __METHOD__ );
        return $source;
{'my string'|i18n_custom('my_context', 'jpn-JP')}

Modified on Thursday 19 April 2012 3:25:26 pm by Côme EDELINE


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from