Re: Debian Live Manual, sisu3

On Sat, Dec 10, 2011 at 9:32 PM, chals <chals@altorricon.com> wrote:

On Thu, Dec 8, 2011 at 2:13 PM, Ralph Amissah <ralph.amissah@gmail.com> wrote:

For Debian Live Manual to use sisu3: (a) a decision needs to be made as to how
(and where) output files should be presented; (b) a change needs to be made in
where processing instructions are given, and; (c) where the configuration
directory (_sisu) is located; (d) to this end a suggestion is made as to what
initial changes need to be made to the Makefile, (including addressing the
issue of generating missing css files). [repost under new heading, with minor
addition (related to document manifest), I would prefer replies to be posted to
this thread]

Ralph: Thank you very much for your patience and time and also for your help.

Following your recommendations sisu3 works locally and everything seems just fine.
You know that there is still some work to do but thanks to you, the CSS which seemed to be one of the main concerns is now found where it should be.

In short, after all the processing, the people who want to read live-manual either have to choose $${FORMAT}/$${LANGUAGE} if selecting the "filetype" output or $${LANGUAGE}/$${FORMAT} if selecting the "language" output. Well, the committed changes build live-manual by "language" but after talking to you and seeing all the improvements that you have made, I have realised that it could even be easier and more convenient to build by "filetype". This could also ease the process of building the .debs as they are named live-manual-$${FORMAT} (I'm not sure about this last statement, it is just a wild guess)

So I have everything ready to commit the changes "by filetype" on top of the "by language" or reverting the latter to send the former. I think that it would be great if someone could help deciding on this as both methods work and keeping in mind that these commits need having sisu3 in the autobuild when it is ready.