Re: [docbook] Indexterm embedded in indexterm/primary or indexterm/secondary

[Norman Walsh]

Yes, that’s stupid. GitHub.com/docbook/docbook 
 

On Wed, 23 Feb 2022, at 18:25, Richard Hamilton wrote:
> Because of a fat-finger error, I just found that if you embed an indexterm 
> inside primary or secondary of an indexterm, the result is legal DocBook 
> according to the 5.0 through 5.2 schemas, including Schematron.
> 
> 
>   
> term
>   
> 
> 
> Probably not a big deal in practice, except that it does lead to an error in 
> an epub when tested with epubcheck, and if the term inside the embedded 
> indexterm appears nowhere else, you get an error saying that there are no 
> entries for that index key.
> 
> If no one sees any reason for that to be valid, I can file an exception 
> (though I forget where, exactly, to do that:-).
> 
> Best regards,
> Dick Hamilton
> ---
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> hamil...@xmlpress.net
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-h...@lists.oasis-open.org
> 
> 

[docbook-apps] Re: XSLT cannot find UnwrapLinks.so

[Norman Walsh]

Jirka Kosek  writes:
> On 11.12.2019 10:10, Frank Arensmeier wrote:
>> When observing a HTML build with strace, I see a ridiculous large number of 
>> entries like this:
>> 
>> stat("/usr/lib/libxslt-plugins/nwalsh_com_xslt_ext_com_nwalsh_saxon_UnwrapLinks.so",
>> 0x7ffc9f117ee0) = -1 ENOENT (No such file or directory)

There’s never been an “so” file for that; it’s a Saxon extension, not
an xsltproc extension.

>> That plugin seems dead
>> (http://nwalsh.com/xslt/ext/com.nwalsh.saxon.UnwrapLinks
>> <http://nwalsh.com/xslt/ext/com.nwalsh.saxon.UnwrapLinks>). Can
>> someone shed some light on this? Why would you need that plugin? Can
>> you download that plugin somewhere?

It’s in the 1.0 stylesheets repository in 
…/xsl-saxon/src/com/nwalsh/saxon/UnwrapLinks.java

    Be seeing you,
  norm

-- 
Norman Walsh  | Men of genius do not excel in any
http://nwalsh.com/| profession because they labor in it,
  | but they labor in it because they
  | excel.--William Hazlitt


signature.asc
Description: PGP signature

[docbook] Re: HTTPS on docbook.org is breaking stuff

[Norman Walsh]

Shaun McCance  writes:
> I maintain a collection of tools in GNOME that includes yelp-check,
> which has a validator that can automatically detect the input type and
> do the appropriate thing to validate. By default it uses xmllint, but
> it has an option to use jing.
[…]
> Is there any way docbook.org could just serve the schemas over HTTP as
> requested? These URIs are kind of API, and the redirects are kind of
> breaking that. xmllint and jing are both popular tools. I can't be the
> only person running into this.

Ugh.

No, apparently there’s no way to serve http: off the current hosting
provider. And the fact that libxml2 doesn’t support https: goes back
to at least 2016.

Double ugh.

I thought that recent schema catalogs included https: variants as well.

I wonder if we can work out why the catalogs aren’t working on Fedora?

Be seeing you,
      norm

-- 
Norman Walsh  | 'I have done that,' says my memory. 'I
http://nwalsh.com/| cannot have done that'—says my pride,
  | and remains adamant. At last—memory
  | yields.--Nietzsche


signature.asc
Description: PGP signature

[docbook-apps] Re: How do I generate a PDF through the gradle DocBookTask

[Norman Walsh]

Loren Cahlander  writes:
> I found Norm Walsh’s grade DocBookTask in his article 
> https://so.nwalsh.com/2018/03/05/easy
[…]
> I need to find the settings for generating a PDF.

I’ve been exploring the answer to that question recently. There are
two obvious avenues: through XSL-FO or through CSS. I’ve made both
work, though the DocBook 2.0 stylesheets for FO aren’t really as well
developed as the HTML ones.

Something as simple as this, should produce FO:

task myPdfDocument(type: DocBookTask) {
  // And tell the pipeline to validate with the schema
  option("schema", "https://docbook.org/xml/5.1/rng/docbook.rng;)
  input("source", "document.xml")

  output("result", "output.fo")
  option("format", "print")
}

I’ve produced PDF with CSS (via AntennaHouse) recently, see the xproc_pdf
task in build.gradle in github.com/xproc/3.0-specification/

        Be seeing you,
  norm

-- 
Norman Walsh  | Waste no more time arguing what a good
http://nwalsh.com/| man should be. Be one.--Marcus Aurelius


signature.asc
Description: PGP signature

[docbook-apps] Re: Some beginner questions for db xslt20-stylesheets

[Norman Walsh]

aanno  writes:
> 1. So far I have used 'java -jar docbook-xslt2-2.3.8.jar -f foprint -o
> out.fo howto.xml' to get an PDF of my document. However, I wonder if
> it is possible to get the _xsl-fo output_ of the document as well.
> There seems to be a lot of options (and I have played around with
> 'return-secondary' but with no useful result), so perhaps this is easy.

I think you’d have to modify the pipeline to do that.

> 2. When I try the '(css)print' format, I only get the error:
> 'XProcException: No CSS processor class defined'. I guess I'm
> missing something here.

Right. You need a tool to do CSS printing. I believe you can use
either AntennaHouse or Prince, but I confess I haven’t tried anything
but AntennaHouse recentluy.

> 3. What are my options for using _math_ inside a docbook document?

You can put MathML in an inlineequation. Successful output is going
to depend on a processor that can render MathML, of course.

If you’ve got a tool that can turn MathML into bitmaps, you could
construct a pipeline to do that, I expect.

> 4. Is it possible to do source code highlighting in docbook?

In the browser, yes. I don’t think there’s a solution for doing it in
print at the moment.

Be seeing you,
      norm

-- 
Norman Walsh  | So, are you working on finding that bug
http://nwalsh.com/| now, or are you leaving it until later?
  | Yes.


signature.asc
Description: PGP signature

[docbook] Re: Which DocBook element to use for NICs?

[Norman Walsh]

Thomas Schraitle <tom_s...@web.de> writes:
>> You can use class attribute to be more specific about value inside
>> systemitem. If there is nothing suitable for you in this list, you can
>> still use rola attribute and invent your own types, e.g.
>> 
>> eth0
>
> An alternative notation would be:
>
>  eth0

I think that would be “better”, but I also think

> What about adding "interface" to the available values of the class
> attribute for future DocBook versions?

Is a perfectly reasonable idea.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | The formula 'Two and two make five' is
http://nwalsh.com/| not without its attractions.--Dostoevsky


signature.asc
Description: PGP signature

[docbook-apps] Re: XML databases

[Norman Walsh]

Camille Bégnis <cami...@neodoc.biz> writes:
> thanks for this interesting discussion, what DB would you use or suggest
> for XML?

I’m strongly biased to suggest a particular commercial database, one
that you can download and use for free from developer.marklogic.com.

But I hear good things about BaseX as well and eXist has been around
for ages.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | There has never been a perfect
http://nwalsh.com/| government, because men have passions;
  | and if they did not have passions,
  | there would be no need for
  | government.--Voltaire


signature.asc
Description: PGP signature

[docbook-apps] Re: XML databases

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
> Agree with your logic. Good for thousands (hard to index)
> Less so for hundreds (I use db indexing)

Yes, but as I said, it depends on the app you’re trying to build.

drinks.nwalsh.com: ~200 small documents, easy to build in a DB, harder outside.
so.nwalsh.com: ~600 documents and growing, easy to build in a DB, *much* harder 
outside
photos.nwalsh.com: ~14,000 documents, same story
tzinfo.nwalsh.com: ~225,000 documents, probably not practical any other way

(Drinks.nwalsh.com is a simple app, you could do that off the
filesystem with a little bit of Python and some cleverness.
So.nwalsh.com would be much harder because it’s using full-text,
semantic, and geospatial indexes and runs queries in real time that
rely on those indexes to perform well.)

> I'd hate to have the data in a corrupt database

Or a corrupt filesystem. I don’t think databases are inherently a
riskier place to put your data. And if having them in a database
encourages you to have a more reliably backup strategy, they’re
arguably less risky.

Backup early. Backup often. And remember: if you copy data to a backup
drive, then remove the data from your computer, you don’t have a
backup, you have a vulnerable data set on a single external drive.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Limited in his nature, infinite in his
http://nwalsh.com/| desires, man is a fallen god who
  | remembers heaven.--Lamartine


signature.asc
Description: PGP signature

[docbook-apps] Re: XML databases

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
> What use cases are there for dropping a few hundred
> XML files into a (purpose built for XML) database?

I put XML in a database for the ability to index and search it,
primarily. Here’s a screenshot of my personal “evernote clone” that
stores a combination of XML and other formats.


The documents that contained the word DocBook (stemmed appropriately,
so DocBooking and DocBooked, if they were words, would also have
matched) are found quickly. The facets are constructed from other
fields in the those documents.

The ability to quickly search and use indexes to build facets allows
me to make an application that would be more difficult without a
database.

>  I can see a risk (db failure) above the file system
> failure risks.

Backups. You want to have backups!

> Has anyone done that assessment and decided in
> favour of a database over the file system?

For a few hundred documents, it’s probably hard to make a compelling
argument for a database unless you want to build applications like the
one I described above.

For a few hundred thousand documents, ti’s probably hard to make a
compelling case for the filesystem.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com> | The finest amusements are the most
http://nwalsh.com/| pointless ones.--Jacques Chardonne


signature.asc
Description: PGP signature

[docbook] Re: Once again tinkering with the DNS for docbook.org

[Norman Walsh]

Hi folks,

Excepting any pockets of the ’net where the DNS change hasn’t propagated yet,
I believe we’re up and running:

  https://docbook.org/
  https://cdn.docbook.org/
  https://tdg.docbook.org/
  http://wiki.docbook.org/ -> https://github.com/docbook/wiki/wiki

If anyone sees anything out-of-the ordinary, please give a shout.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Quotation, n: The act of repeating
http://nwalsh.com/| erroneously the words of
  | another.--Ambrose Bierce


signature.asc
Description: PGP signature

[docbook] Re: Once again tinkering with the DNS for docbook.org

[Norman Walsh]

“Make it so.”

I believe I have configured Netlify to do the right thing with DNS for
all of the docbook.org subdomains. I have changed the nameservers for
docbook.org.

You shouldn’t notice. But let me know if you do!

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | You can pretend to be serious; you
http://nwalsh.com/| can't pretend to be witty.--Sacha Guitry


signature.asc
Description: PGP signature

[docbook] Re: Once again tinkering with the DNS for docbook.org

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
> Works for me Norm, 1930Z?
> docbook.org & www.docbook.org?

It works fine, but it’s http: not https:.

I can’t make it https: and host it at github.com because they don’t
support SSL on custom domain names.

I’ll port it over to netlify which works. For cdn.docbook.org and
tdg.docbook.org, it was easy. There’s a DNS feature called CNAME that
allows you to map one domain to another. If you ask DNS about
cdn.docbook.org, it’ll tell you it’s an alias:

  $ host cdn.docbook.org
  cdn.docbook.org is an alias for boring-mayer-fc55f1.netlify.com.
  boring-mayer-fc55f1.netlify.com has address 104.198.56.15

But I don’t think I can (“I don’t know how to”) make that work for the
root domain (docbook.org) without changing the nameservers to netlify.

In theory, changing the nameservers is straightforward. I configure
the names at netlify, change the DNS NS records, and everything just
works. (Resolution continues to the old hosts until the DNS change
propagates across the internet and then it goes to the new hosts,
which support https:)

In practice, if it isn’t straightforward (“If I [expletive] it up”), I
don’t want to break someone’s production run at 15:00 on Friday
afternoon, so I’ll wait until the weekend.

(Free advice: if you’re relying on the internet for your production
runs, you’re doing it wrong. But I don’t want to be the guy who proves
that to you on Friday afternoon!)

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Everything in the universe goes by
http://nwalsh.com/| indirection. There are no straight
  | lines.--Emerson


signature.asc
Description: PGP signature

[docbook] Once again tinkering with the DNS for docbook.org

[Norman Walsh]

Hi folks,

I was able to get the cdn.docbook.org and tdg.docbook.org subdomains
ported over to https: without changing the DNS servers for
docbook.org, but I think I am going to have to change it in order to
get docbook.org (and www.docbook.org) ported over.

I think it’ll be relatively seamless, but in case it isn’t, fair
warning: I’ll be trying to make the changes next weekend
(10 March 2018).

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Sun System & Network Admin manualIt is
http://nwalsh.com/| important to realize that any lock can
  | be picked with a big enough hammer.


signature.asc
Description: PGP signature

[docbook-apps] Re: Using the DocBook XSLT 2.0 stylesheets with Gradle

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
>  It was probably quite a while since Norm used Windows!

I haven’t done any development on a Windows box in this millenium.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | One should never make one's debut with
http://nwalsh.com/| a scandal. One should reserve that to
  | give interest to one's old age.--Oscar
  | Wilde


signature.asc
Description: PGP signature

[docbook-apps] Re: Using the DocBook XSLT 2.0 stylesheets with Gradle

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
> My position.
>   1. I don't stretch the schema (db simple would likely suffice)
>   2. I haven't updated my stylesheets in ages
>   3. I build html / pdf with svg ... (500k + words)
>   4. I want (need?) to validate as an option.
>   5. All files are on my hard drive
>
> ant lets me pick / choose bits|all
> Am I odd? Minority? Majority?

I don’t know if you’re in the minority or the majority. You’re
definitely in the “I’ve had this working since the previous millenium”
group, though.

There’s no reason you have to change.

That said, if you switch from the 1.0 stylesheets to the 2.0
stylesheets, you’ll find that you need to update your environment with
new tools.

If you want to do that by grabbing all the jars and installing them
locally and setting up your classpath and updating your shell scripts,
etc., by all means go for it. I’ve done it that way lots of times.

>  Who needs steenkin
> esisinternet 
>
> Sorry - that quote stuck from dsssl days Norm - bet you've forgotten it.

I remember the ESIS. :-)

Be seeing you,
          norm

-- 
Norman Walsh <n...@nwalsh.com> | We discover in ourselves what others
http://nwalsh.com/| hide from us, and we recognize in
  | others what we hide from
  | ourselves.--Vauvenargues


signature.asc
Description: PGP signature

[docbook-apps] Re: Using the DocBook XSLT 2.0 stylesheets with Gradle

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
> I stopped at "you don't have to understand it" Norm?
> ... rude words.

Apologies. No disrespect intended.

> I got as far as ant for builds. I can understand most of that.
> Bash script... similar? Maybe
> gradle? Wozzat.
>
> Why make it deeper than needs be?

Well…I’m not sure I agree that it’s deeper than it needs to be.
I’ve been building toolchains for ages: make, ant, bash, perl,
ruby, python, sbt, etc. etc. etc.

I settled on Gradle because of the advantages I outlined in that
posting: it’s significantly better than ant for dealing with Maven and
for extensibility; it’s cross platform (unlike bash); it’s relatively
easy to install on most platforms (unlike make, perl, etc.); and it
transparently deals with a whole lot of the backend infrastructure.

Be seeing you,
          norm

-- 
Norman Walsh <n...@nwalsh.com> | The finest amusements are the most
http://nwalsh.com/| pointless ones.--Jacques Chardonne


signature.asc
Description: PGP signature

[docbook-apps] Using the DocBook XSLT 2.0 stylesheets with Gradle

[Norman Walsh]

Hello,

Of possible interest to the readers of this list:

  https://so.nwalsh.com/2018/03/05/easy

(I found a couple of bugs so there’ll be updates within a day or two,
but I still think it might be of interest.)

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Sun System & Network Admin manualIt is
http://nwalsh.com/| important to realize that any lock can
  | be picked with a big enough hammer.


signature.asc
Description: PGP signature

[docbook] Re: Tinkering with the DNS for docbook.org

[Norman Walsh]

Norman Walsh <n...@nwalsh.com> writes:
> I really need to get cdn.docbook.org available by https. It’s
> currently hosted by github.com as a custom domain and they don’t do
> SSL for custom domains.

This is resolved. Actually, I found a simpler way to resolve it.

I’m going to try to get docbook.org ported over to https as well using
the same approach.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Hanging is too good for a man who makes
http://nwalsh.com/| puns; he should be drawn and
  | quoted.--Fred Allen


signature.asc
Description: PGP signature

[docbook] Re: Tinkering with the DNS for docbook.org

[Norman Walsh]

tl;dr Lech Rzedzicki pointed out that I could accomplish the task with
netlify and a single DNS update. The task is finished and I won’t need
to tinker with nameservers this weekend. Thank you, Lech!

Warren Young <war...@etr-usa.com> writes:
> Go with someone like Cloudflare if you need the scale or 24/7
> availability of a big CDN, but if traffic is low enough to do without,
> you can do what you want with a reverse HTTP proxy server and Let’s
> Encrypt.

For some values of “you”. I have no idea how to setup a “reverse HTTP
proxy server”.

> How much traffic are we talking about here?
>
> (Here’s where you tell me how many people are pulling their
> stylesheets over the web on every document render because they either
> haven’t bothered to set up a local stylesheet catalog or have it
> misconfigured so it gets skipped.)

It’s more significant than that. The default JavaScript and CSS files
for rendering the web pages are hosted at cdn.docbook.org. I expect
there’s lots of traffic. Maybe not “a lot” of bandwidth in the grand
scheme of things at web scale, but still more than I’d carelessly put
in an S3 bucket and pay for out of my own pocket.

And yes, experience at the W3C suggests that there will be people who
point to the CDN and download the entire set of stylesheets from the
web on every render. ¯\_(ツ)_/¯

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com> | Art has to move you and design does
http://nwalsh.com/| not, unless it's a good design for a
  | bus.--David Hockney


signature.asc
Description: PGP signature

[docbook] Tinkering with the DNS for docbook.org

[Norman Walsh]

Hi folks,

I really need to get cdn.docbook.org available by https. It’s
currently hosted by github.com as a custom domain and they don’t do
SSL for custom domains.

I don’t want to change the process for publishing to cdn.docbook.org
dramatically. That limits the options. Near as I can tell, the only
way to do this and stay on github.io is with some kind of proxy via
cloudfare.

Fair enough, I guess.

That means changing the nameservers for docbook.org and that could
cause disruption. At the very least, I’ll have to work out how to configure
the DNS again and there’s a chance I’ll screw it up on my first try.

Rather than just randomly break things on a Monday evening :-), I’ll
plan to make this change next weekend.

