Re: [docbook-apps] Re: DocBook-XSL 1.76.1 release schedule
1.76.1, that is. On Mon, Oct 4, 2010 at 8:29 PM, DeanNelson deannel...@aol.com wrote: Keith, Huh? 1.61.1 ? You're just checking to see if we are awake ;-) ? Dean Nelson In a message dated 10/04/10 19:54:27 Pacific Daylight Time, abdela...@gmail.com writes: Hi, I'll be preparing the 1.61.1 Release Candidate Wednesday 6 Oct 2010. Please have your submissions checked in by the end of tomorrow, 5 Oct 2010. Keith - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Use of xincludes vs. entities
Sam Fischmann wrote: Jirka, your proposal is valuable because it would allow me to define small text variables for each of several contexts and store them in separate definition files. I could then use profiling to conditionally include definition files at the top level of a book and not have to look at miles of logical cruft every time something is wrong with a text variable in my documentation. It does not require multiple catalog sets, would be easy for editors to support, and unlike pure entity-based inclusion, there's an elegant system for overrides. The only unknown here for me is how validation would work. I can see myself putting definitionfile tags at the top of every single file via a global entity so that XIncluded files validate correctly, but that's inelegant again. The idea is to extend DocBook with these new transclusion elements. Of course if you are creating modular documents in any way it is wise to validate result document after all transclusions are resolved. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
[docbook-apps] Differences in olink sitemap: entities vs. xinclude
Hello! While playing with the olink logic (as mentioned here: http://www.sagehill.net/docbookxsl/Olinking.html) I tried 2 different ways to create the sitemap (olink database document). First I've created the sitemap based on entities (as described here: http://www.sagehill.net/docbookxsl/Olinking.html#DatabaseExample). Second - based on xinclude (as described here: http://www.sagehill.net/docbookxsl/OlinkVariations.html#XincludeOlinkdb). When I try to get the final html document using entity-based sitemap (target.database.document) all olink-based hrefs are created correctly without any problems. The problem arise when I try to get the final html document using xinclude-based sitemap - message Error: unresolved olink: targetdoc/targetptr appears. Documents, paths, targetdb files are the same in these two ways. The only difference is in sitemap file. I tried to change the xinclude-based sitemap: 1. Moving namespace declaration from xi:include href ... to the root element (targetset) (like in the samples below) 2. Trying to setup all files on linux-based system with different xsltproc version. 3. Trying to use absolute/relative path in xi:include href=... (testing the influencing of the xi:include href=... URI format). All with no success. For generation I use xsltproc (WinXP) with --xinclude, --xincludestyle options turning on. On linux based machine: xsltproc (Debian Lenny 5.0) with --xinclude, --xincludestyle options turning on. I use xsl:param name=current.docid select=/*/@id/xsl:param while creating final documents as described in tip in the end of this section: http://www.sagehill.net/docbookxsl/Olinking.html#LinkBetweenDocs . I would be appreciated if you tell me where I'm wrong or where I made a mistake. Below are samples of files I use. Thank you! 1. Entity based sitemap === ?xml version=1.0 encoding=utf-8? !DOCTYPE targetset SYSTEM http://path-to-server/docbook-xsl-1.75.2/common/targetdatabase.dtd [ !ENTITY prj1_usr_adm_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_adminguide.target.db !ENTITY prj1_usr_usr_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_userguide.target.db !ENTITY prj2_usr_adm_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_adminguide.target.db !ENTITY prj2_usr_usr_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_userguide.target.db ] targetset targetsetinfoMaster target db for the trunk documents/targetsetinfo !-- Site map for generating relative paths between documents -- sitemap !-- Can be only one root dir for all output -- dir name=olink.mechanism dir name=project1 dir name=trunk document targetdoc=project1_usr_adminguide prj1_usr_adm_targets; /document document targetdoc=project1_usr_userguide prj1_usr_usr_targets; /document /dir /dir dir name=project2 dir name=trunk document targetdoc=project2_usr_adminguide prj2_usr_adm_targets; /document document targetdoc=project2_usr_userguide prj2_usr_usr_targets; /document /dir /dir /dir /sitemap /targetset 2. Xinclude based sitemap (Win machine) === ?xml version=1.0 encoding=UTF-8? targetset xmlns:xi=http://www.w3c.org/2001/XInclude; targetsetinfoMaster target db for the trunk documents using XIncludes/targetsetinfo !-- Site map for generating relative paths between documents -- sitemap !-- Can be only one root dir for all output -- dir name=olink.mechanism dir name=project1 dir name=trunk document targetdoc=project1_usr_adminguide !-- Can be relative path href=/home/me/... -- xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_adminguide.target.db/ /document document targetdoc=project1_usr_userguide xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_userguide.target.db/ /document /dir /dir dir name=project2 dir name=trunk document targetdoc=project2_usr_adminguide xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_adminguide.target.db/ /document document targetdoc=project2_usr_userguide xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_userguide.target.db/ /document /dir /dir /dir /sitemap /targetset 3. Xinclude based sitemap (Linux machine) === ?xml version=1.0 encoding=UTF-8? targetset xmlns:xi=http://www.w3c.org/2001/XInclude; targetsetinfoMaster target db for the trunk documents using XIncludes/targetsetinfo !-- Site map for
Re: [docbook-apps] Re: DocBook-XSL 1.76.1 release schedule
Hi Keith, David Cramer, Kasun Gajasinghe and me are trying to make some refactor of the webhelp module in order to have a more clean separation of the code between the xsl and the java code. The java code is now extracted has a library (as saxon and xalan extensions) named xsl-webhelpindexer, we now have something near to work, the only thing missing is concerning the VERSION file which seems to be a generated file. Do you have any information to help us on creating this file? If there is something to do on sourceforge or freshmeat to release files? It would be cool to have this feature included in 1.76.1. Regards, Cedric, On Tue, Oct 5, 2010 at 5:30 AM, Keith Fahlgren abdela...@gmail.com wrote: 1.76.1, that is. On Mon, Oct 4, 2010 at 8:29 PM, DeanNelson deannel...@aol.com wrote: Keith, Huh? 1.61.1 ? You're just checking to see if we are awake ;-) ? Dean Nelson In a message dated 10/04/10 19:54:27 Pacific Daylight Time, abdela...@gmail.com writes: Hi, I'll be preparing the 1.61.1 Release Candidate Wednesday 6 Oct 2010. Please have your submissions checked in by the end of tomorrow, 5 Oct 2010. Keith - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Re: DocBook-XSL 1.76.1 release schedule
On Tue, Oct 5, 2010 at 2:08 AM, Mimil Mimil mimilo...@gmail.com wrote: The java code is now extracted has a library (as saxon and xalan extensions) named xsl-webhelpindexer, we now have something near to work, the only thing missing is concerning the VERSION file which seems to be a generated file. You want the VERSION to be similar to the one in xsl-saxon/VERSION, for example? Are you not able to copy and modify that one? Thanks Keith, that did the trick. I'll commit the new stuff in a bit. Thanks, David - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Differences in olink sitemap: entities vs. xinclude
Hi, It seems the problem here is simply an incorrect namespace-uri. You are using: xmlns:xi=http://www.w3c.org/2001/XInclude when it should use just w3 as in: xmlns:xi=http://www.w3.org/2001/XInclude I have to say I make that mistake sometimes too. 8^) Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Eduard Tibet eduard.ti...@i-free.com To: docbook-apps@lists.oasis-open.org Sent: Tuesday, October 05, 2010 1:11 AM Subject: [docbook-apps] Differences in olink sitemap: entities vs. xinclude Hello! While playing with the olink logic (as mentioned here: http://www.sagehill.net/docbookxsl/Olinking.html) I tried 2 different ways to create the sitemap (olink database document). First I've created the sitemap based on entities (as described here: http://www.sagehill.net/docbookxsl/Olinking.html#DatabaseExample). Second - based on xinclude (as described here: http://www.sagehill.net/docbookxsl/OlinkVariations.html#XincludeOlinkdb). When I try to get the final html document using entity-based sitemap (target.database.document) all olink-based hrefs are created correctly without any problems. The problem arise when I try to get the final html document using xinclude-based sitemap - message Error: unresolved olink: targetdoc/targetptr appears. Documents, paths, targetdb files are the same in these two ways. The only difference is in sitemap file. I tried to change the xinclude-based sitemap: 1. Moving namespace declaration from xi:include href ... to the root element (targetset) (like in the samples below) 2. Trying to setup all files on linux-based system with different xsltproc version. 3. Trying to use absolute/relative path in xi:include href=... (testing the influencing of the xi:include href=... URI format). All with no success. For generation I use xsltproc (WinXP) with --xinclude, --xincludestyle options turning on. On linux based machine: xsltproc (Debian Lenny 5.0) with --xinclude, --xincludestyle options turning on. I use xsl:param name=current.docid select=/*/@id/xsl:param while creating final documents as described in tip in the end of this section: http://www.sagehill.net/docbookxsl/Olinking.html#LinkBetweenDocs . I would be appreciated if you tell me where I'm wrong or where I made a mistake. Below are samples of files I use. Thank you! 1. Entity based sitemap === ?xml version=1.0 encoding=utf-8? !DOCTYPE targetset SYSTEM http://path-to-server/docbook-xsl-1.75.2/common/targetdatabase.dtd [ !ENTITY prj1_usr_adm_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_adminguide.target.db !ENTITY prj1_usr_usr_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_userguide.target.db !ENTITY prj2_usr_adm_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_adminguide.target.db !ENTITY prj2_usr_usr_targets SYSTEM file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_userguide.target.db ] targetset targetsetinfoMaster target db for the trunk documents/targetsetinfo !-- Site map for generating relative paths between documents -- sitemap !-- Can be only one root dir for all output -- dir name=olink.mechanism dir name=project1 dir name=trunk document targetdoc=project1_usr_adminguide prj1_usr_adm_targets; /document document targetdoc=project1_usr_userguide prj1_usr_usr_targets; /document /dir /dir dir name=project2 dir name=trunk document targetdoc=project2_usr_adminguide prj2_usr_adm_targets; /document document targetdoc=project2_usr_userguide prj2_usr_usr_targets; /document /dir /dir /dir /sitemap /targetset 2. Xinclude based sitemap (Win machine) === ?xml version=1.0 encoding=UTF-8? targetset xmlns:xi=http://www.w3c.org/2001/XInclude; targetsetinfoMaster target db for the trunk documents using XIncludes/targetsetinfo !-- Site map for generating relative paths between documents -- sitemap !-- Can be only one root dir for all output -- dir name=olink.mechanism dir name=project1 dir name=trunk document targetdoc=project1_usr_adminguide !-- Can be relative path href=/home/me/... -- xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_adminguide.target.db/ /document document targetdoc=project1_usr_userguide xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project1/trunk/project1_usr_userguide.target.db/ /document /dir /dir dir name=project2 dir name=trunk document targetdoc=project2_usr_adminguide xi:include href=file:///d:/doc/docbook-xsl/html-xsl/olink.mechanism/project2/trunk/project2_usr_adminguide.target.db/ /document document targetdoc=project2_usr_userguide
[docbook-apps] [ANN] Publican 2.2 released
Publican 2.2 is now released, containing numerous bug fixes, and previews of a couple of major new features that we hope to refine in subsequent releases. There's a full changelog at the end of this post, but the two new features are man page output and support for OPDS. Man page support is pretty raw and untested, but without a preview it's unlikely to get tested robustly, so we are shipping it as is. To build a man page, run: publican build --formats=man --langs=comma-separated_list_of_languages_to_build OPDS support is fully functional, but the final decision on how to segment content has not been been made. We believe the current layout is workable and definitely good enough for people to use it, and hopefully the feedback we receive from its use will help us nail down the final structure. When you install a book in EPUB format to a Publican-generated website, Publican automatically generates OPDS catalog entries to help users obtain the book on their readers. If you add either the Fedora documentation site[0] or Red Hat documentation site[1] to your EPUB reader, you can see the system in action. Feedback very welcome on the OPDS functionality, even if you don't use Publican yourself. Anyone using Fedora 12 or Fedora 13 can download and install the Publican 2.2 package from Koji [2] If Publican 2.2 works for you on Fedora, please leave positive karma in Bodhi so that Publican 2.2 reaches the main Fedora repos sooner.[3] Note that you must be logged in, or your karma won't count. If you use a Linux distro other than Fedora, the source code is available from fedorahosted.[4] We hope to have the Windows installer updated soon. Cheers Rudi, with thanks to Jeff Fearn, on whose post to Publican list I based this announcement. [0] http://docs.fedoraproject.org/opds.xml [1] http://docs.redhat.com/docs/opds.xml [2] Fedora 13 -- http://kojipkgs.fedoraproject.org/packages/publican/2.2/0.fc13/noarch/publican-2.2-0.fc13.noarch.rpm or Fedora 12 -- http://kojipkgs.fedoraproject.org/packages/publican/2.2/0.fc12/noarch/publican-2.2-0.fc12.noarch.rpm [3] Fedora 13 -- https://admin.fedoraproject.org/updates/publican-2.2-0.fc13 or Fedora 12 -- https://admin.fedoraproject.org/updates/publican-2.2-0.fc12 [4] https://fedorahosted.org/releases/p/u/publican/Publican-2.2.tar.gz Cheers Rudi Change log for 2.2: - Extend callout graphics to 40; adjust colour and font BZ #629804 - Make keycombo example consistent with RHEL6 behaviour. BZ #618735 - Restrict CSS style for edition to title pages to avoid applying to bibliographies - Fix images/icon.svg breaking rpm build. BZ #612515 - Fix empty term breaking PDF build. BZ #614728 - Fix footnote not catching modified para. BZ #565903 - Fix SRPM not including web labels. BZ #621036 - Update tocs when home page is updated. BZ #612027 - Don't display stats for unused languages. BZ #613500 - Fix admonitions/varlistentry not having IDs. BZ #616112 - Fix procedure/itemizedlist/orderedlist not having IDs. BZ #612817 - Catch invalid revision in translation. BZ #621721 - Limit index.html redirection to installed languages. BZ #612009 - Fix smaller width being overridden by max_image_width. BZ #613140 - Fix support for def_lang for web sites. BZ #622030 - Remove ant trails from selected links. - Add --novalid option to disable validation when building. BZ #616142 - Revert change to escaping ', , , . BZ #628266 - Add support for product and version splash pages. BZ #613502 - Fix unused version breaking product hiding. - Add support for alerts for parameters. - Add bash completion. - Validate revnumber for changelog. BZ #628464 - Add basic man page support. BZ #632027 - Add basic support for line numbers. BZ #629463 - Add warning messages for out of date translations. - Add productname to IGNOREBLOCKS. BZ #625316 - Add OPDS support. BZ #615831 - Fix translated labels in web nav. BZ #631647 - Remove highlighting from output of prompt tag in html. BZ #618902 - Resize index title font to a sane size. BZ #624392 - Fix misapplied fonts for CJK. BZ #628786 - Fix attributes breaking translation merge. BZ #638816 - Fix entities missing from RPM description. BZ #626254 - Add bridgehead_in_toc parameter. BZ #616123 - Support '--lang all' for lang_stats. - Left align CJK in PDF. BZ #639811 - Fix constraint regex on docname and productname. BZ #640082 - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
