Mirto Silvio Busico, on 2009-08-22:
>
> Maurits van Rees ha scritto:
>> Mirto Silvio Busico, on 2009-08-21:
>>
>>> Hi Maurits,
>>> I've just installed the Plone 3.3.
>>>
>>> Also in the default plone site, the error is still there (in history I
>>> see "Pubblica fatta da ${author} il 20/08/2009 10:43 ")
>>>
>>> How can I apply the
http://dev.plone.org/collective/changeset/94537 to
>>> the buldout generated by the unified installer?
>>>
>>
>> Hm, the dirtiest but fastest method is this:
>>
>> - Locate the plone.app.locales package that your buildout uses.
>>
>> - Find the i18n/plone-it.po file contained in there.
>>
>> - Make the change manually.
>>
>> - Restart your zope instance.
>>
>> (Note that the changeset points to PloneTranslations, but from Plone
>> 3.2 onwards the relevant files of the PloneTranslations product are
>> copied to the plone.app.locales package.)
>>
>> I hope that helps,
>>
>>
> Ok thanks; I'll try it.
>
> I suppose I have to redo the change everytime I run a buildout -n. Correct?
No, as this is a change that you make in the plone.app.locales
package. The next time you run buildout -n buildout will see that you
already have the wanted version of plone.app.locales and continue.
If this works and you only need it on one computer, go for it. But
actually, it is cleaner to use a recipe that I wrote a while ago. Add
this to your buildout.cfg:
[i18noverrides]
recipe = collective.recipe.i18noverrides
source = ${buildout:directory}/translations
destinations = ${instance:location}
and add i18noverrides to the list of parts in buildout.cfg.
'instance' should be the name of the zope instance part of your
buildout.cfg. I am not sure if the unified installer calls that
instance or zeoclient. At least you should list any part that uses
plone.recipe.zope2instance. So you might end up with this instead:
destinations =
${zeoclient1:location}
${zeoclient2:location}
Then create a directory 'translations' in your buildout directory.
Copy the plone-it.po file from plone.app.locales to that directory.
Make the change from the changeset. Best is probably to remove
everything from the file except the headers and those lines containing
the relevant msgid and msgstr (plus comments).
Run bin/buildout, look for errors or warnings reported by the recipe,
start the instance and see if it has worked.
See
http://pypi.python.org/pypi/collective.recipe.i18noverrides for
more details.
--
Maurits van Rees |
http://maurits.vanrees.org/ Work |
http://zestsoftware.nl/"This is your day, don't let them take it away." [Barlow Girl]
_______________________________________________
Product-Developers mailing list
[hidden email]
http://lists.plone.org/mailman/listinfo/product-developers