Comments and suggestions most welcome, of course.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | Simplicity is always a virtue.--Edward
http://nwalsh.com/| Abbey


signature.asc
Description: PGP signature

[docbook] Re: Add a link to a image

[Norman Walsh]

Sascha Manns <sascha.ma...@mailbox.org> writes:
> in some cases it can be useful, if i can add a link to an image. So it
> is "clickable".
> Is it possible to do this with Docbook5?

You can put an inline image inside a link, that’s probably the easiest thing.

Be seeing you,
          norm

-- 
Norman Walsh <n...@nwalsh.com> | There has never been a perfect
http://nwalsh.com/| government, because men have passions;
  | and if they did not have passions,
  | there would be no need for
  | government.--Voltaire


signature.asc
Description: PGP signature

[docbook-apps] Re: REST API description

[Norman Walsh]

Dave Pawson <dave.paw...@gmail.com> writes:
> http://vrici.lojban.org/~cowan/XML/tagsoup/#tsaxon is available if you want to
> use XSLT with an html source.

These days, I’d recommend Henri Sivonen’s validator.nu parser for
reading HTML. Tagsoup is great, but the point of the validator.nu
parser is that it gives the same structures that browsers give, so
it’s a more consistent place to start.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | The finest amusements are the most
http://nwalsh.com/| pointless ones.--Jacques Chardonne


signature.asc
Description: PGP signature

[docbook] Re: missing information in Transition Guide

[Norman Walsh]

victory <victory@gmail.com> writes:
> looks like docbook5 requires clause-which-include-entity-file like
>%fexternalentity;
> in *all* docbook files which use entity defined in it;
>
> even if the main file have the line, those entities cannot be used
>  from included-files if the included-file do not have the clause
>
> DocBook V5.0 The Transition Guide should have this information around
> "Converting DocBook V4.x documents to DocBook V5.0"

Thank you!

I created https://github.com/docbook/docbook.org/issues/17 to track this
issue.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com> | My life has a superb cast but I can’t
http://nwalsh.com/| figure out the plot.--Ashleigh Brilliant


signature.asc
Description: PGP signature

[docbook] Re: TDG 5.1 Redirect

[Norman Walsh]

"Imsieke, Gerrit, le-tex" <gerrit.imsi...@le-tex.de> writes:
> The redirect on http://docbook.org/tdg51/en/html/ leads to
> http://tdg.docbook.org/tdg/5.1/index.html, the documentation of the
> 'index' element.
> It should probably redirect to http://tdg.docbook.org/tdg/5.1/docbook.html

Yes. :-(

https://github.com/docbook/defguide/issues/28

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com> | On the other hand, you have different
http://nwalsh.com/| fingers.


signature.asc
Description: PGP signature

[docbook] Re: author initials in bibliography entries

[Norman Walsh]

"Kraetke, Martin, le-tex" <martin.krae...@le-tex.de> writes:
> In DocBook 5.0, the element authorinitials can appear as children of
> biblioentry, bibliomixed, bibliomset, biblioset but not as children
> of author or personname.

In retorspect, that does seem…odd.

> 
>   
> 
>   
> P.
> Abad
>   
> 

But so does that. I’d expect the “author initials” of P. Abad to be “PA”
or something. That’s really just an abbreviated first name.

I wonder if P. captures the semantics
better. Not that I especially like it, but…

Be seeing you,
          norm

-- 
Norman Walsh <n...@nwalsh.com> | Debugging is 99% complete most of the
http://nwalsh.com/| time--Fred Brooks, jr.


signature.asc
Description: PGP signature

[docbook-apps] DocBook.org may wobble

[Norman Walsh]

Hello world,

I’m attempting to transition docbook.org to being automatically built by
Travis CI on GitHub. This will ease maintenance and contributions. That
may make access to DocBook.org a bit flakey over the next few hours/days.
Apologies in advance.

I’m also going to try to map wiki.docbook.org to the GitHub DocBook
wiki. But that’s a separate thing.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | 'I have done that,' says my memory. 'I
http://nwalsh.com/| cannot have done that'—says my pride,
  | and remains adamant. At last—memory
  | yields.--Nietzsche


signature.asc
Description: PGP signature

[docbook] DocBook.org may wobble

[Norman Walsh]

Hello world,

I’m attempting to transition docbook.org to being automatically built by
Travis CI on GitHub. This will ease maintenance and contributions. That
may make access to DocBook.org a bit flakey over the next few hours/days.
Apologies in advance.

I’m also going to try to map wiki.docbook.org to the GitHub DocBook
wiki. But that’s a separate thing.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | 'I have done that,' says my memory. 'I
http://nwalsh.com/| cannot have done that'—says my pride,
  | and remains adamant. At last—memory
  | yields.--Nietzsche


signature.asc
Description: PGP signature

[docbook] Re: DocBook TC Meeting Minutes 20 July 2016

[Norman Walsh]

d...@rlhamilton.net writes:
>   a. Norm to review the non-normative XML Schema version of 5.1
>   to make sure it has all the latest changes.
>   CONTINUE

I’m still hoping to work on that.


Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com> | The belief in a supernatural source of
http://nwalsh.com/| evil is not necessary; men alone are
  | quite capable of every
  | wickedness.--Joseph Conrad


signature.asc
Description: PGP signature

[docbook] Balisage: The Markup Conference

[Norman Walsh]

FYI: (Hope to see you there!)

Balisage: The Markup Conference
2016 Program Now Available
http://www.balisage.net/2016/Program.html

Balisage: where serious markup practitioners and theoreticians meet every 
August.

The 2016 program includes papers discussing reducing ambiguity in
linked-open-data annotations, the visualization of XSLT execution
patterns, automatic recognition of grant- and funding-related
information in scientific papers, construction of an interactive
interface to assist cybersecurity analysts, rules for graceful
extension and customization of standard vocabularies, case studies of
agile schema development, a report on XML encoding of subtitles for
video, an extension of XPath to file systems, handling soft hyphens in
historical texts, an automated validity checker for formatted pages,
one no-angle-brackets editing interface for scholars of German family
names and another for scholars of Roman legal history, and a survey of
non-XML markup such as Markdown.

XML In, Web Out: A one-day Symposium on the sub rosa XML that powers
an increasing number of websites will be held on Monday, August 1.
http://balisage.net/XML-In-Web-Out/

If you are interested in open information, reusable documents, and
vendor and application independence, then you need descriptive markup,
and Balisage is the conference you should attend. Balisage brings
together document architects, librarians, archivists, computer
scientists, XML practitioners, XSLT and XQuery programmers, implementers of
XSLT and XQuery engines and other markup-related software, Topic-Map
enthusiasts, semantic-Web evangelists, standards developers,
academics, industrial researchers, government and NGO staff,
industrial developers, practitioners, consultants, and the world's
greatest concentration of markup theorists. Some participants are busy
designing replacements for XML while other still use SGML (and know
why they do).

Discussion is open, candid, and unashamedly technical.

Balisage 2016 Program:
http://www.balisage.net/2016/Program.html

Symposium Program:
http://balisage.net/XML-In-Web-Out/symposiumProgram.html

==
Balisage: The Markup Conference 2016  mailto:i...@balisage.net
August 2-5, 2016   http://www.balisage.net
Preconference Symposium: August 1, 2016+1 301 315 9631
==


signature.asc
Description: PGP signature

[docbook-apps] Re: [OT] DocBook XSL license

[Norman Walsh]

"Jan Tosovsky" <j.tosov...@email.cz> writes:
> I'd like to verify if this license is compatible with that found in DocBook
> XSL distribution:
>
> http://docbook.sourceforge.net/release/xsl/current/COPYING or alternatively
> http://docbook.sourceforge.net/release/xsl/current/doc/copyright.html
>
> What do you think?

I think it’s probably ok.

> Btw, do you happen plan changing this license to something more common? :-)

