unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adrian Robert <arobert@cogsci.ucsd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: How to convert char from Emacs-20 internal to UTF-8?
Date: Wed, 16 Mar 2005 14:19:16 -0500	[thread overview]
Message-ID: <1edb21fc2b6a61e8bd8d7b4d77aec1ec@cogsci.ucsd.edu> (raw)
In-Reply-To: <87acp3jyqi.fsf-monnier+emacs@gnu.org>


On Mar 16, 2005, at 12:19 PM, Stefan Monnier wrote:

>> I apologize for the "retro" question, but I was wondering if there 
>> was an
>> easy way to convert a character in the Emacs-20 internal 19-bit 
>> encoding
>> (from FAST_GLYPH_CHAR(glyph)) to UTF-8 (preferable) or straight 
>> Unicode.
>> I'd like to do it fully within C if possible, and it needs to be 
>> efficient.
>
> Since Emacs-21's internal chars are a superset of Emacs-20's internal 
> chars,
> you can just use Emacs-21's facilities like (encode-coding-string <str>
> 'utf-8) or (encode-char <char> 'ucs).

Thanks.  Are the encode-coding-string and encode-char functions a) fast 
enough to be used inside of dumpglyphs() for screen rendering and b) 
something I can easily lift out of 21 and backport to 20?  I'm asking 
because this is for a GNUstep/OS X interface for emacs 20 
(http://emacs-on-aqua.sf.net/), and while we'd like to bring it up to 
date to work with the coming emacs-22 (where I assume this problem 
disappears completely), this is a large job and we'd like to have 
support for 2-byte font and other i18n rendering in the meantime.  (In 
the OpenStep APIs, conversions to native font encoding are handled 
internally, so we don't need all of CCL's generality, but we need to 
get characters in UTF-8 or unicode to give to the APIs in the first 
place.)

  reply	other threads:[~2005-03-16 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 16:46 How to convert char from Emacs-20 internal to UTF-8? Adrian Robert
2005-03-16 17:19 ` Stefan Monnier
2005-03-16 19:19   ` Adrian Robert [this message]
2005-03-16 19:38     ` Stefan Monnier
2005-03-17  3:20     ` Adrian Robert
2005-03-22 17:30   ` Adrian Robert
2005-03-23  4:52     ` Miles Bader

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=1edb21fc2b6a61e8bd8d7b4d77aec1ec@cogsci.ucsd.edu \
    --to=arobert@cogsci.ucsd.edu \
    --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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).