Hi.
So to sum it up, the only correct way to do things is to have both
clipboard and selection. I have misunderstood this issue before.
Now, let's have a look at the other points:
> 1. Ted uses a target named "RTF" (not "text/rtf" like AbiWord
> does). It contains (surprisingly) pretty nice RTF. It _may_ be
> possible to achieve clipboard compatibility with ted. Do you think
> it's worth it?
After I defined AP_CLIPBOARD_RTF simply to "RTF" in ap_UnixClipboard.h
and recompiled, I am able to take a text with bold, italics and so on
and paste it into Ted with all the formatting. It looks great. The
question is - is there any need for the original "text/rtf" target?
> 2. Emacs uses a special format when using non-Latin1 encodings (it
> prefixes them with "\e-A", "\e-B", etc. sequences). I guess it's
> the correct way to encode ISO 10646 under X. We should be able to
> paste international text from Emacs.
This one looks rather complicated. It's simple when you want to
convert it to a particular encoding, supported by Xlib - you can call
gdk_text_property_to_text_list() then. Conversion to Unicode is rather
difficult - I have looked at the Compound encoding doc from X
Consortium and I think hardly anyone has done the full parsing. :( The
only program that accepts more than a single codepage is Emacs and
they do it using MULE and the "compound-text" encoding, which is
mostly written in Emacs Lisp. *sigh* I will hopefully get it working
for the ISO 8859-* charsets but don't expect any Japanese or Chinese
functionality... It's just too much work.
bye,
--
Petr Tesarik
Tel: +420 602 575294 http://www.lupa.cz/
