Hi! > I'm sorry, that wasn't intentional. Can I "fix" it by unmarking the > string from translation for 3.2.x? This one shouldn't be shown to a user > often, it's rather rare string, when a syntax of a filter doesn't match, > which can happen only if a developer develops new filters, I believe.
Just request a freeze-break for 3.2.1. Unmarking the string doesn't fix it but just creates another bug (string not marked for translation...). As you probably doing that and I think that is fine to fix in 3.2.1, 1 of 2 from i18n. Regards, Johannes _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
