> Hi Tim
> I have been exporting from orgmode to PDF time ago, but very basic PDFs,
> playing with some basic options of orgmode. When I tried to produce a
> meeting minute with a logo in the heading, I decided that I should learn
> better a way of exporting, because the minute meeting was a
Ypo writes:
> I've already tried that. But it doesn't seem to understand the HOME
> directory ~~/~. At least at Windows.
I haven't touched Windows for a thousand years :-), but maybe this thread
can help you:
https://stackoverflow.com/questions/13584118/how-to-write-a-path-with-latex
best
>>>>>>> El 03/04/2021 a las 18:00, emacs-orgmode-requ...@gnu.org escribió:
Message: 34
Date: Sun, 04 Apr 2021 00:31:24 +1100
To:emacs-orgmode@gnu.org
Subject: Re: First steps exporting to tex
Message-ID:<871rbr7ag1@gmail.com>
Content-Type: text/plain; charset=u
Hi Jean Louis,
Jean Louis writes:
> Do you have a specific remark on what would be major wrong with the
> default LaTeX export from your viewpoint?
>
> For me, I like larger letters and more space on paper. I find it
> narrow and not enough legible. But that is not typographically
> technical
* Juan Manuel Macías [2021-04-03 20:51]:
> William Denton writes:
>
> > [...] and it looks like a published book or journal article!
>
> Something similar I thought, in my student days, when at the early '90 I
> saw a document printed in word perfect, just because it had a book
> typeface
William Denton writes:
> [...] and it looks like a published book or journal article!
Something similar I thought, in my student days, when at the early '90 I
saw a document printed in word perfect, just because it had a book
typeface (Times Roman), footnotes and many more fancy stuff. It looked
On 3 April 2021, Diego Zamboni wrote:
I fully agree with Tim here - don't make things more complicated than
necessary! Start with standard Org and the standard export, see how it
works and adjust from there.
It's amazing what the combination of Org and LaTeX can do without any extra
>
>
> The org export to latex only needs to be as complicated as you need it
> to be. Org has variables which can be used to add/remove things from the
> preamble and once you have those configured, you don't have to put
> anything in the org file itself. Start simple and add as you find a need
>
Ypo writes:
> Good morning
>
> 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
Hi Ypo,
I think that, as a starting point, the concepts that belong to Org and
those that belong to LaTeX should be separated.
Ypo writes:
> [...]
> 2 template.tex -> this could be added to the SETUPFILE:
> #+LATEX_HEADER: \input{template.tex}. But it seems to have no effect
> on the PDF
Hi Ypo,
Ypo 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
> "Ypo" == Ypo writes:
Ypo> Good morning
Ypo> After reading your interesting advices, I've decided to start
Ypo> my path through LaTeX. I have been some hours trying to start,
Ypo> with little result, but I hope that once established a
Ypo> *workflow* the results will
Good morning
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
13 matches
Mail list logo
