Hi Karsten! 2011/1/11 Karsten Bräckelmann <[email protected]>
> > Descriptions for rules from plugins should also be enclosed with > > ifplugin just like the definitions? > > Looking at the other 30_text_*.cf translations, I'd guess yes. > It looks like it really doesn't matter, because some translations use "ifplugin" and others don't. Just as an example: the rules that require the Bayes plugin are defined correctly inside an ifplugin/endplugin mark, but their translations in the other files are not. Since it doesn't seem to be of any harm, can I be lazy and go without them? > > Should I also include translations for rules in 70_*.cf files? (being > > that a "magic level") > > Good question. The rules in 72_active.cf are mostly stable and don't get > dropped frequently. However, I'd start with the named rule-sets, in > particular those rules that are frequently observed in the spam report. In my git repo I'm working with translations of 72_active.cf in a different file. This way you can get only the relevant file (30_text_pt_br.cf). If we ever decide to include them, I'll merge them into one single file. However, I don't think there would be any problem including those. Even if some of the translated rules are not defined, SpamAssassin doesn't complain. > +1 to eventually replace the existing pt_br translation with a clean and > more complete one. That means your contribution. :) > Well, I just finished all translations, and here's the end result: https://github.com/w3p/spamassassin-pt-br/blob/master/30_text_pt_br.cf The file is in ISO-8859-1, I believe that's the default for SpamAssassin, right? If everything is ok for the dev team, feel free to put the translation in the SVN. Thanks, -- Pedro Padron Tecnologia & Desenvolvimento | W3P Projetos Web +55 11 7518 6664 +55 11 2609 1989 http://www.w3p.com.br/
