From: arthur miller <arthur.miller@live.com>
To: Tim Cross <theophilusx@gmail.com>, Mario Lang <mlang@blind.guru>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Request for partecipating in the project
Date: Mon, 23 Dec 2019 16:04:10 +0000 [thread overview]
Message-ID: <VI1P194MB042906EB2169CF060F52558C962E0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 1715 bytes --]
.
> epub is an HTML based format. Essentially it is an archive file of HTML and metadata.
XML, not html.
> So the issue isn't so much whether it is
> better than HTML but more about some of
> the tools available.
Might be that there are better applications for voice reading then Emacs, albeit I think that your target group is already reading Emacs manual in Emacspeak. I think I will try to set up Emacspeak for myself, have not done it yet.
Anyway, I hinted that epub might not be THE best format for a reference like API docs. I don't think that structure of chapters and especially pages are very good structure for electronic documents, especially not for API docs or references. Do you miss "page structure" on Wikipedia?
Emacs self documentation is good and being able to lookup stuff directly from within your Emacs is priceless, but sometimes I miss an easy overview of the api, for example when I can't remember name of a function or similar.
By the way, what kind of hardware does not have a web browser nowadays? Is not like online Emacs manual is full of javascript and other stuff on the edge of the web technology.
Skickat från min Samsung Galaxy-smartphone
On Mon, 23 Dec 2019 at 17:34, Mario Lang <mlang@blind.guru> wrote:
Tim Cross <theophilusx@gmail.com<mailto:theophilusx@gmail.com>> writes:
> One of the advantages of some ebook formats, such as epub, is that they can
> be more accessible for the blind and vision impaired than PDF or even HTML.
Please name an example where epub clearly is bettern then HTML.
I (a blind user) have never seen one until now.
--
CYa,
⡍⠁⠗⠊⠕
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 3125 bytes --]
next reply other threads:[~2019-12-23 16:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 16:04 arthur miller [this message]
2019-12-23 16:43 ` Request for partecipating in the project Tim Cross
2019-12-23 17:19 ` T.V Raman
-- strict thread matches above, loose matches on Subject: below --
2019-12-22 22:32 arthur miller
2019-12-22 22:46 ` Marcin Borkowski
2019-12-22 21:38 arthur miller
2019-12-22 22:00 ` Marcin Borkowski
2019-12-23 0:03 ` Tim Cross
2019-12-23 1:50 ` arthur miller
2019-12-23 3:23 ` T.V Raman
2019-12-23 6:34 ` Mario Lang
2019-12-23 14:38 ` Tim Cross
2019-12-22 17:23 Sam Qasbah
2019-12-24 4:13 ` Richard Stallman
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=VI1P194MB042906EB2169CF060F52558C962E0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=mlang@blind.guru \
--cc=theophilusx@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).