emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Baoqiu Cui <cbaoqiu@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: docbook export-special
Date: Wed, 27 May 2009 11:46:10 -0700	[thread overview]
Message-ID: <byc1vqaqt8t.fsf@muchbodyking-lm.corp.yahoo.com> (raw)
In-Reply-To: f46c52560905262329m5259b002rb7e32c4f848f8560@mail.gmail.com

Rustom Mody <rustompmody@gmail.com> writes:

> Baoqiu wrote:
>> What do you mean by export-special?
>
> Well the latest org comes with a contributed org-special-blocks.el
> [sorry I misnamed it]
>
>> Do you mean exporting blocks that look like the following lines?
>
>> #+begin_xyz
>> ...
>> #+end_xyz
>
> Yes I guess that would be what I want.

Thanks for the confirmation, Rustom.  Carsten and I had several email
exchanges on this topic last month, and we decided to not support such
special blocks in DocBook exporter (see the following email).

Can you use #+BEGIN_DOCBOOK ... #+END_DOCBOOK instead to achieve what
you want?

Thanks,
Baoqiu

> From: Carsten Dominik <carsten.dominik@gmail.com>
> To: Baoqiu Cui <cbaoqiu@yahoo.com>
> Cc: Carsten Dominik <dominik@science.uva.nl>
> Subject: Re: [Orgmode] Re: markup in environments in latex export
> Date: Wed, 29 Apr 2009 21:24:27 +0200
> 
> Hi Baoqiu,
> 
> thank you very much for your input.  I largely agree with
> your assessment.
> 
> - Carsten
> 
> On Apr 27, 2009, at 7:37 PM, Baoqiu Cui wrote:
> 
> > Hi Carsten,
> >
> > I thought about this during the weekend, and it seemed to me that it  
> > is
> > better to let DocBook exporter ignore such arbitrary ``#+begin_xyz
> > ... #+end_xyz'' blocks.  There are several reasons:
> >
> >  1. LaTeX and DocBook use very different tag/element names.  Even if  
> > we
> >     can find equivalent elements in DocBook for ``xyz'', supporting
> >     such LaTeX specific markups can confuse users.
> >
> >  2. For many ``xyz''s that are supported in LaTeX, we may not be able
> >     to find equivalent elements in DocBook.  There is not similar  
> > thing
> >     in DocBook to do what <div class="xyz"> ... </div> does in HTML,
> >     AFAIK.
> >
> >  3. Supporting these blocks may open a big door for making exported
> >     DocBook XML files invalid.
> >
> > Personally I don't think it is even a good idea to support this LaTeX
> > feature in Org mode.  This feature may benefit a small number of
> > Org+LaTeX users, in some uncommon use cases, but in general it hurts
> > Org-mode's simplicity and cleanness.
> >
> > If I were Chris, I would not mind using real LaTeX syntax in
> >
> > \begin{xyz}
> > ...
> > \end{xyz}
> >
> > Thanks,
> > Baoqiu

next prev parent reply	other threads:[~2009-05-27 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 14:01 docbook export-special Rustom Mody
2009-05-26 23:49 ` Baoqiu Cui
2009-05-27  6:29 ` Rustom Mody
2009-05-27 18:46   ` Baoqiu Cui [this message]
2009-05-28  7:47   ` Rustom Mody
2009-05-28  9:00     ` Carsten Dominik
2009-05-28 12:16       ` Rustom Mody
2009-05-28 16:49         ` Baoqiu Cui
2009-06-03 12:28         ` Rustom Mody

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=byc1vqaqt8t.fsf@muchbodyking-lm.corp.yahoo.com \
    --to=cbaoqiu@yahoo.com \
    --cc=emacs-orgmode@gnu.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

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).