>> Since I'm located in Germany I'd to provide a german interface. >> squirrelmai.po was not changed in CVS. I was willing to do the >> translation but was stopped with the same arguments as mentioned above >> (not >> stable...). > > This baffles me. What is missing in the translations? I believe all the > languages stuff has been pulled into a central cvs branch to unify > translations and save duplication of work.
Florian is right. There are several plugins at offered at <squirrelmail.org> with broken i18n (and other problems as well). They could be fixed. Florian has already provided some patches. Other patches has been available at Tomas Kuliavas' site for (I think) years. If it's OK to make a hostile takeover of a plugin when it's not possible to get hold of the maintainer, there are several things that could be changed. I too have made some patches, but I never put up a site where I released them. I thought about it though. Florian is also right about the fact that some of the plugins shipped with SquirrelMail itself, aren't following the standards. In some cases "setup.php" contains code, for instance. I was planning to remedy this, but never found the time to do it. I know that there are people that have sent in plugins that aren't complete and following the plugin standards. I think that the reason that those plugins never made it to <squirrelmail.org> was that there was a concern that those plugins would generate support questions, but with no active maintainer those questions would do nothing but add overhead to the pluings mailing list. On the other hand, a hack is sometimes better than nothing. I once raised the suggestion that we should certify plugins that conforms to the standard, and the answer I got (if I'm not mistaken) was that only approved plugins should be accepted at <squirrelmail.org>, but the heritage would remain there even though they wasn't up to the stadards of today. One idea is to have more fields describing the plugins at the site, and that those fields should filled out by a SquirrelMail developer when reviewing the plugin. We're already reviewing them anyway, and if no one has time/will to review those fields would just be empty. I don't have access to change any code at <squirrelmail.org>, but there are some things I'd like to clean up. Since I don't have the code it's hard to send patches for it. Maybe we should have all the site code in the CVS as well. That way it would be easier to improve it. I'm a bit tired right now, so maybe I'm not making much sense right now. Just ask if there's something I should clarify. Sincerely, Fredrik. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: squirrelmail-users@lists.sourceforge.net List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
