From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim Burt Newsgroups: gmane.emacs.orgmode Subject: Re: Re: How to get \\ in title or author? Date: Wed, 9 Sep 2009 17:08:46 -0400 Message-ID: <19112.6494.887207.1393@nitrogen.burtket> 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> <23362.1252472459@gamaville.dokosmarshall.org> Reply-To: tcburt@rochester.rr.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1252530573 16473 80.91.229.12 (9 Sep 2009 21:09:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 9 Sep 2009 21:09:33 +0000 (UTC) Cc: Bastien , emacs-orgmode@gnu.org, =?utf-8?Q?S=C3=A9bastien?= Vauban To: nicholas.dokos@hp.com Original-X-From: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Wed Sep 09 23:09:25 2009 Return-path: Envelope-to: geo-emacs-orgmode@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MlUPr-00014J-LZ for geo-emacs-orgmode@m.gmane.org; Wed, 09 Sep 2009 23:09:23 +0200 Original-Received: from localhost ([127.0.0.1]:36395 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlUPq-00020s-RU for geo-emacs-orgmode@m.gmane.org; Wed, 09 Sep 2009 17:09:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MlUPP-0001yw-JV for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 17:08:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MlUPL-0001t4-Lh for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 17:08:55 -0400 Original-Received: from [199.232.76.173] (port=60106 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MlUPL-0001sw-Jf for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 17:08:51 -0400 Original-Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:44805) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MlUPL-0006vm-8w for emacs-orgmode@gnu.org; Wed, 09 Sep 2009 17:08:51 -0400 Original-Received: from nitrogen.burtket ([66.66.26.230]) by hrndva-omta04.mail.rr.com with ESMTP id <20090909210848184.WHXI24259@hrndva-omta04.mail.rr.com>; Wed, 9 Sep 2009 21:08:48 +0000 In-Reply-To: <23362.1252472459@gamaville.dokosmarshall.org> X-Mailer: VM 8.0.12 under 22.2.1 (i486-pc-linux-gnu) X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (1203?) X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-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 Xref: news.gmane.org gmane.emacs.orgmode:17434 Archived-At: X-Import-Rejected-Reason: Exception: 'utf-8' codec can't encode characters in position 1-2: surrogates not allowed Nick Dokos writes: > Bastien wrote: >=20 > > S=E9bastien 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 behaves > > >> as expected. Just a guess. > > > > > > I've asked the question on FCTT (fr.comp.text.tex) and already g= ot an answer > > > of Maneul Pegourie-Gonnard (who is expert on that matter): > > > > > > http://groups.google.fr/group/fr.comp.text.tex/browse_thread/thr= ead/1b1af2e5291270e2# > > > > > > 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 whe= ther > > 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 pre= vents > > the line break to trigger a page break, and the digit lets you a= dd a > > vertical space between the two lines. > >=20 > > In environments like \flushleft \flushright \centering \raggedle= ft > > \raggedright, \\ doesn't have its normal definition (whereas \ne= wline > > behaves normally). > >=20 > > - \newline is the version of \\ with no argument > >=20 >=20 > Bastien, >=20 > Thanks for the summary. There is still one problem, I think, with #+= AUTHOR: >=20 > \author{one \\ two} >=20 > and >=20 > \author{one \linebreak two} >=20 > behave differently (the \linebreak has no effect), so if one wants t= he > first behavior, the exporter's penchant to change \\ to > \\textbackslash{} will not allow it. I'm not sure why \title and \au= thor > 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. =20 - 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 ;-).=20