public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Luis Fernado Silva Castro de Araújo" <luis.nando-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc friendly tufte document class
Date: Tue, 24 Jan 2017 21:11:16 -0800 (PST)	[thread overview]
Message-ID: <88eca349-1b74-485f-ae42-a50958a077d1@googlegroups.com> (raw)
In-Reply-To: <a44af459-fe8b-4b25-a1cd-ae4e16314814-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2670 bytes --]

Thanks for the writer Chris,

I reached the conclusion that the easiest solution would be not to mess 
with the tufte class. Its main advantage seems to be the rational use of 
space. Tufte's design allows for packing information in a clever way, which 
is to say that whenever tables and figures exists in the document, they 
will take less space, whereas the amount of words per page is about the 
same of a tall (regular) latex article page. In my non-scientific tests, 
the difference was of about 15% space saved in heavily image or table 
packed documents. The difference is not big, if that would be the sole 
reason to use that design. I totally see why the R-team is insisting on 
that, as it is actually super useful to present graphs and tables.

Why would one need to save space? Some organizations in certain 
circumstances require a limited number of pages (talking about funders, 
sponsorships, which are the type of org that I deal with), sometimes the 
15% more material can help you convey your findings better. The confort of 
reading a pdf in tufte's design is about the same as a well rendered latex 
document, as it keeps the number of words per line in the 60-80 mark 
depending on the font size.

Another strenght of tufte's design is that fullwidth figures allows for 
complex images to take more space than the actual text. The reader will be 
presented with a larger image to inspect, that could help in seeing the 
details, and so on.

So in the end, the true advantage of tufte's design is not in the fonts, or 
the fancy headings, or titling. The strength is on the larger margin where 
you can put notes and figure captions; and in the fullwidth environment.

These might be easy to achieve w/o even messing with the document class; 
floatrow package seems a great candidate to help achieving the aim of a 
"tuftesque" document in the sense described above. I will investigate 
whether it can mimic some of the design aspects mentioned, and started by 
this 
<http://tex.stackexchange.com/questions/350310/tufte-margin-caption-effect-with-floatrow> 
question at SO.


-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/88eca349-1b74-485f-ae42-a50958a077d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3136 bytes --]

  parent reply	other threads:[~2017-01-25  5:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 10:50 Luis Fernado Silva Castro de Araújo
     [not found] ` <7879f6eb-6853-4890-b843-c69356b280d6-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-24  9:04   ` Václav Haisman
     [not found]     ` <CAKw7uVikt-q9hBi0N-DAZaJT5yc_fGo7HXWHC+1HdfvhpYiiNg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-24  9:10       ` Luis Fernado Silva Castro de Araújo
     [not found]         ` <e382c039-e854-428e-89d4-52aa04f26cf0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-24 20:42           ` Chris MacKay
     [not found]             ` <a3c76c99-3541-4f1d-8e15-58ff465c55a4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-24 20:48               ` Luis Fernado Silva Castro de Araújo
     [not found]                 ` <af50ba79-321c-4d4a-b35b-b8939c5e0ee9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-24 21:13                   ` Chris MacKay
     [not found]                     ` <a44af459-fe8b-4b25-a1cd-ae4e16314814-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-25  5:11                       ` Luis Fernado Silva Castro de Araújo [this message]
     [not found]                         ` <88eca349-1b74-485f-ae42-a50958a077d1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-25 14:54                           ` Chris MacKay
     [not found]                             ` <da6bd44f-1996-4f7f-a32c-3ce94e3051e5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-26  1:47                               ` Luis Fernado Silva Castro de Araújo
     [not found]                                 ` <98b2a8fd-c42f-4768-bc92-b6be6c35551e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-26  3:01                                   ` Chris MacKay
     [not found]                                     ` <27D812EC-9384-4E8D-B38B-15F2225CCA9B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-10  1:16                                       ` lf-araujo
2017-01-24 15:30   ` John Muccigrosso

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=88eca349-1b74-485f-ae42-a50958a077d1@googlegroups.com \
    --to=luis.nando-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).