Skip site navigation (1) Skip section navigation (2)

Re: bugfix: Encoding of config files

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: bugfix: Encoding of config files
Date: 2006-01-24 19:07:50
Message-ID: 43D67B06.3040500@pse-consulting.de (view raw or flat)
Thread:
Lists: pgadmin-hackers
Dave Page wrote:
>  
> 
> 
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de] 
>>Sent: 23 January 2006 23:31
>>To: Dave Page
>>Cc: Magnus Hagander; pgadmin-hackers(at)postgresql(dot)org
>>Subject: Re: [pgadmin-hackers] bugfix: Encoding of config files
>>
>>
>>NB, when reading AND writing!
>>And the wxUtfFile class will behave differently when creating 
>>a file or 
>>rewriting (will preserve encoding in the latter case)
> 
> 
> Err, ok. Well, how does the attached look o'Guru of encoding and such
> things?

No need to detect encoding, file reading/writing committed.

This problem probably persisted before, but problematically the problem 
that when opening a file after a file was opened (just open a file, and 
then open a recent file) is still persistent as problem. Probably a 
not-so-clean destructor (line array?)

Regards,
Andreas

In response to

Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2006-01-24 21:18:59
Subject: Re: bugfix: Encoding of config files
Previous:From: svnDate: 2006-01-24 19:00:25
Subject: SVN Commit by andreas: r4957 - trunk/pgadmin3/src/frm

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group