unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Add non-ASCII characters to morse.el
Date: Wed, 20 Nov 2002 20:33:35 +0100	[thread overview]
Message-ID: <ilu3cpwrq7k.fsf@latte.josefsson.org> (raw)
In-Reply-To: <200211201154.UAA28272@etlken.m17n.org> (Kenichi Handa's message of "Wed, 20 Nov 2002 20:54:05 +0900 (JST)")

Kenichi Handa <handa@m17n.org> writes:

> In article <ilu8yzoscs8.fsf@latte.josefsson.org>, Simon Josefsson <jas@extundo.com> writes:
>> Is there a better way to represent non-ASCII in elisp?
>
> What do you mean?  Some way other than Lisp string?

Yes.  The coding system used by *.el doesn't seem fixed, so if I add a
morse sequence for the euro sign by storing the euro sign literally,
someone else opening the file might read it as a Latin-1 currency
symbol -- and emacs treat the two characters as distinct.  Should I
add a charset cookie to the file perhaps?

>> If anyone has a better source of non-ASCII morse
>> characters, it might be useful as well.  Unfortunately, I
>> think morse has been dropped as an official language, so a
>> canonical source might be difficult to find.
>
> This page shows Japanese version of morse.  But, perhaps,
> it conflicts with English morse.
> 	<http://www5b.biglobe.ne.jp/~a1c/CW_J.htm>

They do conflict.  Interesting.  Is there a universal morse prefix for
language tagging morse code?  Can we use emacs internal charset
guessing algorithm for deciding which morse language to use?  Perhaps
this is too complicated for a toy package.  Unless someone wants to
work on it, I think we should only add non-conflicting characters.
(One character missing in my patch was .../... for ß.)

>> 2002-11-20  Simon Josefsson  <jas@extundo.com>
>
>> 	* play/morse.el (morse-code): Add non-ASCII characters, according
>> 	to table at http://www.soton.ac.uk/~scp93ch/morse/.
> [...]
>> +		     ("Ch" . "----")
>
> It seems that this entry doesn't work because mouse-region
> checks characters one by one.

Thanks.  I think it is supposed to be only one character (a
ligature?), but I don't know how to produce it.

  reply	other threads:[~2002-11-20 19:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 11:25 [PATCH] Add non-ASCII characters to morse.el Simon Josefsson
2002-11-20 11:54 ` Kenichi Handa
2002-11-20 19:33   ` Simon Josefsson [this message]
2002-11-20 21:22     ` Stefan Monnier
2002-11-21 11:30       ` Simon Josefsson
2002-11-22 16:11         ` Karl Eichwalder
2002-11-22 17:00           ` Simon Josefsson

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=ilu3cpwrq7k.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).