unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kenichi Handa <handa@m17n.org>
Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org
Subject: Re: Treatment of LRE,RLE,LRO,RLO,PDF,LRM,RLM
Date: Mon, 01 Nov 2010 05:57:17 -0400	[thread overview]
Message-ID: <E1PCr8f-0003bZ-UC@fencepost.gnu.org> (raw)
In-Reply-To: <tl7vd4hv4ry.fsf@m17n.org> (message from Kenichi Handa on Mon, 01 Nov 2010 17:15:13 +0900)

> From: Kenichi Handa <handa@m17n.org>
> Date: Mon, 01 Nov 2010 17:15:13 +0900
> Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org
> 
> I've just committed a basic infrastructure for displaying
> non-graphic and no-font characters.

Thanks!

> Char-table to control displaying of glyphless characters.
> Each element, if non-nil, is an ASCII acronym string (displayed in a box)
> or one of these symbols:
>   hexa-code: display with hexadecimal character code in a box
    ^^^^^^^^^
Suggest to name this "hex-code" instead.

>   empty-box: display with an empty box
>   thin-space: display with 1-pixel width space
>   zero-width: don't display
> 
> It has one extra slot to control the display of a character for which
> no font is found.  The value of the slot is `hexa-code' or `empty-box'.
> The default is `empty-box'.

What will happen on a TTY?

> glyphless-char-control is a variable defined in `characters.el'.
  ^^^^^^^^^^^^^^^^^^^^^^
Suggest to name this "glyphless-char-display-control".

  reply	other threads:[~2010-11-01  9:57 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tl7hbis1xop.fsf@m17n.org>
     [not found] ` <AANLkTinrGPzGquxPmfigvZLzGbids39yU942sfwKGMYk@mail.gmail.com>
2010-08-19  2:49   ` [emacs-bidi] Treatment of LRE,RLE,LRO,RLO,PDF,LRM,RLM Kenichi Handa
2010-11-01  8:15     ` Kenichi Handa
2010-11-01  9:57       ` Eli Zaretskii [this message]
2010-11-01 11:16         ` Kenichi Handa
2010-11-13 13:51           ` [emacs-bidi] " Eli Zaretskii
2010-11-17  5:58             ` Kenichi Handa
2010-11-17  7:14               ` Kenichi Handa
2010-11-17 12:21               ` Eli Zaretskii
2010-11-17 19:20                 ` Eli Zaretskii
2010-11-13 13:44       ` Eli Zaretskii
2010-11-13 14:07         ` Eli Zaretskii
2010-11-17  3:57         ` Kenichi Handa
2010-11-17 12:26           ` Eli Zaretskii
2010-11-17 12:55             ` Andreas Schwab
2010-11-17 13:24               ` Stefan Monnier
2010-11-18 20:07                 ` Eli Zaretskii
2010-11-17 17:54               ` Eli Zaretskii
2010-11-17 23:59                 ` Stefan Monnier
2010-11-18 20:04                   ` Eli Zaretskii
2010-11-18 22:15                     ` Stefan Monnier
2010-11-19 11:31                       ` Eli Zaretskii
2010-11-20 15:06                       ` Eli Zaretskii
2010-11-19  9:53                     ` Andreas Schwab
2010-11-19 11:31                       ` Eli Zaretskii
2010-11-19 11:47                         ` Andreas Schwab
2010-11-17 19:39             ` Eli Zaretskii
2010-11-26 12:20               ` Eli Zaretskii
2010-11-26 12:29               ` Kenichi Handa
2010-11-27  8:42                 ` Eli Zaretskii
2010-11-29  6:35                   ` Kenichi Handa
2010-11-29 18:06                     ` Stefan Monnier
2010-11-20 14:38           ` 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

  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=E1PCr8f-0003bZ-UC@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).