2015-05-06 40 views
3

我已经创建了一个schemaextender软件包,其中我试图覆盖bikaplone域的某些字符串。我的新包的来源是在这里:https://github.com/rockfruit/bika.uw.giti18n消息:来自多个PO文件的消息的优先顺序

的安装方法,我建议和使用(适用于所有的Plone插件/实例)是这样的:

  • 安装Plone的UnifiedInstaller。
  • 修改'eggs ='和'develop ='行,包含“bika.lims”和“bika.uw”。
  • 运行斌/扩建

采用这种安装方法,我重写不重写。在zope.i18n中,我发现translationdomain.py总是优先选择原始翻译,并且只在原始bika目录中没有相同的字符串时才使用schemaextender包中的那些字符串(即,对于在扩展的Python或TAL代码中翻译的消息打包本身;在所有的Bika或Plone代码中,我的新目录都被忽略)。

我读过buildout.cfg中的zcml = section可能被用来强制zcml加载顺序改变,从而导致消息被优先于先前加载的包。所以,我曾尝试如下修改,但是从bika.lims目录仍然是首选:

zcml = 
    Products.CMFPlone 
    bika.uw 
    bika.lims 

现在,这里有一个线索,我发现。上面链接到的github仓库在根上有一个buildout.cfg,它不使用UnifiedInstaller,而是直接下载Plone和其他依赖项。它不包含zcml =行。

git clone https://github.com/rockfruit/bika.uw.git 
cd bika.uw 
virtualenv . 
./bin/pip install zc.buildout 
bin/buildout 
bin/zeoserver fg & # no idea why 'start' does not work 
bin/zeoclient fg 

我的问题是::但令人惊讶的使用这种安装方法时(对我来说)翻译覆盖两个域的工作(就像买了一个!)我在做什么错了,正常的和推荐的安装程序会阻止我的翻译覆盖文件采取正确的优先顺序?

我很尴尬地承认,但我会无论如何:这让我感到困惑

我粘贴了下面我现有的buildout.cfg,其中今天早上我试图模仿bika.uw.git/buildout.cfg文件的行为,但没有成功。


[buildout] 

# buildout-original.cfg is the Plone 4.3.4 zeocluster unified-installer file. 
extends = 
    buildout-original.cfg 

zeo-address = 8081 
client1-address = 8085 
client2-address = 8086 

effective-user = campbell 
buildout-user = campbell 
user=admin:adminsecret 

need-sudo = no 
var-dir=${buildout:directory}/var 
backups-dir=${buildout:directory}/backups 
deprecation-warnings = on 
verbose-security = on 

eggs = 
    bika.uw 
    bika.lims 
    pudb 
    i18ndude 
    test 
    robot 
    zest.releaser 

develop += 
    /home/campbell/Plone/repos/bika.uw 
    /home/campbell/Plone/repos/bika.lims 

parts = 
    zeoserver 
    client1 
    client2 
    backup 
    zopepy 
    unifiedinstaller 

zcml = 

[zeoserver] 
<= zeoserver_base 
recipe = plone.recipe.zeoserver 
zeo-address = 127.0.0.1:${buildout:zeo-address} 
zserver-threads = 1 

[client1] 
<= client_base 
recipe = plone.recipe.zope2instance 
zeo-address = ${zeoserver:zeo-address} 
http-address = ${buildout:client1-address} 
resources = ${buildout:directory}/resources 
locales = ${buildout:directory}/locales 

[client2] 
<= client_base 
recipe = plone.recipe.zope2instance 
zeo-address = ${zeoserver:zeo-address} 
http-address = ${buildout:client2-address} 
resources = ${buildout:directory}/resources 
locales = ${buildout:directory}/locales 

[versions] 
Cheetah = 2.2.1 
plone.recipe.command = 1.1 
plone.recipe.precompiler = 0.6 
plone.recipe.unifiedinstaller = 4.3.1 
Products.DocFinderTab = 1.0.5 
ZopeSkel = 2.21.2 
collective.recipe.backup = 2.14 
zopeskel.dexterity = 1.5.3 
zopeskekel.dexterity = 1.5.3 
zopeskel.diazotheme = 1.1 

回答

0

我想我的talk我在2012年在阿纳姆的Plone会议作出了名单仍然是准确的。这是po文件的加载顺序:

  1. 区域设置= $ {扩建:目录} /区域设置
  2. ZCML = your.package
  3. 产品按字母顺序,直到并包括Products.CMFPlone
  4. 包注册与z3c。autoinclude
  5. 其余产品
  6. 的i18n文件夹(由PlacelessTranslationService完成)的

在您的情况:从ZCML参数中删除Products.CMFPlone。它混合了订单。