[OGo-Users] ogo 1.1.7-close on sarge doesnt support geman umlauts after upgrade

[Adam Tauno Williams]

>this entries cant get corrected within the webui? there doesn't come an error, but it doesn't 
get changed.
>creating new entries with umlauts works fine, but i need also the old one ;)
>
>within the calender there does exist a week, when trying to check this for "all intranet" the 
user get logged out and get the following error in the screen:
>  class:   NSException
>  name:    UTFConversionException
>  reason:  couldn't convert UTF8 to UTF16, source buffer is to small 
(probably invalid input) !, data: < 4A616E20 6E696368 7420696D 2042FC72 
6F21 >
>  info:
>can somebody advice me the soluton?

Perhaps your PostgreSQL database is still using LATIN1.  If so export you 
database convert it to UTF8,  purge and reload.

If this is your problem the exact procedure is detailed in the PostgreSQL 
chapter of WMOGAG.  Also tells how to check the current encoding.

Also make sure you also upgraded SOPE & libFundation to the appropriate 
level.  See the WMOGAG section on OGo versions.