From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Ypo <ypuntot@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: First steps exporting to tex
Date: Sat, 03 Apr 2021 12:43:00 +0200 [thread overview]
Message-ID: <87a6qf4pjf.fsf@web.de> (raw)
In-Reply-To: <d9457845-3010-f1f1-b8c9-7ee4edc95842@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3373 bytes --]
Hi Ypo,
Ypo <ypuntot@gmail.com> writes:
> After reading your interesting advices, I've decided to start my path
> through LaTeX. I have been some hours trying to start, with little
> result, but I hope that once established a *workflow* the results will
> come and the new invested time will be directed just to get better and
> better results.
>
> My doubts:
>
> a. As first step for my workflow, it seems convenient to use a
> "template" with the LaTeX preambles. So maybe the many existing
> LaTeX templates can be used quickly with orgmode. I found several
> options and opinions. Which one is the best way?
>
>
> 1. #+SETUPFILE: template.setup -> doesn't seem the ideal way,
> because the template.setup file must be modified adding
> #+latex_class to each of the lines.
> 2. template.tex -> this could be added to the SETUPFILE:
> #+LATEX_HEADER: \input{template.tex}. But it seems to have no
I use
#+LATEX_HEADER: \input{ews30setup} % pointing to ews30setup.tex
in the org-file, I export, not a setupfile.
Alternatively you can use #+INCLUDE: template.org
to grab more than just the org-setup.
For an example, see
https://hg.sr.ht/~arnebab/draketo/browse/software/wisp.org?rev=31bb4a1fb49c#L1
#+INCLUDE: ../org-templates/level-1.org
This pulls the actual content of the file:
https://hg.sr.ht/~arnebab/draketo/browse/org-templates/level-1.org?rev=31bb4a1fb49c
There is also a setupfile at the bottom:
https://hg.sr.ht/~arnebab/draketo/browse/software/wisp.org?rev=31bb4a1fb49c#L1632
#+setupfile: ../org-templates/level-1-software.org
This only pulls the changed org-mode settings:
https://hg.sr.ht/~arnebab/draketo/browse/org-templates/level-1-software.org?rev=31bb4a1fb49c
#+HTML_HEAD_EXTRA: <style type="text/css">.tab-software {background-color: #fffbf8 !important; opacity: 1.0; box-shadow: 0px -5px 7px -2px gray;}</style>
#+HTML_LINK_UP: ../software.html
> 3. Another friend told me that .sty templates were the best way.
I don’t yet have sufficient hold of that. To date I’m using the
memoir-class to get the styling I need — where I use styling (that’s not
the draketo site, but the ews document).
> 5. Also we can see this intricate transformation of a LaTeX
> template into orgmode. How to Migrate LaTeX Template into
> org-mode
> <https://github.com/Literate-DevOps/literate-programming-tutorials/blob/master/how-to/00-convert-latex-template-into-org-mode-template/how-to-migrate-latex-template-into-org-mode.org#how-to-migrate-latex-template-into-org-mode>
> 6. ...
>
>
> b. I think that in a good integration, every character shown on
> orgmode should be exported into the PDF output. For example "CENTRE
> LINE SYMBOL": ℄
> How can this integration be done?
Have a look at \DeclareUnicodeCharacter:
https://www.draketo.de/light/english/emacs/char-not-setup-latex
#+latex_header: \usepackage{uniinput}
See
https://git.neo-layout.org/neo/neo-layout/src/commit/705fac448a0d0562e4e1bc16bf0b6cadbe235771/latex/Standard-LaTeX/uniinput.ins
https://git.neo-layout.org/neo/neo-layout/src/commit/705fac448a0d0562e4e1bc16bf0b6cadbe235771/latex/Standard-LaTeX/uniinput.dtx
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2021-04-03 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 9:31 First steps exporting to tex Ypo
2021-04-03 10:15 ` Martin Steffen
2021-04-04 11:04 ` Ypo
2021-04-04 11:36 ` Juan Manuel Macías
2021-04-05 5:05 ` Tim Cross
2021-04-03 10:43 ` Dr. Arne Babenhauserheide [this message]
2021-04-03 12:10 ` Juan Manuel Macías
2021-04-03 13:31 ` Tim Cross
2021-04-03 16:55 ` Diego Zamboni
2021-04-03 17:07 ` William Denton
2021-04-03 17:49 ` Juan Manuel Macías
2021-04-03 18:36 ` Jean Louis
2021-04-03 20:46 ` Juan Manuel Macías
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=87a6qf4pjf.fsf@web.de \
--to=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=ypuntot@gmail.com \
/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).