In the various translation projects I am a member of I have see updates each week and at times each day depending on the package and how much work is being done to it.

I would, personally, like to be able to work on translation and have some page that gives instructions on what is required. Things like where to go, what packages are high priority, how to submit the translation, how to review the translations done by others etc etc etc. are all helpful to novice translators and also to individuals who have never used the site the translations are based at.

On 2 October 2014 12:40, Michele Calgaro <michele.calgaro@yahoo.it> wrote:
> No problem!  I finally had a chunk of time to work on TDE and was able to
> figure out the translation system enough to get this working.  This should
> resolve the majority of the translation-related bugs; translators can now
> pull, translate with KBabel or similar, and commit directly back to tde-i18n as needed.

I was also thrilled by seeing the same commit.
Tim, could you explain briefly how .pot files are created (which sequence of commands are executed)?
I think we need to add some kind of instructions on our wiki about the translation process, so that users can actually work on that actively.

Also, what is the frequency of automatic generation? If it is too frequent (say daily) this may cause a problem when applying patches provided by users, because by the time we get to apply the patch, the generation date included in each file may have change due to the next automatic update. This would require manual intervention on each modified file to apply the patch. I think a good frequency would be something like once a month.
What do you think?

Cheers
  Michele

---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting