translation of an extension

Author Message

Georg Franz

Wednesday 16 July 2003 4:16:06 pm

Hi,

I am trying to make my first extension. I also want to use the translation feature of ez.

I've created the translation files in my extension directory with ezlupdate. But if I load the template, no translation is performed.

Do I have to put the new extension-translation in some ini.append file? Have anybody a tip for me?

Kind regards,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Jan Borsodi

Thursday 17 July 2003 1:47:00 am

To create translations for extensions you must make sure you are using the x18n operator instead of the i18n. The x18n operator is similar to i18n but takes the extension name as the first parameter, ie.
{"Name"|x18n('myextension','design/standard')}
Then create the translation file with lupdate and place it in extension/yourextension/translations.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Georg Franz

Thursday 17 July 2003 5:05:36 am

Hi,

thanx for your quick answer!

Maybe it's a bug of ezlupdate (windows version) or something else:

If you write something like
{"Okay"|x18n('mymodule', 'design/standard')}

the translation file will be "corrupted", in the ts-file following entry is produced:
<name>&apos;design/standard&apos;)}&quot;</name>
(instead of <name>design/standard</name>)

So don't make a whitespace between 'mymodule' and 'design/standard'.

{"Okay"|x18n('mymodule','design/standard')}

will work.

Kind regards,
Emil.

Best wishes,
Georg.

--
http://www.schicksal.com Horoskop website which uses eZ Publish since 2004

Jan Borsodi

Thursday 17 July 2003 5:25:55 am

Yes, it sounds like a bug in ezlupdate. We will take a look at this.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.