First of all, thanks to everybody so far who responded to this question. I reply to my question directly, as I am trying to sum up the replies so far (the complete thread is theoretically below).
There are effectively two "schools", - using LaTeX (Tory, Andreas, John and Brady), and - using org (Dan, Myles(?) and Xavier) The reasons for using LaTeX directly were mainly the simplicity of using LaTeX directly instead of telling org how to export to the format wanted, while the reasons for using org were simplicity of editing in org and the export to different formats (apart from pdf also html). I will not go further into the LaTeX as there is a vast amount of info available on the Internets. My reasoning why I want to use org instead of LaTeX is the same as mentioned in the thread, which is the simplicity of editing in org. In addition, I like the different backends, and that the actual content is separated from the export. I like Dan's approach as it looks relatively simple, although I still have to look into it in detail (and as Joseph notes, there must be a problem in the code). Xavier's approach looks *very* impressive. I like the pdf, and I am seriously thinking of using it, but my problem is the complexity - if it breaks, I have no idea where to fix it. But as the original CV is in org, the data would be there and I simply have to change the export / publishing. So what am I going to do? I think I will start entering the CV into org and then use Xavier's or Dan's approach and then see if I can get a layout I like. I like the idea of Rasmus to re-define the description environment, and I might also play with this. 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. So thanks a lot everybody for their input so far and keep the comments and ideas flowing. Rainer torys.ander...@gmail.com (Tory S. Anderson) writes: > I do mine in LaTeX and haven't had a reason to change that. I keep a > "Master" CV/resumé with all the gratuitous information in all > categories, then make subdirs for each submission and the trimmed-down > versions of my resume that I sent out. At this stage in my > career–where I am still tailoring resumés to employers and not really > keeping a no-holds-barred CV— this is the best workflow I've > found. I'm not sure how I'd go about versioning, trimming, and > tracking things as neatly in an all-org environment. > > I'm presuming you just want a full-disclosure CV, though? Org makes more > sense there. > > Rainer M Krug <rai...@krugs.de> writes: > >> Hi >> >> I am looking for examples / templates for CVs written using org, as I >> decided to ose org for my CV. >> >> I fund this oldish conversation >> >> http://lists.gnu.org/archive/html/emacs-orgmode/2012-04/msg00096.html >> >> and these two templates for using org to write a CV: >> >> https://github.com/punchagan/resume >> https://github.com/fasheng/fsh-orgmode-latex-cv >> >> as well this CV without .org file >> >> http://adamsonj.ninth.su/cv.html >> >> Also, there does not seem to be anything on worg. >> >> - Can somebody give any further info on org and CVs? >> - How do you do it (I don't assume you write your CVs in Word?), or are >> you using LaTeX directly? >> - Any other examples and templates online? >> >> If I get enough, I will compile a summary for worg, but I need examples >> and information. >> >> Thanks, >> >> Rainer > > Andreas Kiermeier <andreas.kierme...@gmail.com> writes: > Hi Rainer, > > like Tory I prepare my CV using latex directly. I've been using > "moderncv" for several years now and have been quite happy with it > (though that was before I've started using org). But even now, I can't > see how using org, would add to what I already have. > > Mind you, I tend to add to my CV (mainly publications and experience) > and revise it when needed, rather than adapt it to different > situations. > > Cheers, > > Andreas > > > > On 19 September 2014 19:40, Tory S. Anderson <torys.ander...@gmail.com> wrote: >> I do mine in LaTeX and haven't had a reason to change that. I keep a >> "Master" CV/resumé with all the gratuitous information in all >> categories, then make subdirs for each submission and the >> trimmed-down versions of my resume that I sent out. At this stage in >> my career–where I am still tailoring resumés to employers and not >> really keeping a no-holds-barred CV— this is the best workflow I've >> found. I'm not sure how I'd go about versioning, trimming, and >> tracking things as neatly in an all-org environment. >> >> I'm presuming you just want a full-disclosure CV, though? Org makes more >> sense there. >> >> Rainer M Krug <rai...@krugs.de> writes: >> >>> Hi >>> >>> I am looking for examples / templates for CVs written using org, as I >>> decided to ose org for my CV. > > John Hendy <jw.he...@gmail.com> writes: > Like the rest, I picked straight LaTeX, as it just felt like forcing Org to > do something unnatural, in my opinion. At least, if you get into any sort > of formatting stuff, it just didn't feel right. Here's some other mailing > list discussions if you haven't run into them: > - https://www.mail-archive.com/emacs-orgmode@gnu.org/msg37000.html > - http://web.archiveorange.com/archive/v/Fv8aAUnm6O4rHfVY6k0p > > And a github repo: > - https://github.com/fasheng/fsh-orgmode-latex-cv > > I still have a bookmarks folder in Chromium from when I was hunting around. > Here are the ones that, apparently, I found worth to make the Ctrl+D cut > for future reference if you're interested > - > http://linux.dsplabs.com.au/resume-writing-example-latex-template-linux-curriculum-vitae-professional-cv-layout-format-text-p54/ > - http://www.latextemplates.com/templates/curriculum_vitaes/6/cv_6.tex > - http://jblevins.org/projects/cv-template/ > - http://nitens.org/taraborelli/cvtex > > I haven't updated mine since 2011, when I updated it for my current job. I > went with an internal CV so that I could list accomplishments that would be > considered confidential (patent applications, internal reports, etc.). I > did create a dummy version, which I've attached (tex/pdf). Re-looking at > it, I can't decide if I still like it or not. At the time, I was really > happy with it as my first LaTeX CV :) I'd also probably consider it a > hybrid CV/resume -- I liked describe some of my previous job > responsibilities, while including papers/presentations/etc. > > > Good luck! > John > > > On Fri, Sep 19, 2014 at 5:29 AM, Andreas Kiermeier < > andreas.kierme...@gmail.com> wrote: > >> Hi Rainer, >> >> like Tory I prepare my CV using latex directly. I've been using >> "moderncv" for several years now and have been quite happy with it >> (though that was before I've started using org). But even now, I can't >> see how using org, would add to what I already have. >> >> Mind you, I tend to add to my CV (mainly publications and experience) >> and revise it when needed, rather than adapt it to different >> situations. >> >> Cheers, >> >> Andreas >> >> >> >> On 19 September 2014 19:40, Tory S. Anderson <torys.ander...@gmail.com> >> wrote: >> > I do mine in LaTeX and haven't had a reason to change that. I keep a >> "Master" CV/resumé with all the gratuitous information in all categories, >> then make subdirs for each submission and the trimmed-down versions of my >> resume that I sent out. At this stage in my career–where I am still >> tailoring resumés to employers and not really keeping a no-holds-barred CV— >> this is the best workflow I've found. I'm not sure how I'd go about >> versioning, trimming, and tracking things as neatly in an all-org >> environment. >> > >> > I'm presuming you just want a full-disclosure CV, though? Org makes more >> sense there. >> > >> > Rainer M Krug <rai...@krugs.de> writes: >> > >> >> Hi >> >> >> >> I am looking for examples / templates for CVs written using org, as I >> >> decided to ose org for my CV. >> >> > > torys.ander...@gmail.com (Tory S. Anderson) writes: > Very nice, John. Thanks for sharing the LaTeX! > > John Hendy <jw.he...@gmail.com> writes: > >> Like the rest, I picked straight LaTeX, as it just felt like forcing Org to >> do something unnatural, in my opinion. At least, if you get into any sort >> of formatting stuff, it just didn't feel right. Here's some other mailing >> list discussions if you haven't run into them: >> - https://www.mail-archive.com/emacs-orgmode@gnu.org/msg37000.html >> - http://web.archiveorange.com/archive/v/Fv8aAUnm6O4rHfVY6k0p >> >> And a github repo: >> - https://github.com/fasheng/fsh-orgmode-latex-cv >> >> I still have a bookmarks folder in Chromium from when I was hunting around. >> Here are the ones that, apparently, I found worth to make the Ctrl+D cut >> for future reference if you're interested >> - >> http://linux.dsplabs.com.au/resume-writing-example-latex-template-linux-curriculum-vitae-professional-cv-layout-format-text-p54/ >> - http://www.latextemplates.com/templates/curriculum_vitaes/6/cv_6.tex >> - http://jblevins.org/projects/cv-template/ >> - http://nitens.org/taraborelli/cvtex >> >> I haven't updated mine since 2011, when I updated it for my current job. I >> went with an internal CV so that I could list accomplishments that would be >> considered confidential (patent applications, internal reports, etc.). I >> did create a dummy version, which I've attached (tex/pdf). Re-looking at >> it, I can't decide if I still like it or not. At the time, I was really >> happy with it as my first LaTeX CV :) I'd also probably consider it a >> hybrid CV/resume -- I liked describe some of my previous job >> responsibilities, while including papers/presentations/etc. >> >> >> Good luck! >> John >> >> >> On Fri, Sep 19, 2014 at 5:29 AM, Andreas Kiermeier < >> andreas.kierme...@gmail.com> wrote: >> >>> Hi Rainer, >>> >>> like Tory I prepare my CV using latex directly. I've been using >>> "moderncv" for several years now and have been quite happy with it >>> (though that was before I've started using org). But even now, I can't >>> see how using org, would add to what I already have. >>> >>> Mind you, I tend to add to my CV (mainly publications and experience) >>> and revise it when needed, rather than adapt it to different >>> situations. >>> >>> Cheers, >>> >>> Andreas >>> >>> >>> >>> On 19 September 2014 19:40, Tory S. Anderson <torys.ander...@gmail.com> >>> wrote: >>> > I do mine in LaTeX and haven't had a reason to change that. I keep a >>> "Master" CV/resumé with all the gratuitous information in all categories, >>> then make subdirs for each submission and the trimmed-down versions of my >>> resume that I sent out. At this stage in my career–where I am still >>> tailoring resumés to employers and not really keeping a no-holds-barred CV— >>> this is the best workflow I've found. I'm not sure how I'd go about >>> versioning, trimming, and tracking things as neatly in an all-org >>> environment. >>> > >>> > I'm presuming you just want a full-disclosure CV, though? Org makes more >>> sense there. >>> > >>> > Rainer M Krug <rai...@krugs.de> writes: >>> > >>> >> Hi >>> >> >>> >> I am looking for examples / templates for CVs written using org, as I >>> >> decided to ose org for my CV. >>> >>> > > Dan Griswold <dgris...@rochester.rr.com> writes: > Unlike the others, I moved my CV from LaTeX to org-mode and I'm happy with > the results. Two things make it work well. > > First, a "cv" class added to org-latex-classes: > > (add-to-list '("cv" > "\\documentclass[10pt]{article}\n\\usepackage[margin=.75in]{geometry}\n%\\usepackage{palatino}\n\\usepackage{sectsty}\n\\sectionfont{\\normalsize\\selectfont\\itshape}\n\\usepackage[T1]{fontenc}\n\\usepackage{libertine}\n\\renewcommand*\\oldstylenums[1]{{\\fontfamily{fxlj}\\selectfont > #1}}" > ("\\section{%s}" . "\\section*{%s}"))) > > Second, something like the following at the top of the org file (replace > with your particulars): > > #+OPTIONS: author:nil timestamp:nil > #+TITLE: > #+DATE: > #+LaTeX_CLASS: cv > > #+BEGIN_LATEX > \begin{flushleft} > \bfseries\Large Curriculum Vitae\hfill Daniel M. Griswold\normalfont > \end{flushleft} > > \vspace{-12pt}% > \begin{flushright} > 69 Stratton Road\\ > Rochester, NY 14610\\ > (585) xxx-xxxx\\ > dgris...@xxxxx.com\\ > \hrulefill > \end{flushright} > #+END_LATEX > > > > > On Fri, Sep 19, 2014 at 5:18 AM, Rainer M Krug <rai...@krugs.de> wrote: > >> Hi >> >> I am looking for examples / templates for CVs written using org, as I >> decided to ose org for my CV. >> >> I fund this oldish conversation >> >> http://lists.gnu.org/archive/html/emacs-orgmode/2012-04/msg00096.html >> >> and these two templates for using org to write a CV: >> >> https://github.com/punchagan/resume >> https://github.com/fasheng/fsh-orgmode-latex-cv >> >> as well this CV without .org file >> >> http://adamsonj.ninth.su/cv.html >> >> Also, there does not seem to be anything on worg. >> >> - Can somebody give any further info on org and CVs? >> - How do you do it (I don't assume you write your CVs in Word?), or are >> you using LaTeX directly? >> - Any other examples and templates online? >> >> If I get enough, I will compile a summary for worg, but I need examples >> and information. >> >> Thanks, >> >> Rainer >> >> -- >> Rainer M. Krug >> email: Rainer<at>krugs<dot>de >> PGP: 0x0F52F982 >> Brady Trainor <algeb...@uw.edu> writes: > On 9/19/2014 2:18 AM, Rainer M Krug wrote: >> Hi >> >> - How do you do it (I don't assume you write your CVs in Word?), or are >> you using LaTeX directly? > > Nice question, I will enjoy reading all the examples in this thread. > > For a bit, I tried to make org do everything, like export resumes to > Word, Writer, LaTeX and ASCII from one tree. Eventually, I couldn't > justify managing all the moving parts, but maybe one day... > > So I abandoned the export to word processors, though I had succeeded in > applying template files. Too much going on behind the scenes for me, and > requests for Word resumes should be rare enough that I just have notes > on how to quickly format a resume there. After all, with so many OS and > fonts, sending a Word document across OS can have unpredictable results. > PDF or plain text is the way to go. (Interpretive dance is okay too.) > > 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. > > But what I do still use is export to ASCII, as editing an ASCII resume > layout is a pain. Here is the crux of my template for that > > #+OPTIONS: toc:nil num:nil > #+NAME: setup # I have no idea what this line is for, I found it on worg > #+BEGIN_SRC emacs-lisp :results silent :exports none > (setq org-ascii-headline-spacing '(0 . 1)) > (setq org-ascii-inner-margin 5) > (setq org-ascii-underline '((ascii nil ?= nil))) > #+END_SRC > > * resume :export: > > #+BEGIN_CENTER > Brady Trainor\\ > algeb...@uw.edu -- (206) 898-4124 > #+END_CENTER > > ** Experience > *** Jan 0000-Present Position > Location\\ > Job description. > > ... etc. > > This is nice for sites that seem to prefer plain text, or demand it. I'm > considering removing the centering, as some sites seem to remove the > whitespace up to first character (B). > > Brady > > > Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Hello, > > Brady Trainor <algeb...@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". > > > Regards, Myles English <mylesengl...@gmail.com> writes: > Hello, > > Nicolas Goaziou writes: > >> Brady Trainor <algeb...@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". > > I did actually make a start on this, I'll dig it out and put it > somewhere accessible, soon. > > Myles > > Rasmus <ras...@gmx.us> writes: > Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > >> Hello, >> >> Brady Trainor <algeb...@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 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 Dan Griswold <kc5...@gmail.com> writes: > Not sure anybody saw this the first time, so I'll try again, with some > expansion. > > Unlike the others who've commented, I moved my CV from LaTeX to org-mode > and I'm happy with the results. Two things make it work well. > > First, a "cv" class added to org-latex-classes: > > (add-to-list '("cv" > "\\documentclass[10pt]{article}\n\\usepackage[margin=.75in]{geometry}\n%\\usepackage{palatino}\n\\usepackage{sectsty}\n\\sectionfont{\\normalsize\\selectfont\\itshape}\n\\usepackage[T1]{fontenc}\n\\usepackage{libertine}\n\\renewcommand*\\oldstylenums[1]{{\\fontfamily{fxlj}\\selectfont > #1}}" > ("\\section{%s}" . "\\section*{%s}"))) > > Second, something like the following at the top of the org file (replace > with your particulars): > > #+OPTIONS: author:nil timestamp:nil > #+TITLE: > #+DATE: > #+LaTeX_CLASS: cv > > #+BEGIN_LATEX > \begin{flushleft} > \bfseries\Large Curriculum Vitae\hfill Daniel M. Griswold\normalfont > \end{flushleft} > > \vspace{-12pt}% > \begin{flushright} > 69 Stratton Road\\ > Rochester, NY 14610\\ > (585) xxx-xxxx\\ > dgris...@xxxxx.com\\ > \hrulefill > \end{flushright} > #+END_LATEX > > Main headings are things like: > > * Education > * Specialization > * Employment > * Publications > * Awards and Honors > > and the details below each of these headings are simply unordered lists > > I really like the easy of editing in org-mode this gives me. > > Hope this helps, > > Dan Joseph Vidal-Rosset <joseph.vidal.ros...@gmail.com> writes: > Le sam. 20 sept. 2014 à 02:49:03 , Dan Griswold <kc5...@gmail.com> a > envoyé ce message: >> Not sure anybody saw this the first time, so I'll try again, with some >> expansion. >> >> Unlike the others who've commented, I moved my CV from LaTeX to >> org-mode and I'm happy with the results. Two things make it work >> well. >> >> First, a "cv" class added to org-latex-classes: >> >> (add-to-list '("cv" >> "\\documentclass[10pt]{article}\n\\usepackage[margin=.75in]{geometry}\n%\\usepackage{palatino}\n\\usepackage{sectsty}\n\\sectionfont{\\normalsize\\selectfont\\ >> itshape}\n\\usepackage[T1]{fontenc}\n\\usepackage{libertine}\n\\renewcommand*\\oldstylenums[1]{{\\fontfamily{fxlj}\\selectfont >> #1}}" >> ("\\section{%s}" . "\\section*{%s}"))) > Hello Dan, hello the list, > > I guess that there is a code problem in this (add-to-list ...) , in my > init.el (or custom.el) , it produces this warning: > > Wrong number of arguments: #[(list-var element &optional append compare-fn) > \204 > J\235\202>\305=\203 > J>\202>\306=\203&\307 > J"\202> > J\211\203< @"\204< A\211\204- )\203D > J\207 > \203R\304 > J C"\202V > JBL\207 [compare-fn element list-var lst append eq eql memql] 5 > 1615569], 1 > > Now a suggestion: there is "moderncv" class in texlive and I wonder if > it is difficult to make an add-to-list for this class in order to export > a CV both in latex and in html. > > I have no time at the moment to try this solution. > > Best wishes, > > Jo. > > Vikas Rawal <vikasli...@agrarianresearch.org> writes: > I know I am being lazy in not trying it out, but if you could share a > PDF, it would give us an idea of what this gives you. > > Vikas > > On 20-Sep-2014, at 6:19 am, Dan Griswold <kc5...@gmail.com> wrote: > >> Not sure anybody saw this the first time, so I'll try again, with some >> expansion. >> >> Unlike the others who've commented, I moved my CV from LaTeX to >> org-mode and I'm happy with the results. Two things make it work >> well. >> >> First, a "cv" class added to org-latex-classes: >> >> (add-to-list '("cv" >> "\\documentclass[10pt]{article}\n\\usepackage[margin=.75in]{geometry}\n%\\usepackage{palatino}\n\\usepackage{sectsty}\n\\sectionfont{\\normalsize\\selectfont\\itshape}\n\\usepackage[T1]{fontenc}\n\\usepackage{libertine}\n\\renewcommand*\\oldstylenums[1]{{\\fontfamily{fxlj}\\selectfont >> #1}}" >> ("\\section{%s}" . "\\section*{%s}"))) >> >> Second, something like the following at the top of the org file (replace >> with your particulars): >> >> #+OPTIONS: author:nil timestamp:nil >> #+TITLE: >> #+DATE: >> #+LaTeX_CLASS: cv >> >> #+BEGIN_LATEX >> \begin{flushleft} >> \bfseries\Large Curriculum Vitae\hfill Daniel M. Griswold\normalfont >> \end{flushleft} >> >> \vspace{-12pt}% >> \begin{flushright} >> 69 Stratton Road\\ >> Rochester, NY 14610\\ >> (585) xxx-xxxx\\ >> dgris...@xxxxx.com\\ >> \hrulefill >> \end{flushright} >> #+END_LATEX >> >> Main headings are things like: >> >> * Education >> * Specialization >> * Employment >> * Publications >> * Awards and Honors >> >> and the details below each of these headings are simply unordered lists >> >> I really like the easy of editing in org-mode this gives me. >> >> Hope this helps, >> >> Dan >> > Xavier Garrido <xavier.garr...@gmail.com> writes: > Hi Rainer, > > You can see mine https://github.com/xgarrido/org-resume that uses > org-mode to produce a LaTeX->PDF (see attached file) file as well as > an HTML version. > > Hope it gives you some ideas. > > Cheers, > Xavier > > Le 19/09/2014 11:18, Rainer M Krug a écrit : >> Hi >> >> I am looking for examples / templates for CVs written using org, as I >> decided to ose org for my CV. >> >> I fund this oldish conversation >> >> http://lists.gnu.org/archive/html/emacs-orgmode/2012-04/msg00096.html >> >> and these two templates for using org to write a CV: >> >> https://github.com/punchagan/resume >> https://github.com/fasheng/fsh-orgmode-latex-cv >> >> as well this CV without .org file >> >> http://adamsonj.ninth.su/cv.html >> >> Also, there does not seem to be anything on worg. >> >> - Can somebody give any further info on org and CVs? >> - How do you do it (I don't assume you write your CVs in Word?), or are >> you using LaTeX directly? >> - Any other examples and templates online? >> >> If I get enough, I will compile a summary for worg, but I need examples >> and information. >> >> Thanks, >> >> Rainer >> > Rainer M Krug <rai...@krugs.de> writes: > Hi > > I am looking for examples / templates for CVs written using org, as I > decided to ose org for my CV. > > I fund this oldish conversation > > http://lists.gnu.org/archive/html/emacs-orgmode/2012-04/msg00096.html > > and these two templates for using org to write a CV: > > https://github.com/punchagan/resume > https://github.com/fasheng/fsh-orgmode-latex-cv > > as well this CV without .org file > > http://adamsonj.ninth.su/cv.html > > Also, there does not seem to be anything on worg. > > - Can somebody give any further info on org and CVs? > - How do you do it (I don't assume you write your CVs in Word?), or are > you using LaTeX directly? > - Any other examples and templates online? > > If I get enough, I will compile a summary for worg, but I need examples > and information. > > Thanks, > > Rainer -- Rainer M. Krug email: Rainer<at>krugs<dot>de PGP: 0x0F52F982
pgpxjlEDwWhj3.pgp
Description: PGP signature
