--- Comment #9 from Seb35 <> ---
Imho the more intuitive and practical meaning of this magic word (by reference
to my comment 8) is the first: page language of the frame. Hence the pages,
called as template, would have a consistent language even if called from a page
in another language. For instance a template could be translated in Arabic,
called from an English page, and an expression {{#time:j F
Y|2013-10-02|{{PAGELANGUAGE}}}} would be displayed in Arabic -- in fact I find
the default language should be Arabic in this case and not English as it is
currently the case, but this would be another bug.

It is also easier to implement since there are no caching problems. With this
solution, the entire logic for choosing the better fallback language of a
template is let to the calling page (e.g. with the resolution of the bug 45096,
or with the fallback mechanisms already on Commons). It would forbid the
conversion of the templates to auto-select the better language according to the
displayed page, but I don’t think it would be a drawback since it’s a new
feature, and there are already hacky ways to achieve that if one wants (e.g. by
parsing {{PAGENAME}}).

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to