1. Export the .PO for Content Types. There must be multiple fields with the labels Title and Body.
2. Translate the strings, save the file.
3. Reimport the .PO in Drupal. Choose to override existing strings.
EXPECTED: Translations imported and matched to their locations/IDs
RESULT: Strings corresponding to msgid's that were already imported are ignored.
See the attached PO's:
10. Content type FIRST EXPORT.po
20. Content type TRANSLATED.po
30. Content type RE-EXPORTED.po
Thanks.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | drupal-locale-import-384794-D6.patch | 2.19 KB | jaydublu |
| 1-2-3 Content type.po.zip | 6.8 KB | Gabriel R. |
Comments
Comment #1
jaydublu commentedThis issue was discussed in http://drupal.org/node/384794
Apparently there's a fix released in Drupal 7, but I rolled a patch for 6.x
Note my comments about the root cause in #22 - I think the D7 'fix' is not a good one.
Comment #2
jose reyero commentedIt seems no one else is interested in testing this for 6.x, so sorry.
Comment #3
Gabriel R. commentedPO handling was so unreliable we had to find other ways to deal with localization.
Maybe someone else will pick this up.