From: arthur miller <arthur.miller@live.com>
To: 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: Sun, 22 Dec 2019 22:32:34 +0000 [thread overview]
Message-ID: <VI1P194MB0429E5527B531648FDC7B2F1962F0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
> AFAIK, ebook readers can render HTML, but > work much better with
> dediacted formats.
You mean some special hardware, or you mean ordinary ebook apps?
On my tablet I just open online manual in Firefox. There is also manual in pdf format, can't device render pdfs?
Skickat från min Samsung Galaxy-smartphone.
-------- Originalmeddelande --------
Från: Marcin Borkowski <mbork@mbork.pl>
Datum: 2019-12-22 23:00 (GMT+01:00)
Till: arthur miller <arthur.miller@live.com>
Kopia: Sam Qasbah <samqasbah@gmail.com>, emacs-devel@gnu.org
Ämne: Re: Request for partecipating in the project
On 2019-12-22, at 22:38, arthur miller <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
[-- Attachment #2: Type: text/html, Size: 2488 bytes --]
next reply other threads:[~2019-12-22 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-22 22:32 arthur miller [this message]
2019-12-22 22:46 ` Request for partecipating in the project Marcin Borkowski
-- 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 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=VI1P194MB0429E5527B531648FDC7B2F1962F0@VI1P194MB0429.EURP194.PROD.OUTLOOK.COM \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
--cc=samqasbah@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).