No Unicode support for DDE links - Issue 15540

(Not sure if that is specific to Writer or Office-wide)

Dear developers, 
please consider making DDE in Office Unicode-aware (see
http://www.openoffice.org/issues/show_bug.cgi?id=15540
).

Thanks a lot for your attention.
WBR,
Kirill Palagin.

Kirill S. Palagin wrote:
> (Not sure if that is specific to Writer or
Office-wide)
> 
> Dear developers, 
> please consider making DDE in Office Unicode-aware
(see
> http://www.openoffice.org/issues/show_bug.cgi?id=15540
).
> 
> Thanks a lot for your attention.
> WBR,
> Kirill Palagin.
> 

Hi,
it is office-wide.

A short debugging shows that the data provided by the
callback function 
doesn't support Unicode but only Ansi.

I don't know at the moment who's the one to care for this
issue.

Regards,
Oliver

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesw.openoffice.org
For additional commands, e-mail: dev-helpsw.openoffice.org

Hi Oliver,

On Friday, 2007-07-13 09:26:14 +0200, Oliver Specht - Sun
Germany -Hamburg wrote:

> >(Not sure if that is specific to Writer or
Office-wide)
> it is office-wide.

Not only.. the problem with DDE is that you don't know in
which encoding
the data arrives. There are several scenarios:

1. The easy one.
   Data source and data sink are both OOo applications: use
Unicode, in
   whatever encoding, utf-16, utf-8, but use the same
encoding on both
   ends.

2. The maybe easy one.
   Data source is on the same machine and within the same
user account
   as the data sink, but the data source is not OOo.
Applicable scenario
   for Windows boxes. Chances are high that both use the
same process
   encoding, but don't necessarily have to.

3. Another maybe easy one. Or not?
   Data source is on the same machine but another user
account, again
   data source is not OOo. Chances are quite high for the
same process
   encoding, but users may have different preferences. For
example, on
   our SunRays some prefer utf-8 locales, and others work in
Latin1
   locales.

4. It's getting complicated.
   Data source is on a completely different machine
somewhere across the
   network, you don't even know what encoding it might send
in.

5. You can't tell the difference.
   AFAIK there is no way for the data sink / DDE client to
differentiate
   and determine the correct encoding from the DDE protocol.
Please
   correct me if I'm wrong.

Conclusion: the best we could do would be to somehow
(possible?) have
a handshake that both, server and client, are OOo instances
and transfer
data in utf-16. If the server is not OOo assume that it
sends data in
the same process encoding OOo is running in. However, that
could be
completely wrong as well.

> A short debugging shows that the data provided by the
callback function 
> doesn't support Unicode but only Ansi.

Probably because the whole DDE mechanism was invented to be
used on
Windows only, but later spread to other platforms. Apart
from that it
was deprecated and replaced by OLE, there are probably no
other clients
than OOo that talk DDE on other platforms than Windows, with
the
exception of some OS/2 applications.

  Eike

-- 
 OOo/SO Calc core developer. Number formatter stricken i18n
transpositionizer.
 OpenOffice.org Engineering at Sun: http://blogs.sun.com/Gu
llFOSS
 Please don't send personal mail to this erlsun.com
account, which I use for
 mailing lists only and don't read from outside Sun. Use
eracksun.com Thanks.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesw.openoffice.org
For additional commands, e-mail: dev-helpsw.openoffice.org