From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Jason Rumney" <jasonr@gnu.org>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: segmentation fault displaying etc/HELLO on Windows
Date: Wed, 30 Jul 2008 16:03:33 +0200 [thread overview]
Message-ID: <f7ccd24b0807300703p26fe2abof3135eed19e4fff9@mail.gmail.com> (raw)
In-Reply-To: <48906865.4000808@gnu.org>
On Wed, Jul 30, 2008 at 15:11, Jason Rumney <jasonr@gnu.org> wrote:
> Indeed, that was the problem. I reduced the buffer size to 1, since
> characters that produce multiple glyphs can't be handled properly by
> uniscribe_encode_char, but passed in a size of 20 (a number I'd picked
> after I'd come across Indic characters that produce more than the 2
> glyphs I'd originally allowed for) to the system function.
I can confirm that it doesn't crash anymore.
And the performance improvement is really great; I've been able to
scroll down the whole etc/NEWS buffer with the redisplay keeping the
pace and not a single undesired recenter in sight...
BTW, one of those questions about weird font selection choices by the
font backend:
In etc/HELLO there are two instances of U+2200 (FOR ALL). The newest
release of DejaVu (2.26) added a glyph for that codepoint to DejaVu
Sans Mono, which I use as default font.
Now the weird thing is, the first FOR ALL in etc/HELLO is shown as
character: ∀ (8704, #o21000, #x2200)
preferred charset: unicode (Unicode (ISO10646))
code point: 0x2200
syntax: . which means: punctuation
category: h:Korean j:Japanese
buffer code: #xE2 #x88 #x80
file code: ESC #x24 #x42 #x22 #x4F (encoded by coding system
iso-2022-7bit-dos)
display: by this font (glyph code)
uniscribe:-outline-DejaVu Sans
Mono-normal-normal-normal-mono-13-*-*-*-c-*-iso10646-1 (#x7A2)
while the second one is
character: ∀ (8704, #o21000, #x2200)
preferred charset: unicode (Unicode (ISO10646))
code point: 0x2200
syntax: . which means: punctuation
category: h:Korean j:Japanese
buffer code: #xE2 #x88 #x80
file code: ESC #x24 #x42 #x22 #x4F (encoded by coding system
iso-2022-7bit-dos)
display: by this font (glyph code)
uniscribe:-outline-MS
Mincho-normal-normal-normal-mono-13-*-*-*-c-*-jisx0208*-* (#x421)
Shouldn't it use DejaVu Sans Mono for both?
Juanma
next prev parent reply other threads:[~2008-07-30 14:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:49 segmentation fault displaying etc/HELLO on Windows Juanma Barranquero
2008-07-30 6:48 ` Jason Rumney
2008-07-30 11:48 ` Juanma Barranquero
2008-07-30 13:05 ` Jason Rumney
2008-07-30 13:11 ` Jason Rumney
2008-07-30 14:03 ` Juanma Barranquero [this message]
2008-07-30 14:19 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Jason Rumney
2008-07-30 15:03 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-07-30 15:26 ` Juanma Barranquero
2008-08-01 12:50 ` Kenichi Handa
2008-08-01 12:56 ` Choice of fonts displaying etc/HELLO (was: Re: segmentation fault displaying etc/HELLO on Windows) Kenichi Handa
2008-08-01 13:17 ` Choice of fonts displaying etc/HELLO Jason Rumney
2008-08-01 13:51 ` Eli Zaretskii
2008-08-05 7:33 ` Kenichi Handa
2008-08-05 18:12 ` Eli Zaretskii
2008-08-06 5:30 ` Kenichi Handa
2008-08-06 6:14 ` Stephen J. Turnbull
2008-08-06 6:29 ` Kenichi Handa
2008-08-06 15:52 ` Stephen J. Turnbull
2008-08-06 17:56 ` Eli Zaretskii
2008-08-07 1:14 ` Kenichi Handa
2008-08-07 3:22 ` Eli Zaretskii
2008-08-07 3:54 ` Kenichi Handa
2008-08-07 4:54 ` Miles Bader
2008-08-07 18:03 ` Eli Zaretskii
2008-08-07 19:30 ` Stephen J. Turnbull
2008-08-11 8:48 ` Miles Bader
2008-08-11 19:03 ` Eli Zaretskii
2008-07-31 1:49 ` segmentation fault displaying etc/HELLO on Windows Kyle M. Lee
2008-07-31 2:03 ` Juanma Barranquero
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=f7ccd24b0807300703p26fe2abof3135eed19e4fff9@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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.