On Oct 11, 2005, at 10:44 AM, Richard M. Stallman wrote: (I guess I was trying to say, "drop XLFD, and if some functionality is lost, update the lisp syntax to fix it".)We don't need to change Emacs for that. You should be able, already,to do whatever you like in Emacs without using
Hi,
I apologize if this is a dumb question, but I've been looking through
the code and can't figure this one out: on the unicode-2 branch, if a
font specifies "iso-10646-1" for XLFD registry/encoding (and then
fontset.c sets 'charset' accordingly), what exactly is getting passed
in struct
On Oct 11, 2005, at 4:01 AM, YAMAMOTO Mitsuharu wrote:
On Fri, 07 Oct 2005 10:53:22 -0400, Adrian Robert
<[EMAIL PROTECTED]> said:
In addition, I've been integrating the Cocoa port's font handling
with xfaces.c, and can say it's onerous for developers. All of
On Oct 9, 2005, at 2:16 PM, Richard M. Stallman wrote:
You're right.. But the population of "power users" in this
case for
whatever reason seems fairly large (just subjective
impression), and
the requirement to learn XLFD (to compose a fontset, or whatever
else) and partake
On Sep 28, 2005, at 4:30 AM, YAMAMOTO Mitsuharu wrote:
On 25 Sep 2005 10:20:31 -0400, Adrian Robert
<[EMAIL PROTECTED]> said:
Even in X11, while XLFD is needed at the lowest level to interact
with the windowing system, is it really necessary to expose the user
to it? In the ol
> > screen. I was also trying to maintain backwards compatibility of
> old > XLFDs, which I'm starting to think was unwise. I've made two
> attempts at
> Regarding this, I think it would be good for people working on
> Emacs.app, w32, and Xft to get together and try to figure out what to
> do w
On Sep 22, 2005, at 2:03 AM, Steven Tamm wrote:
As for the unicode branch, the way that unicode font handling is done
on the Mac (ATSUI) is different from the old-style (Quickdraw) that is
used in the Carbon port.Quickdraw is based on MBTE and converting
it to unicode is hard. I've done
On Sep 15, 2005, at 9:00 AM, Richard M. Stallman wrote:
That's correct -- or actually the GNUstep "version" and the OS X
one
are the same code, with a few ifdefs here and there. The APIs
provided by GNUstep and Cocoa are almost identical (or at least
largely overlapping; pleas
be a perfectly reasonable thing to do.
To release this code in a modified version, which runs only on
a non-free system, would be deleterious to the goals of the GNU
Project.
Please don't ever suggest such a thing to anyone.
IIUC Adrian Robert works mainly on the GNUstep version, which
On Sep 12, 2005, at 3:35 PM, Stefan Monnier wrote:
OTOH if the work can be expected to take in the order of a few
months only
(i.e. a large part of the work you've done on 20.7 can be reused
with little
or no changes), it would also make sense to start from the current
HEAD (to
be 22.1).
Thanks all for the info; I'll start examining the unicode-2 code..
-Adrian
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Hi,
I'm maintaining the Emacs-on-Aqua GNUstep / OS X port, currently
based on emacs 20.7 (http://emacs-on-aqua.sf.net/). I want to update
this to a more recent version but would ideally like to do so against
a stabilized / released version of GNU emacs -- just so I know that
bugs are my
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
> The trunk of the CVS repository (which will becomes Emacs-22)
> already supports OS X (via Carbon).
>
> If that doesn't help you because you want to use some other
> API, I recommend you start from the emacs-unicode-2 branch in
> the CVS repository (which may become Emacs-23). That branch
> chan
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
Hi all,
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 e
16 matches
Mail list logo
