From: Raman <tv.raman.tv@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacspeak and UTF-8 -- possible?
Date: Mon, 13 Aug 2007 14:47:09 -0700 [thread overview]
Message-ID: <1187041629.914642.48950@i38g2000prf.googlegroups.com> (raw)
In-Reply-To: <jwvzm0y7mrl.fsf-monnier+gnu.emacs.help@gnu.org>
>
>
> PS: How ironic that Emacspeak provides "the first really functional
> interface on Linux for [blind and] VI users".
;-) It actually was a first in helping blind users run VI
independently on a
workstation console --- thanks to the wonders of eterm.el in
Emacs 19.26 --- which for the first time made curses-based apps
runnable in an Emacs Term.
As for the character coding issues --- I forcibly set
EMACS_UNIBYTE to T in the Emacspeak setup files a few years ago
to make it clear that the UTF-8 piece needed work. Doing anything
else would just cause bizarre/rude surprizes half-way while one
is working.
Now, when you have a system like Emacs itself which attracts a
large number of developers, it is possible to enable something as
complex as character encoding and translation and over time debug
all of the issues --- we've seen this happen in the case of
mainline Emacs over the last 8 years. However, Emacspeak does not
have this luxury, and pretending that multibyte support works
when it doesn't would only lead to large amounts of frustration
and support questions of the form "why doesnt xxx ." on the
mailing list.
For the record, it should be possible to now add multibyte
support by carefully binding buffer-encoding in the scratch
buffer used to transform text and by setting process-encoding for
that buffer before streaming out the text to the TTS process. But
doing this will require:
A) Manpower Cycles(ramanpower cycles are vanishingly small for
this)
B) Ability to test --- TTS engines, multibyte texts, and
someone who uses it
C) Early users who are sufficiently knowledgeable to be able
to bear the pain, identify problems, and and define
solutions
--Raman
next prev parent reply other threads:[~2007-08-13 21:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 19:24 Emacspeak and UTF-8 -- possible? cmr.Pent
2007-08-07 10:41 ` Tim X
2007-08-08 9:09 ` cmr.Pent
2007-08-08 14:56 ` Stefan Monnier
2007-08-08 23:44 ` Robert D. Crawford
2007-08-09 17:44 ` Stefan Monnier
2007-08-10 7:40 ` Tim X
2007-08-10 5:39 ` Tim X
2007-08-10 9:23 ` grep-find question (Is it a bug of GunWin32 version of "grep") brianjiang
2007-08-10 14:07 ` Eli Zaretskii
2007-08-11 5:55 ` brianjiang
2007-08-11 7:06 ` brianjiang
2007-08-11 10:06 ` Eli Zaretskii
2007-08-12 9:58 ` brianjiang
2007-08-12 18:59 ` Eli Zaretskii
2007-08-10 5:27 ` Emacspeak and UTF-8 -- possible? Tim X
2007-08-11 4:02 ` Stefan Monnier
2007-08-13 21:47 ` Raman [this message]
2007-08-14 18:28 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187041629.914642.48950@i38g2000prf.googlegroups.com \
--to=tv.raman.tv@gmail.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.