• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Deprecated method: use system default encoding or UTF-8

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear all,
For the deprecated method, the API suggested two ways to replace, one is using the system default encoding another is using a specific character-encoding name.
My question is which one to use is appropriated?
Thanks.
 
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I went for ISO-8859-1 to maintain backwards compatibility with potentially existing data files.
The deprecated version uses the ASCII characterset as the ISO-8859-1 does.
Bern
 
Jane Wang
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks a lot!
 
Ranch Hand
Posts: 149
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Could you please tell how you decided ISO-8859-1 as the encoding currently used?
I used UTF-8 and it seems to be compatible with the current db file.
 
Ranch Hand
Posts: 146
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
Me too use UTF-8. It seems that our db was written using the same, and as for as my knowledge linux and windows has a support to UTF-8.
-rameshkumar
 
Bernhard Woditschka
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is of couse a drawback in not using UTF-8 you are bound to ASCII.
I decided againstUTF-* because with UTF-8 the length of the UTF-8 encoded data is not fixed. One char an be 1 or more than one byte.
Bern
 
Ramesh kumaar
Ranch Hand
Posts: 146
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Woditschka,
wodi wrote
---------------------
There is of couse a drawback in not using UTF-8 you are bound to ASCII.
I decided againstUTF-* because with UTF-8 the length of the UTF-8 encoded data is not fixed. One char an be 1 or more than one byte.
----------------------
It would be useful for us if u say what else ur using instred of UTF-8.
regards,
rameshkumar
 
Ranch Hand
Posts: 3404
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Ramesh ,
I think you'll find he has

posted January 01, 2003 05:32 AM
--------------------------------------------------------------------------------
I went for ISO-8859-1 to maintain backwards compatibility with potentially existing data files.


Thanks
 
Bernhard Woditschka
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yep, thats right
The big drawback of this solution is, that it's not internationalzed - (e.g. Japan or China won't be able to use it) so there is still al ot of room for improvement.
Bern
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic