From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: CV in orgmode for export to pdf (and html?
Date: Tue, 23 Sep 2014 11:24:18 +0200 [thread overview]
Message-ID: <m2iokeelkt.fsf@krugs.de> (raw)
In-Reply-To: 87fvfihfh8.fsf@gmx.us
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
Rasmus <rasmus@gmx.us> writes:
> Hi,
>
> Rainer M Krug <Rainer@krugs.de> writes:
>
> Thanks for the summary Rainer.
Hope I didn't forget anything...
>
>> I think that org could be a perfect environment for building CVs if
>> one could come up with an HOWTO and many examples how to do it - and I
>> think this is going into the right direction.
>
> I think the "right" approach is cooking up a reasonable way to
> represent CVs and make an ox-cv with a customized interface (like
> ox-koma-letter where ordering of blocks can also be changed
> "on-the-go") and provide some nice default "themes". It should either
> build on an established LaTeX cv package or just KOMA-Script like
> Xavier's CV (and mine). I didn't check the ox-cv.el that was posted
> carefully.
Yes - this might be the most "org-ish" approach, and the most stable
(over time).
>
> That being said, I don't have much time for this right now.
Isn't there a worg / org page, where these ideas are collected (TODO?
Feature Requests, ...)? I fear that this becomes forgotten again
(including myself!), as CVs are not something one uses regularly...
I unfortunately have not the elisp knowledge to contribute much here.
>
> It would be nicer to handle something like a CV in org than LaTeX.
I completely agree with you - I have it at the moment in LyX, but I am
fixing issues each time I need a CV.
Cheers,
Rainer
>
> Cheers,
> Rasmus
--
Rainer M. Krug
PGP: 0x0F52F982
[-- Attachment #2: Type: application/pgp-signature, Size: 494 bytes --]
next prev parent reply other threads:[~2014-09-23 9:25 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
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 [this message]
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=m2iokeelkt.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@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 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).