emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Tables and environment with parameters
Date: Wed, 21 Jul 2010 21:22:03 +0200	[thread overview]
Message-ID: <87sk3czllw.fsf@mundaneum.com> (raw)
In-Reply-To: CEDD7A1A-8E17-496E-9DA8-AB5A1A5151E3@gmail.com

Hi Carsten,

Carsten Dominik wrote:
> On Jul 12, 2010, at 9:49 PM, Sébastien Vauban wrote:
>> Carsten Dominik wrote:
>>>> Carsten Dominik wrote:
>>>>> On Jun 28, 2010, at 4:30 PM, Sébastien Vauban wrote:
>>>>>> Carsten Dominik wrote:
>>>>>>> On Jun 23, 2010, at 11:30 PM, Sébastien Vauban wrote:
>>>>>>>
>>>>>>>> Since one of the last updates -- I guess --, I now have a problem
>>>>>>>> exporting the tables: I see the meta-tags in the PDF output! Very
>>>>>>>> new...
>>>>>>
>>>>>> Though, in the meanwhile, note that this is not as bad as it could be:
>>>>>> in fact, I'd love to be able to print (when I want it, though) some of
>>>>>> the table meta-information, such as table name and formulas.
>>>>>>
>>>>>> That'd be great to see that, at certain times, in the output PDF --
>>>>>> would we be able to customize its font size or so.
>>>>>>
>>>>>> What do you think?
>>
>> What do you think of that idea for debugging purpose, or for giving more
>> info back to the reader?

Nobody reacted on this point. Does that mean it's useless?  Or is it still a
wished feature by others?  I would love to have, in many cases, the formulas
printed in very tiny characters just below the tables. What do you all think
of this?


>>>> What I called "meta-tags" are the two lines `#+ATTR_LaTeX:' and `#
>>>> +TBLFM:' that weren't visible in the PDF before... Maybe I should say
>>>> "table properties".
>>>>
>>>> So, as I said, for checking purpose, or for giving more information
>>>> (about the formulas) to the reader, that's no so bad to see that, when
>>>> asked for.
>>>>
>>>> Of course, it should be formatted properly, and not interpreted as pure
>>>> LaTeX. In my example, in the PDF, Brutes is written in subscript because
>>>> of the underscore in front of it.
>>>
>>> this might have been fixed, can you please check?
>>
>> Just updated ([2010-07-12 Mon 21:38]).
>>
>> Still not OK for the tables enclosed in =org-special-blocks=, well OK for
>> the other ones:
>
> This is now fixed, thank you for your report.

Yep, it works. Thanks a lot!!

Two remarks, though:

- the org-special-block must begin in column 0; otherwise, it fails.

- the faces applied inside the org-special-block are wrong:

--8<---------------cut here---------------start------------->8---
There are text properties here:
  font-lock-fontified  t
  font-lock-multiline  t
  fontified            t
  pabbrev-added        t
--8<---------------cut here---------------end--------------->8---

  The normal faces are not applied anymore for the lines ATTR_LaTeX and
  TBLNAME, among others.

  It should be:

--8<---------------cut here---------------start------------->8---
There are text properties here:
  face                 org-meta-line
  font-lock-fontified  t
  fontified            t
  pabbrev-added        t
--8<---------------cut here---------------end--------------->8---

  Example:

--8<---------------cut here---------------start------------->8---
#+BEGIN_changemargin {-4.2cm}{0cm}
    #+ATTR_LaTeX: align=lrrrrr
    #+TBLNAME: Autres_Frais_Pro_FNI
    |   |                                            | Invest. total (\EUR) |
    |---+--------------------------------------------+----------------------|
    |   | Documentation et formation                 |               147.50 |
    |   | Publicité (site Web : DNS + hosting 3 ans) |               214.25 |
    |---+--------------------------------------------+----------------------|
    |   | Total                                      |                      |
    | ^ |                                            |                      |
#+END_changemargin
--8<---------------cut here---------------end--------------->8---

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-07-21 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 21:30 Tables and environment with parameters Sébastien Vauban
2010-06-24  6:15 ` Carsten Dominik
2010-06-28 14:30   ` Sébastien Vauban
2010-06-29  7:28     ` Carsten Dominik
2010-06-30 10:27       ` Sébastien Vauban
2010-07-02  4:43         ` Carsten Dominik
2010-07-12 19:49           ` Sébastien Vauban
2010-07-20 15:45             ` Carsten Dominik
2010-07-21 19:22               ` Sébastien Vauban [this message]
2010-08-16 12:01                 ` Carsten Dominik

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=87sk3czllw.fsf@mundaneum.com \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@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.
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).