From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Org as a publishing toolkit
Date: Tue, 10 May 2011 16:39:17 -0500 [thread overview]
Message-ID: <BANLkTikySM5JZZ8u6OEPsAfkVfCzgWq60g@mail.gmail.com> (raw)
In-Reply-To: <m1wrhyjl26.fsf@tsdye.com>
Cool, I will do!
But org doesn't impose some structure that might prevent me from
putting the cover in the first page? Just curious. I wouldn't also
like to have to edit the latex generated afterwards, but that's a
possibility.
Thanks!
Marcelo.
On Tue, May 10, 2011 at 4:35 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
> Aloha Marcelo,
>
> Others might do this differently, but I don't use LaTeX for book
> covers. I only use it for the pages of the book.
>
> It sounds like your cover image is floating, which is something that
> LaTeX does with tables and images. If you are new to LaTeX and don't
> have a feel for how it handles "floats", then I recommend an
> introductory text. Leslie Lamport's book is terrific, but there are
> other good introductions on the Internet.
>
> Org-mode and its LaTeX exporter are *not* going to insulate you from the
> need to learn some LaTeX, especially if you intend to write something as
> complex as a book.
>
> hth,
> Tom
>
> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>
>> Thomas,
>>
>> I have a more specific question. I have already managed to embed an
>> image to act as the cover of the book. However, the image is being
>> shown in the third page. I want the sequence to be like this:
>>
>> 1) Cover image
>> 2) The sub-cover:
>>
>> "Title""
>> My Name
>> Date
>>
>> 3) TOC
>>
>> 4) Intro, chapters...
>>
>> How could I do that?
>>
>> Thanks in advance!
>>
>> Regards,
>>
>> Marcelo.
>>
>> On Tue, May 10, 2011 at 2:19 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>>> Aloha Marcelo,
>>>
>>> The approach I would take here, which might not be what you want, would
>>> be to use inline markup:
>>>
>>> http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-10_3
>>>
>>> You would define the output for the various exporters in the link
>>> definition, with something fancy for LaTeX and whatever else works in
>>> the other export formats you care to support.
>>>
>>> All the best,
>>> Tom
>>>
>>> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>>>
>>>> Cool! Thanks.
>>>>
>>>> Now that you mention it, I was wondering if something like "condition
>>>> export" is possible. For very specific localized LaTeX fetures, it
>>>> would be useful. Take this example:
>>>>
>>>> #+LaTeX_HEADER: \usepackage[T1]{fontenc}
>>>>
>>>> #+LaTeX:\yinipar{\color{red}H}ello World
>>>>
>>>> This created a first-letter that is stylized differently. This won't
>>>> come out in any other exported, so I'd like to do something like
>>>> (NOTE: pseudo-code!)
>>>>
>>>> #+LaTeX:\yinipar{\color{red}H}ello World
>>>>
>>>> #iif not LaTeX
>>>> Hello World
>>>> #end
>>>>
>>>> If it is not possible what I can do is to pre-process the orgfile with
>>>> something like ERB (I'm familiar with Ruby) or another templating
>>>> language before exporting (and even automate it all by calling emacs
>>>> in batch mode ;) ), but it'd be nice if org supported that
>>>> out-of-the-box.
>>>>
>>>> Cheers,
>>>>
>>>> Marcelo.
>>>>
>>>>
>>>> On Tue, May 10, 2011 at 1:31 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>>>>> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>>>>>
>>>>>> Hi list,
>>>>>>
>>>>>> So today I have been reseaching about higher-levels toolkits that
>>>>>> could help me get into TeX (and or LaTeX) and at the same time
>>>>>> allowing me to keep the text in a more human-readable format (easier
>>>>>> to mantain and to convert to other formats if needed).
>>>>>>
>>>>>> I know that if I want beautiful formatted PDFs I will need to get into
>>>>>> TeX / LaTeX, and I already started doing that, but as I said, keeping
>>>>>> the text in a higher level format has benefits that you already know
>>>>>> about.
>>>>>>
>>>>>> So I looked at asciidoc, the lower-level XML-based docbook, markdown,
>>>>>> pandoc, ConTeXt, etc.
>>>>>>
>>>>>> Then I thought, why not try orgmode?
>>>>>>
>>>>>> So, after reading this article:
>>>>>> http://orgmode.org/worg/org-tutorials/org-latex-export.html, I've then
>>>>>> realized how powerful the org-export feature is.
>>>>>>
>>>>>> I can basically do this:
>>>>>> * Keep the text in a (very) human readable format that I'm used to
>>>>>> and that is much better to maintain than any other format I know
>>>>>> (markdown / asciidoc) and integrated with my own orgmode personal
>>>>>> information manager!
>>>>>> * Add / customize the LaTeX output in *ANY* way I want to. Thanks to
>>>>>> org AND babel! From what I can see, there are no limitations on how
>>>>>> complex the LaTeX customizations can be, it can essentially match up
>>>>>> any other "pure" latex documents out there.
>>>>>> * As noted above, fully support LaTeX while still allowing me to export to:
>>>>>> * plaintext
>>>>>> * HTML
>>>>>> * DocBook (and hence an array of other formats)
>>>>>>
>>>>>> I mean, how cool is that? I'm only starting in TeX/LaTeX so I might be
>>>>>> overlooking some limitations, but from what I can see, orgmode is the
>>>>>> most pragmatic and powerful publishing framework I have ever come to
>>>>>> know.
>>>>>>
>>>>>> And what excites me even more is that I can keep my book in my
>>>>>> preferred format and still output a beautifully-formatted PDF book
>>>>>> *and* still support other formats (such as mobi or epub through
>>>>>> docbook). Amazing!
>>>>>>
>>>>>> By the way, if I want to use raw TeX or maybe ConTeXt, is it possible?
>>>>>> Not that I need, only curious :)
>>>>>>
>>>>>> This needs more hype! I don't think people realize how powerful this is ;)
>>>>>>
>>>>>> Cheers!
>>>>>>
>>>>>> Marcelo.
>>>>>>
>>>>>>
>>>>>
>>>>> Aloha Marcelo,
>>>>>
>>>>> The LaTeX export tutorial is a work in progress. I hope you find it
>>>>> useful. When you run across something that doesn't work (or make sense)
>>>>> don't hesitate to come back to the list with a query or suggestion.
>>>>>
>>>>> All the best,
>>>>> Tom
>>>>>
>>>>> --
>>>>> Thomas S. Dye
>>>>> http://www.tsdye.com
>>>>>
>>>>
>>>
>>> --
>>> Thomas S. Dye
>>> http://www.tsdye.com
>>>
>>
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>
next prev parent reply other threads:[~2011-05-10 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 17:52 Org as a publishing toolkit Marcelo de Moraes Serpa
2011-05-10 18:31 ` Thomas S. Dye
2011-05-10 18:48 ` Marcelo de Moraes Serpa
2011-05-10 19:19 ` Thomas S. Dye
2011-05-10 20:53 ` Marcelo de Moraes Serpa
2011-05-10 21:35 ` Thomas S. Dye
2011-05-10 21:39 ` Marcelo de Moraes Serpa [this message]
2011-05-10 22:26 ` Thomas S. Dye
2011-05-11 0:41 ` Marcelo de Moraes Serpa
2011-05-11 1:40 ` prad
2011-05-11 4:52 ` Avdi Grimm
2011-05-11 8:09 ` Rasmus
2011-05-12 6:52 ` Eric S Fraga
2011-05-11 15:15 ` Mike McLean
2011-05-11 16:10 ` Marcelo de Moraes Serpa
2011-05-11 16:33 ` Nick Dokos
2011-05-14 12:32 ` Mike McLean
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=BANLkTikySM5JZZ8u6OEPsAfkVfCzgWq60g@mail.gmail.com \
--to=celoserpa@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).