all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: inter-client cut/copy paste & Small Caps
Date: Wed, 25 Mar 2009 08:01:13 +0900	[thread overview]
Message-ID: <873ad2msp2.fsf@catnip.gol.com> (raw)
In-Reply-To: d2afcfda0903241151r6e3bf0dfk42db2635edace0a0@mail.gmail.com

MON KEY <monkey@sandpframing.com> writes:
> Ignoring WYSIWYG editors (and their clipboard handling) this doesn't
> change that utilization of Small Caps on the web is quite prevalent -
> in many use cases the Small Caps  convey syntax. Simply discarding
> this information is prob. not the best way to promote vigorous
> utilization of 'The One True Editor'. It is worth noting that  Emacs
> handles APL char data from the clipboard in a reasonable way. Is one
> to assume that the relatively infrequently encountered APL syntax is
> considered too significant to discard but it is OK for Small Caps to
> be lossy?

The "APL char data" is preserved because it's already "character level"
information, whereas the small caps info is higher-level formatting
info ("metadata").  They are very different things.

Because of that, there's precious little emacs could _do_ with higher
level formatting data, even if it preserved it -- you can't just insert
such formatted text into a plain text document and expect useful
results...

[I think in the vast majority of cases, small caps are used only for
presentation purposes anyway.]

-Miles

-- 
Corporation, n. An ingenious device for obtaining individual profit without
individual responsibility.





      reply	other threads:[~2009-03-24 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24  0:08 inter-client cut/copy paste & Small Caps MON KEY
2009-03-24  4:13 ` Eli Zaretskii
2009-03-24 18:51   ` MON KEY
2009-03-24 23:01     ` Miles Bader [this message]

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=873ad2msp2.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.