Turns out the license is the MIT license, I think, but we can change
things to make that more clear.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com>  | A rusty nail placed near a
http://www.oasis-open.org/docbook/ | faithful compass, will sway it
Chair, DocBook Technical Committee | from the truth, and wreck the
   | argosy.--Sir Walter Scott


signature.asc
Description: PGP signature

[docbook-apps] Re: Tools to make DocBook easier

[Norman Walsh]

Lars Vogel <lars.vo...@gmail.com> writes:
> May I ask where does the code for the 'org.docbook.task' Gradle
> plug-in lives?

It's in the 2.0 repo:

  https://github.com/docbook/xslt20-stylesheets

It's also on Maven. I have a "getting started" project that uses it.
I should uncloak that, I guess.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com> | In science, "fact" can only mean
http://nwalsh.com/| "confirmed to such a degree that it
  | would be perverse to withhold
  | provisional assent." I suppose that
  | apples might start to rise tomorrow,
  | but the possibility does not merit
  | equal time in physics
  | classrooms.--Stephen J. Gould


signature.asc
Description: PGP signature

[docbook] Re: What is the use of allowing variablelists within variablelists?

[Norman Walsh]

Stefan Knorr <skn...@suse.de> writes:
> To be honest, I still think that allowing (formal|sim)para should be
> enough... but I can accept different opinions. At least this is expected
> and not a bug.

Yes, probably paras would be enough. Except when someone comes along
wanting one other thing. Then one other. By and large, DocBook has
abandoned attempts to be prescriptive. Unless there's a good reason,
anywhere you can put a block element, you can put any block element,
and anywhere you can put an inline, you can put any inline.

It's entirely reasonable to limit the elements you allow in a local
customization.


Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | Everything we love, no doubt, will
http://www.oasis-open.org/docbook/ | pass away, perhaps tomorrow,
Chair, DocBook Technical Committee | perhaps a thousand years hence.
   | Neither it nor our love for it is
   | any the less valuable for that
   | reason.--John Passmore


signature.asc
Description: PGP signature

[docbook-apps] Re: Slides with Docbook

[Norman Walsh]

camille <cami...@neodoc.biz> writes:
> that's really great news. We are interested in contributing to it, is it
> available anywhere yet?

No, not quite. I'll see if I can get it out this week or next, though
after three weeks on the road, I expect to be well and truly swamped
with my day job for a bit.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | Art happens--no hovel is safe from
http://www.oasis-open.org/docbook/ | it, no prince may depend upon it,
Chair, DocBook Technical Committee | and vastest intelligence cannot
   | bring it about.--J. M. Whistler


signature.asc
Description: PGP signature

[docbook] Re: Formatting bug in TDG

[Norman Walsh]

Shaun McCance <sha...@gnome.org> writes:
> http://docbook.org/tdg51/en/html/docbook.html
>
> The blurbs after subscript and superscript are supposed to contain
> subscripts and superscripts, but they don't in the TOC. I'm guessing
> that the code that builds the TOC just calls xsl:value-of on the
> refpurpose instead of applying templates to inline content.

Well spotted and, I believe, fixed for the next update.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com>  | A child becomes an adult when he
http://www.oasis-open.org/docbook/ | realizes he has a right not only
Chair, DocBook Technical Committee | to be right but also to be
   | wrong.--Thomas Szasz


signature.asc
Description: PGP signature

[docbook-apps] Re: Slides with Docbook

[Norman Walsh]

Niels Müller <neinalw...@gmail.com> writes:
> Does anyone make slides with docbook 5? If yes, how?

I've just ported my stylesheets backend to produce the markup that
Reveal.JS needs. Mostly, it's a little rough around the edges. I'll
get it in the next XSLT 2.0 stylesheets release.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | Resist the urge to hurry; it will
http://www.oasis-open.org/docbook/ | only slow you down--Bruce Eckel
Chair, DocBook Technical Committee |


signature.asc
Description: PGP signature

[docbook] Re: How to Contribute to the DocBook Project on GitHub?

[Norman Walsh]

Thomas Schraitle <tom_s...@web.de> writes:
> thanks to the release of the new DocBook XSL stylesheets and the
> move from SourceForge to GitHub. Great to see this!

I've no converted the 'docbook' user to an organization. That means we
can have teams of developers working on different parts of the
project.

> === 1. How to contribute?
> What is the preferred method in regards to collaboration for
> DocBook@GitHub? I can think of some scenarios:
>
> a. Move all(?) DocBook users on SourceForge to GitHub and give them
>write permissions
> b. Only a handful of users get write permissions, others have to create
>pull requests
> c. Something completely different?

I propose that several of us get write permissions to the repos. Now
that we're an org, we can have different teams for different repos.

I propose that everyone, those with write access and everyone else,
submit pull requests for changes. I think that's a nice clean model
and it encourages collaboration and code review.

> === 2. Branching model for DocBook?
> Does the DocBook project has decided yet about a branching model?
>
> For example, some projects consider the master branch as "holy" and
> only stable releases are published. Others create features in a special
> branch and merge them into master after the feature is finished. Some
> project use a develop branch etc. So there are almost endless
> possibilities with Git in comparison to SourceForge.
>
> Speaking of a develop branch: In this regard, I made some good
> experiences with GitFlow[1]. It's "a collection of Git extensions to
> provide high-level repository operations for Vincent Driessen's
> branching model[2]" according to its home page.
>
> What do you think? :)

I think gitflow is nice. I also think that with a bunch of folks
coming over from SourceForge without a lot of git experience, it's
going to be painful to impose a single model. There's plenty to learn
already.

Here's what I do:

1. Fork docbook/repo
2. In ndw/repo, I create a 'dev' branch
3. I do most of my work in 'dev'
4. When I'm ready to release a feature, I squash things down to
   a reasonable number of commits and make a pull request to
   'master' on docbook/repo
5. On docbook/repo, we can get some review or we can be bold
   and just accept the request
6. When it's time to do a release, tag the 'master' branch and
   make the release.

I'll be working to make the release part automatic with Travis CI, but
that's not fully automated yet for all projects.

> -
> [1] https://github.com/petervanderdoes/gitflow-avh
> [2] http://nvie.com/git-model

    Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | Art happens--no hovel is safe from
http://www.oasis-open.org/docbook/ | it, no prince may depend upon it,
Chair, DocBook Technical Committee | and vastest intelligence cannot
   | bring it about.--J. M. Whistler


signature.asc
Description: PGP signature

[docbook] Re: How to Contribute to the DocBook Project on GitHub?

[Norman Walsh]

Stefan Seefeld <ste...@seefeld.name> writes:
> The more important (IMHO) questions are about the infrastructure needed
> to support this:
>
> * A working build system

I've moved to gradle for the repos I'm doing active work on. Other
repos can make their own choices.

> * CI support (travis-ci ?)

Travis CI is the way to go, I think. Again, I think I've got it setup
for the repos I'm actively working on.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com>  | One stops being a child when one
http://www.oasis-open.org/docbook/ | realizes that telling one's
Chair, DocBook Technical Committee | trouble does not make it
   | better.--Cesare Pavese


signature.asc
Description: PGP signature

[docbook-apps] Re: DocBook XSL 1.79.0 release is available

[Norman Walsh]

Stefan Seefeld <ste...@seefeld.name> writes:
>> I'm not sure if this definition of "large open-source project" would fit
>> for a (hypothetical) DocBook organization. However, maybe it would be
>> beneficial to have one as it allows more fine-grained repository
>> permissions? Not sure if that's a good thing for DocBook.
>>
>> Just my thoughts. :))
>
> Yes, I fully agree to the above.

I'm trying to figure it out. Suggestions comments etc most welcome.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | A child becomes an adult when he
http://www.oasis-open.org/docbook/ | realizes he has a right not only
Chair, DocBook Technical Committee | to be right but also to be
   | wrong.--Thomas Szasz


signature.asc
Description: PGP signature

[docbook] Re: How to use classsynopsis and friends

[Norman Walsh]

maxwell <maxw...@umiacs.umd.edu> writes:
> It's too late now, I'm sure, but as a user of DocBook for purposes
> other than software documentation (we use it for grammars), DocBook
> seems bloated with all these tags for software (the aforementioned
>  being a perfect example).

Yes. Well. Fair enough, but

  "DocBook is a schema (available in several languages including RELAX
  NG, SGML and XML DTDs, and W3C XML Schema) maintained by the DocBook
  Technical Committee of OASIS. It is particularly well suited to
  books and papers about computer hardware and software (though it is
  by no means limited to these applications)."

> In our customization, we
> remove all those tags, and add in the ones we need for literate
> programming and for linguistics, using a namespace prefix for our
> tags.

That's absolutely perfect. It's exactly what users should do with
DocBook. You're free to put your linguistic elements in the DocBook
namespace too, if you'd like. See:

http://docbook.org/tdg51/en/html/ch01.html#nsusage

and

http://docbook.org/tdg51/en/html/ch05.html#s-notdocbook

> It always seemed to me like DocBook could have had a much simpler
> model, by putting the software- and hardware-specific tags into a
> separate namespace. That would make it easier for other potential
> users to wade through the remaining elements and decide which of them
> they really need. Obviously that couldn't have happened until DB5, and
> it's probably too late now. I suppose the next best thing would be to
> compile a list of tags that are core DB (meaning about text in
> general), and/or a list of software- and hardware-specific tags, which
> would make it easier for potential users.

You could start with Simplified DocBook as a base.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | Hanging is too good for a man who
http://www.oasis-open.org/docbook/ | makes puns; he should be drawn and
Chair, DocBook Technical Committee | quoted.--Fred Allen


signature.asc
Description: PGP signature

[docbook] Re: How to use classsynopsis and friends

[Norman Walsh]

Stefan Seefeld <ste...@seefeld.name> writes:
> Yes, at this point it's not possible to remove all the original synopsis
> elements, so we'll have to live with them. But if users switch to the
> API extension (if it turns out to be useful to anyone outside a small
> community, that is), these elements may indeed be forgotten as a
> historic accident.

We could, at some future "big bang" changover, DocBook 7.0 for
example, remove them. I suppose.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com>  | Art has to move you and design
http://www.oasis-open.org/docbook/ | does not, unless it's a good
Chair, DocBook Technical Committee | design for a bus.--David Hockney


signature.asc
Description: PGP signature

[docbook] Re: How to use classsynopsis and friends

[Norman Walsh]

Aristedes Maniatis <a...@ish.com.au> writes:
> I guess I'm just not understanding a fundamental concept in docbook
> then. I had always assumed docbook was a pure documentation schema and
> not intended to model real world concepts. When I look at

Well. Every now and then, we've been persuaded to do some modeling
in the aid of documentation. The class/method/fieldsynopsis elements
are one example, cmdsynopsis an older example, and everyone's favorite
mistake msgset.

Generally speaking, I think our forays into modeling have
been...disappointing, but that's where we are.

Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | No man's knowledge here can go
http://www.oasis-open.org/docbook/ | beyond his experience.--John Locke
Chair, DocBook Technical Committee |


signature.asc
Description: PGP signature

[docbook-apps] Moving the DocBook wiki

[Norman Walsh]

Hi folks,

Over the last day or so, I captured the state of wiki.docbook.org as
best I could and ported the pages over to:

  https://github.com/docbook/wiki

I think if I convert the "docbook" user at github into an "organization",
I'll be able to setup wiki.docbook.org to point to it.

In the meantime, feel free to explore and report any problems. If you
send me your github ID, I'll add you as a collaborator and then you
can edit the pages.

Be seeing you,
      norm

-- 
Norman Walsh <n...@nwalsh.com>  | When we are tired, we are attacked
http://www.oasis-open.org/docbook/ | by ideas we conquered long ago.--
Chair, DocBook Technical Committee | Nietzsche


signature.asc
Description: PGP signature

[docbook-apps] Re: Tools to make DocBook easier

[Norman Walsh]

Warren Block <wbl...@wonkity.com> writes:
> What tools are there to make working with DocBook easier? 

I'm just in the process of finishing up a first release of a tool
to make DocBook publishing easier with gradle. Given doc.xml, written
in DocBook, this build.gradle file will download all of the necessary
dependencies and run the transformations.

buildscript {
  repositories {
mavenCentral()
maven { url "http://maven.restlet.org; }
  }

  dependencies {
classpath group: 'org.docbook', name: 'docbook-xslt2', version: '2.0.14'
classpath group: 'com.xmlcalabash', name: 'xmlcalabash1-print', version: 
'1.1.4'
  }
}

repositories {
  mavenLocal()
  mavenCentral()
}

apply plugin: 'org.docbook.task'

import org.docbook.DocBookTask

task publishhtml5(type: DocBookTask) {
  format "html"
  input "doc.xml"
  output "index.html"
}

task publishxhtml(type: DocBookTask) {
  format "xhtml"
  input "doc.xml"
  output "index.html"
}

task publishpdf(type: DocBookTask) {
  format "foprint"
  input "doc.xml"
  pdf "doc.pdf"
}

Needs documentation and such, but it does at least run now. :-)

        Be seeing you,
  norm

