Use the Translate Extension
So far the proposed method for translations is to have each language's community do all the translations manually.
In the Spanish speaking countries we have made multiple attempts at translating the content from the original english versions. However, we have yet to complete that process because manual translation is very time consuming and noticing changes in the originals is difficult.
The Translate extension (https://www.mediawiki.org/wiki/Extension:Translate) is a toll designed specifically to help make translations easy and always based on the original, which on Wazopedia would be english.
Map Editor commented
As I know this is already implemented.
@Jirka Bureš: concerning your questions, it would be my ideal to separate language and location. If a country/region has it's own guidelines, the community can make their local wiki. They either can include parts of the (translated) global content or refer to it for detailed explanation. If communities are not as far as to making their own guidelines or making their own wiki (and there are many), we would like them to be able to read the general information in their language or a language of their choice. Imagine a Czech speaking Wazer living in Ruanda (as an example) and starting to edit, we would rather like him to read the translated global pages instead of using the Czech local guidelines in Malaysia. Of course, a condition is that the global pages only contain info that is applicable to all Wazers in all locations.
Klaas De Smedt commented
We should use the MediaWiki Language Extension Bundle (short: MLEB) where the Translation Extension is part of. More information on the mediawiki page:
Robin Dlc commented
To be honest, I'm unsure about what Translate Extension does... But in the end, what we need, specially for languages shared by many countries, is a tool to monitor the translation progress. What has been translated and what doesn't and also to inform if there are changes in the original. For me is most important to have all this control in our hands than the fact of being automatically translated. Also we must remark that we talk about "translate". Content must remain exactly the same. We are talking about translating the GLOBAL wiki, not about local contents.
The first idea was that we could include the basic information from the global pages in our local pages, which than only needs to be updated once in the global space.
I will reccomend to my Czech friends to not translate the global Wazeopedia into Czech but use the transferred content and gradually add new pages as needed and keep all Czech content on third-level domain under Wazeopedia. The result will be an independent, separete Czech Wazeopedia.
What do you suggest?
@moveez I agree with you. There is a second issue. Imagine that global page is fine and there are a special country additions. We will get nice translated page and. And what else? Special country specific brief but confused page or enlarged duplicate of translation on opposite pole.
It will bring more work for country Wiki Masters. I heard about separated third-level domains for local wikis (e. g. cs.wazeopedia.com). I don't know if it is still valid idea.
If the info on the global pages contradicts local guidelines, it is not global information. That is exactly why I would like the translators join together to discuss the content of the global pages, so it becomes more accurate
@moweez OK. But a lot of information on global page is in contradiction with local guidelines. :( Translation of global wiki and local content is unfortunate solution.
@Jirka:that is how the new Wazopedia is set up: global pages have general global information, only local pages may contain interpretations, guidelines on applications etc. I posted another suggestion to at least explain this in a basic page in the new wiki surrounding
To moweez: Do we need two slightly different versions of Wiki. One version at local space and one in global space? It will bring mess.
I would like to emphasize the importance of the translation extension of global pages in the global space. The main argument is that it will stimulate global discussion and enhance the specific content being really global. Other big advantages are the ease of maintenance for translated content. The argument that translated content is difficult to verify does not stand much ground, as it will count as much for local spaces. In fact, in local spaces, it is even harder to check, because people are perhaps not aware of a global base page. In the global space, at least it is more accessible and better to check, because the link with the base page is clear. However, I do not support an automatic translation possibility, because those translations are often not very accurate. Better no translation than automatic translation.
Hacer traducciones manualmente es un proceso lento, y generalmente mal actualizado.
La experiencia en comunidades de habla español (latino) como la mía, es esa, siendo lo propuesto, el usar extenciones que traduzcan automaticamente, aún sabiendo que la traducción no siempre será tan buena, es lo menos engorroso y estará actualizado.
Las distintas comunidades por país podrán incorporar solo lo específico a cada uno, no aumentando o duplicando información que podría afectar al servidor.
La experiencia de traducciones del TTS podría servir, ayudando a mejorar la traducción cuando se requiera en algunos términos .
Translations do manually is a slow process, and generally poorly updated.
Experience in Spanish-speaking communities (Latin) as mine, is that, being as proposed, using extensions that automatically translate, knowing that translation is not always so good, it is less cumbersome and will be updated.
Different communities by country can incorporate only the specific to each, not increasing or duplicating information that could affect the server.
The experience could serve TTS translations, helping to improve the translation as required in some terms
We discussed it months ago, proposed processes for working on translations using it, and found technical, usability, and manageability issues with it. Don't expect this to happen.
It was mentioned a while ago on a conference with the developers, that the best option for Communities might be to transcluded the global page (or other page from another country) they want to translate, into a special translation space in their local wiki. Then they could run a translation extension on it locally in that space, and use the result in their local wiki.
This has the side effect of duplicating storage server side for these pages, but was the best option available at the time according to the Devs.