Translation of Trac to Spanish/Español [es_ES]

[asmodai@…]

This ticket should be used to coordinate the translation to Spanish.

[asmodai@…]

See also TracTermsEs.

[Jeroen Ruigrok van der Werven]

A first version has been committed as source:sandbox/i18n/trac/locale/es_ES/LC_MESSAGES/messages.po

[maarten@…]

I see this translation still has many german words in it..is it already operational¿

[Jeroen Ruigrok van der Werven]

Fixed in r5821.

[marsanvi@…]

Hi Karlos,

I'm interested in the spanish traslation, if you want I can help you.

Martín Sánchez.

[Jeroen Ruigrok van der Werven]

The files are in the repository. Just open the es_ES messages.po and verify/add to the entries.

[Jeroen Ruigrok van der Werven]

Also let me know if your names are not in THANKS yet.

[raul.garcia@…]

Just started to translate, can someone check this?

[raul.garcia@…]

Hello, Im translating "messages.po", but i don't know if Im doing right. The formatting seems very simple but if anyone can check the file will be perfect. By now I've translated about 35% of the file, I hope it will be finished in about a week or two depending on my spare time.

[raul.garcia@…]

File being translated, 35% translated.

[somervill@…]

Hello!

I would like to help translating as well, so let me know if messages.2.po is the up to date version so I can start checking/translating. thanks.

[Jeroen Ruigrok van der Werven]

The messages.2.po file has been committed to the repository in r8047. Thanks!

[Jeroen Ruigrok van der Werven]

A small note, by the way, Last-Translator is a special header, don't make it plural.

[raul.garcia@…]

Sorry about the "Last-Translator" header.

---

Somervill@ did you start to translate?

[Jeroen Ruigrok van der Werven]

No problems at al Raul, just explaining. :)

[anonymous]

how we can install this translation in trac 0.11 with babel? can't find how to install it ¿?

[Christian Boos]

No chances for Trac 0.11, but see 0.12/TracInstall for 0.12dev, a.k.a. trunk (TracDownload#Tractrunk).

[Christian Boos]

By the way, any chances for some updates? The ​stats say 31% and I think that for being part of the 0.12 release, reaching 50% is not too much to ask for…

[Christian Boos]

jag2kn@… provided some updates, committed in r9743 and updated in r9744. Please review and expand…

@jag2kn: please use this ticket in the future rather than the TracTermsEs page for providing patches or complete messages.po files. Also, please read the TracL10N page, in particular learn about the various ways to get an up to date catalog before starting the translation, it will save you some time ;-)

[jag2kn@…]

@cboos thanks for commit the changes, I will look the links

[robarago@…]

100% coverage (1087 messages) for Spanish Translation remade from scratch.

[anonymous]

Replying to jag2kn@…:

@cboos thanks for commit the changes, I will look the links

Sorry, I uploaded first my translation (messages.3.po) in TracTermsEs page. I attached the same version here for your consideration.

Thank you all.

[Christian Boos]

Nice work, there were no errors and it's nearly complete except for the Javascript messages.

I've committed it as r9844 and also added the messages-js.po catalog in r9845. You need to translate those messages as well to really reach 100% (but hey, only 31 messages, peanuts :-) ).

[robarago@…]

Spanish translation of JavaScript messages (31 messages)

[anonymous]

Replying to cboos:

Nice work, there were no errors and it's nearly complete except for the Javascript messages.

I've committed it as r9844 and also added the messages-js.po catalog in r9845. You need to translate those messages as well to really reach 100% (but hey, only 31 messages, peanuts :-) ).

Ok, I'm attaching the peanuts right now to reach 100%… I suppose this file is converted to trac/htdocs/js/messages/es.js… but how?

[Christian Boos]

I've committed messages-js.po​ in r9848. I previously assumed the 96% figure was due to the missing messages-js.po, but actually in the main catalog you have 1087 messages translated, on a total of 1095 in the .pot file.

So you're nearly there ;-) If you'd like to maintain this translation on the longer term, and you'd like to have commit access to those catalogs, just ask.

As for the generation of the es.js file, this is done using a custom command which extracts the translations from the compiled messages-js.mo file. You can trigger this step by:

$ make compile-es
python setup.py compile_catalog -l es \
    compile_catalog_js -l es generate_messages_js -l es
running compile_catalog
compiling catalog 'trac/locale\\es\\LC_MESSAGES\\messages.po' to 'trac/locale\\es\\LC_MESSAGES\\messages.mo'
running compile_catalog_js
compiling catalog 'trac/locale\\es\\LC_MESSAGES\\messages-js.po' to 'trac/locale\\es\\LC_MESSAGES\\messages-js.mo'
running generate_messages_js
generating messages javascript 'trac/locale\\es\\LC_MESSAGES\\messages-js.mo' to 'trac/htdocs/js/messages\\es.js'

but this will also happen automatically on build and install. See #6353 for details.

[robarago@…]

