https://bugs.kde.org/show_bug.cgi?id=373723
--- Comment #5 from RJVB ---
That's the nice thing of using doxygen: if it generates the HTML for a website
correctly, anything that bundles this same HTML into some kind of archive for
perusing with a dedicated browser ought to provide the same informa
https://bugs.kde.org/show_bug.cgi?id=373723
--- Comment #4 from Olivier Churlaud ---
This is very true, because my focus was to have the apidoc website up and
working.
Currently, I wouldn't trust any other function than the website as shown on
api.kde.org (that you can, of course, generate at ho
https://bugs.kde.org/show_bug.cgi?id=373723
--- Comment #3 from RJVB ---
kapidox also contains the kapidox_generate script, which allows users (and
packagers) to generate their own copy of the API documentation. That's where
qch and chm files can come in.
To which option does this "generator.py
https://bugs.kde.org/show_bug.cgi?id=373723
--- Comment #2 from Olivier Churlaud ---
Hello,
Actually, the qch file doesn't take advandatage of the generator.py thing, nor
of the searchdata.xml.
It's quite unfortunate, but I have no idea how to deal with this. Currently,
the only thing that KApi
https://bugs.kde.org/show_bug.cgi?id=373723
RJVB changed:
What|Removed |Added
CC||oliv...@churlaud.com
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=373723
--- Comment #1 from RJVB ---
I'm trying to attach an example but BKO currently won't let me.
--
You are receiving this mail because:
You are watching all bug changes.
