From: arthur miller <arthur.miller@live.com>
To: Tim Cross <theophilusx@gmail.com>, Marcin Borkowski <mbork@mbork.pl>
Cc: Sam Qasbah <samqasbah@gmail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: Request for partecipating in the project
Date: Mon, 23 Dec 2019 01:50:50 +0000 [thread overview]
Message-ID: <VI1P194MB04290F651CC778AB3537E157962E0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAC=50j_3814GN3sTB=MfejM_v-6PuOmzTQ8O1X8gJ5e1KFdCUg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3307 bytes --]
Isn't epub developed to be electroncal version of printed books, so that electronicall books can keep same logical layout (chapters, paragraphs, pages, etc) as their physical counterparts? Probably not a deal breaker, but software documentation maybe is not really suitable for that kind of publishing.
I think Emacs help is great, but I really miss great overview over the API as found for example in javadoc.
When it comes to accessibility I am not sure if epub offers you that much more of accessibility options then you get from in html, but I might be wrong. Anyway there is a good guide on making information accessible to visually impaired people:
https://www.google.com/url?q=https://www.sabeusa.org/wp-content/uploads/2014/02/A-Guide-to-Making-Documents-Accessible-to-People-Who-are-Blind-or-Visually-Impaired.pdf&sa=U&ved=2ahUKEwjS-9e-0MrmAhWHlYsKHcJ9BZ0QFjACegQIBhAB&usg=AOvVaw3P809blo61Vmg1IzcMSZ6M
Just as a note.
Skickat från min Samsung Galaxy-smartphone.
-------- Originalmeddelande --------
Från: Tim Cross <theophilusx@gmail.com>
Datum: 2019-12-23 01:04 (GMT+01:00)
Till: Marcin Borkowski <mbork@mbork.pl>
Kopia: arthur miller <arthur.miller@live.com>, Sam Qasbah <samqasbah@gmail.com>, emacs-devel@gnu.org
Ämne: Re: Request for partecipating in the project
There is no single ebook-friendly format. Different ebook readers are better/worse with different formats (mobi, epub, etc). Therefore, we probably need to be a little more explicit when talking about ebook formats.
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. There are at least two packages I'm aware of which will allow epub formatted books to also be read directly in Emacs.
My experience with Calibre is that the quality of the output you get depends on both the quality of input (e.g. poorly structured or poorly tagged PDFs will result in poor conversion) and on the settings of Calibre itself (of which there is quite a lot). I'm not sure how well Emacs documentation will convert. My experience with PDFs generated from Latex is not good as Latex is very weak with respect to accessibility and generating modern tagged PDF documents.
On Mon, 23 Dec 2019 at 09:01, Marcin Borkowski <mbork@mbork.pl<mailto:mbork@mbork.pl>> wrote:
On 2019-12-22, at 22:38, arthur miller <arthur.miller@live.com<mailto:arthur.miller@live.com>> wrote:
> Skickat från min Samsung Galaxy-smartphone.
>
>
>> The ebook format allows you to consult the > manual with a smartphone, tablet or epub-> > reader.
>
> Both my smartphone and my tablet read Emacs manual perfectly fine in html format in browser, and I am sure if I wanted to read manuals in pdf format they would work perfectly fine too. What does epub brings that html or pdf does not? Personally I don't even like pdf.
AFAIK, ebook readers can render HTML, but work much better with
dediacted formats.
FWIW, I converted the Emacs manuals to an ebook-reader-friendly format
many years ago, and automatic conversion resulted in a very poor
experience. If someone volunteers to do a better job than Calibri, I'm
all for it!!!
Best,
--
Marcin Borkowski
http://mbork.pl
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 4842 bytes --]
next prev parent reply other threads:[~2019-12-23 1:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 21:38 Request for partecipating in the project arthur miller
2019-12-22 22:00 ` Marcin Borkowski
2019-12-23 0:03 ` Tim Cross
2019-12-23 1:50 ` arthur miller [this message]
2019-12-23 3:23 ` T.V Raman
2019-12-23 6:34 ` Mario Lang
2019-12-23 14:38 ` Tim Cross
-- strict thread matches above, loose matches on Subject: below --
2019-12-23 16:04 arthur miller
2019-12-23 16:43 ` Tim Cross
2019-12-23 17:19 ` T.V Raman
2019-12-22 22:32 arthur miller
2019-12-22 22:46 ` Marcin Borkowski
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=VI1P194MB04290F651CC778AB3537E157962E0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
--cc=samqasbah@gmail.com \
--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).