[05:24] <wakr> hello
[10:50] <Admiral_Chicago> hey there fijam
[10:51] <Admiral_Chicago> have you been able to understand anything of the documentation  / writing it?
[10:52] <fijam> I do not quite get the rules of making the output html files out of docbook
[10:52] <fijam> And is it e.g supposed to work in yelp, or should it just work in a browser
[10:54] <fijam> I should have posted my questions to the mailing list I guess, but had no time/mind to do this. Next week I should finally have plenty of time.
[10:55] <Admiral_Chicago> fijam: both
[10:55] <Admiral_Chicago> it works with anything that can handle HTML
[10:56] <fijam> 'cause as it is now, the links to chapters in yelp won't work
[10:56] <fijam> neither for ubuntu, nor for xubuntu
[10:57] <fijam> I am working on a clean svn pull, and I doubt if I was already able to screw something up.
[11:00] <fijam> and since the links currently point to .html files, instead of .xml files, I bagan to thing that only html output matters. Apparently, I was wrong.
[11:02] <fijam> Admiral_Chicago, how is it supposed to work then?
[11:07] <Admiral_Chicago> fijam: give me  a second
[11:07] <fijam> sure.
[11:08] <Admiral_Chicago> fijam: right now, we had the docs working by pulling them in Firefox
[11:08] <Admiral_Chicago> this is probably broken as we recently moved the Ubuntu docs to the Xubuntu folder
[11:08] <Admiral_Chicago> i don't know if it is broken though
[11:11] <fijam> Since documentation in 'ubuntu' behaves in the same way, I presume that is how it works. As far as I managed to figure it out, the process of making a patch boils down to editing the xml file, validating it, building it to a .html file, checking if it's right and finally using diff to make a patch. I'd be happy though if someone could say how wrong I am.
[11:14] <fijam> To cut the long story short, my biggest concern is whether documentation should be usable in a docbook viewer or is just docbook format a tool of storing and managing the documentation under development.
[11:15] <fijam> And if it's not, how the links should be fixed.
[11:15] <fijam> does it make sense?
[11:18] <Admiral_Chicago> fijam: all you need to do is svn diff > mypatchforsection.diff
[11:18] <Admiral_Chicago> if it is a simple change
[11:19] <Admiral_Chicago> of course validating is also important if you are committing. if not, it isn't (but it is a good practice to follow)
[11:20] <fijam> certainly.
[11:20] <Admiral_Chicago> the docbook format is really a syntax for writing. It should be used to write it but because we are using docbook / XML, we can easily export it to a HTML file
[11:21] <Admiral_Chicago> fijam: to answer your question docbook/xml is both
[11:21] <fijam> so we need to fix the links.
[11:27] <Admiral_Chicago> ah i see your question
[11:28] <Admiral_Chicago> i'll have to think about that, i think you're question is a non issue though
[11:28] <fijam> what do you mean?
[11:29] <Admiral_Chicago> afaik, this is all done when the docs are compiled (maybe by the MAKE file) which may not be how you are doing it
[11:32] <fijam> Admiral_Chicago, output html files are fine. I just wonder what about raw docbook files.
[11:39] <Admiral_Chicago> hmm dunno fijam
[11:40] <fijam> I'll ask on the ML.
[11:44] <Admiral_Chicago> okay
[11:44] <Admiral_Chicago> good idea
[12:33] <ian_brasil> how did you output html from the docbook??
[12:34] <ian_brasil> the make files for me failed due to the move to the topic based help system
[12:36] <ian_brasil> (I have copied the serverguide and changed it to mobileguide , edited the xml and validated using the script and yelp...i then built the pdf with xml2pdf but i am not sure about how to do html output
[12:36] <ian_brasil> any ideas??
[01:10] <ian_brasil> i built the pdf with dblatex not xml2pdf