On 06/10/2014 07:24 AM, Federico Leva (Nemo) wrote: > Gabriel Wicke, 10/06/2014 02:30: >> I'm also curious how the this work will interact with >> https://www.mediawiki.org/wiki/Content_translation, which is also based on >> Parsoid. > > There is no interaction because PageMigration doesn't need to manipulate > HTML. :)
Working on Parsoid HTML can be just an easier way to manipulate wikitext. > AFAIK there are solutions to get the plain text, e.g. people often want to > look up the text of a Wiktionary entry from the API (with varying degrees of > success), but I'm not sure if there is something available to do the > opposite or one would need to build it on top of those existing tools, by > "subtraction". You could of course remove the text content from Parsoid HTML & convert that back to wikitext. I'm still wondering what the longer-term plan for <translate> is once content translation becomes available. To me it seem that there will be a good amount of overlap in its functionality. If content translation will basically replace the <translate> functionality, then that would make things much easier for Parsoid and visual editing. Gabriel _______________________________________________ Wikitext-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitext-l
