Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

table defaults #145

Open
janrito opened this issue Feb 5, 2013 · 5 comments
Open

table defaults #145

janrito opened this issue Feb 5, 2013 · 5 comments

Comments

@janrito
Copy link

janrito commented Feb 5, 2013

As a table header for latex, multimarkdown now inserts this code:

\begin{table}[htbp]
\begin{minipage}{\linewidth}
\setlength{\tymax}{0.5\linewidth}
\centering
\small

It seems to me, these are sensible defaults. However, because these
are hard-coded into multimarkdown C files, it is impossible to change when
needed. A few statements setting these defaults to variables at the beginning
of the latex output would allow the customisation of tables via latex
header includes.

For example, multimarkdown could do something like this:

\ifx\mmtablewidth\undefined
    \def\mmtablewidth{.5\linewidth}
\fi

\ifx\mmtablefont\undefined
    \def\mmtablefont{\centering\small}
\fi

...

\begin{table}[htbp]
\begin{minipage}{\linewidth}
\setlength{\tymax}{\mmtablewidth}
\mmtablefont
@fletcher
Copy link
Owner

fletcher commented Feb 5, 2013

Reasonable request. I'm pretty busy with release of MultiMarkdown Composer 2.0, but will try to get to this as soon as I can.

@janrito
Copy link
Author

janrito commented Feb 6, 2013

Great! Good luck with MMC2.

@fletcher
Copy link
Owner

Hmmm.... Not sure this will work so easily after all. This assumes that one is creating a "complete" document and there is room for includes and set up information.

If this is a simple "snippet", that code would be non-existent, and the call to "\mmtablewidth", for example, would fail. Otherwise, these \ifx conditionals would have to be included before every table. Or would have to treat the first table differently than subsequent tables. None of which seem like very elegant options.

This might stay on the back burner until a better solution arises... I'm open to suggestions.

@janrito
Copy link
Author

janrito commented Apr 27, 2013

I see what you mean. Is there any difference in the latex output (not preamble, etc) when a full document is prepared rather than a fragment?

@fletcher
Copy link
Owner

No. The actual body is the same either way.

F

Sent from my iPhone

On Apr 27, 2013, at 7:00 AM, Sla [email protected] wrote:

I see what you mean. Is there any difference in the latex output (not
preamble, etc) when a full document is prepared rather than a fragment?


Reply to this email directly or view it on
GitHubhttps://github.com//issues/145#issuecomment-17114301
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants