Re-do Spansih translation

you are welcome to commit this yourself after perhaps waiting for feedback. i don't think the module maintainer has to commit translations like he does code.

@moshe: ok, thx for the guidelines

There are new POT files... check it out. This requires splitted .po files as there are some duplicate strings and POTX must run with --mode=multiple to be save.

@marvil07, This is a quick review of your translation. Basically, try to preserve Organic Groups name as is or Translate all occurrences, having both is confusing, I'm not sure how translation in other languages fight with that issue, perhaps @moshe knows.

Blessinsg!

Applying develcuy suggestions(the problem was the comments and mail strings changed accidentally) and improving a lot of strings.

Starting from this revision and using drupal-contrib l10n server I made a 7.2 version.

Now, like hass suggest it's splitted in some files with the Flat package for CVS commit option of the l10n server module. In the attachment there are these files:

• general.po
• includes.po
• root.po
• tests.po
• translations/
  • installer.es.po

So, my question now is how to organize it to commit them.

I have not seen so many files per language in po/ directory on OG. Do I miss something?

I believe renaming them as .es.po it's a good idea, for example general.es.po.

@moshe: I wait for recommendation.

See http://ftp.drupal.org/files/projects/og-5.x-1.x-dev.tar.gz how I named the German files after POTX generated the POT files for me. I'm not sure what export option is this in l10n_server...

I have no idea how to organize this. I would like to follow how other leading modules do it (CCK, Views, votingapi/fivestar, ...)

I've taken a look to the translations of the modules you mentioned.

A little summary:

The majority of the modules use one big single PO file <language_code>.po, including:

• cck-5.x-1.7
• fivestar-5.x-1.12
• views-5.x-1.6
• fivestar-6.x-1.12
• views-6.x-2.0-beta3

VotingAPI(5.x-1.6 and 6.x-2.0-beta3) don't have translation :|

The only one module(I found) that use more than one PO file to translate is cck-6.x-2.0-beta, which have one translation(de) in three files in the following format: <filename>.<language_code>.po, like examples.de.po

I think it's a good idea to follow i10n_server flat format using the files generated by that module, in <filename>.<language_code>.po format.

1. if you have submodules like CCK you should split per submodule. This allows to import only strings for modules that are really used and does not import every unsused translations. This is how it should be.

2. Another issue that came up with OG is a issue i reported at #219007: Poedit reports duplicate message definition. And this is why we have splitted files in OG.

@marvil07, my apologize, l10n_server may confuse because it suggest an export for CVS commit, but this works for core, not for contributed modules. So please dismiss my suggestion.
I strongly recommend to read the Translator's guide.
OG is splitted different in the "he" language code, perhaps because they have a translation team and are fighting with the Poedit issue. Now that @marvil07 is working with the l10n_server which avoids dupes, provides "ready to go" .po files, and interface to collectively colaborate. So... there is no need to split the spanish traslation IMHO.

Blessings!

@develCuy: have you read my comment #11?

First I don't understand why are you not collaborating with the existing Spanish translation as linked from the l10n_server page: http://l10n.drupal.org.es/

Second: general.po, includes.po, root.po, tests.po are not for different modules, so I'd suggest you merge them (after you started collaborating with the existing spanish translation team).

The duplicate string issue seems not exists in your files. Not sure why. I'm going to merge the German files back together as I hopefully found the bug of #219007: Poedit reports duplicate message definition.