https://bugzilla.wikimedia.org/show_bug.cgi?id=57469

--- Comment #5 from [email protected] ---
Ah, I see .. The first example is correct behavior since isolated "<ref>" or
"</ref>" are always parsed back as text and hence there is no need to
nowiki-escape them.

However, the escaping code does need an update to deal with the second example.
It currently only handles matching opening/closing extension tags in the same
text node. 

[subbu@earth tests] echo "&lt;ref&gt;foo&lt;/ref&gt;" | node parse --html2wt
<nowiki><ref>foo</ref></nowiki>
[subbu@earth tests] echo "&lt;ref&gt;foo" | node parse --html2wt
<ref>foo
[subbu@earth tests] echo "&lt;ref&gt;foo<p>&lt;/ref&gt;</p>" | node parse
--html2wt
<ref>foo

</ref>

Unlike escaping for link/heading tags, where we only need to worry about
wikitext on a single-line, the opening and closing tags for extensions can be
split anywhere in the DOM. So, a conservative approach would be to always
escape individual <ref> or </ref> tags which, in some cases, might lead to
excess nowiki escaping, but will always be safe.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to