From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Bugs when converting to LaTeX Date: Fri, 6 Nov 2009 12:52:41 +0100 Message-ID: <52A8F1F4-F9A6-4AA9-8EDD-2DA37428DCE6@gmail.com> References: <87vdi26tv4.fsf@mundaneum.com> <2772DE22-D2EC-48F7-9703-FE1FFA68C91E@gmail.com> <87r5spp6ip.fsf@mundaneum.com> <87ws2328f9.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 1N6NN5-00017E-Fa for emacs-orgmode@gnu.org; Fri, 06 Nov 2009 06:52:51 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6NN0-000168-Cl for emacs-orgmode@gnu.org; Fri, 06 Nov 2009 06:52:50 -0500 Received: from [199.232.76.173] (port=60607 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6NMz-000165-QK for emacs-orgmode@gnu.org; Fri, 06 Nov 2009 06:52:45 -0500 Received: from mail-ew0-f228.google.com ([209.85.219.228]:41596) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N6NMz-00077T-7s for emacs-orgmode@gnu.org; Fri, 06 Nov 2009 06:52:45 -0500 Received: by ewy28 with SMTP id 28so1036369ewy.42 for ; Fri, 06 Nov 2009 03:52:44 -0800 (PST) In-Reply-To: <87ws2328f9.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 On Nov 6, 2009, at 12:34 PM, S=E9bastien Vauban wrote: > Hi Carsten, > > Carsten Dominik wrote: >> On Oct 27, 2009, at 9:47 AM, S=E9bastien Vauban wrote: >>>> >>>> Unfortunately, this is a weakness of the list parser in the LaTeX >>>> exporter. It cannot handle this kind of post-subitem text in an =20 >>>> item list. >>>> 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. > > I'd be glad my level for debugging Emacs Lisp was that high. =20 > Unfortunately, > not sure it is... Hi Sebastian, this is not really an issue for debugging. The list parser used by the LaTeX exporter simply does not cater for text intermittent in a list, and the Lisp structure created by the parser does not have a way to represent such text. So this is not "a bug" you'd have to find, but rather new code which would have to be written..... > > How do you do in such a case? Adding edebug calls in some =20 > functions? Other > way? yes, or (debug) - Carsten > > >>> 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 = =20 >>> faut 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 >>> character is an unbreakable space (*not* a normal space). >> >> Maybe you can fix this by adding your unbreakable space in org- >> emphasis-regexp-components to the end of the second string of =20 >> characters, >> these are the characters allowed after an emphasis string. > > Done it: > > --8<---------------cut here---------------start------------->8--- > ;; Add the unbreakable space as allowed character after an emphasis > ;; string, and modify the maximum number of newlines allowed in an > ;; emphasis > (setq org-emphasis-regexp-components > '(" ('\"{" > "- ., :!?;'\")}\\" > " =09 > \n,\"'" > "." > 4)) > --8<---------------cut here---------------end--------------->8--- > > None of the above 2 mentionned problem seems to disappear, though, =20 > on this > ECM: > > --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 > vite vis-=E0-vis du march=E9./ > > 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. Anyway, under Emacs, the normal space is > converted to an unbreakable one, each time it is before a ":" > character, so that's easy to do, but the output is not =20 > correctly > converted. > --8<---------------cut here---------------end--------------->8--- > > >>> 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? > > Yes. I mean: would I write pure LaTeX from scratch, I would insert =20 > `~' here > and there when I want an unbreakable space to be produced (resulting =20= > in a nice > PDF output). > > Here, as I write pure Org that gets converted, I need to insert a real > unbreakable space in my Org source. That's the source of some =20 > problems, such > as the second above mentionned (emphasis not correct after word =20 > "challenge"). > > Note -- Currently, that character is not converted to a tilde when > exporting to LaTeX. That could be a good option, though. > > Best regards, > Seb > > --=20 > S=E9bastien Vauban > > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten