Before giving my opinion, this is what I thought about the use of Trunk and Branch :

- Trunk is the common code, workspace. It applies all changes to the code (including languages) with possibly subject to validation of members.
- Branch would mirror the Trunk but only for codes validated and ready for release for a new version.

So we all work on the same code source (Trunk) for new features, bug fix, and so on. We merge from Trunk to Branch if code is ok. And plg (or authorised members) will use the Branch as reference to build releases.

I was a little bit in pain to commit my first codes 'cause I could not find the same references between Trunk and Branch.




In my mind, the translation files should be present identically in both parts (Trunk and Branch). And so, even if there is still no effective translation for some tags in a language file.

In this case and consistent with ddtddt's recommendations and rules :
- The default language is always English.
- If a language tag is not translated, we'ld use the english text.
- To find that there are translations to be done, the new tag should be prefixed with /*TODO*/. Thus, if a new release, translation files are valid.

According with the foregoing, I think there should have the same number of translations in the Trunk as in Branch. And still working on the same single and complete code source.

My analysis may be wrong (is it?). In this case, this topic is far to be useless ;-)

Last edited by Eric (2009-10-09 23:38:08)

I don't know what are you looking for.

I can add a new module in trunc with a lot of text.
Work 2 months on this module and change part of text 2 or 3 times.
And just before merge it in a branch, I could decide to remove a lot of text and translation because I can add very efficient icons.

When/where do you expect to do your translations?

I recommend branches to do less, but I am not a translator.

I think that our l10n logic is very poor, and encourage us to review it asap (I made a reco to change it).

nicolas wrote:

I think Vincent is right. But the main problem is to not forgot translations.

The idea to prefix vocab to be translated by /*TODO*/ is not a good idea. I prefer to have a word in english than a word prefixed by TODO.

The main tools we need is a simple way to extract vocabulary to be translated.

+1

nicolas wrote:

I think Vincent is right. But the main problem is to not forgot translations.

The idea to prefix vocab to be translated by /*TODO*/ is not a good idea. I prefer to have a word in english than a word prefixed by TODO.

I perfectly agree with you nicolas. The complex problem is "how to make have the list of new/updated strings to translate for each language". The /*TODO*/ solution is really a very poor solution.

nicolas: the /*TODO*/ method is not about having "/*TODO*/" in the string like this:

$lang['language_key'] = '/*TODO*/ temporary string';

it's:

/*TODO*/ $lang['language_key'] = 'temporary string';

But this solution is absolutely awful for the developer. Imagine you have 42 languages in Piwigo (only 17 or 18 today, certainly much more in the future), each time you update a string or add a key, you would have to modify 42 files :-/ It's just impossible to write this somewhere as the "recommended method to manage new/updated strings". I know it's a pragmatic solution for today because it's manual and we don't have spent the necessary time to manage this correctly, but let's discuss now and find a way to manage translations correctly, at technical level I mean.

nicolas wrote:

The main tools we need is a simple way to extract vocabulary to be translated.

I agree. By now, I don't know if we need a 3 hours coded tool (just a little PHP script) or if we should load our strings into a translation plateform like LaunchPad (need gettext PO files as input). The translation topic is a complex one, but fortunately it is a standard issue in the software world, no doubt other projects have already solved it. I'll investigate (you can do it too ;-)

HI guys

Sharing translations between different releases  means that translations done in one release (e.g., trunk) would  as the result of migrating to this new way of managing translations. Here's what you do: You create a branch in Launchpad, describes all files that start with "widget-2

Thanks


[edit]
Delete links - not related Piwigo

Last edited by ddtddt (2009-11-13 07:14:39)