From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Re: How to get \\ in title or author? Date: Wed, 09 Sep 2009 01:00:59 -0400 Message-ID: <23362.1252472459@gamaville.dokosmarshall.org> References: <87ocpmc3mk.fsf@mundaneum.com> <87tyze4c7b.fsf@bzg.ath.cx> <87eiqhc1tt.fsf@mundaneum.com> <877hwadsb0.fsf@bzg.ath.cx> <87my55rw1b.fsf@mundaneum.com> <878wgou706.fsf@bzg.ath.cx> Reply-To: nicholas.dokos@hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlFKd-0002SI-RR for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 01:02:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlFKZ-0002S6-CF for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 01:02:59 -0400 Received: from [199.232.76.173] (port=50802 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlFKZ-0002S3-9l for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 01:02:55 -0400 Received: from vms173015pub.verizon.net ([206.46.173.15]:33279) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlFKY-0007Ug-Ku for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 01:02:54 -0400 Received: from gamaville.dokosmarshall.org ([98.110.172.159]) by vms173015.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KPO00A3BTXNVAK4@vms173015.mailsrvcs.net> for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 00:00:59 -0500 (CDT) In-reply-to: Message from Bastien of "Wed\, 09 Sep 2009 11\:33\:29 +0800." <878wgou706.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: =?us-ascii?Q?=3D=3Fiso-8859-1=3FQ=3FS=3DE9bastien=3F=3D?= Vauban , emacs-orgmode@gnu.org Bastien wrote: > S=C3=A9bastien Vauban writes: >=20 > >> Maybe \linebreak is less context-sensitive than \newline, which would = mean > >> that there are more contexts (like \title and \author) in which it beh= aves > >> as expected. Just a guess. > > > > I've asked the question on FCTT (fr.comp.text.tex) and already got an a= nswer > > of Maneul Pegourie-Gonnard (who is expert on that matter): > > > > http://groups.google.fr/group/fr.comp.text.tex/browse_thread/thread/1b1= af2e5291270e2# > > > > Sorry (for the others), it's in French. >=20 > Merci! Here is a summary: >=20 > - none of \\ \linebreak or \newline change a paragraph, they just start > a new line >=20 > - with \linebreak, LaTeX tries to justify the resulting text, not with > \newline >=20 > - \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... >=20 > - \\ 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. >=20 > In environments like \flushleft \flushright \centering \raggedleft > \raggedright, \\ doesn't have its normal definition (whereas \newline > behaves normally). >=20 > - \newline is the version of \\ with no argument >=20 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. Thanks, Nick