From: Miles Bader <snogglethorpe@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: entering CJK full-width space
Date: Tue, 28 Jun 2005 21:00:20 +0900 [thread overview]
Message-ID: <fc339e4a05062805001147c37a@mail.gmail.com> (raw)
In-Reply-To: <E1DnAfZ-00055d-00@etlken>
On 6/28/05, Kenichi Handa <handa@m17n.org> wrote:
> Japanese also uses a typography rule to start a paragraph
> with one full-width space in some context. But that is only
> in a well type-set text, and in a plane text, it's rare.
Anyway, isn't two ascii spaces good enough in most contexts?
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-06-28 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 5:06 entering CJK full-width space Werner LEMBERG
2005-06-28 6:52 ` Kenichi Handa
2005-06-28 7:10 ` Werner LEMBERG
2005-06-28 7:38 ` Kenichi Handa
2005-06-28 12:00 ` Miles Bader [this message]
2005-06-28 12:11 ` Kenichi Handa
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=fc339e4a05062805001147c37a@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=miles@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).