Thanks for notice. We're already sending requests with header

I agree that newline "\n" is not a good signal to separate parameters, however for this case we have a nested infobox with attribute "embed=yes", which may be a strong signal to make a segmentation.

Got it, thanks. Please update the thread when the profile translation is implemented in REST API.

Thanks. For our use case it will be easier if /transform/wikitext/to/html keeps data-mw inlined in result HTML.

Ack. When will this happen? And will you keep inlined data-mw in HTML returned by /transform/wikitext/to/html endpoint?

Hi ssastry,

Hi liangent,

Ack. Please update the topic when T128040 is resolved so that we can start working on our side. And I'm wondering what's the ETA about that?

Thanks for the explanation. The problem is we can't get the tokenization results for the last three templates from data-mw, because they're plain strings. Use "Infobox ship image" as an example, from data-mw we can only get

Thanks for debugging! However when trying on http://rest.wikimedia.org/en.wikipedia.org/v1/?doc#!/Transforms/post_transform_wikitext_to_html_title_revision I'm still seeing