Last modified: 2014-08-15 11:09:22 UTC
I created an aggregate group in Translate for the SUL translations (http://lists.wikimedia.org/pipermail/translators-l/2013-May/002276.html ) but the CentralNotice message groups don't show up in the dropdown.
This is per design. Special:AggregateGroups is available specifically and only to group translatable pages.
(In reply to comment #1) > This is per design. Special:AggregateGroups is available specifically and > only > to group translatable pages. It makes sense to exclude message groups defined in configuration files, but not message groups defined on wiki: CentralNotice message groups are equivalent to translatable pages on this. Let's call it a feature request then...
awww :( Adding myself to cc list and voting. I'd love to see this and was thinking about it the first couple times I used this, it would be incredibly helpful given the amount of time that pages are being translated at the same time as central notice banners (and the 'old way' had them all being translated on the same page so people are used to it).
There are two things to this: 1) There are still some inbuilt assumptions in Translate that prevents having a group having messages from different namespaces. 2) Special:Aggregate groups has hardcoded namespace for translatable pages. We would either need to change it to allow aggregate groups in different namespaces (but all subgroups in same namespace) or fix 1. first to allow free mixing. Like Nemo says groups configured by yaml should in all cases be excluded.
