On Dec 18, 2007 7:16 AM, Kent S. Larsen II kent@lusobraz.com wrote:
Turns out that the Proofread Page extension can be used for this. Apparently, Proofread Page is used on Wikisource for proofing scans and entering text from images.
I messed around four a handful of hours after feeling inspired from that website that was linked.
*I got a 'diff' like view of __TOC__ items (en on one side, fr on other other) *If the fr is missing prompt to create it, use a hack to use en as default text. *I found it much easier to have en side read only and the fr side mundanely writeable. *I just did cheesy <form> actions to a hack that pushed the changes as individual __TOC_ edits rather than using that sexy ajax thing they had.
I can see the need for work flow being what drives how you design this. Since I know nothing about actual translations and just did the raw diff edit.
The editing of complete static texts vs editing living wiki content seems quite easy. Especially with major content structure changes where the __TOC__ will get out of whack. Make big changes to en, potentially you could toss out the hours of work on fr.
You may like to look at the work of Alain Desilets who has been working on this for a while and should have some wikis/examples at hand. See http://iit-iti.nrc-cnrc.gc.ca/personnel/desilets_alain_e.html
Some of his work appeared in the WikiSym proceedings, see http://www.wikisym.org/ws2006/proceedings/ as well as some other places.
I'm ccing him so he can point you directly to his work.
Cheers, Dirk
On Dec 18, 2007 12:03 PM, Gabriel Millerd gmillerd@gmail.com wrote:
On Dec 18, 2007 7:16 AM, Kent S. Larsen II kent@lusobraz.com wrote:
Turns out that the Proofread Page extension can be used for this. Apparently, Proofread Page is used on Wikisource for proofing scans and entering text from images.
I messed around four a handful of hours after feeling inspired from that website that was linked.
*I got a 'diff' like view of __TOC__ items (en on one side, fr on other other) *If the fr is missing prompt to create it, use a hack to use en as default text. *I found it much easier to have en side read only and the fr side mundanely writeable. *I just did cheesy <form> actions to a hack that pushed the changes as individual __TOC_ edits rather than using that sexy ajax thing they had.
I can see the need for work flow being what drives how you design this. Since I know nothing about actual translations and just did the raw diff edit.
The editing of complete static texts vs editing living wiki content seems quite easy. Especially with major content structure changes where the __TOC__ will get out of whack. Make big changes to en, potentially you could toss out the hours of work on fr.
--
Gabriel Millerd
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
mediawiki-l@lists.wikimedia.org