[OGo-Developer] encoding of pllist files

[Sebastian Reitenbach]

Hi,

developer@opengroupware.org wrote: 
> On 30.01.2008, at 07:51, Sebastian Reitenbach wrote:
> > while trying to get ogo running against gunstep-base, I figured out  
> > that
> > there are problems with regards to the encodings of installed plist  
> > files,
> > e.g. WebUI/OGoWebMail.lso/Resources/Defaults.plist. This file contains
> > umlauts. The file tool says it is a: ISO-8859 C++ program text, with  
> > very
> > long lines. Without using recode, to recode this file to UTF-8,
> 
> ... just recode them to UTF-8 in your GS branch. I think both  
> templates and .strings files in OGo are already converted to UTF-8.
ah, ok, I'll do.


> 
> > #4  0xb758ed93 in _NSFoundationUncaughtExceptionHandler
> > (exception=3D0x9462d18) at NSException.m:719
> > #5  0xb758f50b in -[NSException raise] (self=3D0x9462d18,  
> > _cmd=3D0xb797a128) at
> > NSException.m:859
> 
> What is the exception?
>    frame 5
>    po self
> 
> Well, probably some syntax error.
I changed the =E4 and =FC in the Defaults.plist file with ae and ue, and then 
the exception was gone. So nothing regarding the syntax. Therefore I had the 
idea about the encoding of these files.


> 
> > I've no idea, whether all plist files should be encoded this way
> 
> Usually plist files should contain no umlauts and are plain ASCII. If  
> they *do* contain umlauts, we should make them UTF-8.
> (would require a conversion in NGParsePropertyListFromBuffer() which  
> is non-Unicode anyways [but UTF-8 would work for German umlauts])
There are some german umlauts in it, but these are commented out, so could 
be dropped as a whole.

thanks
Sebastian