GNU bug report logs -
#71364
Fix Table.el export
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
On Sat, 8 Jun 2024 at 12:19, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Reuben Thomas <rrt <at> sc3d.org>
> > Date: Sat, 8 Jun 2024 11:59:52 +0100
> > Cc: pranshusharma366 <at> gmail.com, lockywolf <at> gmail.com,
> 71364 <at> debbugs.gnu.org
> >
> > On Sat, 8 Jun 2024 at 11:51, Eli Zaretskii <eliz <at> gnu.org> wrote:
> >
> > > From: Reuben Thomas <rrt <at> sc3d.org>
> > > Date: Sat, 8 Jun 2024 11:05:25 +0100
> > > Cc: Pranshu <pranshusharma366 <at> gmail.com>, Vladimir Nikishkin <
> lockywolf <at> gmail.com>,
> > > 71364 <at> debbugs.gnu.org
> > >
> > > Specifically, it works fine if, like me, you do not want to put LaTeX
> markup in tables. This was certainly
> > my
> > > case, as I was using it with org-mode. In this case, any character
> that is active in LaTeX can and
> > should simply
> > > be escaped on output.
> > >
> > > What is basically broken is the ability to export to LaTeX when the
> table contains LaTeX markup.
> >
> > But the function being discussed is said to be specific to export to
> > LaTeX, so it should expect LaTeX markup in the cells, no?
> >
> > No, it is supposed to export arbitrary text as valid LaTeX. At least,
> that is my understanding.
>
> So it's a YES, because I was saying the same thing. Or maybe we
> disagree about whether a function written for exporting to LaTeX
> should or should not expect LaTeX markup.
>
It looks like I was wrong: `table--generate-source-scan-lines` is expecting
LaTeX input.
Good luck with that!
--
https://rrt.sc3d.org
[Message part 2 (text/html, inline)]
This bug report was last modified 111 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.