From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: export of emphasized link Date: Tue, 1 Jun 2010 09:44:25 +0200 Message-ID: <13B6AC83-0AB4-46D0-AD86-F02210B33F93@gmail.com> References: <4C025FCA.7080503@alumni.ethz.ch> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=42333 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OJMms-0004kU-BI for emacs-orgmode@gnu.org; Tue, 01 Jun 2010 04:25:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OJMmq-0003BT-IR for emacs-orgmode@gnu.org; Tue, 01 Jun 2010 04:25:26 -0400 Received: from ey-out-1920.google.com ([74.125.78.147]:47237) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OJMmq-0003BO-Bi for emacs-orgmode@gnu.org; Tue, 01 Jun 2010 04:25:24 -0400 Received: by ey-out-1920.google.com with SMTP id 13so497834eye.34 for ; Tue, 01 Jun 2010 01:25:23 -0700 (PDT) In-Reply-To: <4C025FCA.7080503@alumni.ethz.ch> 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: Michael Brand Cc: Org Mode Hi Michael, On May 30, 2010, at 2:53 PM, Michael Brand wrote: > Hi all, > > An org-mode line with an emphasized link like that one taken from > current Worg: > ---------------------------------------------------------------------- > *Drop an email to [[mailto:bzg%20AT%20altern%20DOT%20org][Bastien]]* > mentioning your username on repo.or.cz I would write this as *Drop an email to* [[mailto:bzg%20AT%20altern%20DOT%20org][Bastien]] i.e. take the link out of the bold section. > ---------------------------------------------------------------------- > shows the bold face in the Emacs Org buffer like expected. But it > does not convert the emphasis and still shows `*' when exported to > some formats: > - HTML: not converted > - LaTeX: could not check because of a missing setup on my side, > from the source code I guess that it converts > - DocBook: not converted > - ...: don't know about other formats and what they should support > > After removing org-bracket-link-regexp from org-html-expand What do you mean by this sentence? What exactly did you do? > and org-docbook-expand the HTML and DocBook exports _are_ converted > and look similar to the highlighting in the Emacs Org buffer. But > the doc string of both functions tell: > "If there are links in the string, don't modify these." > Why should links be modified in org-mode but not in HTML or DocBook? > > If there will be any change I would also like this: > ---------------------------------------------------------------------- > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -3285,6 +3285,7 @@ example *bold*, _underlined_ and /italic/. > This variable > characters, the face to be used by font-lock for highlighting in Org- > mode > Emacs buffers, and the HTML tags to be used for this. > For LaTeX export, see the variable `org-export-latex-emphasis-alist'. > +For DocBook export, see the variable `org-export-docbook-emphasis- > alist'. > Use customize to modify this, or restart Emacs after changing it." > :group 'org-appearance > :set 'org-set-emph-re > ---------------------------------------------------------------------- I have applied this patch. > > And: wouldn't it be nice for maintenance to have only one function > for some sets of functions like > - org-html-expand, org-docbook-expand and possibly more > - org-html-do-expand, org-docbook-do-expand and possibly more > - org-export-html-convert-emphasize, org-export-docbook-convert- > emphasize and possibly more > - org-export-html-convert-sub-super, org-export-docbook-convert-sub- > super and possibly more > - possibly more > because they have almost all code in common. Yes, that would be nice. It would also be nice if all exporters would basically use the same code - but this is not how things happened, unfortunately. - Carsten