On 30 Jan 2006 05:23:00 -0800 "opalpa@gmail.com opalinski from
opalpaweb" <opalpa@gmail.com> waved a wand and this message magically
appeared:

"inter-anally"? Teehee.

On 30 Jan 2006 05:23:00 -0800, "opalpa@gmail.com opalinski from
opalpaweb" <opalpa@gmail.com> wrote, quoted or indirectly quoted
someone who said :

what that a typo or a Freudian slip or a slur?

On Mon, 30 Jan 2006 14:45:13 -0000, "Chris Uppal"
<chris.uppal@metagnostic.REMOVE-THIS.org> wrote, quoted or indirectly
quoted someone who said :

To index and process strings you need them in 16 bit form.  However,
for storage of strings not actively being processed I could imagine
some sort of caching scheme that converts them to UTF-8 for more
compact storage.  All string handling functions would have to be aware
of the two formats and automatically unpack Strings when accessed for
anything other than referencing the string as a whole.

It's new in 1.5.

   -- chris

i discoveded this

import java.nio.charset.Charset;
class StringTest
{
    public static void main(String[] args)
    {
        String defaultEncodingName = System.getProperty( "file.encoding" );
        System.out.println(defaultEncodingName);
    }
}

output:
=====
Cp1252

SO, my platform supports only Cp1252 encoding.

According to DOC >>

byte[]     getBytes()
         Encodes this String into a sequence of bytes using the
platform's default charset, storing the result into a new byte array.

AND

String(byte[] bytes)
         Constructs a new String by decoding the specified array of
bytes using the platform's default charset.

and According to my code here,

byte[] defaultBytes = original.getBytes();
String defaultTrip = new String(defaultBytes);

they should work with platform's default charset  and  that is "Cp1252"
( my discovery)

note, this is not unicode !!.......

but when i printed

System.out.println("defaultTrip = " + defaultTrip);

it prints a unicode !!!!!.....this should have printed some other
complex odd looking sring...is  not it ?

I'm not certain,  but I /think/ that you might be misunderstanding the
relationship between Strings and Charsets.

A String has /no/ Charset, and is not associated with any particular byte
encoding.  (Technically this is only true if you are using the right APIs, but
it close enough to being true to be a good approximation to start from[*]).
That's to say a String contains pure Unicode data, not in any encoding, just
pure characters.  (Compare the way that an int contains pure integer data,
separate from any encoding as big-endian or little-endian, or anything else).
A Charset is only involved when you need to convert a String to bytes (or the
other way around) in order to communicate with external systems or save the
data to file.

So, in your original example, after
   String original = new String("A" + "\u00ea" + "\u00f1" + "\u00fc" + "C");
you have a String, original, which contains pure Unicode.

If you new do:
   byte[] utf8Bytes = original.getBytes("UTF8");
then you have the original data encoded as UTF-8.  And later:
   String roundTrip = new String(utf8Bytes, "UTF8");
which gives you a new String containing pure Unicode data, assembled by
decoding the UTF-8 bytes.  Since UTF-8 is (by design) capable of encoding any
Unicode data, no information will have been lost, and roundTrip will be the
same as original.

When you do the same using the platform-default Charset:
   byte[] defaultBytes = original.getBytes();
   String defaultTrip = new String(defaultBytes);
The only thing that is different is that you are using a different Charset.
So, if that Charset happens to be capable of encoding every character in the
original String, no data will have been lost and roundTrip will be the same as
original.  If you had used any Unicode characters in original which could /not/
be encoded in the platform default Charset then the operation would have
failed.  Since the platform default Charset is machine-specific, that means
that you don't really know what'd gong to happen when you convert Strings into
byte[] arrays using it -- which is why using the platform default Charset is
usually a bad idea.

But the important thing to realise is that Strings don't have Charsets.
Charsets are only used when converting Strings to byte sequences.

   -- chris

([*] We can talk more about that approximation, if you want, but it best to get
the current confusion cleared up first)