Idea: Change the names of translated homepages
Since we’ll not provide informations about languages in the Wiki (we are not is Wikipedia) and pages of the same language can be listed clicking on the appropriate tag, we could reduce the names of the homepages to the language name only.
So we get a better “hierarchy”, for example
- [home icon] > Wiki Home > Dutch
- [home icon] > Wiki Home > Wiki Home Dutch
BTW: How are pages renamed? Is an automatic redirect from the old name created?
I like the idea of organizing the translation pages!
Being a little picky, the WikiHelp [developer.qt.nokia.com] page suggests CamelCase for page titles. With that in mind, we should name the translated pages as WikiHelpGerman instead of WikiHelp_German.
Now my question: Are translations an exception to this rule? ;-)
There was a thread on whether CamelCase should be used [developer.qt.nokia.com], maybe this need some more discussion over there.
I did some thinking about the issue today. We are about to get* the groups feature out of the door and into public beta. Then one could found a … say … Dutch group. For that group, one could request a wiki… See where I’m going?
Other than that, it probably makes sense to come up with some sane form of hierarchy. I just don’t have one at hand right now.
*) Yes, it’s fuzzy. We’re doing proper software development here. :-P
So, if there were a dutch group, the dutch wiki pages would go into that group, right?
Wouldn’t it be nice to have something like country flags on the top for all languages, in which the pages exist. The language could be kept for the next pages, you enter, if the language does not exist, it could display the english version… So to switch the wiki to another language with english as backup strategy..
Alexandra, would it be possible to add a kind of “language dimension” to the wiki at all?
This way, a page would exist only once, but in different languages. Anyone who would be willing would just have to hit a “translate this page” button and go on. Also, if the original page (english I would suggest), changes, all the translated pages could be marked as “dirty”.
Just some random thoughts, don’t shoot me if it’s too complicated to implement or goes too much into a Web CMS direction :-)
I personally think, Volkers idea is somewhat as my suggestion and would be much better than one wiki per language. Especially as the main (perhaps English) would always be present and the translations are optional. and you will not have the different languages got different directions (not too much :-) ).
Translations on the wikis I’ve seen (the KDE ones) are always a pain, and never seems to be possible to find a good solution. Even if groups really rocks our world, what about tags? Should tags be translated too? If not, when one person looks at all the results of the tag “foobar”, then all pages of all languages are found, which is always complicated.
IMVHO, the only sane approach is having completely separated wikis, like wikimedia does. MediaWiki also has a nice feature (namespaces) that helps a lot there, but still has the problem of the categories (in MediaWiki are very similar to the tags, as categories are created when somebody adds a category to a page).
BTW, I suppose integrating the devnet with a third-party wiki like mediawiki is plain impossible/unrealistic, isn’t it?