emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Grant Rettke <gcr@wisdomandwonder.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Bastien <bzg@gnu.org>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Patch adding from-logo commentary ox-koma-letter.el
Date: Sat, 23 Jun 2018 20:32:14 -0500	[thread overview]
Message-ID: <CAAjq1mf-VXwzoRmvWRE331Q3gwdvY-FBnHQ-h+4B_2q3C9ZK1g@mail.gmail.com> (raw)
In-Reply-To: <8736xgeb0j.fsf@nicolasgoaziou.fr>

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

On Thu, Jun 21, 2018 at 4:37 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Grant Rettke <gcr@wisdomandwonder.com> writes:
>> If you like the additional documentation, then I will update it with
>> this and send a new patch.
>
> Let's first merge the complete documentation, then apply it, if you
> don't mind.

Happy to, mistakenly said patch.

Here is the new version. I included detail and examples.

The first one I sent was, well, woefully inadequate!

[-- Attachment #2: 0001-ox-koma-letter.el-Adds-FROM_LOGO-example.patch --]
[-- Type: application/octet-stream, Size: 2991 bytes --]

From b12a9f806cfc218bee2cfff1e550341f5999c70d Mon Sep 17 00:00:00 2001
From: Grant Rettke <gcr@wisdomandwonder.com>
Date: Sat, 23 Jun 2018 20:08:09 -0500
Subject: [PATCH] ox-koma-letter.el: Adds FROM_LOGO example

FROM_LOGO uses LaTeX markup probably unfamiliar to the user.

This example provides detailed documentation and examples of it's use.
---
 contrib/lisp/ox-koma-letter.el | 37 ++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)

diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 37ea4d04c..77dc4ccac 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -77,6 +77,43 @@
 ;;     (See also `org-koma-letter-author'),
 ;;   - EMAIL: Same as AUTHOR. (see also `org-koma-letter-email'),
 ;;
+;; Unlike other variables, FROM_LOGO uses LaTeX markup. FROM_LOGO
+;; provides the 'includegraphics' command to tell LaTeX where to find
+;; the logo. 'includegraphics' needs to know the logo's directory and
+;; file name. The directory can either be relative or absolute, just
+;; as you would expect. LaTeX can use three file types for the logo:
+;; PDF, JPEG, or PNG. The logo can either include or exclude its
+;; extension, which might surprise you. When you exclude its
+;; extension, LaTeX will search the directory for the "best" quality
+;; graphics format. For example if it finds both logo.pdf and logo.png
+;; then it will identify the PDF as "better", and include
+;; logo.pdf. This can be useful, for example, when you are mocking up
+;; a logo in the PNG raster format and then switch over to the higher
+;; quality PDF vector format. When you include the file extension then
+;; LaTeX will include it without searching for higher quality file
+;; types. Whatever file type you choose, it will probably require a
+;; few design iterations to get the best looking logo size for your
+;; letter. Finally, the directory and file name are specified
+;; *without* quotes. Here are some examples with commentary, in the
+;; location of your letter, with a logo named 'logo', to get you
+;; started:
+;;
+;;   Logo in the same directory: \includegraphics{logo}
+;;       or a sub-directory:     \includegraphics{logos/production/logo}
+;;
+;;   Logos specified using absolute paths on Linux or Windows:
+;;
+;;       \includegraphics{/Users/you/correspondence/logo}
+;;       \includegraphics{/Users/you/correspondence/logos/production/logo}
+;;       \includegraphics{c:/you/correspondence/correspondence/logo}
+;;       \includegraphics{c:/you/correspondence/correspondence/logos/production/logo}
+;;
+;;   Logos in the same directory where the "better" quality PDF will
+;;   be chosen over the JPG:
+;;
+;;       \includegraphics{logo.pdf}
+;;       \includegraphics{logo.png}
+;;
 ;; Headlines are in general ignored.  However, headlines with special
 ;; tags can be used for specified contents like postscript (ps),
 ;; carbon copy (cc), enclosures (encl) and code to be inserted after
-- 
2.18.0


  reply	other threads:[~2018-06-24  1:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 17:27 Patch adding from-logo commentary ox-koma-letter.el Grant Rettke
2018-06-19  8:11 ` Nicolas Goaziou
2018-06-20 22:38   ` Grant Rettke
2018-06-21  3:40     ` Van L
2018-06-21  9:37     ` Nicolas Goaziou
2018-06-24  1:32       ` Grant Rettke [this message]
2018-06-27 14:28         ` Nicolas Goaziou
2018-06-28 16:03           ` Grant Rettke

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAAjq1mf-VXwzoRmvWRE331Q3gwdvY-FBnHQ-h+4B_2q3C9ZK1g@mail.gmail.com \
    --to=gcr@wisdomandwonder.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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/org-mode.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).