Multilanguage

[matheo]

Be able to use multilanguages.
Same PID but double field to set title in french (for exemple) and in english

[ThiloWitt]

To translate the title only will not be enough in many cases. Is it possible to use the same PID with a new ID and a new field specifying the language, e.g.: PID = 1, ID = 1, LANG = ENG and then PID = 1, ID = 2, LANG = SPA. This would allow to have the same publication entirely translated and even attached files could have a distinct language. A default language should be selectable and when a translation is created, the form should also show the default language's content for easy translation (similar to what we see in Content).

[trichers]

My solution: I create for each language a extra field. E.g. title-de, title-en, title-fr
and in the template i ask for the current language and show only the fields

[porzellankompass]

I will like to follow @trichers at this.
Cause no one can scope the variety of languages and special designs of pubtypes.
Of course I can set a publication-type representing my language-dev and translations. Put in a relation to my pubtype.
Got it!
I am using only two languages mostly.
So the conclusion to have several pubfields with _de or _en ending is most practible.

[craigh]

Doctrine2 has a method for this already I believe.

[mazdev]

trichters solution so far is good, but we are going to have a permalink issue. As it uses the core_title.

Where you can edit the Groups, there you get a pop up for the Groupname and Description as multilanguage.

I was thinking if we could use the Edit Box for the "title" of the Publication for multilanguage, this would be already a good help. But I didn't figure out yet how to add this to the title field.

[matheo]

Multilanguage is a deeper issue to be treated after the conversion to Doctrine 2.
The multilanguage popup is supported by an apropiated handling of the multilanguage information for Grouptypes only, copied from the Categories system.

[mazdev]

Trichters Solution with always 2 fields for each language so far is a good idea. As I stated before, that the only problem would be the Permalink.

would there be any possibility if we put a second Permalink Form field for the second language and to tell Zikula or Clip which Permalink belongs to which title

Eg:

I create a Form with 2 title, let's say field 1 = title , field 2 title_de

Now put 2 Permalink Form fields: Permalink Field 1 uses "title" for default language, while the second Permalink Field uses "title_de" for the Permalink

Or any possibility to uses the lib/viewplugins/modifier.formatpermalink and how to use it in the Clip templates?