Thanks for doing this Stefan. On Dec 24, 2009, at 4:43 AM, Stefan Schroeder wrote:
Hello Robert, of course, the gettext-library is the same for PHP and C. When it comes to the translation of third-party software, like postgresql, I am somewhat skeptical if it would be worthwhile to translate their error-texts, OTOH I believe they are established applications which should be localized already!? Like Karl mentioned, the important ones (php and postgresql) have probably already been done. Nevertheless when it comes to error-handling, we run into several problems, or challenges, as we say today. First: If the error-texts are translated, any user has a hard time to find it in the manual. And, oops, the manual needs to be translated, too, and in accord with the software! We could solve the problem of finding error texts by prefacing all messages with a message number. There isn't a "manual", just the fossology.org<http://fossology.org> site (doku-wiki). Next problem: I think we should _not_ translate license texts, because this might raise severe legal questions. I agree, unless the translations are done by an organization such as the FSFE. And yes! I'd like to contribute to your project. The first step would be to add the _() markers to all texts that are visible in the UI. This would not have any impact on the functionality. There are Perl-scripts out there to do this automagically. Personally I want to propose the following: I am going to switch the PHP-code in the plugins-dir to make it gettext aware and then I will send you the files (or diffs if you prefer) and you check it for sanity. If you approve you can add me to the SVN commiters and I will check in the files on my own. Sounds great. There is one more decision to make: Should the text be translated automatically (like http://www.debian.org/) based on the language selection in the browser or do we want to offer icons to switch the language manually!? Could use the locale like debian, then have a button to switch also. Thanks! Bob _______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
