------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. http://bugs.kde.org/show_bug.cgi?id=122465 Summary: meinproc is relicensing docs Product: kdelibs Version: unspecified Platform: Debian testing OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: general AssignedTo: coolo kde org ReportedBy: bab debian org Version: (using KDE KDE 3.5.1) Installed from: Debian testing/unstable Packages OS: Linux Hi, I have a KDE application whose documentation is licensed under the GPL. In particular, its index.docbook contains the line: &underGPL; When I build the application and meinproc is run over the docbook files, it generates an HTML title page that looks like: Title (large bold heading) Author Revision number Copyright notice Legal Notice Abstract ... In past versions of KDE, the legal notice was actually a short blurb stating which license was used. Now it is simply a hyperlink with the two words "Legal Notice". So: To find out the license, you must click on the "Legal Notice" hyperlink, and --- it sends you to help:/common/fdl-notice.html, which states that the documentation is licensed under the GFDL version 1.1 or later. I believe this is a serious issue -- the title page that is shown to users in the help centre should not be offering incorrect license information, and in some cases (such as GPLed documentation) it is in fact forbidden to relicense the documentation as GFDL in this way. As for the cause: I'm not too familiar with meinproc internals, but I suspect the culprit is /usr/share/apps/ksgmltools2/customization/kde-chunk.xsl. Around lines 90--100 it does look like the fdl-notice is being dropped into the documentation regardless of what actually appears inside the tag. Commenting out this block in kde-chunk.xsl seems to fix the problem -- the correct contents of .. are displayed on the title page of the HTML documentation (as in earlier KDE versions). I would appreciate if this could be fixed in the stable branch as well as in new releases, since (as mentioned above) offering incorrect license information is a serious issue. Many thanks, Ben.