I think improving VE to understand translate, and expanding the training/documentation for translate are the best next steps. This is also a problem on Meta-Wiki.
Removing the translate setup from the pages seems problematic as we're trying to make info available in languages beyond just English.
-greg
_______________ Sent from my iPhone - a more detailed response may be sent later.
On Apr 1, 2016, at 9:49 AM, Brion Vibber bvibber@wikimedia.org wrote:
So based on notes from Niklas on the bug, it looks like there are two main problems:
- VE treats <translate>...</translate> chunks as uneditable extension
blobs.
- Some/many pages use <translate>...</translate> incorrectly: spanning
paragraphs, markup level boundaries, etc.
So problem 1) can be improved in two ways: 1a) Have VE treat <translate>...</translate> as more or less like plaintext or a div or something 1b) Much fancier sub-document editing
Fixing problem 2) means refactoring broken pages in ways that presumably would require at least some of their translations to be re-created.
I don't know whether 2) is caused by problems in the translation interface, or by people further editing the pages without a detailed understanding of how the <translate> and <!--T:123--> markup bits work, or a combination of both.
-- brion
On Fri, Apr 1, 2016 at 7:39 PM, Brion Vibber bvibber@wikimedia.org wrote:
On Fri, Apr 1, 2016 at 7:35 PM, C. Scott Ananian cananian@wikimedia.org wrote:
Proper VE/Parsoid support for the <translate> extension has been wanted for a while now. It hasn't made a list of quarterly goals yet. Help wanted, certainly.
This is a HUGELY important dogfooding goal; we need to be able to edit the wiki about our own product!
Anything we can do to help out?
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l