all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tak Ota <Takaaki.Ota@am.sony.com>
Subject: ctext-pre-write-conversion barfs
Date: Fri, 22 Feb 2002 22:53:55 -0800 (PST)	[thread overview]
Message-ID: <20020222.225355.01365596.Takaaki.Ota@am.sony.com> (raw)

2002-02-22  Eli Zaretskii  <eliz@is.elta.co.il>

	Support for ICCCM  Extended Segments in X selections:

	* international/mule-conf.el (ctext-no-compositions): New coding
	system.
	(compount-text-no-extensions): Renamed from compound-text.
	(x-ctext-no-extensions, ctext-no-extensions): Aliases for
	compound-text-no-extensions.
	(compound-text): Redefined using post-read and pre-write
	conversions.

	* international/mule.el (non-standard-icccm-encodings-alist)
	(non-standard-designations-alist): New variables.
	(ctext-post-read-conversion, ctext-pre-write-conversion): New
	functions.

`ctext-pre-write-conversion' is called from `writ-region' as

  annotations = build_annotations_2 (start, end,
				     coding.pre_write_conversion, annotations);

As an irregular case write-region sometimes passes a string in
`start'.  It seems like ctext-pre-write-conversion is not prepared to
receive a string in START.

-Tak

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


             reply	other threads:[~2002-02-23  6:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  6:53 Tak Ota [this message]
2002-02-23  8:48 ` ctext-pre-write-conversion barfs Eli Zaretskii
2002-02-23 16:11   ` Tak Ota
2002-02-23 18:51     ` (no subject) Eli Zaretskii
2002-02-23 23:11       ` Tak Ota
2002-02-25  1:11         ` [mew-int 00737] " Kazu Yamamoto
2002-02-25  6:55           ` Eli Zaretskii
2002-02-26 16:51     ` ctext-pre-write-conversion barfs Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020222.225355.01365596.Takaaki.Ota@am.sony.com \
    --to=takaaki.ota@am.sony.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.