* Bugs when converting to LaTeX
@ 2009-10-26 15:46 Sébastien Vauban
2009-10-26 19:17 ` Carsten Dominik
0 siblings, 1 reply; 7+ messages in thread
From: Sébastien Vauban @ 2009-10-26 15:46 UTC (permalink / raw)
To: emacs-orgmode-mXXj517/zsQ
Hello,
Here an ECM (Example Complete and Minimal) showing two bugs occurring when
converting to LaTeX.
--8<---------------cut here---------------start------------->8---
* Bugs
** Conversion to texttt
- Put the command =runit= "in hard"
Not done because of the following word being between quotes...
** Paragraph disappears...
- Add the code if
+ it is above 0
+ it is less than 10
For the other cases, do nothing.
The above paragraph is NOT converted to LaTeX! You don't see it in the
PDF...
--8<---------------cut here---------------end--------------->8---
The second one is more important, as some text is just ignored in the
conversion process.
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Bugs when converting to LaTeX 2009-10-26 15:46 Bugs when converting to LaTeX Sébastien Vauban @ 2009-10-26 19:17 ` Carsten Dominik 2009-10-27 8:47 ` Sébastien Vauban 0 siblings, 1 reply; 7+ messages in thread From: Carsten Dominik @ 2009-10-26 19:17 UTC (permalink / raw) To: Sébastien Vauban; +Cc: emacs-orgmode On Oct 26, 2009, at 4:46 PM, Sébastien Vauban wrote: > Hello, > > Here an ECM (Example Complete and Minimal) showing two bugs > occurring when > converting to LaTeX. > > > --8<---------------cut here---------------start------------->8--- > * Bugs > > ** Conversion to texttt > > - Put the command =runit= "in hard" > > Not done because of the following word being between quotes... > Fixed. > > ** Paragraph disappears... > > - Add the code if > + it is above 0 > + it is less than 10 > > For the other cases, do nothing. > > The above paragraph is NOT converted to LaTeX! You don't see it > in the > PDF... 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. - Carsten ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bugs when converting to LaTeX 2009-10-26 19:17 ` Carsten Dominik @ 2009-10-27 8:47 ` Sébastien Vauban 2009-10-28 9:17 ` Carsten Dominik 0 siblings, 1 reply; 7+ messages in thread From: Sébastien Vauban @ 2009-10-27 8:47 UTC (permalink / raw) To: emacs-orgmode-mXXj517/zsQ Hi Carsten, Carsten Dominik wrote: > On Oct 26, 2009, at 4:46 PM, Sébastien Vauban wrote: > >> Hello, >> >> Here an ECM (Example Complete and Minimal) showing two bugs occurring when >> converting to LaTeX. >> >> >> --8<---------------cut here---------------start------------->8--- >> * Bugs >> >> ** Conversion to texttt >> >> - Put the command =runit= "in hard" >> >> Not done because of the following word being between quotes... >> > > Fixed. OK. Thanks. >> ** Paragraph disappears... >> >> - Add the code if >> + it is above 0 >> + it is less than 10 >> >> For the other cases, do nothing. >> >> The above paragraph is NOT converted to LaTeX! You don't see it in the >> PDF... > > 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... 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é./ 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. 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 correctly converted. --8<---------------cut here---------------end--------------->8--- Best regards, Seb -- Sébastien Vauban _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode-mXXj517/zsQ@public.gmane.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Re: Bugs when converting to LaTeX 2009-10-27 8:47 ` Sébastien Vauban @ 2009-10-28 9:17 ` Carsten Dominik 2009-11-06 11:34 ` Sébastien Vauban 0 siblings, 1 reply; 7+ messages in thread From: Carsten Dominik @ 2009-10-28 9:17 UTC (permalink / raw) To: Sébastien Vauban; +Cc: emacs-orgmode 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bugs when converting to LaTeX 2009-10-28 9:17 ` Carsten Dominik @ 2009-11-06 11:34 ` Sébastien Vauban 2009-11-06 11:52 ` Carsten Dominik 0 siblings, 1 reply; 7+ messages in thread From: Sébastien Vauban @ 2009-11-06 11:34 UTC (permalink / raw) To: emacs-orgmode-mXXj517/zsQ Hi Carsten, Carsten Dominik wrote: > 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. I'd be glad my level for debugging Emacs Lisp was that high. Unfortunately, not sure it is... How do you do in such a case? Adding edebug calls in some functions? Other way? >> 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). > > 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. 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 '(" ('\"{" "- ., :!?;'\")}\\" " \r\n,\"'" "." 4)) --8<---------------cut here---------------end--------------->8--- None of the above 2 mentionned problem seems to disappear, though, on this ECM: --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 vite vis-à-vis du marché./ 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. 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 correctly converted. --8<---------------cut here---------------end--------------->8--- >> 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? Yes. I mean: would I write pure LaTeX from scratch, I would insert `~' here and there when I want an unbreakable space to be produced (resulting 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 problems, such as the second above mentionned (emphasis not correct after word "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 -- Sébastien Vauban _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode-mXXj517/zsQ@public.gmane.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Re: Bugs when converting to LaTeX 2009-11-06 11:34 ` Sébastien Vauban @ 2009-11-06 11:52 ` Carsten Dominik 2009-11-09 8:58 ` Sébastien Vauban 0 siblings, 1 reply; 7+ messages in thread From: Carsten Dominik @ 2009-11-06 11:52 UTC (permalink / raw) To: Sébastien Vauban; +Cc: emacs-orgmode On Nov 6, 2009, at 12:34 PM, Sébastien Vauban wrote: > Hi Carsten, > > Carsten Dominik wrote: >> 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. > > I'd be glad my level for debugging Emacs Lisp was that high. > 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 > 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é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). >> >> 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. > > 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 > '(" ('\"{" > "- ., :!?;'\")}\\" > " > \n,\"'" > "." > 4)) > --8<---------------cut here---------------end--------------->8--- > > None of the above 2 mentionned problem seems to disappear, though, > on this > ECM: > > --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 > vite vis-à-vis du marché./ > > 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. 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 > correctly > converted. > --8<---------------cut here---------------end--------------->8--- > > >>> 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? > > Yes. I mean: would I write pure LaTeX from scratch, I would insert > `~' here > and there when I want an unbreakable space to be produced (resulting > 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 > problems, such > as the second above mentionned (emphasis not correct after word > "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 > > -- > Sébastien 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 ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Bugs when converting to LaTeX 2009-11-06 11:52 ` Carsten Dominik @ 2009-11-09 8:58 ` Sébastien Vauban 0 siblings, 0 replies; 7+ messages in thread From: Sébastien Vauban @ 2009-11-09 8:58 UTC (permalink / raw) To: emacs-orgmode-mXXj517/zsQ Hi Carsten, Carsten Dominik wrote: > On Nov 6, 2009, at 12:34 PM, Sébastien Vauban wrote: >> Carsten Dominik wrote: >>> On Oct 27, 2009, at 9:47 AM, Sébastien Vauban wrote: >>>> 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. >>> >>>> - 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). >>> >>> 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. >> >> 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 >> '(" ('\"{" >> "- ., :!?;'\")}\\" >> " >> \n,\"'" >> "." >> 4)) >> --8<---------------cut here---------------end--------------->8--- >> >> None of the above 2 mentionned problem seems to disappear. I rephrase my sentence: the problem *does not* disappear. Have I missed something when setting `org-emphasis-regexp-components'? --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 vite vis-à-vis du marché./ - Le /challenge/ : efficacité et rapidité... --8<---------------cut here---------------end--------------->8--- Best regards, Seb -- Sébastien Vauban _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode-mXXj517/zsQ@public.gmane.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-11-09 8:58 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-10-26 15:46 Bugs when converting to LaTeX Sébastien Vauban 2009-10-26 19:17 ` Carsten Dominik 2009-10-27 8:47 ` Sébastien Vauban 2009-10-28 9:17 ` Carsten Dominik 2009-11-06 11:34 ` Sébastien Vauban 2009-11-06 11:52 ` Carsten Dominik 2009-11-09 8:58 ` Sébastien Vauban
Code repositories for project(s) associated with this public inbox https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).