From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Bugs when converting to LaTeX
Date: Mon, 09 Nov 2009 09:58:48 +0100 [thread overview]
Message-ID: <87ljigqdkn.fsf@mundaneum.com> (raw)
In-Reply-To: 52A8F1F4-F9A6-4AA9-8EDD-2DA37428DCE6@gmail.com
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
prev parent reply other threads:[~2009-11-09 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ljigqdkn.fsf@mundaneum.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).