Re: [docbook-apps] Creating a DocBook glossary in a distributed documentation production environment

tion. > > The build process described in Bob's book buildsa glossary for > each document based on the terms used in that document. Simple > and automated. > > Hope that helps. > Dick Hamilton > - > XML Press > XML for Technic

[docbook-apps] Creating a DocBook glossary in a distributed documentation production environment

This is half a DocBook question and half a "process" question for anyone on this list working in a distributed DocBook production environment where for a particular assembled document you are generating at least one common glossary. (In this case, the assembled document is planned as a set with two

Re: [docbook-apps] Re: olink element question

> I think you are calling the id attribute of the root element of each file > the "document id", but that isn't an official XML term.  It just means the > id of the document's root element. Ok -- I'm not as clear on this as I thought. In the following, can the xml:id function as the document id (

Re: [docbook-apps] Re: olink element question

On Sun, Sep 6, 2009 at 8:32 PM, Bob Stayton wrote: > Hi Karen, > Yes, the example you provided is correct. It's really just the one in your book, rephrased so that I'm absolutely sure what I'm doing. Which helped! > > I'm afraid there is some ambiguity in the use of "document", especially when >

Re: [docbook-apps] Re: olink element question

> ...  The targetdoc value needs to cover all the content of an > assembled book, not just one chapter.  Think of an olink as a two-part > address: the first part (targetdoc) references the book, and the second part > (targetptr) references a point within that book.  Only when you mean to link > to

[docbook-apps] Re: olink element question

Urp, correction: See the chapter on creating lists Karen On Fri, Sep 4, 2009 at 12:35 PM, Karen Schneider wrote: > I am working on a styleguide and want to clarify naming conventions > for the olink element. I still am struggling to understand this > element so want to make sure

[docbook-apps] olink element question

I am working on a styleguide and want to clarify naming conventions for the olink element. I still am struggling to understand this element so want to make sure that the following is correct (in reference to a file named filenames.xml): For simplicity's sake, use the document's xml:id attribute as

[docbook-apps] Dokuwiki to DocBook

Dear all, I think I know the answer to this but once again I've had questions about exporting from DokuWiki to DocBook. So far what I have found is this: DocBook DokuWiki : http://sourceforge.net/projects/docbookdokuwiki/ Last updated 505 days ago, appears to be based on pre-5.0. A nice idea... a

Re: [docbook-apps] Graphic formats for screenshots

Thanks, all. This is extremely timely and helpful. We will focus on creating a help page for our styleguide specific to creating DocBook-friendly spoons. I mean, PNGs. -- -- | Karen G. Schneider | Community Librarian | Equinox Software Inc. "The Evergreen Experts" | Toll-free: 1.877.Open.ILS (1.

[docbook-apps] Graphic formats for screenshots

As we work on our styleguide, proof of concept, and other stuff that our Documentation Interest Group is doing to lay the groundwork for our project, we wondered if DocBook users had strong feelings about image formats. We will be working with screenshots, and our expected DocBook output is HTML, P

Re: [docbook-apps] DocBook Customization -- Subsets

We've looked at the simplified version of DocBook and it's TOO simple. We have a couple of examples of local style manuals (thank you!). If anyone else wants to share their tag subsets, that would be gratefully received. We appreciate the goal of reducing complexity and ambiguity--makes sense--but

[docbook-apps] Newbie testing of new stylesheet releases

I have been watching these releases coming out and thinking that smoke-testing new releases is often a good way to learn. So if I wanted to test version 1.75.1 of the DocBook XSL & XSL-NS Stylesheets -- perhaps constraining myself to something I'm at least partially familiar with and have some doc

[docbook-apps] Full presentation (Evergreen docs), and Drupal

Here is the full slideset for the 3-hour planning session: http://www.slideshare.net/evergreenils/evergreen-docs-planning-session-2009 Again, per advice from the group (and special thanks to Larry Rowland, whose advice "wrote" a few slides), I was very careful to stress the amount of effort requi

[docbook-apps] DocBook for Evergreen

Just a quick note of thanks to the DocBook community for all the assistance over the past six months. At our first-ever user conference about 20 of us had a three-hour documentation session that concluded with establishing the Evergreen DIGgers (documentation implementation group) and in order, com

Re: [docbook-apps] xlstproc questions (was: CSS begging)

On Sat, May 16, 2009 at 2:50 PM, DeanNelson wrote: > Karen > > Setting the PATH should probably be done in your batch file: > > SET PATH=c:\rubberducky\xslttools;%PATH% This strikes me as a valuable approach for several reasons... multiplied across a community, it would be a good way to troubles

Re: [docbook-apps] xlstproc questions (was: CSS begging)

2009/5/16 Jirka Kosek : > Karen Schneider wrote: > >> C:\XMLTOOLS>xsltproc --stringparam base.dir c:\XMLTOOLS\test7- >> --stringparam html.stylesheet boetest.css >> c:\xmltools\docbook-xsl\xhtml\chunk.xsl >> h:\docsrepo\TechRef\JSONGrammar.xml > > base.dir

[docbook-apps] xlstproc questions (was: CSS begging)

Johann (and Dave and Fabrice), thank you! I am now able to demo "and this is what it looks like, styled" -- which is very useful. I will put my slides on Slideshare early next week. I told myself that would be my last question before Wednesday's talk but the mention of xsltproc raised questions ab

[docbook-apps] CSS for DocBook 5 example

Are there one or two simple cascading stylesheets that are particularly good for demonstrating how CSS can style DocBook output? I see the small example in Stayton's book, p. 71, but have been looking around for other choices and have found a lot of stuff that's really outdated or otherwise not qui

Re: [docbook-apps] Element [...] not allowed in this context

> Things are a little different when you look at how a DocBook document is > rendered (in HTML or XSL-FO or whatever). The current stylesheets render > everything down to a , so you would have 7 levels of hierarchy > out of the box (5 sections inside a chapter inside a book). If that is > not suffi

Re: [docbook-apps] Element [...] not allowed in this context

On Mon, May 11, 2009 at 1:17 PM, Rowland, Larry wrote: > As nearly as I can tell, you are attempting to include a chapter inside a > chapter (StaffServices.xml, which is a chapter includes Cataloging.xml, which > is also a chapter).  You also have a para following the inclusion of > Cataloging.

[docbook-apps] Element [...] not allowed in this context

I have a situation where 3 files validate quite nicely as a project in oXygen (they are a chapter, a sect1, and a glossary), but if I attempt to validate them as part of a larger, nested project (where there is a book followed by chapters and then sect1s), I get the following errors for the chapter

Re: [docbook-apps] Docbook 5.0 and stylesheets

On Fri, May 8, 2009 at 4:58 PM, Bob Stayton wrote: > Hi, > I have some answers. > > 1.  The docbook-xsl-ns stylesheets are DocBook 5.0 stylesheets.  If there is > a 5.0 element they don't support, that should be treated as a bug. > > 2.  DocBook 5.0 has been submitted to OASIS as a proposed OASIS

Re: [docbook-apps] Docbook 5.0 and stylesheets

I thought I'd try to get an update on the questions responded to in this thread from February (responses included below my sig file) because I've been asked questions about DocBook that I expect I'll hear more of as we continue to discuss the use of DocBook in our project. I also had to convince so

Re: [docbook-apps] Very basic svn and DocBook question

Thanks all for the unanimous answer to the checkin question, and to Larry Rowland for the following comment. In terms of tracking the production system used, we use a versioned > production system (based on Ant build files and some extensive > customizations of the standard DocBook transforms) and

[docbook-apps] Very basic svn and DocBook question

As some of you have picked up I am working with a project in the "proof of concept" stage for DocBook. We do have a small amount of documentation developed in DocBook, and we have a dedicated directory, and SVN for revision control. Right now we're producing plain HTML (yeah, I know, but we're gett

[docbook-apps] Proposing a DocBooks workflow for an open source community

Hi folks, this is another high-level post--revisiting discussions from a while back. Thanks for all the great responses to the workshop (I still owe a couple people responses, but it's a nutty week). I work for a support company associated with an open source project. I have been looking at docume

[docbook-apps] Docbooks/documentation workshop

Back in early February I asked for examples for a Docbook workshop. I'm actually still planning a workshop for a conference next month. However, after speaking with various stakeholders, observing people learning and working with Docbook, and following discussions on this list, my objectives have e

[docbook-apps] Transitioning to Docbook

Bram wrote, "We are planning to move to docbook and the initial transition went very smoothly and impressed my non-CS bosses." This caught my eye. I'd love to hear what helped Bram succeed -- it could be very useful for other organizations! Also, what is persuasive for Word users would also be help

Re: [docbook-apps] Producing Open Source Software

> > Admittedly, getting the XML right is sometimes a bit of an issue for > the newbies, but they learn. Very quickly. Simply because their > commits fail to build. And are 2 steps produce all the output needed > to fix it. > > PHP is one Docbook example I've been looking at from all angles because

Re: [docbook-apps] Producing Open Source Software

On Thu, Mar 5, 2009 at 6:58 AM, DavePawson wrote: > Thomas Schraitle wrote: > > Although the above statement contains some truth, open source projects >> fail because of something different: the lack of documentation. :) >> > > Treading very carefully :-) Maybe "fail" is not the word... but ce

[docbook-apps] Docbook, editors, and EBNF

Hi, I'm looking into Docbook and EBNF (Extended Backus-Naur Form, a formal notation for defining syntax). We are using EBNF for documenting syntax for JSON queries. We see the Docbook support for EBNF on the site ("The EBNF elements are part of the standard DocBook V5.0

Re: [docbook-apps] Docbook 5.0 and stylesheets

4.x, just remember to > use the namespace. > > All this is my vision of the issue, I will let experts precise or correct > all if necessary > > Camille. > > > Karen Schneider wrote: > >> Hi, I'm reposting a message from Betty, an intern who is subscri

[docbook-apps] Docbook 5.0 and stylesheets

Hi, I'm reposting a message from Betty, an intern who is subscribed to this list but having difficulty posting.. Note that I think I have partially found the answer from the following document, http://www.docbook.org/docs/howto/ , which includes links to http://docbook.sourceforge.net/release/xsl-n

Re: [docbook-apps] Consistent libxslt error

This is a very diplomatic way of goosing me to buy and read the book -- now scooted up to "can I find a copy in Tallahassee today to drag with me to next week's conference so I can sit in the back of the room and read." thank you. And thanks to Bob Stayton for his slides, which a documentation inte

[docbook-apps] Consistent libxslt error

Another person and I are consistently seeing errors when we run xsltproc, including not just our own files (which validate to docbook 5.0 in xmlmind) but also with the test files provided with xlstproc. The files are still created and all the links work. We are using current versions of libxml2 and

Re: [docbook-apps] Question about XSLT processors

milton > > Managing Writers: A Real World Guide to Managing Technical Documentation > http://xmlpress.net/managingwriters.html > > -Original Message- > *From:* Karen Schneider [mailto:kgschnei...@gmail.com] > *Sent:* Thursday, February 19, 2009 3:04 PM > *To:*

[docbook-apps] Question about XSLT processors

I'm following instructions for Windows on this page: http://evergreen-ils.org/dokuwiki/doku.php?id=documentation:setting_up_docbook_transforms I've made it through all the steps, but I have to tell you these instructions feel like they have a high kludge factor to them -- lots of typing, command-

Re: [docbook-apps] Docbook workshop syllabi?

Wow, good comments all (and I hope more flow) -- I am on the road this week but when I get back and the dust settles, I'll begin working on a syllabus for the workshop and will share it with everyone. Michael, if you want to show me material in draft, I would be happy to give it a novice's look-ove

Re: [docbook-apps] Docbook workshop syllabi?

Terrific! Is there a place things like these are posted? Karen / Equinox On Tue, Feb 10, 2009 at 10:20 AM, DeanNelson wrote: > Karen, > I have not done the webinar, but instead use a document that covers the > basics and how all of the Docbook documentation is done in my shop. It is > designe

[docbook-apps] Docbook workshop syllabi?

Has anyone developed a half-day workshop or one-or-two-hour webinar on Docbook? I work with a software project that is considering a proposal to adopt Docbook for its documentation needs. It has been suggested that a workshop might help build buy-in and bring more people into the native-XML-produc

[docbook-apps] Consultants who work with Docbook implementations

Is there a list or wiki for these? If you are such a consultant, please feel free to contact me directly at k...@esilibrary.com. (Oh, and happy holidays, and all that!) -- -- | Karen G. Schneider | Community Librarian | Equinox Software Inc. "The Evergreen Experts" | Toll-free: 1.877.Open.ILS (