[Zope-dev] default encoding used in ZPublisher.

2005-10-08 Thread Chris Withers

Hi All,

I'd like to backport the change I made to fix: 
http://www.zope.org/Collectors/Zope/1490


...to the 2.8 branch, would anyone have any objections to this?

cheers,

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] default encoding used in ZPublisher.

2005-10-08 Thread Andreas Jung



--On 8. Oktober 2005 19:15:57 +0100 Chris Withers [EMAIL PROTECTED] 
wrote:



Hi All,

I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490

...to the 2.8 branch, would anyone have any objections to this?



The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new major releases. So only bug 
fixes should go into minor releases.


Andreas

pgpPKQ2Bn6iBj.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] default encoding used in ZPublisher.

2005-10-08 Thread Chris Withers

Andreas Jung wrote:



I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490

...to the 2.8 branch, would anyone have any objections to this?


The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new major releases. So only 
bug fixes should go into minor releases.


Well, this is arguably a bug fix and I incorrectly filed it as a new 
feature on the trunk.


Yes, it adds a new zope.conf option, and that's why I filed this as a 
feature, but this is to fix the fact that the hard coded value has left 
me having to patch Zope for customers to get around the fact that it 
wrongly encodes strings sent to it by Plone's 
PlacelessTranslationService as latin-1. The problem is even worse when 
serving XML generated by a ZPT, which is encoded as latin-1 when it 
REALLY should be encoded as utf-8... (See Tres' email from earlier this 
evening)


Especially given the near zero risk of this bug (about 6 lines of code 
changed, and about 7 added) and the 100% backwards compatability (if the 
new zope.conf option is not included in zope.conf, the default is used 
and the default is identical to what it was: latin-1), I'd really like 
to merge this to the 2.8 branch in time for the 2.8.2 release...


Can anyone give me any good reasons not to? ;-)

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] default encoding used in ZPublisher.

2005-10-08 Thread Chris Withers

Andreas Jung wrote:


The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new major releases. So only 
bug fixes should go into minor releases.


In fact, just noticing other mails, I'd also like to merge this to the 
2.7 branch, I just wasn't aware there was going to be a 2.7.8 release...


This would stop the customers in question from having to make the huge 
leap to 2.8.x, which I was fearing they'd have to in order to get this 
specific change...


cheers,

Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] default encoding used in ZPublisher.

2005-10-08 Thread Tino Wildenhain
Am Samstag, den 08.10.2005, 19:15 +0100 schrieb Chris Withers:
 Hi All,
 
 I'd like to backport the change I made to fix: 
 http://www.zope.org/Collectors/Zope/1490
 
 ...to the 2.8 branch, would anyone have any objections to this?

Surely not, but what fix? :-)

Nice to see some movement on this issue

___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] default encoding used in ZPublisher.

2005-10-08 Thread Andreas Jung



--On 8. Oktober 2005 20:10:21 +0100 Chris Withers [EMAIL PROTECTED] 
wrote:



Andreas Jung wrote:



I'd like to backport the change I made to fix:
http://www.zope.org/Collectors/Zope/1490

...to the 2.8 branch, would anyone have any objections to this?


The 2.8 branch is closed for new features. With the time-based schedule
new features should appear regularly with new major releases. So only
bug fixes should go into minor releases.


Well, this is arguably a bug fix and I incorrectly filed it as a new
feature on the trunk.



If you can justify it as a bugfix before god and the world,go ahead :-)

Andreas



pgprjHrFsbeBu.pgp
Description: PGP signature
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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] default encoding used in ZPublisher.

2005-10-08 Thread Chris Withers

Andreas Jung wrote:

Well, this is arguably a bug fix and I incorrectly filed it as a new
feature on the trunk.


If you can justify it as a bugfix before god and the world,go ahead :-)


Cool, will do so to the 2.7 and 2.8 branches tomorrow :-)

cheers,

Chris

PS: I'll mark it as a bug fix in the relevent CHANGES.txt ;-)

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk
___
Zope-Dev maillist  -  Zope-Dev@zope.org
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 )