TRANSLATORS:

There is now a simple way to translate most of gourmet, which requires
no more work/knowledge than how to use a website. To help translate
Gourmet the simple way, go to the following site:
https://launchpad.ubuntu.com/rosetta/products/grecipe-manager/gourmet

When you are done translating at the rosetta site, there are two more
tasks to do that aren't handled by the rosetta system -- these will be
a bit trickier.

1. Translate the gourmet.desktop file for your locale.

2. Copy src/lib/defaults_en.py to an appropriately named file for
   your locale (e.g. defaults_en_GB for great britain, or
   default_es_ES for Spain). Then follow the directions in that file
   to translate it (this sets up default values for units, foods,
   shopping list groups, etc.)

INSTRUCTIONS FOR USING GETTEXT SYSTEM (Obsolete)

Warning: If you use this system, there's no way to ensure you won't
duplicate effort; the rosetta web-based system for gettext files
allows you to collaborate with other translators to avoid duplication
of effort.

If you know and are comfortable with the gettext system, you can follow
the below directions to do translation the old-fashioned/text-based way.

To get started, simply issue 

msginit

This will create a new translation file for your current locale and
will ask you for your e-mail address to add to the file (in case
people want to contact you about your translations).

Next, run grab_strings.sh by issuing
sh grab_strings.sh

This will automatically grab translatable strings and merge them into
anything named *.po  (You can run this again at a later date to update
old translations as the application evolves).

Finally,
sh make_mo.sh

will take a file named e.g. es.po and compile it to a proper
LC_MESSAGES/gourmet.mo file.

NOTE: In addition to the strings contained in gourmet.pot, there is
some more complex translation work to be done in
src/lib/gourmet/defaults_LANG.py

src/lib/gourmet/defaults.py will attempt to grab default unit and
ingredient information out of the correct language file named
defaults_LANGUAGE.  For example, defaults_en.py contains the English
default information about ingredients, ratings, units, etc. (these
things are more complex than one-to-one string translations). To
create a new file, simply copy defaults_en.py and rename
appropriately. Note, you can be more specific if you like-- for
example, defaults_en_UK is used to set up a default file which uses
british over english defaults (there are a few food words that are
different in British and American English).

If you do some translations, please send them to me so I can include
them in the next official release of
Gourmet. <Thomas_Hinkle@alumni.brown.edu>
