On Tuesday, 11 Oct 2016 at 20:55, Eduardo Mercovich wrote:
[...]
> I tried a bit of HTML as documents, but the un-packaged nature of it
> (document + images + css + etc.) always gave me problems with other
> people. Self contained pdfs, on the other hand, just work in every OS.
This is where epu
Hi Philip.
[...]
> My goal is a 1-page PDF invoice [...]
>> If the only specs you'd like to change are just those fonts, and
>> something like Memoir starts with a decent general layout (depending on
>> your needs), then it makes sense to tweak it a bit and from then on,
>> just use the latex exp
On 12 October 2016 at 08:14, Eric S Fraga wrote:
> On Tuesday, 11 Oct 2016 at 20:55, Eduardo Mercovich wrote:
>
> [...]
>
>> I tried a bit of HTML as documents, but the un-packaged nature of it
>> (document + images + css + etc.) always gave me problems with other
>> people. Self contained pdfs, o
On 11 October 2016 at 21:55, Eduardo Mercovich wrote:
> HTML is easier to style, yes. Does that format, exported to pdf, has
> what you need?
No. Almost, but hyperlinks are not clickable.
> Because latex may take more effort, but it's only once.
> Then, you have pdfs with the index, pages of th
Hi Philip.
[...]
>>> What *do* you need exactly?
>> Cantarell for the sans-serif, FreeSerif for the serif, don't care
>> about the mono.
> Oh yes, and #cc for the title background.
HTML is easier to style, yes. Does that format, exported to pdf, has
what you need? Because latex may take mor
On 8 October 2016 at 03:31, Nick Dokos wrote:
> Philip Hudson writes:
>
>> On 7 October 2016 at 23:14, Nick Dokos wrote:
>>> E.g.
>>>
>>> #+LATEX_HEADER: \usepackage{palatino}
>
> I should have said that this changes the font for the whole document.
>
>> Right, that's one of the packages I found
On 8 October 2016 at 09:19, Philip Hudson wrote:
> On 8 October 2016 at 03:31, Nick Dokos wrote:
>> Philip Hudson writes:
>>
>>> On 7 October 2016 at 23:14, Nick Dokos wrote:
E.g.
#+LATEX_HEADER: \usepackage{palatino}
>>
>> I should have said that this changes the font for the wh
Philip Hudson writes:
> On 7 October 2016 at 23:14, Nick Dokos wrote:
>> Philip Hudson writes:
>>
>>> Question: How do I specify how an Org element appears in the
>>> corresponding exported PDF? Specifically the typeface (font).
>>>
>>
>> E.g.
>>
>> #+LATEX_HEADER: \usepackage{palatino}
>
I sh
On 7 October 2016 at 23:14, Nick Dokos wrote:
> Philip Hudson writes:
>
>> Question: How do I specify how an Org element appears in the
>> corresponding exported PDF? Specifically the typeface (font).
>>
>
> E.g.
>
> #+LATEX_HEADER: \usepackage{palatino}
Right, that's one of the packages I found
Philip Hudson writes:
> Question: How do I specify how an Org element appears in the
> corresponding exported PDF? Specifically the typeface (font).
>
E.g.
#+LATEX_HEADER: \usepackage{palatino}
> Meta-question: Where might this question be answered that I haven't
> looked? I haven't managed to
Question: How do I specify how an Org element appears in the
corresponding exported PDF? Specifically the typeface (font).
Meta-question: Where might this question be answered that I haven't
looked? I haven't managed to find it in the manual or on Worg using a
fairly exhaustive variety of search t
11 matches
Mail list logo