-- 
Norman Walsh <n...@nwalsh.com>  | There might very well be nothing;
http://www.oasis-open.org/docbook/ | nor anyone. No one to notice that
Chair, DocBook Technical Committee | there is nothing, and to consider
   | that natural. But that there is
   | something, and, whatever it may
   | be, the strange thing! I shall
   | never cease being amazed at
   | this.--André Gide


signature.asc
Description: PGP signature

[docbook] DocBook 5.1CR4 released

[Norman Walsh]

Hello world,

This morning I uploaded DocBook 5.1CR4 to http://docbook.org/xml/5.1CR4/

This version corresponds to the PRD02/CSPRD02 draft versions submitted to
OASIS. It fixes issue 48

   https://github.com/docbook/docbook/issues/48

The other PRD/CSPRD fixes were all documention/spec related, see:

   http://docbook.org/specs/docbook-v5.1-csprd02.html

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | My fate cannot be mastered; it can
http://www.oasis-open.org/docbook/ | only be collaborated with and
Chair, DocBook Technical Committee | thereby, to some extent, directed.
   | Nor am I the captain of my soul; I
   | am only its noisiest
   | passenger.--Aldous Huxley


signature.asc
Description: PGP signature

[docbook] DocBook V5.1CR3 XSD

[Norman Walsh]

Hello world,

This afternoon (well, local afternoon anyway), I published an XML
Schema version of DocBook V5.1CR3:

  http://docbook.org/xsd/5.1CR3/

I assert that it's a valid XSD. Because Saxon EE said so.

It passed a smoke test on a few DocBook documents, but is surely
buggy. It is also considerably more liberal than the normative DocBook
schemas. I don't expect it to reject any valid DocBook documents, but
it is by no means guaranteed that passing the XSD test means your
document is valid.

Interesting open question: how many of these XSD validation
infilicities could be tested with XSD 1.1 xs:assert statements?

Share and enjoy.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | If you put tomfoolery into a
http://www.oasis-open.org/docbook/ | computer, nothing comes out of it
Chair, DocBook Technical Committee | but tomfoolery. But this
   | tomfoolery, having passed through
   | a very expensive machine, is
   | somehow enobled and no-one dares
   | criticize it.--Pierre Gallois


signature.asc
Description: PGP signature

[docbook] Announcing (informally) DocBook V5.1CR3

[Norman Walsh]

Hello world,

Long time, no see. 

I've (informally) released DocBook V5.1CR3 on docbook.org:

  http://docbook.org/xml/5.1CR3/

I still have to pull together some sort of ZIP file or something to
get it officially released on the OASIS site. That's a task for
tomorrow.

In the meantime, please take CR3 for a test drive, I think 5.1 is very
nearly finished.


Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | We look back on our life as a
http://www.oasis-open.org/docbook/ | thing of broken pieces, because
Chair, DocBook Technical Committee | our mistakes and failures are
   | always the first to strike us, and
   | outweigh in our imagination what
   | we have accomplished and
   | attained.-- Goethe


signature.asc
Description: PGP signature

[docbook] Re: xi:include problem

[Norman Walsh]

Dew, Simon simon@sbdinc.com writes:
 xmllint ver 2.7.8 (on Windows 7 Ultimate, 32-bit) gives:

   xmllint --noout --relaxng %DOCBOOK_XML%\rng\docbook.rng Errors.docbook

On my Mac, xmllint definitely gives confusing errors.

$ xmllint --version
xmllint: using libxml version 20800
   compiled with: Threads Tree Output Push Reader Patterns Writer SAXv1 FTP 
HTTP DTDValid HTML Legacy C14N Catalog XPath XPointer XInclude Iconv ISO8859X 
Unicode Regexps Automata Expr Schemas Schematron Modules Debug Zlib Lzma
$ xmllint --noout --relaxng 
/projects/docbook/docbook/relaxng/schemas/docbook.rng /tmp/err.xml
/tmp/err.xml:14: element info: Relax-NG validity error : Element book has extra 
content: info
/tmp/err.xml:11: element book: Relax-NG validity error : Expecting element 
abstract, got book
/tmp/err.xml:11: element book: Relax-NG validity error : Did not expect element 
book there
/tmp/err.xml:11: element book: Relax-NG validity error : Expecting element 
audiodata, got book
/tmp/err.xml:11: element book: Relax-NG validity error : Expecting element 
example, got book
/tmp/err.xml fails to validate

It definitely appears to have gone off the rails, but the only thing
wrong with that file is the conref attribute.

Curiously, if you remove the conref attribute, the file validates. My
guess is that xmllint percolates the validity error up from the bad
attribute to the info element, decides that the info element doesn't
match any patterns (which, it doesn't) and so it's an extra element.
From there, I don't know what happens.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Time is the old justice that
http://www.oasis-open.org/docbook/ | examines all offenders.--
Chair, DocBook Technical Committee | Shakespeare


signature.asc
Description: PGP signature

[docbook] Re: xi:include problem

[Norman Walsh]

Alex Kleider aklei...@sonic.net writes:
 The way I'm solving the problem is making each xIncluded file a valid
 DocBook file and validating each included file before using xmllint
 and then doing a final validation. This restricts me to making each
 xIncluded component an article since I think this is the lowest
 level element that can be a valid DocBook.

You can go lower then article. You can go to anything with a title,
roughly:

start =
  (db.set
   | db.book
   | db.divisions
   | db.components
   | db.navigation.components
   | db.section
   | db.para)
  | (db.abstract
 | db.mediaobject.content
 | db.audiodata
 | db.imagedata
 | db.textdata
 | db.videodata
 | db.caption
 | db.publishing.blocks
 | db.formal.blocks
 | db.informal.blocks
 | db.formalpara
 | db.inlinemediaobject
 | db.list.blocks
 | db.legalnotice
 | db.verbatim.blocks
 | db.graphic.blocks
 | db.personblurb
 | db.revhistory
 | db.simpara
 | db.step
 | db.stepalternatives)
  | (db.partintro | db.simplesect)
  | db.annotation
  | (db.sect1 | db.sect2 | db.sect3 | db.sect4 | db.sect5)
  | (db.refentry | db.refsection | db.refsynopsisdiv)
  | (db.refsect1 | db.refsect2 | db.refsect3)
  | (db.glossary | db.glossdiv | db.glosslist)
  | (db.bibliodiv | db.bibliolist)
  | (db.setindex | db.index | db.indexdiv)
  | (db.toc | db.tocdiv)
  | (db.task | db.taskprerequisites | db.taskrelated | db.tasksummary)
  | (db.calloutlist
 | db.programlistingco
 | db.screenco
 | db.imageobjectco)
  | (db.productionset | db.constraintdef)
  | (db.msg
 | db.msgexplan
 | db.msgmain
 | db.msgrel
 | db.msgset
 | db.msgsub)
  | (db.qandadiv | db.qandaentry | db.qandaset)
  | (db.equation | db.informalequation)
  | db.cmdsynopsis
  | (db.synopsis.blocks | db.funcsynopsisinfo | db.classsynopsisinfo)
  | db.admonition.blocks
  | db.topic

 Comments?  Are there better ways?

Seems reasonable.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Everything in the universe goes by
http://www.oasis-open.org/docbook/ | indirection. There are no straight
Chair, DocBook Technical Committee | lines.-- Emerson


signature.asc
Description: PGP signature

[docbook] DocBook V5.1CR2 released

[Norman Walsh]

Hello folks,

The second candidate release of DocBook V5.1 has been released. You
can get it from docbook.org

  http://docbook.org/xml/5.1CR2/

or through OASIS at

  
https://tools.oasis-open.org/version-control/browse/wsvn/docbook/xml/5.1CR2/#_xml_5.1CR2_

I've upgraded TDG5.1 to correspond to CR2. 

I haven't got the 5.1 spec built yet, but here's a summary of what's changed
since 5.0 based on my casual inspection of the repository commits:

* Attempt to address issue #303 by moving multimediaparam into the
  *data elements and allowing the *data elements to be repeated

* Added RDFa Lite attributes to DocBook; removed the dbrdfalite
  customization layer

* Fix issue #300 add a class to see/seealso to handle the 'under'
  case.

* Fix issue #277 add a result element

* Updated to support ITS 2.0

* Fixed error in indexterm content model

* Fix RFE 3547943 don't allow secondary without a primary in indexterm

* Fix RFE 3531365 allow navigation components at the beginnings of
  sections

* Fix RFE 3517981 remove spurious, duplicate 'other' value.

* Attempt to implement the whole proposal for accessability attributes
  in CALS tables

* Fix RFE 3530659 allow admonitions in formal objects

* Fix RFE 3571149 allow articles in sets

* Added scope attribute

* Added outputformat as an effectivity attribute

* Added AltGr and Return to keycap

* Rename @fileref to @href (in assemblies only)

* Fixed bug in Schematron assertions, thanks to Hussein Shafie

* Attempt to resolve RFE 3500814, add pgwide to informalexample and
  informalequation

* Make info on structure and module optional

* Implemented recent TC changes:
  http://lists.oasis-open.org/archives/docbook-tc/201203/msg0.html

* Adopted the recent proposals to add attributes/parameters to audio
  and video objects

* Attempt to implement RFE #3368279, make content optional in
  components and sections

* Allow link in extendedlink, in preparation for arc and locator being
  removed in V6.0

* Fix RFE#3406169, allow multiple procedure elements in task

* Fix RFE#3390036, allow tag elements to nest

* Reworked XLink attributes to support simple/extended links

* Added pattern for imagedata SVG and MathML content (so that it could
  be extended by the XInclude schema)

* Added XInclude to images and equations; allow foreign,
  namespace-qualified attributes on the xi:include element

* RFE 3150303, broaden content model of contrib

* RFE 3227210, fix HTML informaltable attributes

* RFE 3274136, allow production to contain rhs+

* RFE 3287339, support ISTC as a biblioid class

* Renamed pattern db.any.docbook to db._any.docbook for consistency

* Fix RFE 3199793, allow xi:include in set

* Fixed RFE 3174769, add securitycontext and other to systemitem

* Fix RFE 3171553, allow dedication in article

* Changed Schematron namespace to official ISO Schematron URI

* Allow topic in chapter and appendix (as an alternative to narrative
  content) per May 2010 TC meeting

* Fix content model of book and part to make topic an alternative, not
  part of the component mixture

* RFE #2964576: move table/informaltable exclusion down to entry where
  it belongs

* Fix RFE 2821653: allow indexterms in footnotes

* RFE 2907131 Allow simplesect in colophon

* RFE 2907125 remark should allow all inlines

* RFE 2907124 make personal name components avialable directly in
  bibliomixed and bibliomset

* RFE 2770858/2791288 add more elements to ubiquitous inlines

* Change xlink from/label/to attributes. They're no longer optional
* RFE 1958051 address should allow orgname

* RFE 2315507 add subtitle to sidebar

* RFE 2067915 Add floatstyle attribute to sidebar

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | My problems start when the smarter
http://www.oasis-open.org/docbook/ | bears and the dumber visitors
Chair, DocBook Technical Committee | intersect.--Steve Thompson,
   | wildlife biologist at Yosemite
   | National Park


signature.asc
Description: PGP signature

[docbook] Re: xi:include problem

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 That's how, not what Mr Walsh!
 Herrumph.

Fair enough. Here's my everyday DocBook pipeline:

p:declare-step version=1.0 name=main
xmlns:exf=http://exproc.org/standard/functions;
xmlns:p=http://www.w3.org/ns/xproc;
  p:input port=source/
  p:output port=result/
  p:input port=parameters kind=parameter/

  !-- The style option specifies the stylesheet. The standard HTML one by 
default. --
  p:option name=style 
select='/projects/docbook/xslt20/xslt/base/html/docbook.xsl'/

  !-- The schema option specifies the schema. The RDFaLite one by default. --
  p:option name=schema 
select='/projects/docbook/docbook/relaxng/schemas/dbrdfalite.rng'/

  !-- Expand XIncludes --
  p:xinclude/

  !-- I've started using some ad-hoc shortcuts in my writing. For
   example, I write about XML so often that I use att instead
   of tag class=attribute. The ndw2db.xsl stylesheet
   normalizes my shortcut markup back into proper DocBook. --
  p:xslt name=normalize
p:input port=stylesheet
  p:document href=/Users/ndw/stylesheets/ndw2db.xsl/
/p:input
  /p:xslt

  !-- Load the stylesheet and the schema. If I specify them as
   options, I want them resolved relative to the current working
   directory, not this stylesheet, so I have to work a little
   harder. --
  p:load name=style
p:with-option name=href select=resolve-uri($style, exf:cwd())/
  /p:load

  p:load name=schema
p:with-option name=href select=resolve-uri($schema, exf:cwd())/
  /p:load

  !-- Validate my (normlized) DocBook markup --
  p:validate-with-relax-ng
p:input port=source
  p:pipe step=normalize port=result/
/p:input
p:input port=schema
  p:pipe step=schema port=result/
/p:input
  /p:validate-with-relax-ng

  !-- And...style it! --
  p:xslt
p:input port=stylesheet
  p:pipe step=style port=result/
/p:input
  /p:xslt
/p:declare-step

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | To the man who is afraid
http://www.oasis-open.org/docbook/ | everything rustles.-- Sophocles
Chair, DocBook Technical Committee |


signature.asc
Description: PGP signature

[docbook] Formal vs. informal

[Norman Walsh]

 I personally never did understand formal vs informal... or it never
 made sense to me?

Maybe those aren't good names but the distinction is simple: formal
objects have required titles, informal ones don't.

table
titleThis is a formal table/title
tgroup.../tgroup
/table

That table will have a title rendered, possibly with a label, and if
the document has a list of tables it will appear in that list. It
might also float.

informaltable
tgroup.../tgroup
/informaltable

That table will just be rendered where it is, with no title or label.
It won't appear in the list of tables if there is one. It won't
float.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | 'Heartless Cynics,' the young men
http://www.oasis-open.org/docbook/ | shout, / Blind to the world of
Chair, DocBook Technical Committee | Fact without; / 'Silly Dreamers,'
   | the old men grin / Deaf to the
   | world of Purpose within.--W. H.
   | Auden


signature.asc
Description: PGP signature

[docbook] Re: Formal vs. informal

[Norman Walsh]

David Cramer da...@thingbag.net writes:
 On 12/11/2013 07:45 AM, Norman Walsh wrote:
 Maybe those aren't good names but the distinction is simple:
 formal objects have required titles, informal ones don't.
 ...

 Wrt this, I've always wondered about procedure. Was
 informalprocedure just way too long? Or did it predate the distinction?

In the beginning, as I recall, we had table, figure, and example with
required titles and equation and procedure with optional titles.

There was resistance to making title on, for example, figure, optional
because books often contained lists of figures with their labels and
titles. Processing systems 20 years ago(!) weren't as flexible as they
are today. Saying that the list of figures should only include those
figure elements that had a child title wasn't practical.

So the informal variants were added.

Making the title required wasn't backwards compatible. We created
informalequation and probably should have created informalprocedure
too, but it just didn't occur to anyone and no one asked.

I suppose making the titles optional and abandoning the informal*
elements is a possibility today. For DocBook V6 or beyond.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | There is always some accident in
http://www.oasis-open.org/docbook/ | the best of things, whether
Chair, DocBook Technical Committee | thoughts or expressions or deeds.
   | The memorable thought, the happy
   | expression, the admirable deed are
   | only partly yours.--Henry David
   | Thoreau


signature.asc
Description: PGP signature

[docbook] Re: xi:include problem

[Norman Walsh]

!-- The schema option specifies the schema. The RDFaLite one by default. 
 --
p:option name=schema 
 select='/projects/docbook/docbook/relaxng/schemas/dbrdfalite.rng'/

 ??? Schema for . output? DBRDFa? Surely not the input docbook?

The DocBook customization that adds RDFa Lite attributes. Which I deleted
today because the DocBook TC decided to make them part of DocBook V5.1 :-)

