From: "Dušan Xmetov" <merkur32@gmail.com>
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/3] gnu: Add mupdf
Date: Mon, 15 Sep 2014 07:20:35 +0200 [thread overview]
Message-ID: <CAN=wXfA4HWZ1YyBm83VUej0YVAxVLL1cbsGVLbfohQC89xtp8g@mail.gmail.com> (raw)
In-Reply-To: <874mw95vi4.fsf@gmail.com>
On 9/15/14, Alex Kost <alezost@gmail.com> wrote:
> Hello, I don't have real comments, I just noticed a couple of typos.
Thanks :)
>>
>> * gnu/packages/pdf.scm (mupdf): New variable.
>> * gnu/packages/patches/mupdf-buildsystem-fix.patch: New vile.
>
> New file.
>
Yup.
>
> 5 * trailing space.
>
They were generated by diff, won't removing them break the patch?
>
>> + (inputs
>> + `(("curl" ,curl)
>> + ("freetype", freetype)
>
> ("freetype" ,freetype)
>
Yup.
>
>> + (synopsis "A lightweight PDF viewer and toolkit.")
>> + (description
>> + "MuPDF is a C library that implements a PDF and XPS parsing and
>> rendering
>> +engine. It is used primarily to render pages into bitmaps, but also
>> provides
>> +support for other operations such as searching and listing the table of
>> +contents and hyperlinks.
>> +
>> +The library ships with a rudimentary X11 viewer, and a set of command
>> line tools
>> +for batch rendering (pdfdraw), examining the file structure (pdfshow),
>> and
>> +rewriting files (pdfclean).")
>> + (license license:agpl3+)))
>
> I think people usually avoid a period in a synopsis and use a double
> space after a period in a description. Also the description should be
> wrapped by 72 (or 78?) characters in a line.
Yup. Thanks for the reply, I'll try to fix the patch, but I don't know
about the trailing spaces, I kind of don't want to touch diff's
output.
next prev parent reply other threads:[~2014-09-15 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 9:15 [PATCH 3/3] gnu: Add mupdf Dušan Xmetov
2014-09-15 4:59 ` Alex Kost
2014-09-15 5:20 ` Dušan Xmetov [this message]
2014-09-15 6:52 ` Ludovic Courtès
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='CAN=wXfA4HWZ1YyBm83VUej0YVAxVLL1cbsGVLbfohQC89xtp8g@mail.gmail.com' \
--to=merkur32@gmail.com \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.