[Zope-dev] Re: CVS: Zope/lib/python/TAL - TALGenerator.py:1.65
Hi! Chris McDonough wrote: Hmm. Without this fix, many CMFDefault (and possibly CMFCore) skins don't work. Is there a way to fix the offending CMF skins so that it works under Zope versions both with this fix and without (so we don't need two versions of CMF)? More importantly, is anyone willing to actually do this work? CMFCore has no skins. CMFDefault is the only product in cvs.zope.org:/cvs-repository/CMF using i18n. CMFDefault has just one template using this pattern: index_html_utils.html uses i18n:attributes=alt title So it would not be much work to change CMF. I'm not talking about third party products building on top of CMF. Plone was already discussed, I don't know what's the case with other products. What about backporting the i18n fix to Zope 2.6.2 ? Using CMF / Plone with i18n support requires Zope 2.6.0 anyway. Maybe we could force people updating CMF / Plone also to update Zope to 2.6.2. This way CMF / Plone could switch to the new spec. Just my 2 cents. Yuppie ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: CVS: Zope/lib/python/TAL - TALGenerator.py:1.65
On Sat, 2003-07-26 at 04:21, Yuppie wrote: CMFCore has no skins. CMFDefault is the only product in cvs.zope.org:/cvs-repository/CMF using i18n. CMFDefault has just one template using this pattern: index_html_utils.html uses i18n:attributes=alt title Sorry for overstating the problem. So it would not be much work to change CMF. Can it be changed in such a way that it works under 2.6.2, 2.7, and HEAD without the fix? It'd be a shame to require that people upgrade to a new version of CMF and/or Zope for one skin. I'm not talking about third party products building on top of CMF. Plone was already discussed, I don't know what's the case with other products. What about backporting the i18n fix to Zope 2.6.2 ? Using CMF / Plone with i18n support requires Zope 2.6.0 anyway. Maybe we could force people updating CMF / Plone also to update Zope to 2.6.2. This way CMF / Plone could switch to the new spec. I don't like breaking b/w compatibility this way, but honestly I don't really understand the issue about why this change was made in the first place, so perhaps I should go read up on that. - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: CVS: Zope/lib/python/TAL - TALGenerator.py:1.65
Chris McDonough wrote: Update of /cvs-repository/Zope/lib/python/TAL In directory cvs.zope.org:/tmp/cvs-serv15492/lib/python/TAL Modified Files: TALGenerator.py Log Message: Merge TAL i18n fixes which break CMF to HEAD from 2.7 branch. The agreement Jim was basically that this backward compatability will only go in 2.7, so that 2.8 will be fully compatible with the spec, however break backward compatability. What now? Phil ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: CVS: Zope/lib/python/TAL - TALGenerator.py:1.65
Hmm. Without this fix, many CMFDefault (and possibly CMFCore) skins don't work. Is there a way to fix the offending CMF skins so that it works under Zope versions both with this fix and without (so we don't need two versions of CMF)? More importantly, is anyone willing to actually do this work? On Fri, 2003-07-25 at 19:13, Philipp von Weitershausen wrote: Chris McDonough wrote: Update of /cvs-repository/Zope/lib/python/TAL In directory cvs.zope.org:/tmp/cvs-serv15492/lib/python/TAL Modified Files: TALGenerator.py Log Message: Merge TAL i18n fixes which break CMF to HEAD from 2.7 branch. The agreement Jim was basically that this backward compatability will only go in 2.7, so that 2.8 will be fully compatible with the spec, however break backward compatability. What now? Phil ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
