Mercurial > pidgin.yaz
view po/README @ 12435:8f98014a4e7d
[gaim-migrate @ 14742]
1. Protecting the --enable-debug warning tests with an "if gcc" check.
2. Adding a number of warning flags to --enable-debug. All cases of the added warnings have been fixed, except:
a. The pointer-arith warnings. I think someone smarter than me should decide whether we need to fix those (and how) or if that should be disabled. That said, I think all the errors left (after you consider the exception listed as "b" below) are in libzephyr.
b. Those in src/protocols/sametime/meanwhile at siege's request. Don't worry about these for now.
3. Noting a few warnings we could enable, and the cases we'd have to deal with. Thoughts on these warnings?
4. I added support for FORTIFY_SOURCE. If your compiler has support for this feature, --enable-debug will set _FORTIFY_SOURCE=2. I'm doing this in --enable-debug for the warnings you get. I wouldn't mind having it on by default for the runtime protections as well. Thoughts?
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Fri, 09 Dec 2005 05:32:59 +0000 |
parents | ebf3b709a77a |
children | fd4630204ad5 |
line wrap: on
line source
Translation README Updated: 04-October-2003 ------------------ Translated .po files may be submitted in whatever native encoding is most convenient (and hopefully canonical). Please ensure that the Content-type: line reflects the proper character set. Updated: 19-April-2003 ------------------ To supply a new translation, you first need a copy of gaim.pot. This can be built by typing: ./update.pl --pot from the gaim/po/ directory. To update an exsting translation, type: ./update.pl LANG where LANG is the language code to update, such as fr or ja. This will build a new gaim.pot and update the translation with the changes. You may then begin editing the updated file. New or updated translations should be sent to the gaim-devel listserv (see http://lists.sourceforge.net/lists/listinfo/gaim-devel) Please check your translations carefully. Make sure you have the same number of newlines and %s or other formatting codes in the translation as you have in the original. Updated: 05-August-2003 ------------------ Before submitting updated or new translations, please run the following command to ensure the file does not contain errors: > msgfmt -c --statistics xx.po The comments at the top of each .po file should appear as follows: # Gaim Xxxxx translation # Copyright (C) 2002, Another Name <email@something.com> # Copyright (C) 2003, Your Name <email@whatever.com> # # This file is distributed under the same license as the Gaim package. # Thank you for flying Valu-Jet.