Re: [Zope] Having problems with the umlauts in Zope 2.6.0
I run 2.6.1 beta 2 (actually the current CVS 2.6-branch) in production, because I had much trouble with 2.6.0 and "german umlaute". 2.6.1b2 works without problems... as far as I can see...:)
I've already installed the 2.6.1b2, but I'm still having the problem with the umlauts. I'll give you some more detail: I've two objects to represent a project proposal (ProjectProposal) and a started project (StartedProposal). Users can create new proposals. This proposals can be taken by one or two students. When this happens, the owner of the proposal will convert it into a started proposal. The system will create a new StartedProposal object with the values of the old object, which will be deleted. Finally the user will be asked to write the name of the students and/or edit the old attributes. The problem is that if the name of the students contain an umlaut, you will see strange characters on its place. However, if you edit this object a second time, the strange characters will be gone. This worked before in zope 2.5.1, but with 2.6.1b2 it doesn't. What could be wrong? I've already set my unicode "latin-1" in sitecustomize.py Thanks, Josef
On Friday 07 February 2003 2:29 pm, Josef Meile wrote:
I've already set my unicode "latin-1" in sitecustomize.py
undo that and try again -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson
I've already set my unicode "latin-1" in sitecustomize.py
undo that and try again I did it, but it didn't work. Anyway, I could solve it.
I was doing the following: <dtml-with myObject> <dtml-var editForm> </dtml-with> and I replaced it by: <dtml-let ObjUrl="_.str(myObject.absolute_url())"> <dtml-call "RESPONSE.redirect(ObjUrl+'/editForm')"> </dtml-let> Strangely I don't have those umlaut problems when modifying my properties.
Josef Meile wrote:
I run 2.6.1 beta 2 (actually the current CVS 2.6-branch) in production, because I had much trouble with 2.6.0 and "german umlaute". 2.6.1b2 works without problems... as far as I can see...:)
I've already installed the 2.6.1b2, but I'm still having the problem with the umlauts. I'll give you some more detail:
I've two objects to represent a project proposal (ProjectProposal) and a started project (StartedProposal). Users can create new proposals. This proposals can be taken by one or two students. When this happens, the owner of the proposal will convert it into a started proposal. The system will create a new StartedProposal object with the values of the old object, which will be deleted. Finally the user will be asked to write the name of the students and/or edit the old attributes.
The problem is that if the name of the students contain an umlaut, you will see strange characters on its place. However, if you edit this object a second time, the strange characters will be gone. This worked before in zope 2.5.1, but with 2.6.1b2 it doesn't. What could be wrong? I've already set my unicode "latin-1" in sitecustomize.py
I've had similar problems with diacriticals for french. Setting the locale in my start script seemed to take care of the problem. From my start script for Zope 2.6.0 on Linux (Debian and Redhat): exec /usr/bin/python /var/lib/zope260/z2.py -w 8080 -f 8021 -u zope -L "en_CA.ISO-8859-1" "$@" which sets the locale to Canadian english with ISO-8859-1 encoding which gives me the characters I need for such things as the accented e in Montréal. I still have some oddities in the ZCatalog though. Jim Gallacher
participants (3)
-
Jim Gallacher -
Josef Meile -
Toby Dickenson