--- PFC <[EMAIL PROTECTED]> 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 WIN
$ 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
--- PFC <[EMAIL PROTECTED]> wrote:
>
> > +--+
> > | 私はガラス
> > +--+
>
> You say it displays correctly in xterm (ie. you did
+--+
| 私はガラス
+--+
You say it displays correctly in xterm (ie. you didn't see these in your
xterm).
There are HTML/XML unicode
I am not sure why the characters did not display properly
in the mailling list archives.
http://archives.postgresql.org/pgsql-sql/2005-05/msg00102.php
but when i do the select in my screen (xterm -u8) i do
see the japanese glyphs properly.
Regds
Mallah.
--- Rajesh Mallah <[EMAIL PROTECTE
Hi ,
I would want to know what is the difference between databases
that are created using UNICODE encoding and SQL_ASCII encoding.
I have an existing database that has SQL_ASCII encoding but
still i am able to store multibyte characters that are not
in ASCII character set. for example:
tradein_c
