unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cesar Crusius <cesar.crusius@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Cesar Crusius <cesar.crusius@gmail.com>,
	jhanschoo@gmail.com, emacs-devel@gnu.org
Subject: Re: [ELPA] New Package: greek-polytonic.el
Date: Mon, 16 Jul 2018 09:23:45 -0700	[thread overview]
Message-ID: <pxwhefg35eum.fsf@ccrusius.svl.corp.google.com> (raw)
In-Reply-To: <83pnzn8982.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Jul 2018 18:57:01 +0300")

[-- Attachment #1: Type: text/plain, Size: 2949 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Cesar Crusius <cesar.crusius@gmail.com> Cc: Cesar Crusius 
>> <cesar.crusius@gmail.com>,  jhanschoo@gmail.com, 
>> emacs-devel@gnu.org Date: Sat, 14 Jul 2018 18:37:23 -0700  
>> >>  I'm not sure what you mean by "want the decomposed 
>> >>  characters  
>> >> to appear in the text," but when I am writing polytonic 
>> >> Greek  and type the sequence above, all I want is to see an 
>> >> alpha+macron+acute in front of me.  
>> >  On display or in the buffer?  If on display, then Emacs 
>> > should  already do that, provided that the font you are using 
>> > supports  the composed characters.  That's because by default 
>> > we have the  auto-composition-mode turned on.    I was 
>> > talking about what's in the buffer.  I think that if the 
>> > user types a sequence of characters, Emacs should generally 
>> > put  those characters unaltered in the buffer.  If the user 
>> > wants a  precomposed character, she could always type that 
>> > character's  codepoint using "C-x 8 RET", no?    But maybe I 
>> > don't know enough about the expectations of users  who would 
>> > use greek-polytonic input method, maybe in some use  cases 
>> > such automatic composition in the buffer is expected? 
>>  Maybe we're talking about different things...   (snip) 
> 
> More accurately, input methods normally read ASCII characters 
> and produce non-ASCII characters, whether accented or not.  By 
> contrast, your original text: 
> 
>> For example, the sequence <alpha>+<combining macron>+<combining 
>> acute accent> is not represented by any precomposed character, 
>> but appears frequently in critical editions of 
>> classics. greek-polytonic.el allows for the input of combining 
>> characters themselves, and substitutes such sequences with 
>> their Unicode-canonical precomposed equivalents if they exist;

That's not mine, but the OP's text :)

> led me to believe that your input method takes three non-ASCII 
> characters, alpha combining macron and combining acute accent, 
> and produce from them a single composed character which is their 
> NFC precomposed character.  This is not what an input method 
> should do, IMO. 
> 
> However, I see now that no such NFC composition is being done 
> for non-ASCII input (right?), so I guess I misunderstood; sorry 
> about that.

No need to be sorry about anything -- wonders of written 
communication. I think we're on the same page now.

> (snip) 
> 
>> By the way, I'm all for greek.el supporting polytonic Greek 
>> natively and naturally. I don't remember what the problems 
>> were,  but I gave up on it quickly when trying polytonic 
>> because it  didn't work. 
> 
> I was talking about adding your input method to greek.el.

Not /my/ input method, I'm just encouraging the OP to think about 
making this an improvement to greek.el instead of a separate 
package, as you suggested in your first e-mail :)

Cheers,

-- 
Cesar Crusius

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]

  reply	other threads:[~2018-07-16 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-14  9:29 [ELPA] New Package: greek-polytonic.el Johannes Choo
2018-07-14 11:16 ` Eli Zaretskii
2018-07-14 17:11   ` Cesar Crusius
2018-07-14 18:32     ` Eli Zaretskii
2018-07-15  0:31       ` Richard Stallman
2018-07-15  1:37       ` Cesar Crusius
2018-07-16 15:57         ` Eli Zaretskii
2018-07-16 16:23           ` Cesar Crusius [this message]
2018-08-08 13:12             ` Johannes Choo

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=pxwhefg35eum.fsf@ccrusius.svl.corp.google.com \
    --to=cesar.crusius@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jhanschoo@gmail.com \
    /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).