[Zope-Checkins] CVS: Zope3/lib/python/Zope/I18n - i18n.zcml:1.8

[Stephan Richter]

Update of /cvs-repository/Zope3/lib/python/Zope/I18n
In directory cvs.zope.org:/tmp/cvs-serv18258/lib/python/Zope/I18n

Modified Files:
	i18n.zcml 
Log Message:
Finished Zope 3 Unicode support. Zope 3 should now be able to handle all 
unicode formats. Note that ebcoding and decoding unicode strings is based
on the parameters we get from the browser in HTTP_ACCEPT_CHARSET.

All "text strings" (strings that represent human language text) internally 
in Zope 3 should be unicode strings from now on! I have not checked all of 
Zope 3, so if you see a non-unicode text string somewhere, please convert
it simply by putting 'u' before the string literal.

Note that binary data, such as images are not to be encoded. 

The encoding happens on the HTTPRequest/HTTPResponse abstraction level. 
That means that currenty FTP does not profit from this new code; however
FTP is always data anyhow.


=== Zope3/lib/python/Zope/I18n/i18n.zcml 1.7 => 1.8 ===
 
 <!-- Setup charset negotiation -->
-<adapter factory="Zope.Publisher.Browser.BrowserCharsets."
-         for="Zope.Publisher.Browser.IBrowserRequest."
+<adapter factory="Zope.Publisher.HTTP.HTTPCharsets."
+         for="Zope.Publisher.HTTP.IHTTPRequest."
          provides="Zope.I18n.IUserPreferredCharsets."
          />