Page MenuHomePhabricator

MassMessage should not cut title
Closed, InvalidPublic

Description

What I paste:

{{subst:#switch:{{subst:CONTENTLANG}}|es=CEE Primavera 2016 Encuesta|#default= CEE Spring 2016 Survey|hu=CEE Tavasz 2016 kérdőív|sq=Anketa e CEE Spring 2016|et=Kesk- ja Ida-Euroopa kevad (CEE Spring) 2016 küsitlus|tr=Orta ve Doğu Avrupa (CEE) Bahar 2016 Anketi|uk=Опитування учасників CEE Spring 2016|az=Vikibahar 2016" iştirakçılarının sorğusu|ru=Опрос участников Вики-весны 2016|ba=Вики-яҙ 2016 конкурсында ҡатнашыусыларҙын һорау алыу|mk=Анкета за СИЕ Пролет 2016|lv=CEE Spring 2016 aptauja|be=Апытанне CEE Spring 2016|bg=Проучване относно ЦИЕ Пролет 2016|el=Δημοσκόπηση CEE Spring 2016}}

What I get:
https://bg.wikipedia.org/w/index.php?title=Потребител_беседа%3ABase&action=historysubmit&type=revision&diff=7435325&oldid=6548800
What I expect:

== Проучване относно ЦИЕ Пролет 2016 ==

Event Timeline

@Base that limitation isn't based on the mass message extension. Likely, the reason is that the maximum section name limit is applied before the wikitext would be parsed. I copied and pasted the section heading at https://en.wikipedia.beta.wmflabs.org/w/index.php?title=User_talk%3ADannyS712&type=revision&diff=391441&oldid=391395, and it also got cut off.

Nemo_bis subscribed.

@Base that limitation isn't based on the mass message extension. Likely, the reason is that the maximum section name limit is applied before the wikitext would be parsed. I copied and pasted the section heading at https://en.wikipedia.beta.wmflabs.org/w/index.php?title=User_talk%3ADannyS712&type=revision&diff=391441&oldid=391395, and it also got cut off.

Indeed, so this isn't a MassMessage bug but MediaWiki core design; closing as invalid for clarity as long a the report title is phrased this way.

There is a case to be made for a feature request of the kind "Allow MassMessage to carry template calls bigger than size limits" (which IMHO is not a very good idea), but that's not a very good idea because we cannot know how a certain wikitext will end up being parsed in a local wiki: the workaround is to create a template locally to host your desired content, which MassMessage can subst; creating many local templates of course is not especially nice either, but we end up in T6547 territory.

I think the way to go is to formulate this as some feature requests to improve the sending of a translatable page.