emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] Re: Bugs when converting to LaTeX


From: Carsten Dominik
Subject: Re: [Orgmode] Re: Bugs when converting to LaTeX
Date: Wed, 28 Oct 2009 10:17:35 +0100

Hi Sebastien,


On Oct 27, 2009, at 9:47 AM, Sébastien 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 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. 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éliser ce qui est dans le code COBOL, comment faire ?
   Discussions avec le business, relire le COBOL ? Chez nous, la
tarification n'est pas modélisée. Pourtant, c'est là qu'il faut aller
   vite vis-à-vis du marché./

You need to configure `org-emphasis-regexp-components' and increase the number of newlines allowed in these expressions.


The above "question" (in a FAQ) should be in italics. But, to do so, we
   have to split it in multiple chunks in italics:

- /S'il faut remodéliser ce qui est dans le code COBOL, comment faire ?/
   /Discussions avec le business, relire le COBOL ?/ /Chez nous, la
tarification n'est pas modélisée./ /Pourtant, c'est là qu'il faut aller
   vite vis-à-vis du marché./

 - Le /challenge/ : efficacité et rapidité...

Here, the word challenge is not in italics because the following character
   is an unbreakable space (*not* a normal space).

Note -- I'm forced to use such characters in order to get my 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- emphasis-regexp-components to the end of the second string of characters, these are the characters allowed after an emphasis string.

HTH

- Carsten





reply via email to

[Prev in Thread] Current Thread [Next in Thread]