[Zope-CMF] Re: I18n-skins: Why I did what I did :-)

[Erik Lange]

At 04:40 PM 3/4/03, Yuppie wrote:
>Hi!
>
>
>Gitte Wange wrote:
>>Tres Seaver wrote:

<snip>

>>>Can somebody from each side draft a proposal for / against the use of
>>>msgids?  I don't have enough direct experience using I18N / L10N tools
>>>to have a feel for the tradeoffs, but I don't see consensus emerging
>>>here.

<snip>

>There are many other tradeoffs, but I think this is the most important issue:
>
>
>Use Case
>========
>
>A CMF contributor checks in changes to a zpt, including relevant changes 
>to some messages. The only way I can see to notify CMF translators of the 
>changes is to give the messages new ids.
>
>
>Solution 1: implicit msgids
>
>Each change results in a new msgid. Translators have to review all changes.
>
>
>Solution 2: explicit msgids
>
>Relevant changes result in new messages. CMF contributors have to assign 
>new unique msgids. If they don't follow this policy, it's hard to discover 
>wrong translations. Translators review only changed messages with new msgids.
>
>
>So the policy for CMF contributors would be:
>
>1. Decide if translators should be notified of your change.
>
>2. If yes: Find a new unique msgid or an existing msgid that fits to your 
>new message and change the msgid.
>
>
>If CMF contributors can live with this policy, I can live with explicit 
>msgids.
>
>
>>>>Should the locale directory in root or in CMFDefault? I guess one 
>>>>catalog for CMFDefault, CMFTopic and CMFCalendar would be enough, so 
>>>>locale would be a cross package directory.
>>>
>>>
>>>
>>>I don't think this will work;  there will be no sane way to discover
>>>the location of the 'locale' directory if it is not nested inside a
>>>product.  (The top-level "CMF-1.x" directory is not "bound" to the
>>>product directories after installation).
>>
>>I think there should be a 'locale' directory in every product. Then the 
>>translations won't get mixed up, and you don't need a particular CMF 
>>product in order to have the translations.
>
>Well, it depends on some other questions:
>
>- Do we ship with translation files? Is the cvs the right place for 
>translation files?
>
>- Is there a way to import .po files using a script or do people import 
>.po files TTW?
>
>
>Cheers,
>
>Yuppie

How has this problem been solved in the Plone community?

What's the Plone-users experience with the chosen solution?

Has this issue been discussed in details in the Plone community, and if, 
what were the conclusions?

Let's work together now, and share our knowledge, making our common base 
the best framework available :-)


Regards,
Erik Lange