From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ASCII table export should use tabs?
Date: Mon, 28 Mar 2011 10:40:09 +0100 [thread overview]
Message-ID: <87pqpbmvly.fsf@ucl.ac.uk> (raw)
In-Reply-To: <AANLkTimU_+FNaGew-X6P2C4gkTZDQJeBCT7wChps6s5U@mail.gmail.com> (Samuel Wales's message of "Sun, 27 Mar 2011 12:30:36 -0700")
Samuel Wales <samologist@gmail.com> writes:
> I wonder if org should export ASCII tables using tabs.
>
> If I send to this list, I can be confident that everybody will know to
> display in a monospace font. That is not true for non-technical
> audiences. Yet I think there are times when I want to send ASCII
> instead of HTML. At least, I am not confident that /I/ know that HTML
> will display correctly.
>
> Tabs are not a perfect solution, as they will break with long entries.
> Still, you can read a broken table with tabs easier than a table
> displayed in a proportional font, which I believe most nontechnical
> people use.
>
> What do you think?
>
> Samuel
I don't think Tabs will work well because either the tab positions are
unknown (depending on how the document is being read) or the tab
positions, if fixed, will be less than optimal for any given table.
For most non-technical audiences, I would recommend exporting to either
HTML or PDF if you're worried about tables being formatted correctly. I
don't send ascii formatted text from org to hardly anybody.
If you're sending email, as much as I dislike HTML messages, I do send
the odd one using org-mime-org-buffer-htmlize if there is formatting
that is critical to the understanding of the document.
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.115.g00134.dirty)
prev parent reply other threads:[~2011-03-28 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 19:30 ASCII table export should use tabs? Samuel Wales
2011-03-28 9:40 ` Eric S Fraga [this message]
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=87pqpbmvly.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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).