Trying to unravel a copy/paste puzzle

I received an email yesterday from a developer. He is working on a
project which is trying to get copy and paste to work between some Java
applications that his team wrote and some Tcl applications.

He tells me that the Java applications are text editors for files which
contain non-roman characters (Japanese, Korean, Russian, Chinese). The
characters being displayed are Unicode.

The Tcl applications are also displaying the same kinds of characters.

When the user attempts to paste non-roman characters, from one to the
other, all they get is a series of question marks and garbage
characters.

They find that they can copy and paste from tcl to tcl or from java to
java. However, any time they try to go from apps written in one to the
other, they get the garbage/question marks.

Can anyone suggest some things I can try so as to figure out what is
going wrong?

.

Relevant Pages

  • Javac-compilor error
    ... discipline id.e.programming Java. ... from standard input and writes to standard output, but it is possible to redirect the input ... error occurs while trying to open the file, an exception of type IllegalArgumentException ... then this number of characters, then extra spaces are added to the front of x to bring ...
    (Fedora)
  • Re: gotchas.html: Missing Hex
    ... >> There is a difference between entering characters into ... existence of Java than the amount of words in the JLS and VMS (VM ... The problem with Java is that it is, in fact, a necessary restriction ... Java is a strongly typed language, ...
    (comp.lang.java.help)
  • Re: Cons cell archaic!?
    ... So you are saying it's a blob of molton, but better blob than C or Java? ... indeed we will no longer need either assembly languages or C, ... practical way to learn what these recognized characters mean. ...
    (comp.lang.lisp)
  • Re: Is anything easier to do in java than in lisp?
    ... > Java chars are now just like C chars, only they are fixed to 16 bit ... they are not unicode chars. ... using the first 128 characters as-is and the last 128 characters only ... the claim that a java character is a Unicode character is not ...
    (comp.lang.lisp)
  • Re: Is anything easier to do in java than in lisp?
    ... > Java chars are now just like C chars, only they are fixed to 16 bit ... they are not unicode chars. ... using the first 128 characters as-is and the last 128 characters only ... the claim that a java character is a Unicode character is not ...
    (comp.lang.java)