emacs-wiki-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[emacs-wiki-discuss] Re: Muse-wiki milestone reached


From: drkm
Subject: [emacs-wiki-discuss] Re: Muse-wiki milestone reached
Date: Sun, 10 Jul 2005 02:01:10 +0200
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (windows-nt)

Xavier Maillard writes:

> On 9 Jul 2005, Michael Olson uttered the following:

>> Sounds interesting! Can you point me to some documentation
>> concerning the form that the XML should have? I know the syntax
>> of XML somewhat, but I don't know how an outputted XML document
>> should "look" in this case.

> Here is the problem :) Depending of what muse is used, the XML
> may be different.

> For example, if I write a "book" using Muse, I don't want the XML
> to be the same as if I was writting a journal/blog entry.

  Hum, I don't think so.  The base element of Muse is the page.
So each Muse file will result in an XML document, whose the root
is a PAGE (or all Muse file of a specific project will go in a
unique document, with several page, or an ELisp function will
select the pages to output, etc.).

  The following element (when going deeper) is something like a
section (for example in Planner: tasks, schedule, notes, etc.).
And so on.  Planner can create its own elements (tasks can have a
specific format in XML).

  Indeed, you will have different sets of XSLT scripts.  For
example, a set that interpret the pages as Blog entries.  Or more
as Wiki entries.  Or as ...  Muse projects can associates XSLT
scripts with projects.  And the XSLT transformation itself can
easily be started by Muse, with the right arguments.

  But really, I don't know Muse nor EmacsWiki enough.  Maybe I'm
completely wrong.  But I'll be really confused if we'll not be
able to identify a generic (or not so generic) structure for Muse
pages.

--drkm





reply via email to

[Prev in Thread] Current Thread [Next in Thread]