Unexpected results in attempting a patch

[Frank H. Ellenberger]

Hi,

Am Dienstag, 21. September 2010 um 03:36:29 schrieb Yawar Amin:
> You’re right that there is actually a program that transforms our source
> XML files into browser-friendly HTML. I don’t have a script per se, I just
> run the command directly (the following assumes you’re in the
> guide/whatever-locale/ directory, e.g. guide/C/):
>
> xsltproc -o output_html/ ../../xsl/general-customization.xsl
> gnucash-guide.xml
>
> A little explanation: output_html is a directory that will automatically be
> created and filled with the output HTML. You can specify any name that
> makes sense. ../../xsl/general-customization.xsl is a relative path to the
> XSL stylesheet we are using to turn the raw input XML into the HTML we
> want, and it has to be that exact name.
>
> At this point, the generated HTML guide will be in the output_html
> directory, and you can open any of the files in there with your browser.
> But the problem is you won’t be able to see any images–screenshots, icons,
> etc. If that’s OK, you can ignore the next bit. If not, a quick fix is to
> run:
>
> cd output_html
> ln -s ../figures
> ln -s ../../../stylesheet
>
> Now if you reload any page where you didn’t see any image before, it will
> appear now.
>
> Note that when you’re ready to prepare your patch, you don’t want the
> output_html directory to be mentioned anywhere in it, so delete it before
> doing the patch:
>
> rm -rf output_html

Shouldn't this stuff be done somewhere by "make & make install"?

Frank