ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "amano.kenji via ntg-context" <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "amano.kenji" <amano.kenji@proton.me>
Subject: Re: How can I design a book cover with front cover, back cover, and spine?
Date: Tue, 06 Sep 2022 11:15:07 +0000	[thread overview]
Message-ID: <qjPjlLwhMUTAoMPt4N0-2KPHFVoM5P3GREja3Hhjy27-_rOsaTPXrfdM2w1W_lhhaxRIixe4rjhyZWNsDWn3AXy3Cu_UP3hSRqTrL7Ac9VQ=@proton.me> (raw)
In-Reply-To: <b22c1107-dffa-695c-eba6-741daabab3eb@fiee.net>

Is it a good idea to design a book cover with front cover, back cover, and spine in ConTeXt? Or, is there a better software for designing book cover?

Do print shops just accept a book cover design as a PDF file which can be created by anything including ConTeXt?

Is it a good idea to set left margin and right margin differently for digitally distributed PDFs? Digital PDFs don't need different margins on the left and the right, but a digital PDF with different margins on the left and the right can be used in a physical book.

------- Original Message -------
On Tuesday, September 6th, 2022 at 9:50 AM, Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:


> Am 06.09.22 um 10:20 schrieb amano.kenji via ntg-context:
> 
> > Let's assume that I'm writing an A4 book.
> > 
> > How can I design front cover, spine, and back cover of the book with ConTeXt?
> > 
> > I've read many PDF files, but none that I can remember actually had book spine on it. Some had back cover. Most had front cover.
> > 
> > Do printing houses make spine and back cover for authors so that back cover and spine don't need to be typeset by LaTeX or ConTeXt?
> 
> 
> No, they don’t, you must provide an extra PDF in the right size.
> Often, printshops provide a template.
> 
> If I don’t have a design that goes over the spine, I use a cover.tex
> that imports front and back of my main PDF and just add the spine text.
> Everything placed on a layer.
> This way, my main PDF contains everything except the spine – makes sense
> for proofreading or digital distribution.
> 
> Spine width depends mostly on page number and paper weight (thickness),
> but also on the binding technology used – ask your printshop.
> 
> Hraban
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2022-09-06 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  8:20 amano.kenji via ntg-context
2022-09-06  8:29 ` Marcus Vinicius Mesquita via ntg-context
2022-09-06  9:50 ` Henning Hraban Ramm via ntg-context
2022-09-06 11:15   ` amano.kenji via ntg-context [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='qjPjlLwhMUTAoMPt4N0-2KPHFVoM5P3GREja3Hhjy27-_rOsaTPXrfdM2w1W_lhhaxRIixe4rjhyZWNsDWn3AXy3Cu_UP3hSRqTrL7Ac9VQ=@proton.me' \
    --to=ntg-context@ntg.nl \
    --cc=amano.kenji@proton.me \
    /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.
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 NNTP newsgroup(s).