From: Baoqiu Cui <cbaoqiu@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: Custom docbook stylesheets.
Date: Mon, 22 Jun 2009 23:13:30 -0700 [thread overview]
Message-ID: <byctz275vg5.fsf@yahoo.com> (raw)
In-Reply-To: kpskhs6qe0.fsf@flexo.cle.vtiinstruments.lcl
Hi Dale,
Dale Smith <dsmith@vtiinstruments.com> writes:
> Dale Smith <dsmith@vtiinstruments.com> writes:
>
>>>>> 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.
>>
>> Well, it took me a while, but it found it. It's the format-spec
>> function. (Actually, http://edward.oconnor.cx/2009/06/format-spec
>> clued me in.)
>>
>> I'll have a go at it today and see if I can send in a patch.
>
> Ok. This works for me. Docs are not updated. That would push me
> over the 10 line limit. ;^)
Thanks for working on this patch, which looks very good to me! Yes, I
think format-spec is the right way to go, and it does make the command
format more flexible.
> Now we can easily add other options, like %s for stylesheets or
> whatever. Maybe something like %p to set parameters. (As in the
> --stringparam option to xsltproc).
I like %s (for stylesheets). For %p, I guess we can use it to format a
*set* of parameters.
> What would be cool is a way to allow the user to *add* custom spec
> chars to the default set. (hint hint)
Will we make it *too* flexible by doing this? ;-)
Thanks again!
Baoqiu
next prev parent reply other threads:[~2009-06-23 6:13 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
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 [this message]
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=byctz275vg5.fsf@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
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).