MoodleDocs talk:Language planning
- Should translators be expected to structure pages?
I think there is no other way. As competent as our documentation steward is, to be able to structure a page, you should be able to understand what is on the page. Providing help and a good example on the en pages should be sufficient.
- Should pages be provided in English?
I don't understand this question. The documentation exists in English, so the pages are here. I think I like the interlanguage links. Those can be a good start for the empty documentation in some language packs: "This page does not excists yet in this language. The English version is here. Feel free to translate or update yourself ;-)" .
- Certain language pack doc file content has been changed a lot plus links have been added e.g. Developer documentation.
If you want to keep the content the same over all the languages, then a wiki was not a good idea. However, the pros are far more important then the cons. Here the interlanguage link to en could solve some issues.
- How should versioning be managed? How important is versioning?
For security reasons, everyone should work with the latest code, so only for the latest code there is a need for documentation. On the other hand, I didn't see the content of the current doc pages change over the past 3 years, so that won't be a problem.
- How many interlanguage links should core category pages contain?
Only from Translated to English. On the English pages could come a link to a "language portal page", a starting point for the different languages of MoodleDocs, like this one: [[1]]
- Features to consider using: Export pages and Import pages
I don't see the use for it like it is implemented today. An export to a printable page or a static HTML may be??? No, don't see the use for it at all.
--koen roggemans 03:33, 14 February 2006 (WST)
- Clever Translation Coordinator, thanks for your comments - very helpful :-) --Helen Foster 17:29, 23 February 2006 (WST)
