From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Bugs when converting to LaTeX Date: Wed, 28 Oct 2009 10:17:35 +0100 Message-ID: References: <87vdi26tv4.fsf@mundaneum.com> <2772DE22-D2EC-48F7-9703-FE1FFA68C91E@gmail.com> <87r5spp6ip.fsf@mundaneum.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N34f3-0007TS-O6 for emacs-orgmode@gnu.org; Wed, 28 Oct 2009 05:17:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N34ey-0007Pl-3C for emacs-orgmode@gnu.org; Wed, 28 Oct 2009 05:17:45 -0400 Received: from [199.232.76.173] (port=50336 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N34ex-0007Pa-Ph for emacs-orgmode@gnu.org; Wed, 28 Oct 2009 05:17:39 -0400 Received: from mail-ew0-f228.google.com ([209.85.219.228]:34592) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N34ex-0006vA-FL for emacs-orgmode@gnu.org; Wed, 28 Oct 2009 05:17:39 -0400 Received: by ewy28 with SMTP id 28so582656ewy.42 for ; Wed, 28 Oct 2009 02:17:38 -0700 (PDT) In-Reply-To: <87r5spp6ip.fsf@mundaneum.com> 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: =?ISO-8859-1?Q?S=E9bastien_Vauban?= Cc: emacs-orgmode@gnu.org Hi Sebastien, On Oct 27, 2009, at 9:47 AM, S=E9bastien Vauban wrote: >> >> Unfortunately, this is a weakness of the list parser in the LaTeX =20 >> exporter. >> It cannot handle this kind of post-subitem text in an item list. =20 >> This really >> must be fixed, and it is on my list, but it is hard. > > Hopefully, this will be fixed soon, because this is quite scary. =20 > Though, that > does not imply it is easy to do... Be my guest to give it a try. > > Here a couple of other conversion bugs that I found: > > --8<---------------cut here---------------start------------->8--- > - /S'il faut remod=E9liser ce qui est dans le code COBOL, comment =20 > faire ? > Discussions avec le business, relire le COBOL ? Chez nous, la > tarification n'est pas mod=E9lis=E9e. Pourtant, c'est l=E0 qu'il = faut =20 > aller > vite vis-=E0-vis du march=E9./ You need to configure `org-emphasis-regexp-components' and increase =20 the number of newlines allowed in these expressions. > > The above "question" (in a FAQ) should be in italics. But, to do =20= > so, we > have to split it in multiple chunks in italics: > > - /S'il faut remod=E9liser ce qui est dans le code COBOL, comment =20 > faire ?/ > /Discussions avec le business, relire le COBOL ?/ /Chez nous, la > tarification n'est pas mod=E9lis=E9e./ /Pourtant, c'est l=E0 qu'il = faut =20 > aller > vite vis-=E0-vis du march=E9./ > > - Le /challenge/ : efficacit=E9 et rapidit=E9... > > Here, the word challenge is not in italics because the following =20= > character > is an unbreakable space (*not* a normal space). > > Note -- I'm forced to use such characters in order to get my =20= > LaTeX PDF > correctly outputted. I don't understand that. Could you please elaborate? Maybe you can fix this by adding your unbreakable space in org-=20 emphasis-regexp-components to the end of the second string of =20 characters, these are the characters allowed after an emphasis string. HTH - Carsten