1095 messages translated (msgcat'd with original messages.pot)

[Christian Boos]

msgcat is just merging common messages…

$ msgcat.exe trac/locale/messages.pot trac/locale/es/LC_MESSAGES/messages.po  > messages.po
$ msgfmt --statistics messages.po
1087 translated messages, 8 untranslated messages.

You need to do msgmerge here:

$ msgmerge.exe trac/locale/es/LC_MESSAGES/messages.po  trac/locale/messages.pot  > messages.po
..................................................................................................................... done.
$ msgfmt --statistics messages.po
1087 translated messages, 7 fuzzy translations, 1 untranslated message.

Or alternatively install the Python tools and make update-es.

See all the details about the 4 possible ways in TracL10N#TranslationWorkflow.

[robarago@…]

Replying to cboos:

msgcat is just merging common messages…

$ msgcat.exe trac/locale/messages.pot trac/locale/es/LC_MESSAGES/messages.po  > messages.po
$ msgfmt --statistics messages.po
1087 translated messages, 8 untranslated messages.

You need to do msgmerge here:

$ msgmerge.exe trac/locale/es/LC_MESSAGES/messages.po  trac/locale/messages.pot  > messages.po
..................................................................................................................... done.
$ msgfmt --statistics messages.po
1087 translated messages, 7 fuzzy translations, 1 untranslated message.

Or alternatively install the Python tools and make update-es.

See all the details about the 4 possible ways in TracL10N#TranslationWorkflow.

Ok. Let's see…

$ msgmerge messages.po messages.pot > messages.po.new
.............................................................................................................. done.
$ msgfmt --statistics messages.po.new
1094 translated messages, 1 untranslated message.
$ vim messages.po.new # Translation session not very heavy
$ msgfmt --check messages.po.new # No output, is this good?
$ msgfmt --statistics messages.po.new
1095 translated messages

Please, note my original messages.po is different from yours. Mine is from 'msgcat', but this command produced nearly the same effect but for one only message. I'm attaching this new version with one last message translated.

Of course I can give a try and became long term translation maintainer. Please send me information about it.

Thank you very much.

[robarago@…]

1095 messages translated (msgmerge'd with original messages.pot)

[Christian Boos]

Roberto, I've committed messages.5.po​ in r9852. Thanks a lot!

I've sent you a mail with the details for your account so that you can continue the maintenance at your convenience.

[anonymous]

Hi, I'm trying to translate to spanish my trac (0.12), how can I do that? many thanks.

[anonymous]

Replying to anonymous:

Hi, I'm trying to translate to spanish my trac (0.12), how can I do that? many thanks.

Trac 0.12 has 100% translation to Spanish (Spain) as you can test here ​http://trac.edgewall.org/demo-0.12. All you should do is set your browser language to es_ES to see translation working.

Thank you for your offer.

[anonymous]

Thanks for your help, I tested it with firefox and crhome both in spanish but my trac stil in English. There is something in my trac.ini that i have to change?? I have installed the 0.11 and then I upgraded it to the 0.12. I'm working in linux but I also tested with a spanish windows xp and the trac is also in English.

Many thanks and best regards.

[anonymous]

You should see the files messages.po and messages-js.po in the trac/locale/es/LC_MESSAGES directory of your trac 0.12 installation (I've downloaded an tested OK with 0.12.1).

You should also configure your browser language to Spanish (Edit→Preferences→Content→Language and promote Español [es] to first place in Firefox, i.e.).

Then, reloading any trac page should work.

Please, read trac FAQ or report this issue to users forum if necessary, since I'm not i18n expert but a mean translator.

[anonymous]

I have not installed BABEL, is that the problem? Babel is necesary to use the translation utility?

[anonymous]

I've intalled babel reintalled the trac 0.12 and all is working now correctly, thanks for all

[manuel.viera.tirado@…]

Hi,

First of all, thanks for the spanish translations, good job.

I've been watching your TracTermsEs and read that the way is to look for a term valid in Spanish and American latin spanish also.

Wouldn't it better to try to separate it in several files? I mean es_ES, es_AR, etc.

Thanks and best regards, Manuel Viera.

[raragon]

Sorry, I'm not actively maintaning this page. In fact, I didn't followed myself in Trac version 0.12 and I hadn't time to update it. So feel free to fork to TracTermsEsAr if you need it.

Only a link with a short warning text in the begining of this page would be nice…

Thank you for you interest.

[manuel.viera.tirado@…]

My idea is the opossite of yours. I don't want to make es_AR, I want to recycle your es_ES and make it real, I mean, complete es_ES with the words that we really use here in Spain, instead of get together all the spanish of the world into one es_ES. In that way there will be several es_XX, one per region.

[anonymous]

I'm a native spanish speaker from Spain and I think my translation of 0.12 is not very neutral, in fact.

You're welcomed to any contribution, not only to the TracTermsEs page but for the translation itself, but I don't see TracTermsEs as a mandatory guide for next release, only as a suggestion since it's very outdated and no actual work (messages.po or messages-js.po) was derived AFAIK from any contributor of this page.

[tezcatl@…]

Hi! I've just filed ticket:10928 with a diff for updated Spanish translation, fixed some mistranslated strings and fuzzies. This is just for version 0.12.4

FWIW, I'm native spanish speaker from México, so I'm just going to give a fix to 1.0dev catalog but I'd like better start a new translation for es_MX variant, since the userbase of my organization is mexican and we'd also helping new translators become acustomed to standard translation tools for software.

Best regards to everyone.

[Christian Boos]

Replying to tezcatl@…:

FWIW, I'm native spanish speaker from México, so I'm just going to give a fix to 1.0dev catalog but I'd like better start a new translation for es_MX variant, since the userbase of my organization is mexican and we'd also helping new translators become acustomed to standard translation tools for software.

I've approved the creation of the ​Spanish (Mexico) Team on Transifex. Speaking of Transifex, it seems I have some maintenance to do there (new "Releases"), and also the instructions on TracL10N regarding Transifex are very much out of date… so I'm not sure at this point what the current workflow with Transifex is/should be.

I'm also not sure how Mexican Spanish compares to "Spanish Spanish", but it would be great if you could also maintain the es catalog "in passing" ;-)