!-- I've started using some ad-hoc shortcuts in my writing. For
 example, I write about XML so often that I use att instead
 of tag class=attribute. The ndw2db.xsl stylesheet
 normalizes my shortcut markup back into proper DocBook. --

 Catch up Mr W! I've had those for yonks. Wrong list for emacs macros 
 though

I don't use emacs macros for it, though. I literally write

  paraThe attrevisionflag/att attribute.../para

!-- Load the stylesheet and the schema. If I specify them as
 options, I want them resolved relative to the current working
 directory, not this stylesheet, so I have to work a little
 harder. --
p:load name=style
  p:with-option name=href select=resolve-uri($style, exf:cwd())/
/p:load

p:load name=schema
  p:with-option name=href select=resolve-uri($schema, exf:cwd())/
/p:load


 exfproc... are these 'standard' inasmuch as ... Calabash has them?

They're standard exproc.org functions, if that helps.

 Does this stop on error Norm?

Yes. Goes bang on error.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | To think is not enough; you must
http://www.oasis-open.org/docbook/ | think of something.--Jules Renard
Chair, DocBook Technical Committee |


signature.asc
Description: PGP signature

[docbook] Re: Equations and figures as descendants of an example

[Norman Walsh]

Erik Leunissen e.leunis...@hccnet.nl writes:
 I've construed a docbook 5.0 xml document whose structure appears to
 be invalid because it holds equation's and figure's as descendants
 of an example.

 - I'm curious about the rationale regarding this being invalid.

I think, generally speaking, it would be unsual to see a titled figure
nested inside a titled example. How, for example, would you label such
a figure?

What's your motivation for putting figures and equations inside an
example?

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | It is necessary to try to surpass
http://www.oasis-open.org/docbook/ | oneself always; this occupation
Chair, DocBook Technical Committee | ought to last as long as
   | life.--Christina, Queen of Sweden


signature.asc
Description: PGP signature

[docbook] Re: xi:include problem

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 Step 1, process the xinclude
 Step 2. Validate


With, uh, a technology like, uhm, XProc maybe? :-)

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Wandering in a vast forest at
http://www.oasis-open.org/docbook/ | night, I have only a faint light
Chair, DocBook Technical Committee | to guide me. A stranger appears
   | and says to me: My friend, you
   | should blow out your candle in
   | order to find your way more
   | clearly. This man is a
   | theologian.-- Diderot


signature.asc
Description: PGP signature

[docbook] Re: HTML5 Audio + Video multiple sources

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 I'm interested in your (and anyone elses) thoughts on HTML5 Norm?

It's not what I would have done, but no one asked me. As a refinement
of HTML for use in browsers as a skeleton to hang JavaScript actions
on, it's a very good fit. As a vocabulary to tag documents, it's
better than HTML4 if a bit...quirky.

 What functionality is lost please?

The HTML5 image/video elements, AFAICT, have no facilities for setting
the size or scaling, for example. In HTML+CSS you'd do that by
wrapping eleven divs with random class names [stop being fascetious -ed]
around the video and using CSS to style them.

We have width and depth (yes, I wish we'd named that height),
contentwidth and contentdepth, align, valign, scale, and scalefit
as attributes on the data element and carefully considered rules for how
they interact, see: http://docbook.org/tdg51/en/html/imagedata.html

If we adopted something isomorphic to HTML5, we'd lose the size and
scaling controls.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Internet connection, $19.95 a
http://www.oasis-open.org/docbook/ | month. Computer, $799.95. Modem,
Chair, DocBook Technical Committee | $149.95. Telephone line, $24.95 a
   | month. Software, free. USENET
   | transmission, hundreds if not
   | thousands of dollars. Thinking
   | before posting, priceless.
   | Somethings in life you can't buy.
   | For everything else, there's
   | MasterCard.--Graham Reed, in the
   | Scary Devil Monastery


signature.asc
Description: PGP signature

[docbook] Re: Equations and figures as descendants of an example

[Norman Walsh]

Erik Leunissen e.leunis...@hccnet.nl writes:
 First off: I feel a bit uncomfortable that I don't quite grasp the
 reason that you asking these questions. Maybe there is an implicit
 misunderstanding. I'm going to try to be explicit ...

Sorry. I wasn't trying to make you uncomfortable. I'm absolutely
not suggesting that you're wrong or that you don't have a good use
case, it's just not one that I understand yet.

 What's your motivation for putting figures and equations inside an
 example?

 I've got the feeling that asking for a motivation is like turning the
 world upside down. Have you never seen a theoretical exposition in a
 textbook that clarifies it's theory with an example, where a figure is
 used (regardless titles, regardless figure labels)?

I can't think of one where the figure was nested inside the example, but
I'm not disputing that it's a logical possibility.

 Before I continue, I'd like to check whether there is anything wrong
 with my understanding. Maybe it's the case that you mean something
 quite different with an example than I do?

Part of our miscommunication may be a question of perspective. I tend
to think of figure, table, example, and equation as all members of a
class of thing (which we call formal objects because they have a
title).

So I see allow figure in example as naturally leading to allow
figure in table and allow table in equation. Historically, DocBook
has not allowed formal objects to nest.

However, they aren't really all exactly uniform. For even more distant
historical reasons, the title on equation is optional. And I can see
that example can easily be taken as broader than figure, table, or
equation.

That said, this still feels a bit weird to me:

example
  titleExample of something/title

  paraSome prose./para

  figure
titleFigure title/title
mediaobject.../mediaobject
  /figure
/example

I'd still like to better understand what your examples actually look
like and what your rendering expectations are. Again, not because I
think they're wrong, just because it would help me understand.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Reason's last step is the
http://www.oasis-open.org/docbook/ | recognition that there are an
Chair, DocBook Technical Committee | infinite number of things which
   | are beyond it.-- Pascal


signature.asc
Description: PGP signature

[docbook-apps] Re: Syntax highlighting

[Norman Walsh]

Jan Tosovsky j.tosov...@email.cz writes:

 On 2013-12-09 Norman Walsh wrote:
 
 ... future work on XSL FO has largely been abandoned.

 Does it mean that XSL-FO 2.0/next is not planned any more? Is there any
 citation for this?

http://www.w3.org/XML/XPPL/

  This WOrking (sic) Group is no longer active, because of
  insufficient participation. The specifications are no longer
  maintained.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Mankind are always happy for
http://www.oasis-open.org/docbook/ | having been happy; so that if you
Chair, DocBook Technical Committee | make them happy now, you make them
   | happy twenty years hence by the
   | memory of it.--Sydney Smith


signature.asc
Description: PGP signature

[docbook-apps] Re: Syntax highlighting

[Norman Walsh]

Jan Tosovsky j.tosov...@email.cz writes:
 While I don't plan to upgrade my generating workflow to XSL 2.0 stylesheets
 in the near future, I am quite curious whether the proposed HTML+CSS
 approach can really cover all common needs:

 1. ToC and Index with page numbers
 2. Bookmarks
 3. Double-sided version (different recto/verso margins, header/footer
 content)
 4. Running header-footers (differences amongst title, blank or recto/verso
 pages)
 5. Absolute positioning of title page graphics or other page elements
 6. Using PDF format for images
 7. Change bars

Some of those things are easy, some not so easy. But I expect they can
all be done. Not from the stock HTML stylesheets that you'd use on the
web, but from a HTML-for-print stylesheet. I hear that O'Reilly now
uses HTML+CSS for their print books.

The reality is that free XSL FO tools never really matured. The
commercial ones all work, but all have extensions to handle things
that weren't fully specified.

There's a large community focused on HTML+CSS+JS these days. It seems
more likely (to me) that free HTML+CSS print tools will come along
before greatly improved free XSL FO tools. Especially since future work
on XSL FO has largely been abandoned.

There are commercial HTML+CSS print formatters today that seem to be
comparable to the XSL FO ones. AntennaHouse supports both and
PrinceXML seems to do a competent job.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Everything that irritates us about
http://www.oasis-open.org/docbook/ | others can lead us to an
Chair, DocBook Technical Committee | understanding of ourselves.--Carl
   | Jung


signature.asc
Description: PGP signature

[docbook-apps] Re: HTML5 Audio + Video multiple sources

[Norman Walsh]

Peter Fleck peterfl...@gmail.com writes:
 video
   source src=video.ogg type=video/ogg / 
   source src=video.mp4 type=video/mp4 /
   source src=video.webm type= video/webm
 /video

 If tried different ways but haven't been able to do it yet, is it possible?

Not really. HTML5 brings significant new functionality to the realm of
audio and video. It's probably time to revisit the markup that DocBook
provides.

Historically, neither browsers nor other rendering tools provided any
facility for mutiple representations or fallback. Among the design
goals for the existing mediaobject markup was the ability to provide
for multiple alternatives in the DocBook source with the understanding
that the transformation from DocBook to the output format would pick
the right one.

It was never an elegant design in part because the transformation
tools rarely had any clue what the actual capabilities of the ultimate
viewing tool would be.

It also produced markup that's several layers deep. Those layers are
needed in the case where multiple alternatives must be selected by the
transformation tool, but in the (very common case) that no
alternatives are provided, they're just extra tags.

The situation is muddied further by the fact that, as alternatives,
the videodata element has attributes that appear to be badly factored.

For example, it seems likely that no matter which of two or three
video alternatives you have, you want the content width, content
depth, scaling, alignment and such to be the same.

In defense of the odd factoring, bear in mind that for raster images,
the choices are less clear. If a medium-resolution black and white
image is an alternative for a high-res four color image, then perhaps
you do want the size, scale, and alignment to differ between the two
images.

I'm not sure what the right answer is. If HTML5 is going to represent
the state of the art for the forseable future, an argument can be made
that we should simply copy its model. But we'd lose functionality if
we did that (functionality that in the HTML5 world is pushed off to
random nesting divs with class attributes).

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Labor, n. One of the processes by
http://www.oasis-open.org/docbook/ | which A acquires property for
Chair, DocBook Technical Committee | B.--Ambrose Bierce


signature.asc
Description: PGP signature

[docbook-apps] Syntax highlighting

[Norman Walsh]

Hello world,

A fair bit of effort in the DocBook stylesheets goes into parsing,
decomposing, annotating, and recomposing program listings for the
purpose of adding line numbers to them. There's also a bunch of work
that goes into syntax highlighting them.

Occasionally, this takes a *long* time.

It appears that modern systems do this in the JavaScript layer on the
client. They also use tables to render line numbers.

I'm tempted to move in this direction. Comments?

As long as I'm airing dirty laundry, I'm also tempted to abandon the
XSL stylesheets and work instead on a purpose-built HTML+CSS rendering
for printing.

I should say that this note is particularly about the XSLT 2.0
stylesheets that I've been working on, not the standard ones.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Resist the urge to hurry; it will
http://www.oasis-open.org/docbook/ | only slow you down--Bruce Eckel
Chair, DocBook Technical Committee |


signature.asc
Description: PGP signature

[docbook] Re: adding to toc

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 I have set phrases, plain text in para elements.
 I want to use these as targets for cross linking.
 What's the best markup pls?

 e.g.1.3.30
 Is anchor xml:id=a.1.2.30/1.3.30
 suitable?
 I'm thinking of writing a macro to do this by hilighting
 the text.
 Then another to create the xref.

That's what anchor is for. But if they're actually phrases, I think I'd
be tempted to use phrase:

  phrase xml:id=a.1.2.301.3.30 or whatever the phrase is/phrase.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Men never do evil so completely
http://www.oasis-open.org/docbook/ | and cheerfully as when they do it
Chair, DocBook Technical Committee | from a religious
   | conviction.--Blaise Pascal


signature.asc
Description: PGP signature

[docbook] Re: Simplifying image markup

[Norman Walsh]

 You mean introducing graphic element back?

 http://www.docbook.org/tdg/en/html/graphic.html

Well, not *exactly*. :-)

 :-) Certainly we can revisit design and offer something simpler. At that
 time we should check whether we are aligned with what HTML5's
 audio/video elements offer.

