[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Add non-ASCII characters to morse.el

From: Simon Josefsson
Subject: Re: [PATCH] Add non-ASCII characters to morse.el
Date: Wed, 20 Nov 2002 20:33:35 +0100
User-agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.3.50 (i686-pc-linux-gnu)

Kenichi Handa <address@hidden> writes:

> In article <address@hidden>, Simon Josefsson <address@hidden> 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  <address@hidden>
>>      * 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 via email to

[Prev in Thread] Current Thread [Next in Thread]