On Sun, 27 Dec 2009 21:56:45 +0000 "Gobeille, Robert" <[email protected]> wrote:
> Thanks for doing this Stefan. > On Dec 24, 2009, at 4:43 AM, Stefan Schroeder wrote: > oops. I missed this message. > 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. Which is a bit of a hack, but can be useful for more then just 'bother, this isn't in my language'. (Quickly finding the error springs to mind). This brings up the problem of partial translations in the UI. I thought about this for a while, and depending on how the fossology infrastructure works, something like this might work: * Fossology is provided for download (as it is now), with en_US as its default language * Other *complete* translations (that means string complete in the po file, and the relevant documentation) gets shipped in the tarball and can be selected by magic buttons (see the last comment in this thread by Robert) * Other partial translations get listed on the wiki (/wiki/IncompleteL18N ?). This lets people think 'oh look, $my_language needs some love', and contact a listed person to help with the work. > There isn't a "manual", just the fossology.org<http://fossology.org> > site (doku-wiki). Is the wiki able to cope with localisation > 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. Definitely leave legal texts alone. [trim] > 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. Sounds like a safe fall back. kk > Thanks! > > Bob -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian contributor / gNewSense Maintainer http://www.kgoetz.id.au No, I won't join your social networking group
signature.asc
Description: PGP signature
_______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
