@Shine
There was an explanation how TX works.
Packages are available (should be) from XOOPS svn if mamba got them from
http://sourceforge.net/projects/gtlt or free mirror sevicing mostly used for sharing warez such as Mirrorcreator.com.
Quote:

Current Dutch core translation is 100%, or there is a 2nd Dutch team ?

All core files are OK, Infidex will not plant the update on servers before 2.5.6 or 2.5.7 releases, still needs a lot of testing which I'm doing when got time.

Modules, most are reviewed, corrected and uploaded to TX (English languages are available from the selected module thread under Blue-Move forum, with translations as well), rest are not accepting translations and will be removed by Sunday or Monday.

All language files are up to date with latest announced by the module maintainer, atm Mamba, which is the only one responding to bugs.

TX is in times easier then NotePad + and Winmerge, because with every new release of core and/or module, u have to verify every single file of XOOPS or the module for changes, additions and removals. TX does this automatically. As team leader or member of team, u have only one task - to keep your translation on the prepared templates (source languages) up to date, clean of mess. As I mentioned in another Thread, regarding TX core progression, some "leaders" will be replaced as the given example bellow.

Once you've clicked on the language team, let's say Greeks
https://www.transifex.com/projects/p/xoops/language/el_GR/
There are 3 columns:
1. Name of file 2 progress meter 3. date of last modification
bellow this 3 columns, there is a small light blue bar, by clicking it once, u will see the files in reverse order sorted, eg. 0% translated to rest.

Everyone is free to use whatever he/she wants, but the end result as I already noticed for some modules, are 90% for Dutch (only for Dutch). Thanks to Notepad + and outdated language files. For example News module listed on TX, the language files hosted on XOOPS Modules are for 1.68 Beta1, no idea where rest using Notepad + got their English templates.

Translations for me are:
1. at first place - localized distributive of module/core/template (well, themes here)
2. on understandable language (which not mean word by word or google translator)
3. on the latest language files, otherwise user will read something which is not on adequate position or even _AM_SOMETHING_GOES_HERE

There are 3 ways of downloading languages at the moment:
1. TX Console client
2. Old-fashion way by click/rename or click/overwrite existing files.
3. By MadFish script (if u are team leader)

Once again, I'm getting angry only with one-two developers here, not with Translators :), everyone is free to use whatever they want, for me is not a problem, it's not for Mamba too, it's a voluntary project and everyone spend their free time if they want. No one is forcing translators to use TX.

Quote:

Spanish team to

You're team is not by one, especially for modules, otherwise looks strange... from where do u got so much time and will for translations ? :)
And yours, pt-BR, Slovaks, Italian and French are the most active :)

DCrussader,
Could you check news module lang files in TX? I translated 4 files, but in last distribution (1.67 Final) there were 5 files - I can't find source of newsletter.php

Thanks

Quote:

Look at the translation history of each file.

when I can´t sleep I translate to waste the time, and I am interested in to promote Xoops at Spanish people.

Quote:

Hehe, same as me... but except me so far no one else uses XOOPS :)

Quote:

Files on TX are for 1.68B1 and they're 4, newsletter.php is outdated file from the time of XOOPS 2.0, but no one of the devs reads what I'm posting. It's optional, but in every distribution of xx-XX_News-168beta.zip should be a readme file with short how to - so the user of the selected localization to make it in the way how he/she wants.

Newsletter.php is mail template, same as mail_template/ folder which have to be moved inside the SQL in 2.6.0 at least. Hopefully Mamba will point them to this issue, /help to be removed from any module, core_language folder, mail_template/ to be moved inside SQL and each module as function, Keep It Simple, Stupid, don't mean the end user to use advanced techniques to set up simple Newsletter or Welcome mail template.

Quote:

O.K. :)

When translation is completed per file, there is a function to be reviewed and to ping the project leaders as Reviewed and Completed. Use it once, all files per module are completed. The other option is downloading by yourself and packing or posting in the dedicated module thread.

I think, I have to spend a few time with Transifex to learn this utill. in this moment I can't find a function to be reviewed and to ping the project leaders as Reviewed and Completed, but propabbly it's my mistake.

When a package of module's translations will be done and checked, I can send it by mail too - e.g to mamba.

Post message to each module thread in Blue-move or PM/mail me, mamba is too busy with other things to take care and for the languages.

Section Proofreading:
http://help.transifex.com/intro/translating.html?highlight=proofread%20translations

But this is for teams with more then one man :)
Not applicable for Spanish and my.....

Once you hit your language on XOOPS Modules for example and if u're team leader, u should be able to click Edit language field team. (translating and writing on forums is not good idea) :)

There are Coordinators (Team leaders), Members, Reviewers (those which have to proofread the files before release).

Avoid use TM (Translation Memory), when TX 0.1 was launched, there was full of .... crappy translators, such as kids which even can't speak and write in they're own language, and bcz of that - Forums are translated as Forms, Article as Product and so on, double read everything which is supposed to be at 0%, but thanks to TM starts at 1% or 5%

The other good, really good feature is Glossary, again not applicable for one man teams :)
Glossary contains common words used in translations, eg. XOOPS Story to be translated as Article, or favorite XOOPS WEIGHT to be translated as Order and such. So once core is translated with Article instead of Story and Order instead of Weight, to not make mess with the modules, and to be used Story and Weight.