Page MenuHomePhabricator

Allow languageConverter to process interface message
Open, Needs TriagePublic

Description

As of now, if we were to set up interface language, we can not take advantage of the LanguageConverter, which works better in many ways where we don't have to create different page for variations of the same language. It is not possible now to ask LanguageConverter to process interface message based on a default and interface-language. I hope something like a magicword which could process interface message automatically using LanguageConverter.

Event Timeline

Viztor created this task.Aug 7 2019, 1:23 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 7 2019, 1:23 AM
Viztor added a comment.Aug 7 2019, 1:31 AM

It's extremely difficult now to have interface message translated, while a lot easier for content. Suppose a template is transcluded in a system message, there does not exist a way where we can localize these templates without duplicating them, which is possible for content.

Shizhao added a subscriber: Shizhao.Aug 7 2019, 3:16 AM

In the past it was indeed the allow languageConverter to process interface message, but then I can't remember why it was forbidden.

Viztor added a comment.Aug 7 2019, 5:51 AM

I feel like we could have a magicword to invoke the processor manually if that ever becomes a problem in any case.

Could you provide a specific example with links for this problem, and what you would expect to happen?

Viztor added a comment.Aug 7 2019, 3:52 PM

Could you provide a specific example with links for this problem, and what you would expect to happen?

So if a MW:MSG is set to include a template. LanguageConverter will not work. You will have to create a different template for each language variation.