emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: CV in orgmode for export to pdf (and html?)
Date: Mon, 22 Sep 2014 10:30:12 +0200	[thread overview]
Message-ID: <m2tx405a7f.fsf@krugs.de> (raw)
In-Reply-To: <87zjdvdxkh.fsf@gmx.us> (rasmus@gmx.us's message of "Sat, 20 Sep 2014 01:01:34 +0200")

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

Rasmus <rasmus@gmx.us> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> Brady Trainor <algebrat@uw.edu> writes:
>>
>>> And I did have a decent export to LaTeX resume from org, but after 
>>> discovering moderncv, I've switched, though I will be curious to read 
>>> others' methods of org-to-moderncv export.
>>
>> One option could be to define a specialized latex back-end dedicated to
>> moderncv class, much like "ox-koma-letter.el" does for "scrlttr2".
>
> You can even do it all on the LaTeX side, e.g. redefining description
> (or using ¤+ATTR_LATEX) to make use of the description form
>
>     "- year :: item"
>
> Together with rebinding the title-command it should be pretty easy to
> make a CV.

I am not a LaTeX expert, so could you please elaborate a bit on this, as
it sounds like a reasonable approach, and also relatively easy to
implement?

Rainer

>
> I never worked the LaTeX CV classes as I did not care for their
> default looks, but it's very easy to use KOMA for CVs.
>
> —Rasmus

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]

  reply	other threads:[~2014-09-22  8:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19  9:18 CV in orgmode for export to pdf (and html?) Rainer M Krug
2014-09-19 10:10 ` Tory S. Anderson
2014-09-19 10:29   ` Andreas Kiermeier
2014-09-19 15:06     ` John Hendy
2014-09-19 17:15       ` Tory S. Anderson
2014-09-22  8:24         ` Rainer M Krug
2014-10-29 19:35   ` Karl Voit
2014-09-19 15:38 ` Dan Griswold
2014-09-19 19:52 ` Brady Trainor
2014-09-19 20:18   ` Nicolas Goaziou
2014-09-19 23:01     ` Rasmus
2014-09-22  8:30       ` Rainer M Krug [this message]
2014-09-21 19:59     ` Myles English
2014-09-22  8:31       ` Rainer M Krug
2014-09-22 21:37       ` Myles English
2014-09-23  6:56         ` Rainer M Krug
2014-09-22  8:28   ` Rainer M Krug
2014-09-20  0:49 ` Dan Griswold
2014-09-20  5:56   ` Vikas Rawal
2014-09-22  8:32     ` Rainer M Krug
2014-09-20  6:36   ` Joseph Vidal-Rosset
2014-09-22  8:32     ` Rainer M Krug
2014-09-22  8:23   ` CV in orgmode for export to pdf (and html? Rainer M Krug
2014-09-22 11:55     ` Nick Dokos
2014-09-23  9:06     ` Rasmus
     [not found]     ` <87fvfihfh8.fsf@gmx.us>
2014-09-23  9:24       ` Rainer M Krug
2014-09-20  7:45 ` CV in orgmode for export to pdf (and html?) Xavier Garrido
2014-09-22  8:33   ` Rainer M Krug

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=m2tx405a7f.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).