ietf
[Top] [All Lists]

RFC 1345 as an input method (In reply to http://www.ietf.org/mail-archive/web/ietf/current/msg47588.html)

2008-04-02 22:57:54
·  To: IETF General Discussion Mailing List <ietf at ietf.org> 

·  Subject: RFC 1345 as an input method 

·  From: Mr Kim Sanders <Mr.Kim.Sanders at shaw.ca> 

·  Date: Wed, 2 Apr 2008 

·  Cc: John C Klensin <john-ietf at jck.com>;  <46D7B176.1040206 at 
alvestrand.no> 

·  In-reply-to:  Harald Alvestrand <harald at alvestrand.no> 

·  List-help: <mailto:ietf-request(_at_)ietf(_dot_)org?subject=help> 

·  List-id: IETF-Discussion <ietf.ietf.org> 

·  List-post: <mailto:ietf(_at_)ietf(_dot_)org> 

·  List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, 
<mailto:ietf-request(_at_)ietf(_dot_)org?subject=subscribe> 

·  List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, 
<mailto:ietf-request(_at_)ietf(_dot_)org?subject=unsubscribe> 

·  References: <873ay9ncf7(_dot_)fsf(_at_)benfinney(_dot_)id(_dot_)au> 
<001401c7e608$1fab5f00$6801a8c0(_at_)oemcomputer> 
<878x80l46v(_dot_)fsf(_at_)benfinney(_dot_)id(_dot_)au> 
<000401c7e6db$bb2774e0$6801a8c0(_at_)oemcomputer> 
<87bqcwi0nu(_dot_)fsf(_at_)benfinney(_dot_)id(_dot_)au> 
<003401c7e6e6$c4d97280$6801a8c0(_at_)oemcomputer> 
<877inkhxor(_dot_)fsf(_at_)benfinney(_dot_)id(_dot_)au> 
<003001c7e771$6b4911e0$6401a8c0(_at_)DGBP7M81> 
<87ps1bgi4r(_dot_)fsf(_at_)benfinney(_dot_)id(_dot_)au> 
<D28B0973-20A4-41E9-B0EF-D5D8A6C2C0B5(_at_)osafoundation(_dot_)org> 
<46D74C06(_dot_)10202(_at_)alvestrand(_dot_)no> 
<E19E81A74788C5BC950EFBFA(_at_)p3(_dot_)JCK(_dot_)COM> 
<46D7B176(_dot_)1040206(_at_)alvestrand(_dot_)no> 



It would appear to me that the answer regarding consistency among the input 
methods, especially in how the variable-length character mnemonic [shorthand]s 
are framed, is answered in http://rfc.net/rfc1345.html at the end of section 
2.4, part way down [Page 5].  I quote:—

      One prominent character in the reference character set is reserved

       for identifying variable-length mnemonics, namely the underline

       character "_". This character is intended as a delimiter both in the

       front and in the end of the mnemonic. An example of its use would be:

       (&=intro):

                   &_j3210_ &_j4436_&_j6530_
     



These mnemonic shorthands could logically be used in personal Word Processing 
programs for macros (thus speeding up the keying in of data) as well as in 
non-Unicode-based genealogy programs (which only allow decimal ALT-code entry 
for characters not seen on the keyboard).  Naturally, one could devise one's 
own system using mnemonic tables such as RFC 1345 for ideas.

  I personally am considering http://rfc.net/rfc1345.html (which appears to be 
used liberally in http://www.gloser.org/es/faq/shortcuts/ and 
http://www.eki.ee/letter/) along with other mnemonic layouts such as can be 
found at http://www.eki.ee/knab/kbdiakr.htm as well as more specialized sites 
like el_tigre's suggestion of 26 Jul 06 for Croatian at 
http://www.phrasebase.com/forum/read.php?action=print&TID=15844 and Vietnamese 
conventions (such as described at http://en.wikipedia.org/wiki/Telex_%28IME%29 
and http://en.wikipedia.org/wiki/VIQR).

    As to the matter of IMEs (such as EMACS and SCIM), I'll leave that aspect 
to those specializing in that type of IME.

_______________________________________________
IETF mailing list
IETF(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
<Prev in Thread] Current Thread [Next in Thread>
  • RFC 1345 as an input method (In reply to http://www.ietf.org/mail-archive/web/ietf/current/msg47588.html), Mr Kim Sanders <=