I believe we did that for DocBook 5.

 Also approach for delivering one image in
 multiple resolutions is now being developed for HTML so if we are going
 to simplify something we should be prepared for upcoming changes.

Yes. Any pointers?

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Nearly all men can stand
http://www.oasis-open.org/docbook/ | adversity, but if you want to test
Chair, DocBook Technical Committee | a man's character, give him
   | power.--Abraham Lincoln


signature.asc
Description: PGP signature

[docbook] Re: Linking to an Unknown Amount of Targets (1:n relationships)?

[Norman Walsh]

Bob Stayton b...@sagehill.net writes:
 I know the issue in the past with adding it to the stylesheet was: How
 do you render a multi-link? We assumed it required a dynamic
 presentation, so when the user clicked on the link they got a list of
 targets to choose from. In HTML, you could generate a pop-up list, but
 in PDF?

My plan is to do something along the lines Eric proposed:

http://www.balisage.net/Proceedings/vol7/html/Vlist01/BalisageVol7-Vlist01.html

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | To think is not enough; you must
http://www.oasis-open.org/docbook/ | think of something.--Jules Renard
Chair, DocBook Technical Committee |


signature.asc
Description: PGP signature

[docbook] Re: Simplifying image markup

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 Should we consider allowing bare imagedata/audiodata/videodata
 elements in DocBook? I suppose they'd be both inline and block
 elements.

 How to include the text alternative for accessibility please?

You'd have to use the wrappers for that.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | The sudden disappointment of hope
http://www.oasis-open.org/docbook/ | leaves a scar which the ultimate
Chair, DocBook Technical Committee | fulfillment of that hope never
   | entirely removes.--Thomas Hardy


signature.asc
Description: PGP signature

[docbook] Simplifying image markup

[Norman Walsh]

Hi folks,

A friend was griping about the complexity of mediaobjects earlier today.

  figure xml:id=ex.pythagorean
titleThe Pythagorean Theorem Illustrated/title
mediaobject
  imageobject condition=print
imagedata fileref=figs/print/db5d_ref01.pdf/
  /imageobject
/mediaobject
  /figure

I grant that there are a few more layers of wrapper in there than
you'd really like. The wrappers exist for good reasons, but mostly
related to dealing with multiple output formats (CMYK, hi-res color,
low-res color, etc.).

Those uses are less common today than they were a decade ago.

What I assume my friend wants is an img tag. Adding a parallel image
structure to DocBook doesn't appeal to me, but it did occur to me that
we could allow imagedata in more places:

  figure xml:id=ex.pythagorean
titleThe Pythagorean Theorem Illustrated/title
imagedata fileref=figs/print/db5d_ref01.pdf/
  /figure

It leaves a slightly odd element name but it's a single tag. I assume
that audiodata and videodata would be equally useful.

Should we consider allowing bare imagedata/audiodata/videodata
elements in DocBook? I suppose they'd be both inline and block
elements.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | We live on an island surrounded by
http://www.oasis-open.org/docbook/ | a sea of ignorance. As our island
Chair, DocBook Technical Committee | of knowledge grows, so does the
   | shore of our ignorance.--John 
   | Archibald Wheeler


signature.asc
Description: PGP signature

[docbook] Re: Possible Catalog Issues for DocBook 4/5: Missing 'www' in System Identifier?

[Norman Walsh]

Thomas Schraitle tom_s...@web.de writes:
 Well, I had always the (wrong?) impression, that the system identifier
 for the docbook.org domain contains a www. Using a Web browser to
 access the URL is usually not a problem (as both URLs work, with and
 without www). However, an XML catalog resolver wants the *exact*
 string. If someone tries to use such a system identifier, he will get
 into problems.

I originally configured docbook.org such that www.docbook.org was a
redirect to docbook.org. But in the course of moving it to different
servers, that configuration has apparently been lost. I will try to
fix that.

 For example, oXygen 15 creates a DocBook file which contains the www.

Ugh.

 However, they also use the above catalog file. I guess, this problem
 hasn't occured yet as all the XML tools try to find the public
 identifier first. Assuming there is a correct entry in the XML catalog,
 the system identifier never gets resolved (and doesn't need to).

 Is this ambiguous? I would say yes. Or at least confusing. 

 What would the experts recommend here?

I never intended the www to be used in the docbook.org domain.

I guess I recommend that you don't use it. :-)

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | A wonder is often expressed that
http://www.oasis-open.org/docbook/ | the greatest criminals look like
Chair, DocBook Technical Committee | other men. The reason is that
   | *they are like other men in many
   | respects.*-- Hazlitt


pgpvwgILeF8Wb.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

David Cramer da...@thingbag.net writes:
 Can you point me to what you based
 the Calabash implementation on?

I based it on the simple assumption that what occurs between the
parenthesis in xpath() must be an XPath expression. In XML Calabash,
an XPath 2.0 expression.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | There is always some accident in
http://www.oasis-open.org/docbook/ | the best of things, whether
Chair, DocBook Technical Committee | thoughts or expressions or deeds.
   | The memorable thought, the happy
   | expression, the admirable deed are
   | only partly yours.--Henry David
   | Thoreau


pgpc6xcBnetU4.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

Bob Stayton b...@sagehill.net writes:
 There's an xpath() scheme and it's pretty widely supported, I believe.

 I cannot seem to find any information about the xpath() scheme in
 xpointer, except your earlier email mentioning that you implemented it
 in Calabash. It is listed on the W3C XPointer Registry, but the
 specification link goes to the W3C spec for XPath 2.0. I doubt the
 xpath() scheme supports the entire XPath 2.0 standard. Do you know
 where the scheme originated and who maintains it? And which processors
 have implemented it?

I don't believe there's an independent spec for it. If you claim to support
the xpath() scheme, I believe the expectation is that you will support all
of XPath (1 or 2).

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | One must look for one thing only,
http://www.oasis-open.org/docbook/ | to find many.--Cesare Pavese
Chair, DocBook Technical Committee |


pgprKIisdp2Tt.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

Bob Stayton b...@sagehill.net writes:
 This use case could be satisfied with the xpath scheme in XPointer,
 but I'm not finding any processors that support it, or even any
 information about that scheme.

It's supported in XInclude in my XML Calabash processor. :-)

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | The facts, although interesting,
http://www.oasis-open.org/docbook/ | are usually irrelevant.
Chair, DocBook Technical Committee |


pgpwekOdc6u2O.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

Fekete Robert frob...@balabit.hu writes:
 Having recently moved to docbook 5, I also deeply miss the xpointer()
 scheme.

How did moving to DocBook 5 change anything? It hasn't been removed
From DocBook in any sense. Tools that supported it in 4 should also
support it in 5, one imagines.

 The functionality that I sorely miss is the possibility to
 reference a tag using its ID, and xinclude everything that's within
 the referenced tag, except the tag itself:
 xi:include href=blah.xml xmlns:xi=http://www.w3.org/2001/XInclude;
 xpointer=xpointer(//note[@id='mynote']/*)/

That looks like the xpath() scheme to me.


Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | The facts, although interesting,
http://www.oasis-open.org/docbook/ | are usually irrelevant.
Chair, DocBook Technical Committee |


pgpzGeJZQ49Gm.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

Alexey Neyman sti...@att.net writes:
 3.1: [[[
 Attributes other than those listed above may be placed on the xi:include 
 element. Unprefixed attribute names are reserved for future versions of this 
 specification, and must be ignored by XInclude 1.0 processors.
 ]]]

 Should it be XInclude 1.1 (current version of the spec) here?

Yes, probably, thanks!

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | We are thinking beings, and we
http://www.oasis-open.org/docbook/ | cannot exclude the intellect from
Chair, DocBook Technical Committee | participating in any of our
   | functions.--William James


pgpzLrrk3ykrb.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

Hussein Shafie huss...@xmlmind.com writes:
 The new XInclude Working Draft:

 http://www.w3.org/TR/xinclude-11/

 looks good. It attempts to fix some of the problems of XInclude 1.0:

Thanks.

 However, the attribute copying feature as described in the Working
 Draft seems too restrictive to be really useful.

 Excerpts from the Working Draft: --- 4.3 Attribute Copying when
 processing XML ... Any namespace qualified attribute that appears on
 the xi:include element will be copied onto every top-level included
 item that is an element information item.

 If the element information item already has an attribute with the same
 qualified name, its value is changed to the value specified on the
 xi:include element. ---

 [1] Any namespace qualified attribute poses a problem as most
 schemas use attributes which are not namespace qualified. In practice,
 this makes attribute copying as described above useful only for
 attribute xml:id.

The intent, and I'll try to clarify this in the next draft, is that
you'd use additional, namespace qualified attributes to pass along
information that a subsequent step would use to resolve duplicate IDs
and such.

There are two problems:

1. Copying non-namespace qualified attributes means that you can't
pass attributes named parse and href, etc. And it means if XInclude
1.2 adds a range attribute, then that may collide with existing
documents. Using namespaces avoids this problem.

2. There's no strategy for resolving ID/IDREF errors that is the
single, right answer. The DocBook transclusion requirements document
lists half a dozen possibilities. By using your own attributes, you
can identify (to a downstream step) what policies you want to use in
each XInclude case.

 [2] There are still duplicate ID validation errors in cases such as
 the following one:

 --- ?xml version='1.0'? document
 xmlns:xi=http://www.w3.org/2001/XInclude;
 xmlns:eg=http://example.org/namespace/example; pThis example
 includes a “definition” paragraph from some document twice using
 attribute copying./p

 xi:include href=src.xml xpointer=element(def)/

 xi:include xml:id=def2 href=src.xml xpointer=element(def)/

I have to say, I'm not sure I ever even thought of doing this with
xml:id.


 /document ---

 where src.xml is:

 --- document paraSome paragraph./para para xml:id=defSome
 phrase xml:id=ph1definition/phrase./para paraSome other
 paragraph./para /document ---

 which gives us (duplicate ID error for xml:id=ph1):

Right. That's why you need a second step to do the right thing.

The goal of attribute copying in XInclude 1.1 is to provide a
mechanism for some downstream process to be able to know where the
XInclude boundaries occurred.

Today, you simply can't tell so you have no hope of fixing things.

 I don't know if it is possible to solve problems [1] and [2] while
 keeping the XInclude spec 1.1 as simple and as generic as it currently
 is. However, I would really like to see these problems solved
 elegantly because if this is the case, then may be DocBook 5.1 would
 not need to have its own, DocBook specific, transclusion mechanism:

My goal is to build, as a separate spec, a vocabulary of extension
attributes to use in, for example an XProc pipeline, to provide
flavors of ID/IDREF fixup.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | All professional men are
http://www.oasis-open.org/docbook/ | handicapped by not being allowed
Chair, DocBook Technical Committee | to ignore things which are
   | useless.-- Goethe


pgpMRRUjJcXq6.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1

[Norman Walsh]

Bob Stayton b...@sagehill.net writes:
 Hi Norm,
 I read through the new spec and it looks good.  I have just a couple of 
 comments.

 1. The first example in C.6 uses frigid=line=2,6. Unless you are
 introducing a refrigerator identification system, I think that should
 be fragid. 8^)

Thanks. Paul noticed that bug moments after the last call draft was
officially published. Because that's always the way it is. I've
already fixed the sources, it'll be fragid next time around :-)

 It also says There are four of them, but I think lines=2,6 is
 inclusive, so that would be five lines, no? The output example seems
 to include the fifth blank line that puts /pre on its own line.

No, per RFC5147, I think that's lines 3, 4, 5, and 6 of the file.
I think the newline is part of line 6.

I'd be curious if you check RFC5147 and see if you think I'm
misinterpreting it.

 2. In C.7, the example of attribute copying, I would like to see a
 second example that replaces xml:id. I presume that works even when
 the xpointer is using the xml:id in the source file to fetch the
 content.

Ok. I can add another example.

 Regarding xml:id fixup, this feature only applies to the top-level
 included element. If there are duplicate xml:ids in its descendants,
 then further fixup will be required after inclusion, right?

It fixes all the references properties, but if you really have
duplicate IDs and such, you'll need to do some post-processing to
actually get the results you want.

 3. This document does not address any improvements to xpointer. I
 still use xsltproc for its implementation of the xpointer() scheme of
 xpointer, but that scheme never became a standard. What is the status
 of using some kind of xpath syntax in xpointer?

There's an xpath() scheme and it's pretty widely supported, I believe.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com | Society is immoral and immortal; it can
http://nwalsh.com/| afford to commit any kind of folly, and
  | indulge in any kind of vice; it cannot
  | be killed, and the fragments that
  | survive can always laugh at the
  | dead.--Henry Adams


pgpEefBOiMVRP.pgp
Description: PGP signature

[docbook] Re: xinclude.mod

[Norman Walsh]

Sascha Manns saigk...@googlemail.com writes:
 i just would like to ask i can use xinclude.mod with DocBook 4.5.

 The backround: I have a project which is written in DB4.5. I'm using a Oxygen 
 XML Editor for preparing the Code. But the validy fails with the error that 
 xinclude isn't defined.
 In http://forums.deltaxml.com/topic/144/ i found out that a

 !DOCTYPE article PUBLIC -//OASIS//DTD DocBook XML V4.5//EN
  http://www.docbook.org/xml/4.5/docbookx.dtd; [
 !ENTITY % xinclude SYSTEM http://www.docbook.org/xml/4.5/xinclude.mod;
 %xinclude;
 ]

 is possible. But on this place docbooc.org/xml/4.5/ a xinclude.mod isn't 
 available.

