pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rajesh Mallah <mallah_rajesh@yahoo.com>
To: pgsql-sql@postgresql.org
Subject: Re: Significance of Database Encoding
Date: Sun, 15 May 2005 19:16:50 -0700 (PDT)
Message-ID: <20050516021650.78342.qmail@web31014.mail.mud.yahoo.com> (raw)


--- PFC <lists@boutiquenumerique.com> wrote:
> 
> > $ iconv -f US-ASCII -t UTF-8  < test.sql > out.sql
> > iconv: illegal input sequence at position 114500
> >
> > Any ideas how the job can be accomplised reliably.
> >
> > Also my database may contain data in multiple encodings
> > like WINDOWS-1251 and WINDOWS-1256 in various places
> > as data has been inserted by different peoples using
> > different sources and client software.
> 
> 	You could use a simple program like that (in Python):
> 
> output = open( "unidump", "w" )
> for line in open( "your dump" ):
> 	for encoding in "utf-8", "iso-8859-15", "whatever":
> 		try:
> 			output.write( unicode( line, encoding ).encode( "utf-8" ))
> 			break
> 		except UnicodeError:
> 			pass
> 	else:
> 		print "No suitable encoding for line..."


This may not work . Becuase ,conversion to utf-8 can be successfull (no runtime error)
even for an incorrect guess of the original encoding but the  result will be  an 
incorrect utf8. 

Regds
Rajesh Kumar Mallah


> 
> 	I'd say this might work, if UTF-8 cannot absorb an apostrophe inside a  
> multibit character. Can it ?
> 
> 	Or you could do that to all your table using SELECTs but it's going to be  
> painful...
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
> 


		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail 



view thread (5+ messages)

Message-ID: <20050516021650.78342.qmail@web31014.mail.mud.yahoo.com>
Permalink:  ../20050516021650.78342.qmail@web31014.mail.mud.yahoo.com/
Also on:    postgresql.org/message-id/20050516021650.78342.qmail@web31014.mail.mud.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: mallah_rajesh@yahoo.com
  Subject: Re: Significance of Database Encoding
  In-Reply-To: <20050516021650.78342.qmail@web31014.mail.mud.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox