-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi there,
I've just made a new release for the Drupal Core POT files, available here:
http://ftp.drupal.org/files/projects/drupal-pot-6.x-1.1.tar.gz
This includes all changes that were made between 6.2 and 6.13.
You may want to update your translation.
Cheers, Gerhard
Hi Gerhard,
On Saturday 25 July 2009 23:06:35 Gerhard Killesreiter wrote:
Hi there,
I've just made a new release for the Drupal Core POT files, available here:
http://ftp.drupal.org/files/projects/drupal-pot-6.x-1.1.tar.gz
This includes all changes that were made between 6.2 and 6.13.
You may want to update your translation.
Cheers, Gerhard
Thanks for the update. I've already updated the Greek translation, committed and tagged the files and created a new release (actually two, because of the problem I faced, which I'm about to describe).
The new releases came up, I downloaded them, but inside the profiles/default/translations directory, the el.po file does not seem to be complete. I've located new strings that appeared with the drupal-pot-6.x-1.1 release and which do not exist in el.po, but exist in the partial po files in the other directories. That's why I created two releases, just in case I did something wrong with the cvs tagging myself.
What's wrong?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Vasileios Lourdas schrieb:
Hi Vasileios!
Thanks for the update. I've already updated the Greek translation, committed and tagged the files and created a new release (actually two, because of the problem I faced, which I'm about to describe).
The new releases came up, I downloaded them, but inside the profiles/default/translations directory, the el.po file does not seem to be complete. I've located new strings that appeared with the drupal-pot-6.x-1.1 release and which do not exist in el.po, but exist in the partial po files in the other directories. That's why I created two releases, just in case I did something wrong with the cvs tagging myself.
What's wrong?
I am not sure I understand...
Can you give me examples for strings that seem to be missing?
Cheers, Gerhard
On Sunday 26 July 2009 16:50:55 Gerhard Killesreiter wrote:
I am not sure I understand...
Can you give me examples for strings that seem to be missing?
Cheers, Gerhard
For example: In modules-blogapi.po, the string "Invalid categories submitted." is new. In modules/blogapi/translations/modules-blogapi.el.po the string exists, however in profiles/default/translations/el.po it does not. Isn't el.po the concatenation of all individual .po files?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Vasileios Lourdas schrieb:
On Sunday 26 July 2009 16:50:55 Gerhard Killesreiter wrote:
I am not sure I understand...
Can you give me examples for strings that seem to be missing?
Cheers, Gerhard
For example: In modules-blogapi.po, the string "Invalid categories submitted." is new. In modules/blogapi/translations/modules-blogapi.el.po the string exists, however in profiles/default/translations/el.po it does not. Isn't el.po the concatenation of all individual .po files?
Apparently it is not: I compare it to the .de translation and there the de.po also contains only the strings from installer.pot.
Cheers, Gerhard
On Sun, Jul 26, 2009 at 4:35 PM, Gerhard Killesreitergerhard@killesreiter.de wrote:
For example: In modules-blogapi.po, the string "Invalid categories submitted." is new. In modules/blogapi/translations/modules-blogapi.el.po the string exists, however in profiles/default/translations/el.po it does not. Isn't el.po the concatenation of all individual .po files?
Apparently it is not: I compare it to the .de translation and there the de.po also contains only the strings from installer.pot.
profiles/default/translations/$langcode.po contains all the strings for the install profile, while individual module translations such as modules/blogapi/translations/$langcode.po contains strings for the individual modules.
Gábor