That's someone else's extension to DocBook. It's unfortunate that they
chose a docbook.org URI for their system identifier (there's clearly a
catalog involved so the fact that it was never stored there didn't
prevent it from working).

 So it is moved to another place or can't we use it?

It appears to ship as part of the Oxygen distribution, so you probably
already have a copy. Look in

  {wherever Oxygen is installed}/frameworks/docbook/4.4/dtd/xinclude.mod

Hope that helps.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | One does what one is; one becomes
http://www.oasis-open.org/docbook/ | what one does.--Robert Musil
Chair, DocBook Technical Committee |


pgp1UCqH4VPc7.pgp
Description: PGP signature

[docbook-apps] Table option for program listings

[Norman Walsh]

Hi folks,

There was some discussion a while ago about how to format program listings.
I never found a solution that I think is wholly satisfactory, but I did 
implement
the table option in the XSLT 2.0 stylesheets,
https://github.com/docbook/xslt20-stylesheets

If you specify asTable=true in the linenumbering param or PI, you'll
get a two column table. This has the feature that you can
cut-and-paste the listing without the generated line numbers. It has the
flaw that if you have a superscript or subscript or anything that causes
the line height to vary, the line numbers will get out of sync.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | In great affairs men show
http://www.oasis-open.org/docbook/ | themselves as they wish to be
Chair, DocBook Technical Committee | seen, in small things they show
   | themselves as they are.-- Chamfort


pgpzTWgfDnXkz.pgp
Description: PGP signature

[docbook] Possible (brief?) {www.}docbook.org and wiki.docbook.org downtime

[Norman Walsh]

Hi folks,

I'm moving the DNS for {www.}docbook.org and wiki.docbook.org around today.
There may be some short period of downtime. Or not. Hard for me to say.
In theory, if you get the current DNS entries, you'll go to the current
sites and as the new DNS entries propagate, you'll go to the new sites.
So, with luck, you'll never notice.

But if you do, well, it's me again :-)

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Nothing ever gets anywhere. The
http://www.oasis-open.org/docbook/ | earth keeps turning round and gets
Chair, DocBook Technical Committee | nowhere. The moment is the only
   | thing that counts.--Jean Cocteau


pgpw2lPia2ubO.pgp
Description: PGP signature

Re: [docbook-apps] Possible (brief?) {www.}docbook.org and wiki.docbook.org downtime

[Norman Walsh]

David Goss dg...@mueller-inc.com writes:
 I'm encountering an error, Element caption in namespace
 'http://docbook.org/ns/docbook' encountered in figure, but no template
 matches whenever I try to build documents that previously built without
 a hitch. Could this problem be caused by docbook.org server changes?

I *really* don't think so. That sounds like a stylesheet problem. Did
you change your stylesheets recently?

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | He who will not reason is a bigot;
http://www.oasis-open.org/docbook/ | he who cannot is a fool; and he
Chair, DocBook Technical Committee | who dares not is a slave.--Sir
   | William Drummond


pgpEM7uFBJ18v.pgp
Description: PGP signature

[docbook] Hosting {www,wiki}.docbook.org?

[Norman Walsh]

Hi folks,

Anyone out there got spare bandwidth and a static IP address to host
the DocBook websites? They're generating more traffic than I can
afford setup with dynamic DNS through dynect.

I'm exploring a couple of other possibilities, but...I'm open to
suggestions.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Nothing ever becomes real till it
http://www.oasis-open.org/docbook/ | is experienced--even a proverb is
Chair, DocBook Technical Committee | no proverb to you until your life
   | has illustrated it.-- Keats


pgpJlLvVoKcX7.pgp
Description: PGP signature

[docbook] wiki.docbook.org is back

[Norman Walsh]

FYI: I believe the DNS changes have percolated through and all the sites
are up and running. Let me know if you think I'm wrong...

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | It is undesirable to believe a
http://www.oasis-open.org/docbook/ | proposition when there is no
Chair, DocBook Technical Committee | ground whatsoever for supposing it
   | is true.--Bertrand Russell


pgpmTBHt90Xe4.pgp
Description: PGP signature

[docbook] DocBook sites

[Norman Walsh]

Hi folks,

Sorry for the long downtime on wiki.docbook.org. I *think* I've now
got it sorted. I've updated a bunch of DNS information and I believe
that everything will work when those changes percolate through the
interwebs.

Sometime next week, I'll be moving docbook.org over to a new server.
You shouldn't notice, but if you do...

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | If God created us in his own
http://www.oasis-open.org/docbook/ | image, we have more than
Chair, DocBook Technical Committee | reciprocated.-- Voltaire


pgpAPEboXGS7n.pgp
Description: PGP signature

[docbook-apps] Re: Better rendering for programlisting

[Norman Walsh]

David Cramer da...@thingbag.net writes:

 On 05/05/2012 10:38 AM, davep wrote:

 1. Stick with what we have now. 2. Use the table solution and
 accept the limitation that all lines must always be the same
 height.

 Why is this an issue Norm? How often in a fixed width font do users
 want exponents/Drop caps etc?

That's sort of the question. Is it OK if a graphic or superscript in a
programlisting causes all of the line numbers to be weirdly
out-of-sync?

AFIACT, all of the table solutions I've seen online apply specifically
to plain-text program listings, where there's no opportunity for other
things to appear.

In DocBook, other things can appear. Is that the author's problem,
the production editor's problem, or the stylesheet's problem?

 The callouts cause the lines that contain them to be a little higher
 than the others, causing the line numbers to become out of whack. If
 you have more than a couple of callouts, the code listing ends up
 extending beyond the line numbers and obviously the line numbers
 aren't accurate.

I think we can make the callout case work. We can use CSS to adjust
the line-height so that callouts don't cause a problem. The more
pressing issues are: what about cases where CSS isn't applied and what
about program listings that contain other line-height-altering markup?

 I'm open to suggestions on 3, but I'm not likely to figure it out
 myself.

 Thoughts? Other suggestions?

 You've obviated the line numbers by putting content in col 2... why
 not finish the job and put co in col 3?

Because that won't help. There could still be a superscript or image
(think inlinemediaobject) in the programlisting.

 Then I could cut/paste?

 That should be hard requirement for html outputs.

It's hard alright.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | I often marvel that while each man
http://www.oasis-open.org/docbook/ | loves himself more than anyone
Chair, DocBook Technical Committee | else, he sets less value on his
   | own estimate than on the opinions
   | of others.--Marcus Aurelius


pgp36pOijo5v8.pgp
Description: PGP signature

[docbook-apps] Re: Better rendering for programlisting

[Norman Walsh]

David Cramer da...@thingbag.net writes:

 1. Remove the alt text, so that when the user copies the code listing
 nothing comes with it, but then you don't have alt text.

All things considered, that seems the least objectionable.

 2. Use SyntaxHighligher with modifications to allow callouts. This
 gives you syntax highlighting, line numbering, and copy, but has the
 tradeoffs mentioned in my previous posting in this thread.

Requiring complex JavaScript goo seems...suboptimal.

 3. a. Put the code listing in the page twice, once formatted however
 you like with callouts, syntax highlighting, line numbering, etc, and
 another time completely unmodified. If JavaScript is turned on, hide
 the unmodified version and show the modified version, but provide a
 Copy button which copies the content of the unmodified version into
 the clipboard
b. Instead of a Copy button, use a Raw button/link which opens
 a small window showing the unmodifed version of the listing. And
 instead of putting the code listing in the page twice, put the
 unmodified listing in a separate file which is loaded in a new window
 when the user clicks the Raw link.

Both 3a and 3b seem to impose pretty significant expectations on the
rendering system. (With respect to generated files, filenames, linking
etc.)

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | O for a Muse of fire, that would
http://www.oasis-open.org/docbook/ | ascend / The brightest heaven of
Chair, DocBook Technical Committee | invention, / A kingdom for a
   | stage, princes to act / And
   | monarchs to behold the swelling
   | scene!--William Shakespeare, Henry
   | V


pgpVBl5qIcMup.pgp
Description: PGP signature

[docbook] Re: DocBook.org Site Broken?

[Norman Walsh]

Thomas Schraitle tom_s...@web.de writes:
 don't know if anybody is working on that, but... the following URL gives me a 
 403 (Forbidden) error: 

   http://docbook.org/xml/5.1b7/

 Also other links. The whole site seems to be broken. Have anybody the same 
 issues?

I don't know what changed on the server, but I think I've flipped it back.

Let me know if you're still having troubles.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Ambition, n. An overmastering
http://www.oasis-open.org/docbook/ | desire to be vilified by enemies
Chair, DocBook Technical Committee | while living and ridiculed by
   | friends when dead.--Ambrose Bierce


pgp9aViQ6NHSz.pgp
Description: PGP signature

[docbook] Re: DocBook.org Site Broken?

[Norman Walsh]

Thomas Schraitle tom_s...@web.de writes:
 don't know if anybody is working on that, but... the following URL gives me a 
 403 (Forbidden) error: 

   http://docbook.org/xml/5.1b7/

 Also other links. The whole site seems to be broken. Have anybody the same 
 issues?

Dang it. I'm sure that worked before. I'll investigate when I can.
Today, hopefully. Sorry for the inconvenience.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | If God created us in his own
http://www.oasis-open.org/docbook/ | image, we have more than
Chair, DocBook Technical Committee | reciprocated.-- Voltaire


pgp61kyD24mYP.pgp
Description: PGP signature

[docbook-apps] Better rendering for programlisting

[Norman Walsh]

Hello world,

The current rendering for verbatim environments, when line numbers are
enabled, has a significant deficiency: you can't cut-and-paste the
listing without also getting the line numbers and separators.

Looking around at other sites with numbered program listings, the
solution seems to be to use tables. Put the line numbers in the first
column and the listing in the second.

That works, mostly, but if anything in the listing causes a variation in
line height (such as a larger callout), the numbers and the lines get
out of sync.

Using one-line-per-row fixes this, but then cut-and-paste doesn't work
again; the selection crosses over all the columns in each row.

An alternative solution uses nested divs and some slightly fancy CSS.
Naturally, it doesn't work in IE.

I've put an example online: http://nwalsh.com/scratch/out.html

The callout graphics in the listing are intentionally broken because
that was the easiest way to introduce variation. At this font-size,
the callouts are actually ok.

So:

1. Stick with what we have now.
2. Use the table solution and accept the limitation that all lines
   must always be the same height.
3. Find a way to tweak the CSS solution so that IE doesn't fall over

