Frank Peters wrote:
> Hi lepennuisic,
>
>> About the multilingue support i think your solution and
implementation is very complex and non-intuitive.
>>
>> I think the wikipedia solution ( mediawiki powered ) of simple tag
in a page and languages on the left panel is more simple, as an exemple
take a look at the spreadsheet page :
>>
>> http://en.wikipedia.org/wiki/Spreadsheet
>>
>> If you clic on the left language panel 'french' the page :
http://fr.wikipedia.org/wiki/Tableur appears.
>>
>> that system is base on simple tag : [[fr:Tableur]] on the Speadsheet
page and i believe it's a better solution than a complex structure.
>
> Thanks for the hint. Indeed, I didn't know that beahviour and I like it.
> This would definitely allow us to get around the requirement of
> sharing the same title. I will see if (and how) that can be
implemented with
> our OOo wiki, particularly how we can dynamically display the
language switch.
>
> Any pointers?
How about the plone solution of Andreas?
We have a lot of very good feedback of the docu volunteers working on
OOoAuthors.org with this tool.
One of the reasons for OOoAuthors.org was the very uncomfortable stuff
on the documentation project.
The suggested solution of Andreas could be a a way to bring all the
power of documention.openoffice.org an OOoAuthors.org together again.
Andreas sent You a mail about it some time ago and post a hint yesterday
too.
It will be great to get some feedback for this idea.
Kind regards
Marko
>
> I would still like to propose to have the structure of the documentation
> pieces be in parallel for different languages. That would allow to easier
> keep track of the available docs pieces.
>
> Frank
>
>
>
>
>>> PROPOSED SOLUTION
>>> -----------------
>>> The solution would include having a fixed agreed-upon structure
>>> for documentation that would allow to place different doc
>>> languages side-by-side.
>>>
>>> If all languages follow the same, well-defined structure scheme
>>> it would be easy to implement a language switcher in the wiki
>>> that does the switch programmatically without having to
>>> maintain matching tables.
>>>
>>> This only applies to documentation. The mother native-lang
>>> project may still keep its wiki structure as preferred.
>>>
>>> IMPLEMENTATION
>>> --------------
>>> The structural scheme of the Documentation wiki content is as follows:
>>>
>>> wiki/Documentation/$DocTypeOrBook/$SubSections/$SubSubSections
>>>
>>> Examples for $DocTypeOrBook are
>>> - FAQ
>>> - HowTos
>>> - OOoAuthorsManuals
>>> - BASIC Guide
>>>
>>> Examples for $SubSections are
>>> - FAQ/Writer
>>> - Howtos/Calc
>>> - OOoAuthorsManuals/Getting Started Guide
>>> - BASIC Guide/Language
>>>
>>> $SubSubSections are furthr subdivisions (if required). I think you get
>>> the idea.
>>>
>>> The idea is to maintain a parallel structure for "native languages"
>>> alongside the docs, for example:
>>>
>>> wiki/Documentation/FAQ for FAQs in en, or
>>> wiki/Documentation/en/FAQ for FAQs in en
>>> (would require move of topics in the wiki)
>>> wiki/Documentation/fr/FAQ for FAQs in fr
>>> wiki/Documentation/de/FAQ for FAQs in de
>>>
>>> Likewise, for a particular FAQ, for example:
>>>
>>> wiki/Documentation/FAQ/Writer/General/HowToFormatACharacter (in en)
>>> wiki/Documentation/fr/FAQ/Writer/General/HowToFormatACharacter (in fr)
>>> wiki/Documentation/de/FAQ/Writer/General/HowToFormatACharacter (in de)
>>>
>>> The langugage ISO code after the wiki/documentation part
>>> of the path would be the identifier. This approach would allow
>>> to use Google to either
>>>
>>> * search documentation in all languages by searching
>>> through wiki/Documentation
>>>
>>> * search documentation in a particular languae by searching
>>> through, e.g. wiki/Documentation/fr
>>> (this would require to move all English documentation to
>>> wiki/Documentation/en)
>>>
>>> Switching languages would be handled by a language bar
>>> that is easy to be set up and switches languages by
>>> changing the language ISO coide in the URL.
>>>
>>> *However*, this requires the wiki pages to share a common
>>> page name. In the current mediawiki version, this page
>>> name is also displayed as the page title. I understand that
>>> it is inacceptable for a non-English wiki page to display
>>> an English page title.
>>>
>>> With the updated wiki engine (that will hopefully be available
>>> soon), however, we will get the DISPLAYTITLE functionality that
>>> allows a different title to be displayed. This would allow the
>>> pages to share a common page name, but still display a
>>> localized title.
>>>
>>> We would also need to agree upon a wiki page title scheme
>>> that makes it easy to handle the URLs. Engslih being the
>>> lingua franca of IT, I propose to use English page names
>>> for the wiki pages. That means, even if you create a French
>>> page inside the French Documentation hierarchy it would need to
>>> have an English page name (that would only affect its URL!).
>>>
>>> We also need to have a basic migration strategy in place to
>>> handle existing documents without too much hassle, meaning
>>> moving them to the new hierarchy and possibly renaming them.
>>>
>>> The result of all this would be that a Documentation page
>>> contains a language bar marking the currently shown language
>>> and all potentially available languages. Since mediawiki
>>> displays links to non-existing pages differently, it's readily
>>> visible which pages need translation and which languages
>>> are available for a given page.
>>>
>>> Clicking that language would bring you to the localized
>>> version of that page. This localization does not have to be
>>> a "mere" translation. Instead, the native-lang community
>>> can decide to describe a given topic in a completely different
>>> way depending on the cultural requirements.
>>>
>>> Another issue that must be addressed is how to get notified
>>> if wiki page localizations get out of sync. To be able to
>>> do that, one must define a master language and I don't know if
>>> we actually want to do that.
>>>
>>> Thanks for your help and thoughts on this
>>> Frank
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
[EMAIL PROTECTED]
>> For additional commands, e-mail:
[EMAIL PROTECTED]
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
