[z3-five] Re: First steps cont'd - i18n with Five 1.1b

[David Pratt]

Hi there. Wonderful news. It is working!  It there a tool for gathering 
the i18 up in my ZPT to create the pot files instead of doing this by 
hand.  I have heard of i18dude or something like this.  Any 
recommendations would be helpful. I guess worst case, I can try SGML 
parser.  I am totally looking forward to what Five brings to the 
table!!!

Regards,
David


On Sunday, July 24, 2005, at 04:05 PM, yuppie wrote:

> Hi David!
>
>
> David Pratt wrote:
>> Well. I got rid of the nasty PTS.  I start over with an empty 
>> database in a fresh clean zope 2.8 with a single instance of CMF 
>> 1.5.2. now.  Ran tests on Five including i18 test and all looks good.
>
> Using Five 1.1b for CMF 1.5.2 translations works for me. I didn't test 
> it thoroughly, but looks good so far.
>
>> Checked configuration.zcml at root of CMFDefault product and added 
>> i18 namespace so now have:
>> <configure
>>     xmlns="http://namespaces.zope.org/zope"
>>     xmlns:i18n="http://namespaces.zope.org/i18n"
>>     i18n_domain="cmf_default">
>>   <include file="bridge.zcml"/>
>>   <include file="implements.zcml"/>
>>   <include package=".browser"/>
>>   <i18n:registerTranslations directory="locales" />
>> </configure>
>
> That should work.
>
>> I noticed also that there is a browser folder that also contains a 
>> configuration.zcml so I also added locales folder and same contents 
>> of locales folder I made at root of CMFDefault product here as well.
>
> This doesn't make sense. Please make yourself familiar with ZCML. 
> "<include package=".browser"/>" includes browser/configuration.zcml in 
> the main configuration. One 'i18n:registerTranslations' is enough.
>
>> Get following error.  If I remove the i18translate attribute from 
>> title tag, error disappears.  Is there anything else I could try in 
>> the interim.  I really want this to work badly.
>
> Your error is a result of the conflicting 'i18n:registerTranslations' 
> settings. Please have a look at your log/event.log, it should have 
> logged the configuration error.
>
> If you set "debug-mode on" in your etc/zope.conf, Zope will not start 
> until all configuration errors are resolved.
>
>
> HTH,
>
> 	Yuppie
>