Re: [docbook-apps] Validating against Schematron

2020-07-30 Thread Richard Hamilton
Well that explains it. I was under the impression that jing and trang were 
stuck in amber back in 2009. I just checked and the version I had was from 2009.

I just tried the 2018 version, and it works fine with .sch files.

Thanks for setting me straight.

Dick
---
XML Press
XML for Technical Communicators
http://xmlpress.net
hamil...@xmlpress.net



> On Jul 29, 2020, at 23:59, Norman Tovey-Walsh  wrote:
> 
> Richard Hamilton  writes:
>> Running it using docbook.sch, I get a namespace error on db:, which is
>> strange, since db is properly declared in the Schematron file. I even
>> modified a test file so that it also used the prefix db: defined the
>> same way, but no luck.
> 
> If I grab the latest 5.2 repo and build it, jing (20181222) validates
> src/test/docbook/pass/article.001.xml with build/docbook.sch without any
> errors.
> 
> And if I take out the version attribute, I get:
> 
> $ jing build/docbook.sch src/test/docbook/fail/article.001.xml
> /Users/ndw/Projects/docbook/docbook/src/test/docbook/fail/article.001.xml:1: 
> error: assertion failed:
>  If this element is the root element, it must have a version attribute.
> 
>Be seeing you,
>  norm
> 
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
> 
>> The greatest of all secrets is knowing how to reduce the force of
>> envy.--Cardinal De Retz


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org



Re: [docbook-apps] Validating against Schematron

2020-07-30 Thread Norman Tovey-Walsh
Richard Hamilton  writes:
> Running it using docbook.sch, I get a namespace error on db:, which is
> strange, since db is properly declared in the Schematron file. I even
> modified a test file so that it also used the prefix db: defined the
> same way, but no luck.

If I grab the latest 5.2 repo and build it, jing (20181222) validates
src/test/docbook/pass/article.001.xml with build/docbook.sch without any
errors.

And if I take out the version attribute, I get:

$ jing build/docbook.sch src/test/docbook/fail/article.001.xml
/Users/ndw/Projects/docbook/docbook/src/test/docbook/fail/article.001.xml:1: 
error: assertion failed:
  If this element is the root element, it must have a version attribute.

Be seeing you,
  norm

--
Norman Tovey-Walsh 
https://nwalsh.com/

> The greatest of all secrets is knowing how to reduce the force of
> envy.--Cardinal De Retz


signature.asc
Description: PGP signature


Re: [docbook-apps] DocBook XSL: The Next Generation

2020-07-30 Thread Norman Tovey-Walsh
> I suspect I'm not part of this "we", but for a different "we": we get
> them via dblatex + (Xe)LaTeX.

Yes. I’m interested in this too. Peter Flynn and I have corresponded on
the topic a few times.

Be seeing you,
  norm

--
Norman Tovey-Walsh 
https://nwalsh.com/

> When you don’t create things, you become defined by your tastes rather
> than ability. Your tastes only narrow and exclude people. So
> create.--Why the Lucky Stiff


signature.asc
Description: PGP signature


Re: [docbook-apps] DocBook XSL: The Next Generation

2020-07-30 Thread Norman Tovey-Walsh
> Thanks Norm. Yes, that can be an interesting way. I've heard about that, but 
> I'm not so much into this topic ATM. As far as I know, the above tools are 
> commercial. Do you know an open source solution?

https://www.print-css.rocks/ lists a couple in addition to AH and
PrinceXML. I haven’t tried them. I’m surprised there aren’t more, TBH.

> I can fully understand your position. :) I'm sure it's fun, especially when 
> you come from a XSLT 1.0 background. That's a huge step forward. On the other 
> side, it's also a huge task, I guess. ;)

It’s bigger than a bread box, perhaps, but it’s not a gargantuan task.
The FO stylesheets in the 1.0 and 2.0 projects probably contain most of
the answers one needs, it’s just a question of restructuring them into
modern, XSLT 3.0 with a rationalized set of options.

Be seeing you,
  norm

--
Norman Tovey-Walsh 
https://nwalsh.com/

> 'All is vanity,' saith the Preacher. But if all were only vanity, who
> would mind? Alas, it is too often worse than vanity: agony, darkness,
> death also.--Thomas Hardy


signature.asc
Description: PGP signature


Fw: [docbook-apps] DocBook XSL: The Next Generation

2020-07-30 Thread Shlomi Fish
This email bounced due to spamcop:

Begin forwarded message:

Date: Thu, 30 Jul 2020 14:26:24 +0300
From: Shlomi Fish 
To: Eric Streit 
Subject: Re: [docbook-apps] DocBook XSL: The Next Generation


Hi Eric,

On Wed, 29 Jul 2020 09:41:19 +0200
Eric Streit  wrote:

