From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Generic LaTeX class support (scrlttr2/isodoc)
Date: Tue, 21 Sep 2010 23:09:46 +0530 [thread overview]
Message-ID: <817hiff125.fsf@gmail.com> (raw)
In-Reply-To: <81hbhjf1vi.fsf@gmail.com> (Jambunathan K.'s message of "Tue, 21 Sep 2010 22:52:09 +0530")
[-- Attachment #1: Type: text/plain, Size: 71 bytes --]
I am attaching sample files from my work-area for ready consumption.
[-- Attachment #2: sample-isodoc.tex --]
[-- Type: text/plain, Size: 983 bytes --]
% Created 2010-09-21 Tue 22:02
\documentclass{isodoc}
\usepackage[latin1]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{t1enc}
\usepackage{textcomp}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage{pdfpages}
\usepackage{mystyle}
\providecommand{\alert}[1]{\textbf{#1}}
\title{}
\author{Jambunathan K}
\date{21 September 2010}
\begin{document}
\letter
[
date =
20100921
,
to =
Orgmode Mailing List \\
GNU Mailing List \\
World Wide Web \\
Internet - 111111
,
opening =
Friends
,
subject =
Composing letters using isodoc
,
closing =
Thanks
,
enclosures =
org-latex-generic.el
org-scrlttr2.el
org-isodoc.el
org-letter-utils.el
,
]
{
I would like to share with you a little utility that helps me
compose formal letters within Org mode. Would you like to try it?
}
\end{document}
[-- Attachment #3: sample-isodoc.isodoc --]
[-- Type: text/plain, Size: 543 bytes --]
#+LaTeX_CLASS: isodoc
#+LATEX_HEADER: \usepackage{mystyle}
#+OPTIONS: toc:nil
#+TITLE:
* letter
** options
*** date
20100921
*** to
[[bbdb:Orgmode%20Mailing%20List][bbdb:Orgmode Mailing List]]
*** opening
Friends
*** subject
Composing letters using isodoc
*** closing
Thanks
*** enclosures
org-latex-generic.el
org-scrlttr2.el
org-isodoc.el
org-letter-utils.el
** body
I would like to share with you a little utility that helps me
compose formal letters within Org mode. Would you like to try it?
[-- Attachment #4: sample-scrlttr2.scrlttr2 --]
[-- Type: text/plain, Size: 484 bytes --]
#+LaTeX_CLASS: scrlttr2
#+LaTeX_CLASS_OPTIONS: [jambu]
#+OPTIONS: toc:nil
* letter
** to
[[bbdb:Orgmode%20Mailing%20List][bbdb:Orgmode Mailing List]]
** subject
Composing letters using scrlttr2
** opening
Friends
** body
I would like to share with you a little utility that helps me
compose formal letters within Org mode. Would you like to try it?
** encl
org-latex-generic.el
org-scrlttr2.el
org-isodoc.el
org-letter-utils.el
** closing
Thanks
[-- Attachment #5: sample-scrlttr2.tex --]
[-- Type: text/plain, Size: 1003 bytes --]
% Created 2010-09-21 Tue 21:51
\documentclass[jambu]{scrlttr2}
\usepackage[latin1]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{t1enc}
\usepackage{textcomp}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage{pdfpages}
\providecommand{\alert}[1]{\textbf{#1}}
\title{sample-scrlttr2}
\author{Jambunathan K}
\date{21 September 2010}
\begin{document}
\maketitle
\begin{letter}
{
Orgmode Mailing List \\
GNU Mailing List \\
World Wide Web \\
Internet - 111111 \\
Cosmos
}
\setkomavar{subject} {
Composing letters using scrlttr2
}
\opening {
Friends
}
I would like to share with you a little utility that helps me
compose formal letters within Org mode. Would you like to try it?
\encl {
org-latex-generic.el
org-scrlttr2.el
org-isodoc.el
org-letter-utils.el
}
\closing {
Thanks
}
\end{letter}
\end{document}
[-- Attachment #6: Type: text/plain, Size: 2972 bytes --]
Let me know if you have any questions or suggestions.
Jambunathan K.
Jambunathan K <kjambunathan@gmail.com> writes:
> This is a follow upon my earlier posts in the following threads:
>
> [1] 'Composing letters using org-mode and scrlttr2'
> [2] Composingletters using Org mode and the LaTeX isodoc clas'
>
> I am attaching four files
> - org-latex-generic.el
> - org-letter-utils.el
> - org-scrlttr2.el
> - org-isodoc.el
>
> Functionality is easily explained by usage rather than by words.
>
> Usage Notes:
>
> 1. Load libraries
> - (require 'isodoc)
> - (require 'scrlttr2)
>
> 2. C-x C-f 'sample-letter.scrlttr2' and/or 'sample-isodoc.isodoc'. File
> extensions are important and they are indicative of the LaTeX classes
> targetted for export.
>
> 3. You will be offered a Org outline structure. Fill in the same. In the
> 'To' address field you have an option just to insert a bbdb link as
> opposed to the whole address.
>
> Remember to fill in the LCO file for scrlttr2 and style file for
> isodoc.
>
> 4. Do a C-c C-e l or C-c C-e d.
>
> 5. See that your letter is nicely exported.
>
> 6. YMMV.
>
> Additional Notes:
>
> Files have helpful docstring. Core functionality is in
> org-latex-generic-sectioning. Rest all are bells and whistles.
>
> ,----[ C-h f org-latex-generic-sectioning RET ]
> | org-latex-generic-sectioning is a Lisp function in
> | `org-latex-generic.el'.
> |
> | (org-latex-generic-sectioning LEVEL HEADING)
> |
> | Rules for emitting Org headings as LaTeX fragments.
> | Currently a heading could be configured to start a LaTeX
> | environment, emit a LaTeX command, set optional arguments (with
> | heading as key and entry body as value) and mandatory
> | arguments. See `org-latex-generic-scrlttr2-sectioning-alist' and
> | `org-latex-generic-isodoc-sectioning-alist'.
> |
> | [back]
> `----
>
> Watch Out For:
>
> 1. Have no empty lines in .scrlttr2/.isodoc file. If that doesn't help
> remove it from the generated tex file.
>
> I have a strong reason to believe org-latex.el is generating
> extraneous newlines in (org-export-latex-subcontent ...) at line 1029
> or thereabouts.
>
> 2. Have no commas in the bbdb address field. C-h f
> org-letter-utils-bbdb-export is probably not upto the task.
>
> 3. Remove \date directive in the isodoc tex file.
>
> 4. Also see FIXME notes in the org-latex-generic.el
>
>
> Implementation Notes:
>
> The key idea is to mirror the LaTeX commands in terms of Org
> headlines. Start with C-h f org-latex-generic-sectioning for further
> exploring. Try mapping the headline structure of .scrlttr2/.isodoc file
> with the corresponding tex file and compare it against the settings of
> of different variables in the org-scrlttr2.el/org-isodoc.el
>
> Footnotes:
> [1] http://lists.gnu.org/archive/html/emacs-orgmode/2010-07/msg01060.html
> [2] http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg00466.html
>
>
> Jambunathan K.
>
>
> Attachments:
[-- Attachment #7: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-09-21 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 17:22 Generic LaTeX class support (scrlttr2/isodoc) Jambunathan K
2010-09-21 17:39 ` Jambunathan K [this message]
2011-02-08 20:54 ` Allen S. Rout
2011-02-09 23:59 ` Allen S. Rout
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=817hiff125.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--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).