That's ok if they are on different continents. That is actually a plus because work is getting done 24 hours a day. What they need is a support group chat for each other. They would all be able to read English if they are translating right? Teach a few simple wiki markup such as links and what to do with categories. Then they help others who in turn help others. We have over 40 in a chat who help each other and have fun at the same time. And they were all scared of the wiki but couldn't believe how easy it was once they started. They are actually waiting on me for more translations to do because I can't keep up with them. I know there is only 1 translating this language or that language. We have that too. One person is doing Swahili while another one is working on Japanese. Also, you mark pages for translation. You control whether to include templates or exclude variables in template calls. They are really just translating the page title and text. Images, tell them to add -fr.png or -es.png to the end then upload the changed files. Tom
---Sent from my iPhone Unfortunately that won't work for our workflow. My translators are on different continents from me and aren't well versed in mediawiki stuff. Since we use the collection extension to print our manuals I was planning to provide Word documents for them to use, both in English and in the target language, and then update the wiki based on markups. On Tue, Jun 03, 2014 at 9:52 AM, Tom <t...@hutch4.us <mailto:t...@hutch4.us>> wrote: Use the translate extension! Since you admit human proofreaders will have to go through and verify translations, why not perform both tasks at the same time. The translate extension allows for connection to a translation service and can auto fill the translation for you. At the same time a translator can make adjustments so you're not creating lots of pages with inaccurate translations. Tom Sent from my iPhone > On Jun 3, 2014, at 12:37 PM, John Bibby <johnbibbyjohnbi...@gmail.com> wrote: > > I too have a similar problem, and would like to know the best way of > dealing with it - in particular if file-names also need to be translated. > > JOHN BIBBY > > >> On 3 June 2014 17:33, Yan Seiner <y...@seiner.com> wrote: >> >> I am tasked with translating our wiki into a couple of languages. We have >> several thousand pages, and just creating all of the sub-pages is a >> monumental task. >> >> I've looked at the various translate extensions, and they seem to be >> either on the fly, or assisted manual. >> >> Is anyone aware of a translation extension or script that would spider >> through the wiki, using Google or MS to translate each page, and create the >> appropriate language sub-pages? >> >> I know that human proofreaders would have to go through each page after >> that and fix/correct/rewrite the automatic translations, but at least all >> of the subpages, with the appropriate images, templates, etc. would be in >> place, making the job much, much simpler. >> >> --Yan >> >> _______________________________________________ >> MediaWiki-l mailing list >> MediaWiki-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l > _______________________________________________ > MediaWiki-l mailing list > MediaWiki-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