I'm open to suggestions on 3, but I'm not likely to figure it out myself.

Thoughts? Other suggestions?

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Ahhh. A man with a sharp wit.
http://www.oasis-open.org/docbook/ | Someone ought to take it away from
Chair, DocBook Technical Committee | him before he cuts himself.--Peter
   | da Silva


pgpMnRLPuvKqc.pgp
Description: PGP signature

[docbook-apps] Re: Indexing.

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 Are you asking more about the indexing task itself or about the technical
 aspect?

 The docbook aspects please Thomas

The sources for The Definitive Guide have quite a bit of index markup from
the O'Reilly copyedit. That might be a good place to look for examples.

 Speaking about the indexing task itself, IHMO this is something that some
 books don't take it seriously enough. An index is a service to make the book
 more accessible to readers. I've seen lots of bad index which came just as an
 alibi, but with no value.
 So it isn't a surprise that a good index takes time and energy. When I've
 created the index of my book, it took lots of iterations and I guess it still
 isn't perfect. :)

Indexing is an art.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | There is no kind of dishonesty
http://www.oasis-open.org/docbook/ | into which otherwise good people
Chair, DocBook Technical Committee | more easily and frequently fall
   | than that of defrauding the
   | government.--Benjamin Franklin


pgp2y9Pk5YZcB.pgp
Description: PGP signature

[docbook-apps] Re: Indexing.

[Norman Walsh]

davep da...@dpawson.co.uk writes:
 I did made a note to for myself some time back that anindexterm  inside a
 footnote caused an error. I was using oXygenXML v12 at the time. Not sure
 if this is still the case.

 Footnotes aren't normally indexed is one piece of advice. So perhaps
 docbook is right.

I have a vague recollection that we may have loosened that restriction.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | She was mostly immensely relieved
http://www.oasis-open.org/docbook/ | to think that virtually everything
Chair, DocBook Technical Committee | that anybody had ever told her was
   | wrong. (Mrs. E. Kapelsen)--Douglas
   | Adams


pgpSgqUmlw0k9.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1 Requirements

[Norman Walsh]

Norman Walsh n...@nwalsh.com writes:
 In the course of trying to work out how best to address transclusion 
 requirements
 for DocBook, some of us concluded that we should try to push this feature 
 further
 up the stack. We've got concrete evidence of progress now:

   http://www.w3.org/TR/2012/NOTE-xinclude-11-requirements-20120214/

It would be very useful to get some review of these requirements.
Naturally, we want to know about any cases where you think the
proposal is inadequate, but in terms of judging interest it would be
valuable to hear just that you read it, care, and think it sounds
good.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Consume less, share more.
http://www.oasis-open.org/docbook/ | 
Chair, DocBook Technical Committee |


pgp8oALOsEO8c.pgp
Description: PGP signature

[docbook] Re: How to Xinclude an Introduction in a chapter (ie, no section)?

[Norman Walsh]

Bob Stayton b...@sagehill.net writes:

 xi:include href=test-intro.xml xpointer=xpointer(/simplesect/*)
 xmlns:xi=http://www.w3.org/2001/XInclude/

As time progresses, it may be that the xpath() scheme will become more
widely available than the (never finished) xpointer() scheme.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Syllables govern the world.--John
http://www.oasis-open.org/docbook/ | Selden
Chair, DocBook Technical Committee |


pgplj2v7auXgt.pgp
Description: PGP signature

[docbook] Re: How to Xinclude an Introduction in a chapter (ie, no section)?

[Norman Walsh]

Jeffrey Walton noloa...@gmail.com writes:
 Its unfortunate the folks who wrote the standard have decided to make
 a task which should be simple so difficult (from the dumb user
 perspective, which is what I am).

Yes. Well. There were big plans that never materialized and so we
wound up sort of half-way across the chasm. If it's any consolation,
although the problem you have should be simple, there are a great many
problems not far away from it that are actually quite a bit trickier.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Almost every man wastes part of
http://www.oasis-open.org/docbook/ | his life in attempts to display
Chair, DocBook Technical Committee | qualities which he does not
   | possess, and to gain applause
   | which he cannot keep.--Dr. Johnson


pgpf4Hlx3RTpT.pgp
Description: PGP signature

[docbook] Re: XInclude 1.1 Requirements

[Norman Walsh]

David Cramer da...@thingbag.net writes:
 While we're cracking things open, would it be possible to extend the
 element scheme [1] so you could do:

 xi:include href=foo.xml xpointer=element(someId/*)/

 Short of the full xpath support that was in the xpointer() scheme,
 that would provide a lot of benefit for a small change.

Many processors support the xpath() scheme which lets you do this, I
believe.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | To probe a hole we first use a
http://www.oasis-open.org/docbook/ | straight stick to see how far it
Chair, DocBook Technical Committee | takes us. To probe the visible
   | world we use the assumption that
   | things are simple until they prove
   | to be otherwise.--E. H. Gombrich


pgpfWRxrlEvJK.pgp
Description: PGP signature

[docbook] Re: Modeling social media conversations?

[Norman Walsh]

Lech Rzedzicki l...@kode1100.com writes:
 On Tue, Jan 24, 2012 at 2:54 PM, Norman Walsh n...@nwalsh.com wrote:
 Hello world, anyone done any work modeling social media conversations?

 I'd say it needs to modeled as a simplified form of Semantic Web,
 following RESTful approach.
[...]
 Finally how's that related to docbook? ;)

It's related because I want to incorporate the postings into a DocBook
document. I'm not trying to model the entire service, just collections
of postings. Granted, it's a stretch...

But something like this:

http://norman.walsh.name/2012/01/22/shortform-t.xml

and this:

http://norman.walsh.name/2012/01/22/shortform.xml

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Any sufficiently advanced
http://www.oasis-open.org/docbook/ | technology is indistinguishable
Chair, DocBook Technical Committee | from a rigged demo.


pgp8EGXywedOB.pgp
Description: PGP signature

[docbook] Re: fop1.extension problem with XSL Stylesheets

[Norman Walsh]

Paul Tremblay paulhtremb...@gmail.com writes:
 FOP needs the table-layout attribute to be set to fixed in order to
 render tables, but the stylesheet only sets this attribute to fixed
 if fop.extenstion != 0. If I change the above to

 xsl:when test=$fop.extensions != 0 or $fop1.extension != 0

 Then the code works fine.

 Am I missing something?

I doubt it. I'm not sure who added $fop1.extension, but it wasn't me :-/

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | The effects of weakness are
http://www.oasis-open.org/docbook/ | inconceivable, and more prodigious
Chair, DocBook Technical Committee | than those of the most violent
   | passions.--Cardinal De Retz


pgp1ZRPqWmFJ0.pgp
Description: PGP signature

[docbook] Re: Updated online edition of TDG 5.1

[Norman Walsh]

Thomas Schraitle tom_s...@web.de writes:
 I've found a small bug, it seems the screenco element is not correctly 
 processed:

   http://www.docbook.org/tdg51/en/html/ch05.html#ch05-genstruct

 Also the callout images are not displayed.

Thanks. I think that's fixed. Trying to get out another release today.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | To achieve great things we must
http://www.oasis-open.org/docbook/ | live as though we were never going
Chair, DocBook Technical Committee | to die.-- Vauvenargues


pgpO60L2ysoq1.pgp
Description: PGP signature

[docbook] DocBook.org updated, new schemas

[Norman Walsh]

Hi folks,

This morning, I published an update to DocBook.org. The update moves a
bunch of stuff around, but hopefully loses nothing. I have added
redirects where I thought it was practical. Please report any problems
you find.

The updates are:

DocBook 5.1b6
DocBook Simplified 5.1b6-1
DocBook Website 5.1b6-1
DocBook Slides 5.1b6-1
DocBook HTML Forms 5.1b6-1

I've also published an update to DocBook TDG5.1 for DocBook 5.1b6.

The big changes that I can think of off the top of my head are broader
use of XLink and the new multimedia changes. I'll craft a better
change long for V.next, I promise.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | We cannot put off living until we
http://www.oasis-open.org/docbook/ | are ready. The most salient
Chair, DocBook Technical Committee | characteristic of life is its
   | coerciveness: it is always urgent,
   | 'here and now' without any
   | possible postponement. Life is
   | fired at us point blank.--José
   | Ortega Y Gasset


pgpwCX7FY4zq7.pgp
Description: PGP signature

[docbook] Re: No DocBook Meetup at XML Prague (10 Feb 2012)

[Norman Walsh]

Peter Flynn pe...@silmaril.ie writes:
 I'm still interested in the idea of running a DocBook conference of
 some sort; please let me know if you have any suggestions.

 What about in conjunction with Balisage?

Before, after, or during? I'd be happy to host an evening session during
the conference, if that's of interest. Before and/or after is trickier.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | We cannot put off living until we
http://www.oasis-open.org/docbook/ | are ready. The most salient
Chair, DocBook Technical Committee | characteristic of life is its
   | coerciveness: it is always urgent,
   | 'here and now' without any
   | possible postponement. Life is
   | fired at us point blank.--José
   | Ortega Y Gasset


pgp1RVg65qh9I.pgp
Description: PGP signature

[docbook] No DocBook Meetup at XML Prague (10 Feb 2012)

[Norman Walsh]

Hi folks,

The XML Prague organizers have informed me that they aren't going to
be able to host the DocBook meetup due to insufficient registrations.
There were way to many good topics for one day anyway, so I'm not that
surprised. And now I only have to find a way to go to four things at
once instead of five.

I'm still interested in the idea of running a DocBook conference of
some sort; please let me know if you have any suggestions.

And, of course, I still hope to see you all at XML Prague!

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | He that overvalues himself will
http://www.oasis-open.org/docbook/ | undervalue others, and he that
Chair, DocBook Technical Committee | undervalues others will oppress
   | them.--Dr. Johnson


pgpVub7FaVxBZ.pgp
Description: PGP signature

[docbook] Re: Consistent handling of all purely presentational characters such a quotes, parenthesis, square brackets, slashes

[Norman Walsh]

 My current thinking leads me to overloading phrase element yet again
 and doing something like:

 phrase rend=surround_with_parenthesis2.5phrase
 role=unitin/phrase/phrase (or http://pastie.org/3165754 )

Do you get imperial units both with and without the parenthetical
metric equivalents? If not, I think I'd be inclined to choose
some markup for the lengths and leave the rest to styling.

Depending on your back end, you might get away with simply:

  length2.5in/length

It's not too difficult to break that into 2.5 and in from just the
text content. And it's not too hard (probably) to enumerate all the
valid length units and determine which are imperial and which are
metric.

You could go whole hog, I suppose:

  length magnitude=2.5 units=inches system=imperial2.5in/length

but that seems like it might be overkill :-)

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | So, are you working on finding
http://www.oasis-open.org/docbook/ | that bug now, or are you leaving
Chair, DocBook Technical Committee | it until later? Yes.


pgpDjY3iJSKbG.pgp
Description: PGP signature

[docbook-apps] Re: How to use Calabash with the DocBook XSL1.0 Stylesheets?

[Norman Walsh]

Thomas Schraitle tom_s...@web.de writes:
[...]
 Or start using the DocBook XSLT 2.0 stylesheets. :-)

 Actually I did, but wasn't successfull. :-)

 The usual docbook.xsl works like a charm. I don't have any problems with it 
 so 
 far. However, for some unknown reason, the chunk.xsl doesn't work for me 
 (yet). I used Saxon9 with the original DocBook XSLT 2.0 stylesheet like this:

 $ saxon9 -xi -s:en/xml/DoCookbook.xml \
  -xsl:frameworks/db-xslt2/xslt/base/html/chunk.xsl

 Interestingly, this doesn't print any Writing ... messages. I get these 
 files now:

   chunk-appendix-d62e5692.html  chunk-book-d62e2.html
   chunk-chapter-d62e2464.html  chunk-chapter-d62e475.html
   chunk-preface-d62e179.html  [...]

 Ok, it seems, the naming has been changed, but strangly I didn't get an 
 index.html file. My naive thought was to have some navigation headers, but 
 they don't show up in my HTML files. Maybe there is some magic which I've 
 missed. I would love to use the chunking stylesheet too. :-)

Hmm. I'll look into that. Can you send me a source document?

 Oh, by the way: 
 When I've played with the XSLT2 stylesheets, I've came across some bugs. As I 
 wasn't sure if you prefer still the Sourceforge ticker or Github, I used the 
 former. Here are some pointers, hope they are helpful:

 #3464876  xslt2: keycap/@function not used
 #3464633  xslt2: Parameter img.src.path has no effect
 #3450421  xslt2: Relative paths for transclusion do not work
 #3431422  xslt2: menuchoice is not correctly rendered 

Github would be more convenient, actually. Sigh. I need to get this
all cleaned up.

Be seeing you,
  norm

-- 
Norman Walsh n...@nwalsh.com  | Old age is the most unexpected of
http://www.oasis-open.org/docbook/ | all the things that happen to a
Chair, DocBook Technical Committee | man.-- Trotsky


pgpAY6CkEiHmZ.pgp
Description: PGP signature