translations/is/README.txt

This directory contains the POT files for the various Drupal core modules.

Translation
===========

Translators should start by getting all of them and translate them to their
language of choice.

The translated files should be stored in contrib-cvs/translations/<id>,
where <id> is the ISO 639 language code. If you don't know your code, ask
in drupal-devel.

You should only put the individual translated files in this directory.
A script will generate a merged <id>.po file. Make sure to fill out the
header section of each file and rename them to .po from .pot.

Contrib modules should offer a POT file, too. It should be distributed in
their own subdirectory in contrib-cvs/modules.


Creation
========

The POT files are created by running the script extractor.php (also in this
directory) on all Drupal files that contain translatable strings.
Don't forget the themes/ subdirectory. Example command line:

  php extractor.php *.php includes/*.inc modules/*.module themes/*/*/*

All files get their own POT file unless they contain less than ten strings.
Those will be merged in the general.pot file. This special POT file also
contains all strings that occur more than once in the Drupal source files.
This will help translators to maintain a single translation for them. 


Updating
========

Once in a while we will create new POT files in this subdirectory as
sometimes strings get added or changed. Translators should then run
msgmerge on their auto-generated <id>.po file against each new POT file
and put the resulting PO file back in their subdirectory.


$Id: README.txt,v 1.2 2004/10/18 22:41:02 goba Exp $

Gerhard Killesreiter
1	This directory contains the POT files for the various Drupal core modules.
2
3	Translation
4	===========
5
6	Translators should start by getting all of them and translate them to their
7	language of choice.
8
9	The translated files should be stored in contrib-cvs/translations/<id>,
10	where <id> is the ISO 639 language code. If you don't know your code, ask
11	in drupal-devel.
12
13	You should only put the individual translated files in this directory.
14	A script will generate a merged <id>.po file. Make sure to fill out the
15	header section of each file and rename them to .po from .pot.
16
17	Contrib modules should offer a POT file, too. It should be distributed in
18	their own subdirectory in contrib-cvs/modules.
19
20
21	Creation
22	========
23
24	The POT files are created by running the script extractor.php (also in this
25	directory) on all Drupal files that contain translatable strings.
26	Don't forget the themes/ subdirectory. Example command line:
27
28	php extractor.php .php includes/.inc modules/.module themes///
29
30	All files get their own POT file unless they contain less than ten strings.
31	Those will be merged in the general.pot file. This special POT file also
32	contains all strings that occur more than once in the Drupal source files.
33	This will help translators to maintain a single translation for them.
34
35
36	Updating
37	========
38
39	Once in a while we will create new POT files in this subdirectory as
40	sometimes strings get added or changed. Translators should then run
41	msgmerge on their auto-generated <id>.po file against each new POT file
42	and put the resulting PO file back in their subdirectory.
43
44
45	$Id: README.txt,v 1.2 2004/10/18 22:41:02 goba Exp $
46
47	Gerhard Killesreiter