From: "川幡 太一" <kawabata.taichi@gmail.com> ( Taichi KAWABATA )
To: "Per Starbäck" <per@starback.se>
Cc: Juri Linkov <juri@jurta.org>,
"Stephen J. Turnbull" <stephen@xemacs.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org
Subject: Re: new Emacs HELLO file??
Date: Sun, 13 Sep 2009 02:51:51 +0900 [thread overview]
Message-ID: <87ws44qceg.fsf%kawabata.taichi@gmail.com> (raw)
In-Reply-To: <912155b0909120652s1649303o8468150c79c53f9b@mail.gmail.com> ("Per Starbäck"'s message of "Sat, 12 Sep 2009 15:52:06 +0200")
>> In <912155b0909120652s1649303o8468150c79c53f9b@mail.gmail.com>,
>> Per Starbäck wrote:
> 2009/9/8 Stephen J. Turnbull <stephen@xemacs.org>:
> > IMO, a better way to do this would be to change the HELLO file to be a
> > Lisp library, and encode it in UTF-8. The table of greetings can
> > simply be wrapped into a string, and add a table of "languages we have
> > preferred fonts for" in Lisp.
> Also if there's a hello command that creates a buffer ("*Hello*"?) dynamically,
> it could put a greeting for the appropriate locale at the top.
In some way, it is already realized by `sample-text' attribute of
`set-language-info-alist' function.
`HELLO' file may be useful for symbols and scripts not yet (or cannot
be) supported by Emacs as language, but are already encoded by the
UCS/Unicode.
Regards,
--
----------------------------------------------------
kawabata.taichi@gmail.com KAWABATA, Taichi
next prev parent reply other threads:[~2009-09-12 17:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 21:27 new Emacs HELLO file?? kawabata.taichi
2009-08-28 22:19 ` Juri Linkov
2009-08-29 2:16 ` 川幡 太一
2009-08-29 3:31 ` Stefan Monnier
2009-08-29 5:46 ` Daniel Clemente
2009-08-29 22:43 ` Juri Linkov
2009-08-30 1:16 ` kawabata.taichi
2009-08-30 3:12 ` Eli Zaretskii
2009-08-31 3:33 ` Richard Stallman
2009-08-31 16:10 ` kawabata.taichi
2009-08-31 17:07 ` Rupert Swarbrick
2009-08-31 16:16 ` Juri Linkov
2009-08-30 20:48 ` Juri Linkov
2009-08-31 15:12 ` Chong Yidong
2009-08-31 16:14 ` Juri Linkov
2009-08-31 16:15 ` Andreas Schwab
2009-08-31 16:32 ` David Kastrup
2009-08-31 17:02 ` Andreas Schwab
2009-09-01 11:41 ` Kenichi Handa
2009-09-01 21:27 ` Juri Linkov
2009-09-03 13:07 ` Kenichi Handa
2009-09-06 18:20 ` 牛粥
2009-09-06 20:01 ` Eli Zaretskii
2009-09-06 21:08 ` 牛粥
2009-09-07 1:02 ` Kenichi Handa
2009-09-07 1:01 ` Kenichi Handa
2009-08-31 17:55 ` Eli Zaretskii
2009-08-31 22:03 ` Andreas Schwab
2009-09-08 0:12 ` kawabata.taichi
2009-09-08 2:53 ` Stephen J. Turnbull
2009-09-12 13:52 ` Per Starbäck
2009-09-12 17:51 ` 川幡 太一 [this message]
2009-09-08 3:11 ` Eli Zaretskii
2009-09-12 17:45 ` Taichi KAWABATA
2009-09-12 19:39 ` Eli Zaretskii
2009-09-15 5:20 ` Kenichi Handa
2009-09-15 8:08 ` David Kastrup
2009-09-15 17:20 ` Eli Zaretskii
2009-09-15 17:12 ` Eli Zaretskii
2009-09-09 0:47 ` Juri Linkov
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=87ws44qceg.fsf%kawabata.taichi@gmail.com \
--to=kawabata.taichi@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=per@starback.se \
--cc=schwab@linux-m68k.org \
--cc=stephen@xemacs.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.