Christian Straßer <[EMAIL PROTECTED]> writes:

> Hello everybody,
>
> I'm not sure for what discussion list my problem is better, but as
> it is planner-related I decided to post it here.  I have the
> problem, that when I insert planner-pages in pages of other
> muse-projects with <insert file="filename"> then the
> planner-specific css-styles are not working properly, although I use
> the same style sheet for the muse-html publishing style. The mistake
> is related to tasks and notes, which are published like follows:

I hadn't thought before about the possibility of including Muse pages
that are published to different styles.  The problem occurs because
the markup for the current page is used on the inserted page.

I've start to work on a fix, but I want to get some feedback from the
community at large before I change anything.

There are several possibilities.  One is to allow the publishing style
to be specified as part of the <include> tag.  For example:

  <include file="../plans/Work.muse" style="planner-html">

Another possibility would be to try and figure out what publishing
style to use for the remote file based on its entry in
muse-project-alist.  Muse has logic that can be used to pick the
remote publishing style that has the same extension as the output of
the current file will have.  Then, the following would "just work".

  <include file="../plans/Work.muse">

So does anyone see any use case for the first possibility?  Does
anyone feel particularly strongly that the second possibility is
better?

(Or we could even do the second, but allow the first, if someone
specifies something for "style".  I'd still like to know at least one
person would bother using it, though, before I implement that.)

-- 
Michael Olson -- FSF Associate Member #652 -- http://www.mwolson.org/
Interests: Lisp, text markup, protocols -- Jabber: mwolson_at_hcoop.net
  /` |\ | | | Projects: Emacs, Muse, ERC, EMMS, Planner, ErBot, DVC
 |_] | \| |_| Reclaim your digital rights by eliminating DRM.
      See http://www.defectivebydesign.org/what_is_drm for details.

Attachment: pgpf5eQB0otLe.pgp
Description: PGP signature

_______________________________________________
Planner-el-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/planner-el-discuss

Reply via email to