unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: dalanicolai <dalanicolai@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] add epub support to doc-view
Date: Wed, 26 Jan 2022 21:28:55 +0100	[thread overview]
Message-ID: <CACJP=3=DG3k5h2Rfpii9Z=Dpx2B=f2-6o9wqdmufio2EdCQkYw@mail.gmail.com> (raw)
In-Reply-To: <CACJP=3mmKOy4zVmZmDBRMSft7d3PTUYaTkucjMwTVH2TKWg8uw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Just a gentle reminder, because I am not sure if you have seen this.
I think this patch is more or less ready for merging (all previous feedback
 has been processed, and it is only a small patch).
Otherwise... no pressure, just checking

On Fri, 14 Jan 2022 at 21:02, dalanicolai <dalanicolai@gmail.com> wrote:

> And another, updated, patch, adding an extra option to configure the epub
> font-size
>
> On Fri, 14 Jan 2022 at 17:15, dalanicolai <dalanicolai@gmail.com> wrote:
>
>> So here is a second version of the patch. But it adds a few more
>> extensions to the list
>> I forgot about them, as I don't use or experimented with them, but I
>> figured that
>> this is a good opportunity to add the support for those extensions also.
>> A small comment for those who are interested, the CBZ (and by mupdf
>> unsupported CBR)
>> files seem to be just zipped/rarred collections of image files (I guess
>> usually png/jpg). So
>> supporting those extensions doesn't really require the `mutool` command
>> if emacs would
>> just uncompress the collections.
>>
>> I guess there is not much more to comment on in addition to the comments
>> within the patch/files.
>>
>

[-- Attachment #2: Type: text/html, Size: 1888 bytes --]

  reply	other threads:[~2022-01-26 20:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  2:20 [PATCH] add epub support to doc-view dalanicolai
2022-01-11  2:32 ` Po Lu
2022-01-11  9:34   ` dalanicolai
2022-01-11  9:50     ` Tassilo Horn
2022-01-11 10:04       ` dalanicolai
2022-01-11 10:08         ` dalanicolai
2022-01-11 10:15         ` Robert Pluim
2022-01-11  9:59     ` Robert Pluim
2022-01-11 10:09       ` dalanicolai
2022-01-11  2:48 ` Stefan Monnier
2022-01-11  3:30   ` Stefan Kangas
2022-01-11 10:01     ` dalanicolai
2022-01-11 10:16       ` Robert Pluim
2022-01-13  9:14         ` dalanicolai
2022-01-11  9:59   ` dalanicolai
2022-01-11 10:13     ` dalanicolai
2022-01-11 14:39     ` Stefan Monnier
2022-01-13  9:25       ` dalanicolai
2022-01-14 16:15         ` dalanicolai
2022-01-14 20:02           ` dalanicolai
2022-01-26 20:28             ` dalanicolai [this message]
2022-01-27 16:05               ` Lars Ingebrigtsen
2022-01-27 21:09                 ` Iñigo Serna
2022-01-28 13:47                   ` Lars Ingebrigtsen
2022-01-28 19:51                     ` Iñigo Serna
2022-01-29 17:07                 ` dalanicolai

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='CACJP=3=DG3k5h2Rfpii9Z=Dpx2B=f2-6o9wqdmufio2EdCQkYw@mail.gmail.com' \
    --to=dalanicolai@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).