VisualEditor: Content inside templates for translation of templates does not render in friendly ways
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• Jaredzimmerman-WMF
	Oct 7 2014, 3:46 AM

Description

translate syntax in VE

Translated text should probably not display with syntax in VE

Version: unspecified
Severity: minor

Attached:

Details

Reference: bz71730

Related Objects
Search...

Status	Subtype	Assigned	Task
Open		None	T351374 Improve Translatable Pages based on research input
Open		None	T131516 Reduce or eliminate the need for the user to touch <translate> tags and unit markers
Open		None	T143327 Make the Translate extension be based on DOM, not strings
Resolved		Esanders	T73730 VisualEditor: Content inside templates for translation of templates does not render in friendly ways
Open	Feature	None	T55974 Create a VisualEditor plugin tool to add/edit translations and translation variables (Translate extension)
Resolved		Arlolra	T50891 Parsoid should support <translate> and <tvar> natively as they are not normal parser tags
Declined		ssastry	T105186 Support Translate extension in Parsoid
Resolved		Arlolra	T55874 Add a generic extension registration mechanism
Open		None	T49344 Internal nodes should eventually be in a separate document ("sub-documents")
Resolved		ihurbain	T261181 Make Translate extension compatible with Parsoid
Resolved		Nikerabbit	T44239 Translatable pages (pages using Translate extension syntax) can create unusable section edit (editsection) links
Resolved		Nikerabbit	T274881 Change translation variable (tvar) syntax
Resolved		ihurbain	T291855 Adjust meta tags handling for annotations
Resolved		ihurbain	T292285 Add messages for the Translate annotation in the Translate extension
Resolved		ihurbain	T295170 Move Parsoid's Translate implementation into the Translate extension repo
Resolved		ihurbain	T296107 Special treatment for translation unit marker comments in <translate>
Resolved		ihurbain	T295837 Analyze newline dirty diffs introduced by Parsoid around <translate> tags for rendering impacts
Resolved	BUG REPORT	ihurbain	T295233 PHP Notice: Trying to get property 'parentNode' of non-object
Resolved		ssastry	T295406 Look at selser failures in rt-testing caused by the Annotations feature
Resolved		ihurbain	T295330 WrapAnnotations breaks DSR correctness in some cases
Resolved	BUG REPORT	ihurbain	T296169 Parsoid sometimes nests the annotation tags when round-tripping wikitext
Declined	BUG REPORT	ihurbain	T296485 Annotation nesting detection is not well handled when annotations span over an attribute
Resolved	BUG REPORT	ihurbain	T296412 Rendering difference between legacy and Parsoid with <translate> tags around a heading
Open	BUG REPORT	None	T296408 Rendering difference between legacy and Parsoid with newlines after styling and <translate> tags
Resolved	BUG REPORT	ihurbain	T297770 Extended annotation ranges sometimes duplicate the closing tag when round-tripping with edits
Resolved	BUG REPORT	Arlolra	T299685 Some headings are missing on the main page on Meta-Wiki in Parsoid rendering
Resolved		ihurbain	T295834 Add special handling for annotation tags in template arguments
Resolved	BUG REPORT	ihurbain	T296392 Old syntax tvar breaks templates
Resolved	Feature	ihurbain	T305066 Make extended annotation ranges uneditable
Resolved	BUG REPORT	matmarex	T303298 mw:Placeholder elements are editable in VE
Open	BUG REPORT	None	T360267 {{TRANSLATIONLANGUAGE}} is not handled in Parsoid parses

Event Timeline

• bzimport raised the priority of this task from to Low.Nov 22 2014, 3:50 AM

• bzimport added a project: VisualEditor-EditingTools.

• bzimport set Reference to bz71730.

• Jaredzimmerman-WMF created this task.Oct 7 2014, 3:46 AM

see https://www.mediawiki.org/wiki/Communication?veaction=edit

Yeah, the Translate extension fundamentally doesn't work with VisualEditor in its current form, as I understand it. Much sadness.

I assume you mean translate tags as shown in the screenshot, because "translate templates" don't exist.

No, it means the ghastly mess that is {{TNTNTNTNTTNT}} :-)

(In reply to James Forrester from comment #4)

No, it means the ghastly mess that is {{TNTNTNTNTTNT}} :-)

The screnshot seems to be about this excerpt:

<translate>

More details at {{ll|Social media|Social media}}.
</translate>

{{ll}} only creates a link to Special:MyLanguage (which is not even in Translate now). (In the Translate docs we recommend to use Special:MyLanguage directly, but what can you do.)
So the summary currently mentions the only thing which is not in the screenshot. :)

Jdforrester-WMF added a project: VisualEditor.Nov 24 2014, 4:04 PM

Jdforrester-WMF moved this task from To Triage to Freezer on the VisualEditor board.Nov 24 2014, 4:20 PM

Nemo_bis changed the status of subtask T50891: Parsoid should support <translate> and <tvar> natively as they are not normal parser tags from Open to Stalled.Jan 28 2015, 6:57 AM

Aklapper mentioned this in T67653: VisualEditor: avoid causing "Translation unit markers in unexpected position" edit abort.Sep 29 2015, 8:25 PM

Arlolra closed subtask T50891: Parsoid should support <translate> and <tvar> natively as they are not normal parser tags as Resolved.Dec 29 2015, 11:39 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 29 2015, 11:39 PM

As described, this doesn't happen any more. VE + Translate still sucks, but that isn't not this ticket.

Restricted Application added a project: User-Ryasmeen. · View Herald TranscriptDec 17 2020, 7:12 PM

• Elitre unsubscribed.Jan 25 2021, 11:31 AM

VisualEditor: Content inside templates for translation of templates does not render in friendly waysClosed, ResolvedPublicActions

Description

Details

Related ObjectsSearch...

Event Timeline

VisualEditor: Content inside templates for translation of templates does not render in friendly ways
Closed, ResolvedPublic
Actions

Related Objects
Search...