From: Tim Burt <tcburt@rochester.rr.com>
To: nicholas.dokos@hp.com
Cc: Bastien <bastienguerry@googlemail.com>,
emacs-orgmode@gnu.org,
"Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Subject: Re: Re: How to get \\ in title or author?
Date: Wed, 9 Sep 2009 17:08:46 -0400 [thread overview]
Message-ID: <19112.6494.887207.1393@nitrogen.burtket> (raw)
In-Reply-To: <23362.1252472459@gamaville.dokosmarshall.org>
Nick Dokos writes:
> Bastien <bastienguerry@googlemail.com> wrote:
>
> > Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> >
> > >> Maybe \linebreak is less context-sensitive than \newline, which would mean
> > >> that there are more contexts (like \title and \author) in which it behaves
> > >> as expected. Just a guess.
> > >
> > > I've asked the question on FCTT (fr.comp.text.tex) and already got an answer
> > > of Maneul Pegourie-Gonnard (who is expert on that matter):
> > >
> > > http://groups.google.fr/group/fr.comp.text.tex/browse_thread/thread/1b1af2e5291270e2#
> > >
> > > Sorry (for the others), it's in French.
> >
> > Merci! Here is a summary:
> >
> > - none of \\ \linebreak or \newline change a paragraph, they just start
> > a new line
> >
> > - with \linebreak, LaTeX tries to justify the resulting text, not with
> > \newline
> >
> > - \linebreak can take an argument to let LaTeX decides whether the line
> > should be broken or not. The default \linebreak always triggers a
> > break, but \linebreak[2] will let LaTeX decides depending on whether
> > the result is acceptable or not, and \linebreak[0] prevents any line
> > break...
> >
> > - \\ can take two arguments: one star and one digit. The star prevents
> > the line break to trigger a page break, and the digit lets you add a
> > vertical space between the two lines.
> >
> > In environments like \flushleft \flushright \centering \raggedleft
> > \raggedright, \\ doesn't have its normal definition (whereas \newline
> > behaves normally).
> >
> > - \newline is the version of \\ with no argument
> >
>
> Bastien,
>
> Thanks for the summary. There is still one problem, I think, with #+AUTHOR:
>
> \author{one \\ two}
>
> and
>
> \author{one \linebreak two}
>
> behave differently (the \linebreak has no effect), so if one wants the
> first behavior, the exporter's penchant to change \\ to
> \\textbackslash{} will not allow it. I'm not sure why \title and \author
> behave differently: I guess it's because \author is expanded inside a
> \tabular, whereas \title is not.
Indeed, multiple authors should be separated by two backslashes (\\)
in the \author{} command[*] in the standard LaTeX classes
(e.g. article, report, book). Nick has correctly noted that the
argument of \author{} is used inside a tabular environment, and \\ has
a special meaning that should be added to Bastien's summary above.
- In a tabular environment the \\ is necessary to signal the
end of one row and the beginning of the next.
So, from the perspective of standard LaTeX classes, any instance of \\
in the \author{} command should not be converted during export.
Good afternoon,
Tim
[*] Bastien has also reported that \\ works in a recent message to the
mailing list. If that was an experimental result, then this reply
only adds theoretical support so that others don't have to get out
their LaTeX debugging skills and "dust them off" (as Nick said ;-).
next prev parent reply other threads:[~2009-09-09 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 12:59 How to get \\ in title or author? Sébastien Vauban
2009-09-07 22:33 ` Bastien
2009-09-08 7:50 ` Sébastien Vauban
2009-09-08 3:33 ` Bastien
2009-09-08 21:01 ` Sébastien Vauban
2009-09-09 3:33 ` Bastien
2009-09-09 5:00 ` Nick Dokos
2009-09-09 9:47 ` Sébastien Vauban
2009-09-09 10:34 ` Bastien
2009-09-10 14:30 ` Sébastien Vauban
2009-09-10 18:02 ` Carsten Dominik
2009-09-10 18:30 ` Nick Dokos
2009-09-09 14:26 ` Nick Dokos
2009-09-09 14:43 ` Bastien
2009-09-10 14:27 ` Sébastien Vauban
2009-09-09 21:08 ` Tim Burt [this message]
2009-09-09 2:15 ` Brian van den Broek
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=19112.6494.887207.1393@nitrogen.burtket \
--to=tcburt@rochester.rr.com \
--cc=bastienguerry@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
--cc=wxhgmqzgwmuf@spammotel.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).