Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Here you have the po file. I edited it with opEdit in debian Linux using utf-8 charset. I don't know if the encoding will be adequate, could someone test it? I installed it locally in my site and it seems my pot file is a bit outdated. I renamed the file to .text because the system doesn't allow me to attach .po files.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | es.po__0.patch | 7.91 KB | Farreres |
| #1 | recipe-es.po_.patch | 14.67 KB | Farreres |
| recipe-es.txt | 6.55 KB | Farreres |
Comments
Comment #1
Farreres commentedI have tried to complete the translation for Spanish. After I translated the using the pot file distributed in the module, only part of the texts got translated. I have tried with xgettext from the php code, and this is what I got. No pot file, don't know how to generate. It would be great if someone could give me a hint about what to do to correctly translate the module.
I attach the translation after my xgettext processing of the PHP. It has a patch name so I can attach it, but it is not a patch file, it is directly the .po file as I edited it.
Comment #2
Farreres commentedFinally the good one, I hope. Not really a patch, it's directly the spanish po translation.
Comment #3
green monkey commentedclosed on age - if still active - please resubmit
Comment #4
scottprive commentedThis was never checked in so we should leave it open. When someone does a big sweep of all i18n issues, this can be included.
Comment #5
jvandervort commentedRecipe 5.x branch moved to unsupported.