How should we make a multilanguage Page.
I have installed a Localizer but no Messagecatalog until now. Maybe we start with the sandard Plone one and can do more afterwards.
Some questions
Which languages we should respect ?
(for me german, english)
Who is translating (not content but menus, etc...) ?
How we deal with multi_language content ?
I propose, since translations are mostly never synchronized, each piece language should be an own document. so if we have a tutorial in English and German, just have two documents indtead of one multilanguage one, where is a language button.
mfg winfried
On Friday, Jun 20, 2003, at 08:42 America/New_York, Winfried Ritsch wrote:
How should we make a multilanguage Page.
I have installed a Localizer but no Messagecatalog until now. Maybe we start with the sandard Plone one and can do more afterwards.
Some questions
Which languages we should respect ?
(for me german, english)
Who is translating (not content but menus, etc...) ?
How we deal with multi_language content ?
I propose, since translations are mostly never synchronized, each piece language should be an own document. so if we have a tutorial in English and German, just have two documents indtead of one multilanguage one, where is a language button.
I definitely want to support multiple languages, I would like to broaden to PD community beyond English speakers. While I think the multi-language content is currently not in sync, I do not think we should organize around that.
Instead I think we should plan the site around having one single structure, then the user would choose the language. There is currently not much Pd material that is in other languages besides English, so I think we could for now make a page dedicated to non-English PD docs that don't fit into the structure. If we have a separate document for every translation, then the navigation is going to get very messy as people add translations.
I think we should allow any language that someone is willing to translate for.
.hc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Winfried Ritsch wrote:
Which languages we should respect ? (for me german, english)
We should respect any language. Plone, with the help of Localizer, is designed to build multilanguage community sites.
How should we make a multilanguage Page.
Let's find how.
Hans-Christoph Steiner wrote:
Instead I think we should plan the site around having one single structure, then the user would choose the language.
Yes!
There is currently not much Pd material that is in other languages besides English, so I think we could for now make a page dedicated to non-English PD docs that don't fit into the structure.
There should be no specific pages for non-english materials and users. If the site is first built in english, there should be a way to translate everything without changing the site structure. I looks very possible with Plone/Zope/Localizer.
If we have a separate document for every translation, then the navigation is going to get very messy as people add translations.
If documents are made multi-lingual, they will show with the user's preferred languages (for me it would be french, then english).
I think we should allow any language that someone is willing to translate for.
Yes!
- -- Marc
Hello,
I think we should allow any language that someone is willing to translate for.
me to, so I propose to have as much languages as possible using the plone message catalog and add our definition for the surface. The content should be handled individually.
mfg winfried
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Plone Message Catalog is missing in Localizer... :-( I notice that the Members section is fixed. :-) - -- Marc
Marc Lavallée writes:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Plone Message Catalog is missing in Localizer... :-( I notice that the Members section is fixed. :-)
fixed...
I have forgotten. I hope this was the actual version.
mfg winfried
-
Hans-Christoph Steiner -
Marc Lavallée -
Winfried Ritsch