From: ohki@gssm.otsuka.tsukuba.ac.jp
To: Eli Zaretskii <eliz@gnu.org>
Cc: Atsuo Ohki <ohki@gssm.otsuka.tsukuba.ac.jp>, 22815@debbugs.gnu.org
Subject: bug#22815: 25.0.91; emacs-module.*
Date: Fri, 26 Feb 2016 18:16:05 +0900 [thread overview]
Message-ID: <5098.1456478165@smr00> (raw)
In-Reply-To: Your message of "Fri, 26 Feb 2016 11:10:57 +0200" <83lh67et0e.fsf@gnu.org>
Eli Zaretskii writes:
> > From: Atsuo Ohki <ohki@gssm.otsuka.tsukuba.ac.jp>
> > Date: Fri, 26 Feb 2016 16:28:09 +0900
> >
> > This is not a bug report, but feature enhancemnt for emacs-module.*
> >
> > API of emacs-module has two Lisp string related functions,
> > `copy_string_contents' and `make_string'.
> > Those functions assume UTF-8 encoded strings,
> > but it becomes flexible if a user can specify a specific encoding.
>
> Thanks.
>
> But why cannot the module convert the string to UTF-8 before passing
> it to Emacs?
>
Because, an external module could use a coding system other then UTF-8.
I have used emacs-module capability to plugin CANNA server interface
(CANNA server is a rather out of dated KANA-KANJI converter for japanese),
and CANNA server uses euc-jp encoding for communication.
next prev parent reply other threads:[~2016-02-26 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 7:28 bug#22815: 25.0.91; emacs-module.* Atsuo Ohki
2016-02-26 9:10 ` Eli Zaretskii
2016-02-26 9:16 ` ohki [this message]
2016-02-26 9:46 ` Eli Zaretskii
2016-02-26 10:09 ` ohki
2016-02-26 18:26 ` Eli Zaretskii
2016-02-26 23:21 ` ohki
2016-02-27 8:19 ` Eli Zaretskii
2016-03-29 10:05 ` Philipp Stephani
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=5098.1456478165@smr00 \
--to=ohki@gssm.otsuka.tsukuba.ac.jp \
--cc=22815@debbugs.gnu.org \
--cc=eliz@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).