emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Baoqiu Cui <cbaoqiu@yahoo.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Custom docbook stylesheets.
Date: Thu, 28 May 2009 07:31:26 +0200	[thread overview]
Message-ID: <8D94BFF5-12B8-49EF-9FF9-8BFD7BE30276@gmail.com> (raw)
In-Reply-To: <byctz36pe2c.fsf@muchbodyking-lm.corp.yahoo.com>


On May 27, 2009, at 8:59 PM, Baoqiu Cui wrote:

> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On May 27, 2009, at 2:13 AM, Dale Smith wrote:
>>
>>> Greetings List,
>>>
>>> I was suprised an pleased to discover that the docbook exporter has
>>> the ability to apply the stylesheets to transform to fo and to also
>>> process that to pdf.  Somehing I'd like to see is a document  
>>> specific
>>> way to specify the stylesheet.  I tried setting
>>> org-export-docbook-xslt-proc-command in a "Local Variables:"  
>>> section,
>>> but it seems the variable is being used from a different buffer.
>>>
>>> So, what do you think about some kind of document property to
>>> overrride a global setting?
>
> Thanks for the suggestion, Dale.  I think this is a very good idea,  
> and
> I will try to make the changes to support local variables overriding  
> the
> global settings.
>
> Maybe we can have a separate variable called
> org-export-docbook-stylesheet to make it easier to set in each file  
> and
> flexible to use (in org-export-docbook-xslt-proc-command, etc.).  What
> do you think?
>
>>> The current org-export-docbook-xslt-proc-command is a format string,
>>> with a fixed order of arguments (the fo filename and then the input
>>> docbook filname).  Thats probably good enough for most (all?) xslt
>>> processors, but things may be more limited when it comes to also
>>> specifying the stylesheet.  Do we need to have some kind of special
>>> markers in the format string for where the different options go?
>>> Something like $i $o and $s (for in, out, and stysheet)?
>
> I thought about doing something similar to make the commands easier to
> set, but stopped pursuing that after seeing the format string style
> worked fine.  I am not sure if any other Emacs modes/packages have  
> done
> something like this, i.e. using (semi)named arguments.
>
>> Maybe we could have something like #+XSLT: or so to configure buffer-
>> local setting for this variable......
>
> Thanks for the suggestion, Carsten!  It's a little hard for me to  
> decide
> which way is better to specify the stylesheet: "#+XSLT" or "Local
> Variables:".  Maybe "#+XSLT" is better?  I don't see many local
> variables being used in Org mode...  Please advise.

This is only a mater of convenience.  The #+ syntax is easier to
set up and refresh, so I prefer it for stuff that is frequently changed.
But you can also use file variables of course....

- Carsten

  reply	other threads:[~2009-05-28  5:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27  0:13 Custom docbook stylesheets Dale Smith
2009-05-27  9:39 ` Carsten Dominik
2009-05-27 18:59   ` Baoqiu Cui
2009-05-28  5:31     ` Carsten Dominik [this message]
2009-05-28 14:17       ` Dale Smith
2009-06-23 15:29       ` Dale Smith
2009-06-22 15:25     ` Dale Smith
2009-06-22 19:05       ` Dale Smith
2009-06-23  6:13         ` Baoqiu Cui
2009-06-23 15:10           ` Dale Smith
2010-05-03 19:25           ` Dale P. Smith
2010-05-13  5:39             ` Carsten Dominik
2010-05-13 14:11               ` Dale P. Smith
2010-05-13 18:19                 ` Carsten Dominik
2010-05-13 18:51                   ` Dale P. Smith
2010-05-13 19:45                     ` Baoqiu Cui
2010-05-13 21:09                       ` Dale P. Smith
2010-05-13 23:15                         ` [PATCH] " Baoqiu Cui
2010-05-14 11:39                           ` Carsten Dominik
2010-05-15  4:01                             ` Baoqiu Cui
2010-05-15  6:13                               ` Carsten Dominik
2010-05-13 19:06               ` Baoqiu Cui

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=8D94BFF5-12B8-49EF-9FF9-8BFD7BE30276@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=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
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).