Druckbare Version
Hi everyone,
I'm developing a site in 3 languages. I'm using MM to prsent the firms' projects.
Some datas like Description must be translated so I thought to create 3 attributes : desc_fr, desc_en and desc_es, for example.
But i'm asking if its better to use translatedtext for example and how it works.
Thanks for your help.
Zitat:
Zitat von Charled
never do that!
* make your MM e.g Companies [mm_companies] and set checkbox for multilanguage and set languages en, fr and es (one of all is the default language; e.g. en)
* generate your attributes e.g.
** Name [text]
** City [text]
** Zip [text]
** ....
** Description [translated longtext]
* generate rendersettings and input mask and so on...
* create your first item => you can see at input field of description an icon as hint for translation
* fill out the mask => note: the fallback language is always filled in first - in your example is this en
* with the select in the right top corner you can switch to fr or es
* at description you can see the en text as helper to translate your text - translate to fr or es
thats all
in the frontend, the text is then automatically output, which language the page tree has or the fallback language...
Hi Zonky,
Thanks for your answer.
Just tried : great feature !
Note: the attributes translated select and translated tags are only for special applications and tables that do not come from MM. Please use the untranslated select and tags here. When selecting the alias column, however, you cannot currently use a translated alias - use the id column or another column with unique values.
Note sure I understand what this means.:eek:Zitat:
Zitat von zonky
o.k. - do not use translated select and translated tags ... or ask me first ;-)Zitat:
Zitat von Charled
Now it's clear. ;-) ;-)Zitat:
Zitat von zonky