--===============1730812739== Content-Type: multipart/signed; boundary="nextPart21905982.2TixniF7Yu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart21905982.2TixniF7Yu Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline (Please try to keep the subject even if you read the digest). On Tuesday 31 January 2006 16:37, Korky Kathman wrote: > Andras thank you for your response. > > In working on creating a Kubuntu Desktop Guide from the orignal > Ubuntu source, If you bring up any XML document, you'll notice that > the DTD is > > "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" > > One difficulty is that I cannot seem to get this loaded into Quanta > 3.5. =46irst of all, did you look at the tutorials on=20 http://quanta.kdewebdev.org/docs.php ? Especially=20 http://quanta.kdewebdev.org/tutorials/quanta-docbook/quanta.html and=20 the two presentation. Also the "Extending Quanta Plus" and "Converting=20 a DTD to a DTEP" sections of the handbook should be useful for you. > I have looked at the DTD items under the menu option but dont=20 > seem to find a way to get those aligned with this external DTD > source.=20 DTD->Load & Convert DTD: select the docbookx.dtd you need and it will=20 create a new DTEP that can be used by Quanta. > This could be the biggest issue I have as you read on. Some=20 > detailed instruction here might help. The progam seems to always > want to load the HTML 4.01 Transitional. It works with whatever DTEP you select (from the available ones). See=20 Settings->Configure Quanta->Environment->Default DTD (this will be the=20 default if no project is loaded) or Project->Project=20 Properties->Default DTD (this is the default for all newly created=20 project files or for those which don't have a !DOCTYPE line). > Secondly, Ubuntu does not use the docbook standard that KDE does > (unfortunately). So therefore the XML toolbars don't help too much. You can create your own versions based on those and modify the=20 description.rc so the right ones are loaded. Or save a Project View=20 with the toolbars you want. > I have loaded the one that simply has the XML validity check and the > Xsltproc tab. (Toolbars, load Global, docbook, xmltoolbar). > > When I click the check-XML button, I typically choose DTD-external > (again not sure this is correct), then click the Validate. The code > spins in the message area, but gives no valid or not valid check. I > am assuming this goes back to the fact that it doesn't know which DTD > to validate against? Sincerely I don't know, as that tool was not written by me. Did you=20 selected the .dtd file in the Definition URI line?=20 > Finally clicking on the Xsltproc button, I check to use the current > document (in this case preface.xml), enter the source XSL (which is a > very long URL: > /usr/share/apps/ksgmltools2/customization/kde-chunk.xsl and must be > entered EVERY time you wish to regen. I enter the output file to be > ~/preface.html. This produces no output file whatsoever. Again, I'm not sure about this, but send me the xsl and some xml files=20 and I can try. I think in order to remember the long URL, you should=20 not close the dialog, but keep it running in the background. Andras =2D-=20 Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org --nextPart21905982.2TixniF7Yu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD4HZaTQdfac6L/08RAh7nAJ0aEugpIMa8oYOCDq778hfsJoL74wCgk6Ac 0lc9S60RtYCTctdFYD/bNC8= =G7Bq -----END PGP SIGNATURE----- --nextPart21905982.2TixniF7Yu-- --===============1730812739== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Quanta mailing list Quanta@mail.kde.org https://mail.kde.org/mailman/listinfo/quanta --===============1730812739==--