unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@ni.aist.go.jp>
To: emacs-devel@gnu.org
Subject: charprop.el and uni-*.el
Date: Mon, 04 Feb 2008 17:24:55 +0900	[thread overview]
Message-ID: <E1JLwdL-0003mt-OP@etlken.m17n.org> (raw)

I intended to put files charprop.el and uni-*.el under
lisp/internatinal in CVS, and someone who re-generats them
from admin/unidata/UnicodeData.txt (perhaps by getting the
recent version of that file from unicode.org) commits them.

And, this part in src/Makefile.in:

#ifdef HAVE_UNIDATA
UNIDATA=${admindir}unidata/UnicodeData.txt

${lispsource}international/charprop.el: temacs${EXEEXT} ${UNIDATA}
	RUNEMACS="$(RUN_TEMACS)"; \
	cd ${admindir}unidata; \
	$(MAKE) $(MFLAGS) \
	  RUNEMACS="$${RUNEMACS}" DSTDIR=${lispsource}international
#endif

was just for my conveninence, and I forgot to delete it.

So, I'm going to commit charprop.in and uni-*.el in CVS and
delete the above target in src/Makefile.in.  Any objection?

In the future, I'll write a code to gradually generate data
in uni-*.el from UnicodeData.txt (storing it under etc) on
demand, but for the moment, I don't have a time to do that.
If someone can work on it, I appreciate it very much.

---
Kenichi Handa
handa@ni.aist.go.jp

PS. As I didn't reach the Internet in the weekend, I read
mails this morning, and I have not yet understood well which
problems are already solved, and which are not.  :-(




             reply	other threads:[~2008-02-04  8:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04  8:24 Kenichi Handa [this message]
2008-02-04 10:17 ` charprop.el and uni-*.el Kim F. Storm
2008-02-04 11:03   ` Kenichi Handa
2008-02-04 15:15 ` Dan Nicolaescu
2008-02-04 20:50 ` Eli Zaretskii
2008-02-05  0:39   ` Kenichi Handa
2008-02-11  5:35 ` Kenichi Handa
2008-02-11 10:05   ` Jason Rumney
2008-02-12  7:28     ` Kenichi Handa
2008-02-12  9:15       ` Jason Rumney
2008-02-12  9:25         ` Lennart Borgman (gmail)
2008-02-13  5:32           ` Kenichi Handa
2008-02-13  9:33             ` Juanma Barranquero
2008-02-13 16:32               ` Lennart Borgman (gmail)
2008-02-13 16:41                 ` Juanma Barranquero
2008-02-13 17:06                   ` Lennart Borgman (gmail)
2008-02-13 17:36                     ` Juanma Barranquero
2008-02-13 18:17                       ` Lennart Borgman (gmail)
2008-02-13 20:49                         ` Juanma Barranquero
2008-02-14  1:33                           ` Stefan Monnier
2008-02-14  1:37                             ` Juanma Barranquero
2008-02-14 10:56                         ` Lennart Borgman (gmail)
2008-02-16 12:12                         ` Lennart Borgman (gmail)
2008-02-16 17:48                           ` Juanma Barranquero
2008-02-16 20:49                             ` Lennart Borgman (gmail)
2008-02-14  8:11                     ` Jason Rumney
2008-02-13  5:29         ` Kenichi Handa
2008-02-11 19:00   ` Glenn Morris
2008-02-12  6:25     ` 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=E1JLwdL-0003mt-OP@etlken.m17n.org \
    --to=handa@ni.aist.go.jp \
    --cc=emacs-devel@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).