On Friday, April 1, 2016, C. Scott Ananian <canan...@wikimedia.org> wrote:

> Arlo actually implemented the Parsoid side of this:
> https://phabricator.wikimedia.org/T50891


<3


> We still need VE support: https://phabricator.wikimedia.org/T55974


 Cool, will concentrate my efforts there. :)

I hope we can figure out a nice intermediate behavior that keeps the
annotations and doesn't act too surprising to the user. I can't dedicate
huge amounts of time to it but would be happy to help where I can.

-- brion

 --scott
>
> On Fri, Apr 1, 2016 at 1:00 PM, Gregory Varnum <gregory.var...@gmail.com
> <javascript:;>>
> wrote:
>
> > 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 <bvib...@wikimedia.org
> <javascript:;>> wrote:
> > >
> > > So based on notes from Niklas on the bug, it looks like there are two
> > main
> > > problems:
> > >
> > > 1) VE treats <translate>...</translate> chunks as uneditable extension
> > > blobs.
> > >
> > > 2) 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 <bvib...@wikimedia.org
> <javascript:;>>
> > wrote:
> > >>
> > >> On Fri, Apr 1, 2016 at 7:35 PM, C. Scott Ananian <
> > canan...@wikimedia.org <javascript:;>>
> > >> 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 <javascript:;>
> > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> > _______________________________________________
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org <javascript:;>
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
> (http://cscott.net)
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org <javascript:;>
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
_______________________________________________
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to