Re: http://epubmaker.pglaf.org/

Walt Farrell <[email protected]> Fri, 26 Apr 2019 20:49:06 -0400
Newsgroups gmane.culture.literature.e-books.gutenberg.volunteers
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============3476103734913081513==
Content-Type: multipart/alternative;
 boundary="------------E62F2FDA9446686269619BF1"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------E62F2FDA9446686269619BF1
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 4/26/2019 7:42 PM, Rick Tonsing wrote:
> Is http://epubmaker.pglaf.org the same app the White Washers use for 
> uploaded files?
>
> Some people at Distributed Proofreaders think the results are 
> different between the http://epubmaker.pglaf.org/ results and the WW 
> results published at PG.  I don't believe it but thought I'd ask here 
> before submitting an opinion to the DP forum.
>
> Specifically what they are claiming is that the oversized image 
> (greater than 800 x 1200px or 128KB) reduction for the epub and mobi 
> formats is different.

I can't answer the question, but as I recall the discussion it was about 
whether out-of-line (linked) images are included in the epub and mobi 
output files, not whether large images are reduced in size when included.

That is, some are saying that when the text includes a small image, 
which is linked to a larger version that the user can click on in a web 
browser, the epub/mobi files do not contain the larger images at all; 
only the smaller in-line ones. Others are saying the files contain both. 
And some are contending that it's different when we use 
ebookmaker.pglaf.org to generate the files, vs whatever the White 
Washers are doing to generate them.

But they are also talking about two different situations. One with the 
linked files, and another where @media queries are used to simply hide 
one file or the other depending on whether we're in a browser or in the 
epub/mobi version.

So it's really very confusing, to me.

-- 
Walt


--------------E62F2FDA9446686269619BF1
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 4/26/2019 7:42 PM, Rick Tonsing
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAA5S-6aX5uVyuKsUc4UcSSvOyz711SYn4seM7EmmJKtDGkMMfw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div dir="ltr">
          <div dir="ltr">
            <div dir="ltr">
              <div class="gmail_default"
                style="font-family:georgia,serif;font-size:large">Is <a
                  href="http://epubmaker.pglaf.org" target="_blank"
                  moz-do-not-send="true">http://epubmaker.pglaf.org</a>
                the same app the White Washers use for uploaded files? 
                <br>
              </div>
              <div class="gmail_default"
                style="font-family:georgia,serif;font-size:large"><br>
              </div>
              <div class="gmail_default"
                style="font-family:georgia,serif;font-size:large">Some
                people at Distributed Proofreaders think the results are
                different between the <a
                  href="http://epubmaker.pglaf.org/" target="_blank"
                  moz-do-not-send="true">http://epubmaker.pglaf.org/</a>
                results and the WW results published at PG.  I don't
                believe it but thought I'd ask here before submitting an
                opinion to the DP forum.</div>
              <div class="gmail_default"
                style="font-family:georgia,serif;font-size:large"><br>
              </div>
              <div class="gmail_default"
                style="font-family:georgia,serif;font-size:large">Specifically
                what they are claiming is that the oversized image
                (greater than 800 x 1200px or 128KB) reduction for the
                epub and <span class="gmail-gr_ gmail-gr_116
                  gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards
                  gmail-gr_disable_anim_appear gmail-ContextualSpelling"
                  id="gmail-116"><span class="gmail-gr_ gmail-gr_178
                    gmail-gr-alert gmail-gr_spell gmail-gr_inline_cards
                    gmail-gr_run_anim gmail-ContextualSpelling"
                    id="gmail-178">mobi</span></span> formats is
                different.</div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <p>I can't answer the question, but as I recall the discussion it
      was about whether out-of-line (linked) images are included in the
      epub and mobi output files, not whether large images are reduced
      in size when included.<br>
    </p>
    <p>That is, some are saying that when the text includes a small
      image, which is linked to a larger version that the user can click
      on in a web browser, the epub/mobi files do not contain the larger
      images at all; only the smaller in-line ones. Others are saying
      the files contain both. And some are contending that it's
      different when we use ebookmaker.pglaf.org to generate the files,
      vs whatever the White Washers are doing to generate them.</p>
    <p>But they are also talking about two different situations. One
      with the linked files, and another where @media queries are used
      to simply hide one file or the other depending on whether we're in
      a browser or in the epub/mobi version.</p>
    <p>So it's really very confusing, to me.<br>
    </p>
    <p>-- <br>
      Walt<br>
    </p>
  </body>
</html>

--------------E62F2FDA9446686269619BF1--

--===============3476103734913081513==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZ3V0dm9sLWQg
bWFpbGluZyBsaXN0Cmd1dHZvbC1kQGxpc3RzLnBnbGFmLm9yZwpodHRwOi8vbGlzdHMucGdsYWYu
b3JnL21haWxtYW4vbGlzdGluZm8vZ3V0dm9sLWQKVW5zdWJzY3JpYmU6IGh0dHA6Ly9saXN0cy5w
Z2xhZi5vcmcvbWFpbG1hbi9vcHRpb25zL2d1dHZvbC1k

--===============3476103734913081513==--