> thanks!
>   

You should thank Norman - not me. Please reply to list:

https://www.shlomifish.org/philosophy/computers/netiquette/email/reply-to-list.html

> Eric
> 
> Le 29/07/2020 à 09:40, Shlomi Fish a écrit :  
> > Hi, Norman!
> > 
> > On Tue, 28 Jul 2020 17:12:03 +0100
> > Norman Tovey-Walsh  wrote:
> > 
> >> Hello world,
> >>
> >> A few days ago, I released the first version of the DocBook xslTNG
> >> Stylesheets. These are a complete rewrite of DocBook to HTML stylesheets
> >> in XSLT 3.0.
> >>
> >> The goal of the stylesheets is to produce clean, semantically rich
> >> HTML(5) that can be beautifully rendered with CSS (and a dash or two of
> >> JavaScript, if you wish) in the browser and in print. I’ve done my best
> >> in all cases to make sure that the presentations are accessible. If you
> >> find something that isn’t accessible, please report it.
> >>
> >> I made the 1.1.1 release yesterday. (The small fix over 1.0.0 from
> >> Friday is that annotations are now more accessible.)
> >>
> >> See https://xsltng.docbook.org/ for details.
> >>
> >> Or https://so.nwalsh.com/2020/07/25-docbook-xsltng for more blather
> >> about it from me.
> >>
> > 
> > Thanks for your work, and for sharing it!
> > 
> >> Be seeing you,
> >>   norm
> >>
> >> --
> >> Norman Tovey-Walsh 
> >> https://nwalsh.com/
> >>
> >>> Wit consists in seeing the resemblance between things which differ, and
> >>> the difference between things which are alike.--Madame De Stæl  
> > 
> > 
> > 



-- 

Shlomi Fish   https://www.shlomifish.org/
https://www.shlomifish.org/humour/bits/facts/Emma-Watson/

In the Technion, there are many ways to get from one place to the other, but
they are all the same length.
— https://www.shlomifish.org/humour.html

Please reply to list if it's a mailing list post - https://shlom.in/reply .


-- 

Shlomi Fish   https://www.shlomifish.org/
Freecell Solver - https://fc-solve.shlomifish.org/

“God is dead.” — Nietzsche
“Nietzsche is dead.” — God
“Nietzsche is God.” — dead(via fortune-mod)

Please reply to list if it's a mailing list post - https://shlom.in/reply .

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org



[docbook-apps] regarding olinks

2020-07-30 Thread Bob Stayton
After the recent discussion of olinks, I came across this paper I wrote 
for a conference in 2005 describing olinks, titled "Linking Outside the 
Box". It might be of interest to those contemplating using olinks.


http://www.sagehill.net/presentations/XML2005/linkingOutside.pdf

--
Bob Stayton
b...@sagehill.net



[docbook-apps] DocBook xslTNG version 1.2.0 released

2020-07-30 Thread Norman Tovey-Walsh
Hi folks,

Hopefully frequent release announcements won’t be too distracting. I
expect the pace will slow down after the obvious kinks are sorted out.

* Reworked CALS table formatting to fix #48. Starting with this release,
  it should be possible to process arbitrarily long tables. This is
  accomplished by processing the tables in a single forward pass.
  Consequently, it is no longer possible for the stylesheets to work out
  the align-char-width by inspecting the cells in the column. If an
  align-char-width is not specified with a PI, the default
  $align-char-width will be used.

* Updated the documentation in the reference guide to be explicit about
  build prerequisites. (Fix #49.)

* Changed the default chunking rules so that the first section of a
  chapter, appendix, or other component is included in the chunk with
  that component. This will improve the presentation of components that
  have only a short amount of introductory material before the first
  section (and greatly improve the presentation when there is no
  introductory material before the first section). (Fix #45.)

* Updated the JavaScript libraries to avoid use of .replaceAll() which
  is not yet widely (enough) supported. (Fix #52.)

* Updated the CSS for admonitions so that it’s more easily configured
  with CSS variables. I tweaked the presentation of code inside
  admonitions to avoid contrasting background colors that I found
  aesthetically problematic.

* Changed the CSS for literal so that it will imply white-space: nowrap.
  Adding a role="break" will return white space to normal.

* Documented that building on Windows does not work. (Close #44.)

* Added trademark marks (™,℠,©,®) for the trademark element. For the
  moment, this is done with ::after in CSS rather than putting the marks
  explicitly in the HTML output.

* Changed package, markup, token, returnvalue, type, and errorcode
  formatting to use code instead of span.

Be seeing you,
  norm

--
Norman Tovey-Walsh 
https://nwalsh.com/

> Why do writers write? Because it isn't there.--Thomas Berger


signature.asc
Description: PGP signature