[docbook-apps] [ANN] Release of XMLmind XSL-FO Converter v6.4.2

[Hussein Shafie]

XMLmind XSL-FO Converter v6.4.2 (February 29, 2024). Maintenance release:

- Updated most software components in XMLmind XSL Utility and XMLmind 
XSL Server.

- Official support of Java™ 21 and macOS Sonoma (version 14).

More information in https://www.xmlmind.com/foconverter/changes.html

-
What is XMLmind XSL-FO Converter?
-

XMLmind XSL-FO Converter is an XSL-FO processor similar to Apache FOP, 
RenderX XEP or Antenna House XSL Formatter, except that it generates 
RTF, WML, ODT and DOCX file formats rather than PDF.


XMLmind XSL-FO Converter is available as a Java™ software component, a 
.NET software component, a desktop application and a server-side 
application (Java Servlet).


The desktop application called "XMLmind XSL Utility" 
(https://www.xmlmind.com/foconverter/xsl_utility.html) makes it easy 
converting DITA, DocBook, XHTML and XSL-FO documents to a variety of 
formats (PDF, RTF, WML, ODT, DOCX, HTML, EPUB, Web Help, etc).


XMLmind XSL Utility also makes it easy customizing the deliverables it 
generates (PDF, DOCX, EPUB, Web Help, etc) and this, without modifying 
configuration files by hand and without prior knowledge of XSLT. See 
https://www.xmlmind.com/foconverter/_distrib/xslutil/doc/help/com.xmlmind.xslutil.ConversionEditor.html#customizing_xslt


Home page: https://www.xmlmind.com/foconverter/



-
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] Multiplatform toolchain for outputting "nice" PDF

[Richard Hamilton]

There is a section in Chapter 1 of The Definitive Guide titled "What's New
in DocBook V5.0" that covers 4.5 to 5.0. I don't know of anything that
extends that to 5.1 or beyond.

Best regards,
DIck Hamilton
hamil...@xmlpress.net

On Tue, Jan 23, 2024 at 2:51 AM Norm Tovey-Walsh  wrote:

> > If I'm not mistaken, there is no direct summary of changes between
> DocBook 4.5
> > and 5.1.
>
> And that seems like an awful oversight on my part. I’ll plan to update
> The Definitive Guide to include a comprehensive list-of-changes
> appendix. I sort of thought that already existed, but I guess I’m not as
> clever as I think I am ;-)
>
> Be seeing you,
>   norm
>
> --
> Norm Tovey-Walsh 
> https://norm.tovey-walsh.com/
>
> > Thanks to words, we have been able to rise above the brutes; and thanks
> > to words, we have often sunk to the level of the demons.--Aldous Huxley
>


-- 

XML Press
XML for Technical Communicators
http://xmlpress.net

[docbook-apps] [ANN] Call for proposals: XML Prague 2024

[Jirka Kosek]

Dear XML enthusiasts,

We are glad to announce that the call for proposals for the XML Prague 
2024 conference is open now.


The XML Prague conference is a three-day event on XML for developers, 
markup geeks, information managers and students. It will be held on June 
6-8, 2024, at the Prague University of Economics and Business, W. 
Churchill sq., Prague, Czech Republic.


The conference will include:

- Two full days of single-track sessions on topics such as:
* AI and markup
* Markup and the Extensible Web
* Semantic visions and the reality
* Publishing for the 21st century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
- A multitrack unconference day for informal discussions and networking

The conference will provide an overview of successful technologies, with 
a focus on real-world applications versus theoretical exposition.


You can find more information and submit your proposals on our 
conference website: https://www.xmlprague.cz


CFP: https://www.xmlprague.cz/cfp/

Registration is open and you can enjoy early-bird prices:
https://www.xmlprague.cz/conference-registration/

Please take note of the following important dates:

April 2nd – End of CFP
May 1st – Notification of acceptance/rejection
May 27th – Final paper (for those who will provide it)
June 6th–8th – XML Prague 2024 conference

This year we would like to encourage new speakers. Full paper submission 
is no longer needed and there will be shorter slots available for those 
who would like to introduce or demo something “smaller”.


If you have any questions, if you are interested in sponsorship or if 
you want to make a suggestion, please send an email to i...@xmlprague.cz


We look forward to hearing from you and seeing you at the conference.

Sincerely,

Jirka Kosek
on behalf of XML Prague crew




OpenPGP_signature.asc
Description: OpenPGP digital signature

Re: [docbook-apps] Multiplatform toolchain for outputting "nice" PDF

[Norm Tovey-Walsh]

> If I'm not mistaken, there is no direct summary of changes between DocBook 4.5
> and 5.1.

And that seems like an awful oversight on my part. I’ll plan to update
The Definitive Guide to include a comprehensive list-of-changes
appendix. I sort of thought that already existed, but I guess I’m not as
clever as I think I am ;-)

Be seeing you,
  norm

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> Thanks to words, we have been able to rise above the brutes; and thanks
> to words, we have often sunk to the level of the demons.--Aldous Huxley


signature.asc
Description: PGP signature

Re: [docbook-apps] Multiplatform toolchain for outputting "nice" PDF

[Jean-Christophe Helary]

> On Jan 22, 2024, at 15:47, Thomas Schraitle  wrote:
> 
> If I'm not mistaken, there is no direct summary of changes between DocBook 4.5
> and 5.1.
> 
> However, you can review the changes between 4.5 and DocBook 5.0 here:
> 
>   https://tdg.docbook.org/tdg/5.0/ch01#introduction-whats-new
> 
> There is another summary that also includes changes between DocBook 5.0 and 
> 5.1
> which you can see here:
> 
>   https://tdg.docbook.org/tdg/5.2/ch00-online#changes-in-52
> 
> Hope that helps. :)

It does. Thank you.

---------
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] Multiplatform toolchain for outputting "nice" PDF

[Thomas Schraitle]

Hi,

On 20.01.24 16:46, l@tlo wrote:

A year and a few months later, here we are, ready for an upgrade.

We're moving to a Ubuntu container that has fop 2.9.

Now, I'd like to move to DocBook 5.1 but I'd like to know if there is there an 
online document that summarizes the major differences between DocBook 4.5 and 
5.1.


If I'm not mistaken, there is no direct summary of changes between DocBook 4.5
and 5.1.

However, you can review the changes between 4.5 and DocBook 5.0 here:

  https://tdg.docbook.org/tdg/5.0/ch01#introduction-whats-new

There is another summary that also includes changes between DocBook 5.0 and 5.1
which you can see here:

  https://tdg.docbook.org/tdg/5.2/ch00-online#changes-in-52

Hope that helps. :)


--
Gruß/Regards
  Thomas Schraitle


-
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] Guidance for running XSLT distribution build, for local development

[Peter Desjardins]

Thanks for pointing out the xslTNG project! I hadn't realized what that is,
and I'm so glad to know about it!

I think that looks like a more appropriate project for additions. I'll
continue exploring the next generation distribution and see how far I get.

Peter

On Sun, Jan 21, 2024 at 12:19 PM Norm Tovey-Walsh  wrote:

> > Thanks for your patience with my beginner build questions! Has anyone
> run a build to generate a
> > release distribution lately? Can you share how you did that?
>
> I’ve done releases recently for the xslTNG stylesheets. I’m not sure
> who’s managing releases for the 1.0 stylesheets these days.
>
> Be seeing you,
>   norm
>
> --
> Norm Tovey-Walsh 
> https://norm.tovey-walsh.com/
>
> > Any sufficiently advanced technology is indistinguishable from a rigged
> > demo.
>

Re: [docbook-apps] Guidance for running XSLT distribution build, for local development

[Norm Tovey-Walsh]

> Thanks for your patience with my beginner build questions! Has anyone run a 
> build to generate a
> release distribution lately? Can you share how you did that?

I’ve done releases recently for the xslTNG stylesheets. I’m not sure
who’s managing releases for the 1.0 stylesheets these days.

Be seeing you,
  norm

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> Any sufficiently advanced technology is indistinguishable from a rigged
> demo.


signature.asc
Description: PGP signature

[docbook-apps] Guidance for running XSLT distribution build, for local development

[Peter Desjardins]

Hello! I'm working on a new output format that I would like to offer as a
contribution (if my skills are up to the task). I want to build the XSL
distribution from my fork of the repository so I can test my changes. I
haven't worked with DocBook distribution builds in the past, and I think
I'm missing some important context.

It looks like CI will build release distributions in the DocBook
organization . I don't think
that covers my fork of the repo though. Is that something I could turn on
in my forked repository configuration?

I also thought it might be easier to build locally using make. I tried
building on my MacOS laptop using the instructions in the xsl10-stylesheets
repository .
That didn't work, because of invalid paths to the expected Ubuntu file
system. I'm considering running an Ubuntu 14.04 virtual machine to
replicate the expected build environment. Or maybe edit the .xmlc file
paths?

Thanks for your patience with my beginner build questions! Has anyone run a
build to generate a release distribution lately? Can you share how you did
that?

Peter

Re: [docbook-apps] Multiplatform toolchain for outputting "nice" PDF

[l@tlo]

A year and a few months later, here we are, ready for an upgrade.

We're moving to a Ubuntu container that has fop 2.9.

Now, I'd like to move to DocBook 5.1 but I'd like to know if there is there an 
online document that summarizes the major differences between DocBook 4.5 and 
5.1.

Thank you in advance.

> On Nov 15, 2022, at 1:16, Jean-Christophe Helary  
> wrote:
> 
> For some historical reasons (and maybe others, I don't know), the tool chain 
> used in the project where I'm in charge of the manual uses a very outdated 
> tool chain based on the following elements:
> 
> • DocBook XSL Stylesheets 1.75.2 ("dbk") or above
> • DocBook XML 4.5 ("docbook-xml-4.5")
> • fop 1.1 ("fop-1.1")
> • libxml2 2-2.7.7 ("libxml2-2.7.7")
> • Saxon 6-5-5 ("saxon")
> • XMLmind Web Help Compiler ("whc")
> • Ant 1.7.1 or above ("apache-ant")
> 
> I'm still investigating the reasons why we're stuck 15 years in the past, but 
> I'd like to move on.
> 
> Currently, the PDF that's built from our DocBook set is, not visually 
> pleasant, to say the least.
> 
> There are few contributors to the documentation but ideally I'd like 
> something that works equally well on the three major platforms that are Linux 
> / Windows and macOS.
> 
> A friend of mine who also is a DITA specialist converted the set to DITA and 
> semi-automatically produced a really nice PDF and there are no reasons why we 
> would not be able to have something equally nice with a modern DocBook 
> toolchain.
> 
> So the question is, what are the options?
> 
> Thank you in advance for your help.
> 
> 
> -- 
> Jean-Christophe Helary @brandelune
> https://traductaire-libre.org
> https://mac4translators.blogspot.com
> https://sr.ht/~brandelune/omegat-as-a-book/


-
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] Size?

[Dave Pawson]

I write a journal. In pen and ink.
Read it into text, slot it into docbook XML.
Just passed 1400 A4 pages. 639486 words.

I've decided docbook works well for me
;-)

happy new year folks.

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Updated schedule for OASIS mail list system upgrade

[Scott McGrath]

We Recently announced the migration to a new List Mail system for this
list. We've modified the implementation process to allow the legacy system
to continue running a bit longer and to have a shorter downtime during
transition.


*The system cut-over is now scheduled for the first week of January *


Miss the original announcement?  Here it is...

The legacy list engine in use since 2003 will be replaced in this upgrade.
You are receiving this message because you are a subscriber to the list
receiving this message.

This transition will provide significant improvements and will change how
you interact with your mail lists.  See below for more information about
the changes, the transition schedule and what you can do to help.

Changes to Expect

The new platform is built in a modern web environment and mail delivery
mechanism. with a number of new features to improve both your platform user
experience and ability to engage with the OASIS community.  Key features
include:


   -

   Mail systems that you can depend on!  The new tools support and comply
   with major deliverability and anti-spoofing standards.  This will eliminate
   many of the sending and deliverability issues your group may be experiencing



   -

   Modern web interface and design for your committee internal work and
   public presentation of your work



   -

   If you are on this public list in addition to Technical Committees, Open
   Projects, and other community engagement mail lists you can manage this
   experience in one cohesive package



   -

   All archives created in the legacy email system will be migrated and
   available cohesively with your new work in the new platform.  All URL links
   for assets in the old platform will redirect to the new location



   -

   After the cutover starts, you will be directed where to send future
   messages for this list and where to find the archives. Any message sent to
   a legacy list address after the cutover begins will receive an auto reply
   with the new list address and archive location.



   -

   After the migration you can continue using the mail list as before. If
   you wish to join additional public lists or modify your delivery to the new
   digest delivery, you will be required to create or login to an existing
   OASIS public community or member account to manage your subscriptions.
   This account system will be used to confirm your email address once (as
   opposed to each subscription) and will be the same account you may be using
   now for OASIS membership, submitting e-CLA forms etc. Legacy-style
   subscribe and unsubscribe email messages to the server will not be
   respected in the new system.



The Transition Schedule

During the cut-over the first week of January, There will be some system
downtime during the cutover. During the downtime you will not receive email
messages sent to this list or have access to the archive.  All messages
sent after the cut-over begins will receive an auto reply announcing the
new list address and archive location.

We will announce the timing specific as we get closer to the transition.

What You Should Do Now

If you no longer wish to subscribe to this list, send a message to
[listname]-unsubscr...@lists.oasis-open.org

Otherwise, watch for further messages in the coming days to include the new
list mailing address and archive location.

Feel free to contact me with any questions, and thanks for your patience
with the inevitable short-term inconvenience implementing these
improvements will bring.

-- 
Scott McGrath

Chief Operating Officer

OASIS Open


+1 781-929-7308 Mobile
scott.mcgr...@oasis-open.org
www.oasis-open.org

[docbook-apps] Deep link anchor for HTML headings with docbook-xsl

[Martin]

Dears,

I'm probably not the first one who would like a "deep link" icon
after HTML headings (and maybe figure and table titles, too).

In some wikis (here: Trac) it's implemented like this:


Something
 ¶


The paragraph symbol is typically hidden and only visible when
hovering:

* > .anchor:link, * > .anchor:visited {
visibility: hidden;
}

h1:hover .anchor, h2:hover .anchor, h3:hover .anchor,
h4:hover .anchor, h5:hover .anchor, h6:hover .anchor,
span:hover .anchor {
visibility: visible;
}

Has someone already created an XSL template to get the same
effect with DocBook and can share it here?

Thank you!

Martin



-
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] changes coming to this mail list system

[Scott McGrath]

I am very pleased to announce a new List Mail system will be implemented
for this list shortly.

The legacy list engine in use since 2003 will be replaced in December.  You
are receiving this message because you are a subscriber to the list
receiving this message.

This transition will provide significant improvements and will change how
you interact with your mail lists.  See below for more information about
the changes, the transition schedule and what you can do to help.

Changes to Expect

The new platform is built in a modern web environment and mail delivery
mechanism. with a number of new features to improve both your platform user
experience and ability to engage with the OASIS community.  Key features
include:


   -

   Mail systems that you can depend on!  The new tools support and comply
   with major deliverability and anti-spoofing standards.  This will eliminate
   many of the sending and deliverability issues your group may be experiencing



   -

   If you are on this public list in addition to Technical Committees, Open
   Projects, and other community engagement mail lists you can manage this
   experience in one cohesive package



   -

   All resources created in the legacy email system will be migrated and
   available cohesively with your new work in the new platform.  All URL links
   for assets in the old platform will redirect to the new location



   -

   After the migration you will be directed where to send future messages
   for this list and where to find the archives.



   -

   After the migration you will be required to create or login to an
   existing OASIS public community or member account to manage your
   subscriptions.  Legacy-style subscribe and unsubscribe email messages to
   the server will not be respected.



The Transition Schedule

Starting 14 December, there may be as much as several days of system
downtime. During the downtime you will not receive email messages sent to
this list or have access to the archive.

We will announce the timing specific as we get closer to the transition.

What You Should Do Now

If you no longer wish to subscribe to this list, send a message to

[listname]-unsubscr...@lists.oasis-open.org

Otherwise, watch for further messages in the coming days to include the new
list mailing address and archive location.

Feel free to contact me with any questions, and thanks for your patience
with the inevitable short-term inconvenience implementing these
improvements will bring.

Scott...

-- 
Scott McGrath

Chief Operating Officer

OASIS Open


+1 781-929-7308 Mobile
scott.mcgr...@oasis-open.org
www.oasis-open.org

[docbook-apps] [ANN] Release of XMLmind XML Editor v10.6

[Hussein Shafie]

Release of XMLmind XML Editor v10.6. Highlights:

==
Release of XMLmind XML Editor Web Edition v1.1

XMLmind XML Editor Web Edition (XXEW for short) is a 100% 
JavaScript, lightweight, streamlined, implementation of XMLmind XML 
Editor running in the web browser, thus not requiring any installation 
on the user side. More information»[1].


What's new in this version?[2]
===
[1] https://www.xmlmind.com/xmleditor/web_edition.shtml
[2] https://www.xmlmind.com/xmleditor/_web/doc/manual/changes.html

Other changes:

- Minor enhancements and bug fixes.
- Updated several software components (XMLmind DITA Converter, XMLmind 
Web Help Compiler, Apache FOP, Apache Batik, etc).
- XMLmind XML Editor officially supported on macOS Sonoma (version 14) 
and on Java™ 21 platforms.


More information in https://www.xmlmind.com/xmleditor/changes.html



---
What is XMLmind XML Editor?

XMLmind XML Editor is a strictly validating, near WYSIWYG, XML editor, 
having extensive DITA, DocBook, XHTML and MathML support and industrial 
strength DOCX import and export facilities. Its users are generally 
technical writers, engineers and scholars who use it to write large, 
complex, modular, documents.


Personal Edition is free to use by many persons and organizations.

New Web Edition is a 100% JavaScript, lightweight, streamlined, 
implementation of XMLmind XML Editor running in the web browser, thus 
not requiring any installation on the user side.


Home page: https://www.xmlmind.com/xmleditor/

Download: https://www.xmlmind.com/xmleditor/download.shtml

-
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] AI ... db metadata 'extras'?

[Dave Pawson]

Yes thanks - how much more can you add to oXygen :-)

regards

On Fri, 27 Oct 2023 at 06:03, Radu Coravu  wrote:
>
> Hi Dave,
>
> Thanks for posting the link, I hope you enjoyed the live webinar!
>
> Regards,
>
> Radu
>
> Radu Coravu
> Oxygen XML Editor
>
> On 10/26/23 19:29, Dave Pawson wrote:
> > https://www.oxygenxml.com/events/2023/webinar_transforming_technical_content_creation_through_ai_powered_writing.html
> >
> > regards
>
>
> ---------
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

---------
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] AI ... db metadata 'extras'?

[Radu Coravu]

Hi Dave,

Thanks for posting the link, I hope you enjoyed the live webinar!

Regards,

Radu

Radu Coravu
Oxygen XML Editor

On 10/26/23 19:29, Dave Pawson wrote:

https://www.oxygenxml.com/events/2023/webinar_transforming_technical_content_creation_through_ai_powered_writing.html

regards



-
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] AI ... db metadata 'extras'?

[Dave Pawson]

https://www.oxygenxml.com/events/2023/webinar_transforming_technical_content_creation_through_ai_powered_writing.html

regards
-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Statement of Use for DocBook version 5.2

[Norm Tovey-Walsh]

Hi folks,

A few weeks ago, Bob sent out a request for statements of use. I’ve
quoted it below. These statements are an important part of the OASIS
process. If you can provide a statement of use, please do!

Bob Stayton  writes:
> Hello,
>
> I'm the Chair of the OASIS DocBook Technical Committee.  The Committee is in 
> the last stages of
> getting The DocBook Schema Version 5.2 through the OASIS approval process.  
> We need to submit
> three Statements of Use of the new schema, and I would like to ask if any 
> participants in the
> DocBook user community might like to submit one.  You need not be a member of 
> OASIS to submit
> one.  Here are the requirements for making such a Statement: 
>
> * It is a written statement that a party has successfully used or implemented 
> that specification in
>  accordance with all or some of its conformance clauses, identifying those 
> clauses that apply,
>  and stating whether its use included the interoperation of multiple 
> independent implementations.
>   The conformance clauses for DocBook 5.3 are:
>
> * This specification normatively defines DocBook V5.2 with a RELAX NG grammar 
> and a set of
>  Schematron assertions. A conformant DocBook V5.2 document must be valid 
> according to both the
>  grammar and the assertions.
> * The reference documentation describes additional constraints and processing 
> expectations. A
>  conformant DocBook V5.2 document should respect those constraints and 
> anticipate those
>  processing expectations.
> * See http://www.relaxng.org/for a list of tools that can validate an XML 
> document using RELAX
>  NG. Note that not all products are capable of evaluating the Schematron 
> assertions in the
>  schema.
>
> * The Statement of Use must be made to a specific version of the 
> Specification and must include
>  the Specification’s approval date.  In this case DocBook Schema Version 5.2 
> Committee
>  Specification 01, dated 19 July 2023, available at
>  https://docs.oasis-open.org/docbook/docbook/v5.2/cs01/docbook-v5.2-cs01.html
>
> * The Statement from a nonmember should be submitted to the comment facility:
>  http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=docbook
>
> The DocBook TC will evaluate and vote to accept any Statements that are 
> submitted.  Let me know
> if you have any questions.
>
> Any help you can provide on this issue would be much appreciated.  If you are 
> unable to submit a
> statement, perhaps you could refer me to other users whom I could contact.
>
> Bob Stayton
> Chair, OASIS DocBook Technical Committee
>  b...@sagehill.net 

Be seeing you,
  norm

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> We are thinking beings, and we cannot exclude the intellect from
> participating in any of our functions.--William James


signature.asc
Description: PGP signature

[docbook-apps] Fwd: Reminder: Oxygen AI Positron: Transforming Technical Content Creation through AI-Powered Writing starts in 1 Hour

[Dave Pawson]

AI and docbook?
>From Oxygen editor presentation... (in the world of AI)
Given a docbook marked up document: How to add (in metadata) 'what
questions does this document answer?


I'm hoping George will make the presentation available as a recording?
Some rather smart 'add ons' appropriate to docbook.

regards


-- Forwarded message -
From: George Bina 
Date: Wed, 25 Oct 2023 at 14:58
Subject: Reminder: Oxygen AI Positron: Transforming Technical Content
Creation through AI-Powered Writing starts in 1 Hour
To: 


Oxygen AI Positron: Transforming Technical Content Creation through
AI-Powered Writing

Wed, Oct 25, 2023 4:00 PM - 5:00 PM BST

This is a reminder that *"Oxygen AI Positron: Transforming Technical
Content Creation through AI-Powered Writing"* will begin in 1 Hour on:

Wed, Oct 25, 2023 4:00 PM - 5:00 PM BST

Please send your questions, comments and feedback to: supp...@oxygenxml.com

How to Join the Webinar

Wed, Oct 25, 2023 4:00 PM - 5:00 PM BST

Add to calendar: Outlook® Calendar

| Google Calendar™

| iCal®


1. Click the button to join the webinar at the specified time and date:
Join Webinar


Note: This link should not be shared with others; it is unique to you.

Before joining, be sure to check system requirements

to avoid any connection issues.

2. Choose one of the following audio options:

To use your computer's audio:

When the webinar begins, you will be connected to audio using your
computer's microphone and speakers (VoIP). A headset is recommended.

or

*To use your telephone:*

If you prefer to use your phone, you must select "Use Telephone" after
joining the webinar and call in using the numbers below.

Australia: +61 2 9091 7604

Access Code: 511-829-629
Audio PIN: Shown after joining the webinar
Calling from another country?


Webinar ID: 683-583-235

To Cancel this registration

If you can't attend this webinar, you may cancel your registration

at any time.

This email was sent on behalf of the event organizer by GoTo Webinar. To
review the organizer's privacy policy, exercise any applicable privacy
rights, or stop receiving their communications, please contact the
organizer directly.

Stop GoTo Webinar emails

. Report spam


333 Summer Street . Boston, MA 02210 . Privacy Policy
 . Anti-spam Policy
 . www.goto.com/webinar
©2023 GoTo, Inc.


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

[docbook-apps] [ANN] Version 26 of the Oxygen XML Editor is Now Available!

[Alin Belu]

Hi everyone,

We are proud to announce that *Oxygen XML Editor/Author version 26* is 
now available!


Listing below some new features which may be useful for our DocBook users:

Author
==

* When renaming an XML element in the Author visual editing mode with 
change tracking enabled, the change is now tracked as an element 
deletion followed by the newly renamed element insertion. This 
enhancement provides a more accurate representation of the changes made 
during the renaming process.


* Content Completion Configuration (cc_config.xml) files provide a 
simple and efficient way to configure the content completion proposals 
Oxygen offers to users for a specific document type. By default, when 
defining rules in a content completion configuration file, if multiple 
rules match a certain element context, then only the first one that 
matches is applied. Now it is possible to combine multiple rules by 
setting the merge="true" attribute on the rules that match a single 
element context. This allows for a more intuitive and flexible way of 
specifying the content completion behavior via content completion 
configuration files.


XSLT / XQuery / XPath
==

* XSLT and XQuery Transformation and Debugging Updated to Use Saxon 
Version 12.3.


* Saxon added more extension functions and instructions in the Saxon 
namespace, as well as experimental implementations for version 4.0 
extensions. These functions are now supported and included in the list 
of proposals of the content completion assistant. Some examples include: 
fn:all(), fn:all-different(), fn:all-equal(), fn:characters(), 
fn:contains-sequence(), fn:ends-with-sequence(), fn:expanded-QName(), 
fn:foot(), fn:deep-equal(), fn:parse-uri(), fn:xdm-to-json(), and many 
more. For details, see 
https://www.saxonica.com/documentation12/index.html#!functions/saxon.


* The saxon:evaluate(), saxon:eval(), and saxon:expression() extension 
functions have been dropped, but the same effects (and more) can be 
achieved using the xsl:evaluate standard XSLT 3.0 instruction. Also, the 
saxon:parse-html() extension function is now synonymous for 
fn:parse-html() (a new function proposed for XPath 4.0). If you use any 
of these functions you will need to update your code before using Saxon 
12.3.


* XPath 4.0 syntax extensions are now fully supported.

* When using the Extract Function action (found in the contextual menu's 
Refactoring submenu) to extract XSLT functions, XPath expressions are 
rebuilt based on the current context. The context is passed as a 
parameter in the newly created function. This ensures that the extracted 
functions seamlessly integrate into the existing code, providing a more 
efficient and reliable development process.


* Two new AI functions are now available in the content completion 
proposals for XSLT, XQuery, XPath, and Schematron. The 
ai:transform-content(instruction, content) function can be used to 
rephrase content and the ai:verify-content(instruction, content) 
function can be used to perform validation checks on the existing 
content. These extension functions are added by the Oxygen AI Positron 
Assistant plugin, enabling the use of AI-based processing from XPath 
expressions.


XML Refactoring
==

* Some refactoring actions can be applied on specific documents, thus 
providing a way to select only those documents. A new optional 
filesFilter attribute can be used in the descriptor file when creating 
custom refactoring operations to specify a default resources filter by 
using a file pattern or list of file patterns separated by a comma (e.g. 
filesFilter="*.dita, *.xml" will select only the files with either .dita 
or .xml extensions).


File Comparison
==

* A new Merge Documents with Change Tracking Highlights action is 
available in the Tools menu. It can be used to merge two XML files 
(based on a 2-way mode comparison). All the files involved in the 
process are merged by saving the visual comparison results as a separate 
document with highlighted tracked changes that can later be reviewed and 
accepted or rejected.


* A new Merge Directories with Change Tracking Highlights action is 
available in the Tools menu. It can be used to merge two directories 
(based on a 2-way mode comparison). All pairs of modified XML files 
involved in the process are merged by saving the visual comparison 
results as documents with highlighted tracked changes that can later be 
reviewed, with the option to accept or reject these changes.


* The file comparison tool has a new action in the File menu called Save 
Comparison as Document with Tracked Changes. This action allows you to 
merge two compared documents based on the differences detected and save 
the results as a specified file that includes the special change 
tracking marks. You can load the resulting file in Oxygen's Author mode 
so you can 

[docbook-apps] Statement of Use for DocBook version 5.2

[Bob Stayton]

Hello,

I'm the Chair of the OASIS DocBook Technical Committee. The Committee is 
in the last stages of getting The DocBook Schema Version 5.2 through the 
OASIS approval process.  We need to submit three Statements of Use of 
the new schema, and I would like to ask if any participants in the 
DocBook user community might like to submit one.  You need not be a 
member of OASIS to submit one. Here are the requirements for making such 
a Statement:


 * It is a written statement that a party has successfully used or
   implemented that specification in accordance with all or some of its
   conformance clauses, identifying those clauses that apply, and
   stating whether its use included the interoperation of multiple
   independent implementations.  The conformance clauses for DocBook
   5.3 are:

 o This specification normatively defines DocBook V5.2 with a RELAX
   NG grammar and a set of Schematron assertions. A conformant
   DocBook V5.2 document must be valid according to both the
   grammar and the assertions.
 o The reference documentation describes additional constraints and
   processing expectations. A conformant DocBook V5.2 document
   should respect those constraints and anticipate those processing
   expectations.
 o See http://www.relaxng.org/for a list of tools that can validate
   an XML document using RELAX NG. Note that not all products are
   capable of evaluating the Schematron assertions in the schema.

 * The Statement of Use must be made to a specific version of the
   Specification and must include the Specification’s approval date. 
   In this case DocBook Schema Version 5.2 Committee Specification 01,
   dated 19 July 2023, available at
   https://docs.oasis-open.org/docbook/docbook/v5.2/cs01/docbook-v5.2-cs01.html

 * The Statement from a nonmember should be submitted to the comment
   facility:
   http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=docbook

The DocBook TC will evaluate and vote to accept any Statements that are 
submitted.  Let me know if you have any questions.


Any help you can provide on this issue would be much appreciated. If you 
are unable to submit a statement, perhaps you could refer me to other 
users whom I could contact.


Bob Stayton
Chair, OASIS DocBook Technical Committee
b...@sagehill.net

Re: [docbook-apps] Accented characters in HTML documentation

[Jirka Kosek]

On 20.09.2023 21:47, Esteban Zimanyi wrote:

In the resulting HTML on Github Pages
https://mobilitydb.github.io/MobilityDB-workshop/
the accentuated characters have been replaced by �

Any idea how to solve this?


Most likely this is encoding issue. For legacy reasons DocBook 
stylesheets use ISO-8859-1 encoding whereas most current web serves 
expect that you upload content in UTF-8 encoding. Encoding can be easily 
changed, see http://www.sagehill.net/docbookxsl/OutputEncoding.html


--
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
 Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--


OpenPGP_signature
Description: OpenPGP digital signature

[docbook-apps] ANN] Release of XMLmind XML Editor v10.5

[Hussein Shafie]

XMLmind XML Editor v10.5 (September 1, 2023): Highlights:

==
Release of XMLmind XML Editor Web Edition v1.0, a 100% JavaScript, 
lightweight, streamlined, implementation of XMLmind XML Editor running 
in the web browser. See https://www.xmlmind.com/xmleditor/web_edition.shtml


- New Web Edition License: 
https://www.xmlmind.com/xmleditor/license_xxew.html.


- Existing licenses modified to allow deploying and using the 
desktop app and/or the web app: Site License: 
https://www.xmlmind.com/xmleditor/license_xxe_site.html, Corporate 
License: https://www.xmlmind.com/xmleditor/license_xxe_corp.html, 
Developer License: https://www.xmlmind.com/xmleditor/license_xxe_dev.html.


- Price list: https://www.xmlmind.com/xmleditor/web_edition.shtml.
==

Other changes:

- Minor enhancements and bug fixes.

- Updated most software components (XMLmind DITA Converter, XMLmind 
XSL-FO Converter, XMLmind Word To XML, etc).


More information in https://www.xmlmind.com/xmleditor/changes.html



---
What is XMLmind XML Editor?

XMLmind XML Editor is a strictly validating, near WYSIWYG, XML editor, 
having extensive DITA, DocBook, XHTML and MathML support and industrial 
strength DOCX import and export facilities. Its users are generally 
technical writers, engineers and scholars who use it to write large, 
complex, modular, documents.


Personal Edition is free to use by many persons and organizations.

New Web Edition is a 100% JavaScript, lightweight, streamlined, 
implementation of XMLmind XML Editor running in the web browser, thus 
not requiring any installation on the user side.


Home page: https://www.xmlmind.com/xmleditor/

Download: https://www.xmlmind.com/xmleditor/download.shtml

-
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] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

On 1 Aug 2023, at 15:21, Paul Hoadley  wrote:

> On 1 Aug 2023, at 13:14, Paul Hoadley  > wrote:
> 
>> While I suspect this will work eventually
> 
> I'm still holding out hope...

Got there in the end, thanks to an answer by Jukka Matilainen to my post on 
Stack Overflow:

https://stackoverflow.com/questions/76848364/how-can-i-embed-docbook-xslt-transformation-in-a-java-web-app/

Jukka showed how to integrate a custom URLStreamHandler to source all resources 
from the classpath. Here's a small project that demonstrates the concept:

https://github.com/paulhoadley/DocBookInJar

Thanks to Norm and Benjamin for additional help on the list here.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

[docbook-apps] [ANN] Release of XMLmind XML Editor Web Edition 1.0.0-beta4

[Hussein Shafie]

Fourth public release of XMLmind XML Editor Web Edition, version 
1.0.0-beta4, is freely available for testing.


Added features and bug fixes documented in 
https://www.xmlmind.com/xmleditor/_web/doc/manual/changes.html


---
What is XMLmind XML Editor Web Edition?
---

XMLmind XML Editor Web Edition (XXEW for short) is a 100% JavaScript, 
lightweight, streamlined, implementation of XMLmind XML Editor running 
in the web browser, thus not requiring any installation on the user side.


Released version 1.0.0-beta4, which is feature complete, is freely 
available for testing. XXEW will become a commercial product at the end 
of the beta test period.


* Online demo: https://www.xmlmind.com/xmleditor/_web/demo/index.html

* Screencast explaining "the basics" (for those unfamiliar with XMLmind 
XML Editor): 
https://www.xmlmind.com/xmleditor/_screencast/xxew_basics/xxew_basics.html


* More information: https://www.xmlmind.com/xmleditor/web_edition.shtml


-
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] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

On 1 Aug 2023, at 13:14, Paul Hoadley  wrote:

> While I suspect this will work eventually

I'm still holding out hope... I've now got a catalog.xml mapping every .xsl, 
.xml, .ent, and .dtd file to its 'classpath:' URI equivalent. (Another aside: 
given that's a really simple string manipulation, can I make my own resolver 
that doesn't need the catalog.xml? What would it extend, which method would I 
override, and how would I provide that to Saxon's Transformer?)

Anyway, now this:

Error at char 9 in expression in xsl:param/@select on line 18 column 57 of 
l10n.xsl:
  FODC0002  I/O error reported by XML parser processing
  file:///xsl/docbook-xsl-1.79.2/common/l10n.xsl. Caused by 
java.io.FileNotFoundException:
  /xsl/docbook-xsl-1.79.2/common/l10n.xsl (No such file or directory)
at parameter local.l10n.xml on line 18 column 57 of l10n.xsl:
 invoked by global parameter local.l10n.xml at 
file:///xsl/docbook-xsl-1.79.2/common/l10n.xsl#18

Where that line involves a call to document(''):



Looks like it's insisting on load itself from a file, and then (obviously) 
can't find it at that URI. How do we tell whoever is resolving calls to the 
document() function to use the classpath?


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

[Some of this exchange unintentionally fell off-list.]

On 29 Jul 2023, at 22:37, Norm Tovey-Walsh  wrote:

> So what’s happened here is that classpath:/xsl/juno-driver.xsl has
> succeeded and now it’s trying to import docbook.xsl. Unfortunately, the
> java.net class doesn’t like classpath:, so the attempt to resolve
> “docbook.xsl” agains the base URI fails.
> 
> That said, I’m a little surprised that the XML Resolver doesn’t do the
> right thing for you in this case. They’re not found in the catalog, I
> suppose.

I think this was my blunder. At one point I was doing this:

factory.setURIResolver(new StandardURIResolver());

Although that class claims to support classpath: URIs, it's not an 
org.xmlresolver class. Omitting that line gets me further. (What gets used by 
default, XMLCatalogResolver?)

> If you use the full, absolute URI for the base stylesheet and setup a
> catalog to map that to the classpath: URI, I think it’ll work.

> On 30 Jul 2023, at 15:50, Norm Tovey-Walsh  wrote:
> 
>> Sounds promising... could you give me a little more hand-holding here? What 
>> would the full,
>> absolute URI look like here, and how do I set up a catalog and provide that 
>> to the machinery?
> 
> Sure. If you look in, for example, the xslTNG jar file, you’ll find a
> catalog in xmlresolver/catalog.xml that does the mapping for xslTNG. If
> you check out the repo, you’ll find targets in build.gradle that
> construct it from sources. It’s a bit fussy because I’m mapping a couple
> off different flavors for some resources.
> 
> If you’re using the latest XML Resolver (which is what you’ll get with
> Saxon 11+), then constructing a corresponding catalog for the URIs of
> your stylesheets should “just work”. The resolver will look for
> xmlresolver/catalog.xml files in jars on the classpath.

After a lot of trial and error (quick aside: I cannot, for the life of me, get 
any SLF4J logging output from Saxon or org.xmlresolver classes), if I do this:

private Document transformDocument(Document document) throws 
TransformerException, FileNotFoundException {
DOMResult result = new DOMResult();
TransformerFactory factory = TransformerFactory.newInstance();
InputStream is = 
XmlTest.class.getResourceAsStream("/xsl/juno-driver.xsl");
Source source = new StreamSource(is, "file:/xsl/juno-driver.xsl");
Transformer transformer = factory.newTransformer(source);
transformer.transform(new DOMSource(document), result);
return (Document) result.getNode();
}

with this catalog.xml:



   
   
   
   
   
   
   


I get as far as the catalog goes. That is, at this point it fails with:

Error 
  XTSE0165: I/O error reported by XML parser processing
  file:/xsl/docbook-xsl-1.79.2/lib/lib.xsl: /xsl/docbook-xsl-1.79.2/lib/lib.xsl 
(No such
  file or directory)
javax.xml.transform.TransformerConfigurationException: 
net.sf.saxon.s9api.SaxonApiException: I/O error reported by XML parser 
processing file:/xsl/docbook-xsl-1.79.2/lib/lib.xsl

Which seems pretty reasonable, because that's the next included file in 
fo/docbook.xsl and it's not in the catalog.

While I suspect this will work eventually, it seems more than slightly bogus. 
The 'name' attributes in the catalog.xml don't seem to matter until I get down 
to the DocBook files, at which point it seems to be imperative that they're 
'file:' URIs. Why am I setting the system ID on that first StreamSource using a 
'file:' URI? Is this all working as expected, and I just need to finish the 
catalog?

(And if anyone can tell me how to turn on SLF4J logging output, I suspect that 
would be a big help!)


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Benjamin DE DARDEL]

Yes it works via files :
- docbook xls stylesheets are embedded in the resources jar
- they are copied in $HOME/.ant4docbook directory to be used by an internal
or external processor (that generates files).
I understand that you prefer an 'in memory' approach for your web app.

Le sam. 29 juil. 2023 à 19:47, Paul Hoadley  a écrit :

> On 29 Jul 2023, at 6:28 pm, Benjamin DE DARDEL <
> benjamin.dedar...@gmail.com> wrote:
>
> This is an old problem that I looked into some time ago.
> I use my ant4docbook project daily to generate pdfs, from docbook, markdown 
> and docbook xsl1.xx.
> Surely there are some interesting things to take in there.
>
>
> Thanks for the suggestion. I've had a browse over the source. It seems
> like any reference to the embedded DocBook XSL is via Files, which is
> something I want to avoid. Ideally, I'd like to get this to run "out of the
> JAR". Am I missing some code in ant4docbook that would demonstrate that
> approach?
>
> The next step is to use xsltng + an html to pdf converter (chromium cef pdf?).
>
>
> For the moment, at least, I'd like to see if I can get to PDF via FO,
> which means the v1 or v2 stylesheets.
>
>
> --
> Paul Hoadley
> https://logicsquad.net/
> https://www.linkedin.com/company/logic-squad/
>
>

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

On 29 Jul 2023, at 6:28 pm, Benjamin DE DARDEL  
wrote:

> This is an old problem that I looked into some time ago.
> I use my ant4docbook project daily to generate pdfs, from docbook, markdown 
> and docbook xsl1.xx.
> Surely there are some interesting things to take in there.

Thanks for the suggestion. I've had a browse over the source. It seems like any 
reference to the embedded DocBook XSL is via Files, which is something I want 
to avoid. Ideally, I'd like to get this to run "out of the JAR". Am I missing 
some code in ant4docbook that would demonstrate that approach?

> The next step is to use xsltng + an html to pdf converter (chromium cef pdf?).

For the moment, at least, I'd like to see if I can get to PDF via FO, which 
means the v1 or v2 stylesheets.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Benjamin DE DARDEL]

Hi,

This is an old problem that I looked into some time ago.
I use my ant4docbook project daily to generate pdfs, from docbook,
markdown and docbook xsl1.xx.
Surely there are some interesting things to take in there.
The next step is to use xsltng + an html to pdf converter (chromium cef pdf?).

Regards,
Benjamin

Le ven. 28 juil. 2023 à 22:35, Paul Hoadley  a écrit :

> On 29 Jul 2023, at 13:48, Paul Hoadley  wrote:
>
> I'll put together a minimal example and see if you can put me in the right
> direction.
>
>
> To recap, I'm building a Java project that will encapsulate the DocBook
> stylesheets and some classes to do some transformations, all packaged as a
> JAR to become part of a larger web app. The project uses the standard Maven
> layout, and Saxon-HE 12.3. I've put the XSL in src/main/resources/xsl:
>
> paulh@elmo xsl % pwd
> /Users/paulh/Projects/Java/janus/src/main/resources/xsl
> paulh@elmo xsl % ls -l
> total 688
> drwxr-xr-x@ 48 paulh  staff1536 29 Jul  2020 docbook-xsl-1.79.2
> -rw-r--r--   1 paulh  staff   16681 24 Jul 10:41 header-footer.xsl
> -rw-r--r--   1 paulh  staff7494 28 Jul 14:23 juno-driver.xsl
> -rw-r--r--   1 paulh  staff8689 24 Jul 14:33 table.xsl
> -rw-r--r--   1 paulh  staff  307717 18 Jul 12:49 titlepage.xsl
>
> juno-driver.xsl is the top-level customisation stylesheet, and it imports
> the others:
>
>   
>   
>   
>   
>
> To be clear, addressing the XSL stylesheets as files on the filesystem
> works just fine. That is, this does exactly what it should:
>
> private Document transformDocument(Document document) throws
> TransformerException, FileNotFoundException {
> DOMResult result = new DOMResult();
> TransformerFactory factory = TransformerFactory.newInstance();
> factory.setURIResolver(new StandardURIResolver());
> InputStream is = new FileInputStream(new
> File("/Users/paulh/Projects/Java/janus/src/main/resources/xsl/juno-driver.xsl"));
> Source source = new StreamSource(is,
> "file:/Users/paulh/Projects/Java/janus/src/main/resources/xsl/juno-driver.xsl");
> Transformer transformer = factory.newTransformer(source);
> transformer.transform(new DOMSource(document), result);
> return (Document) result.getNode();
> }
>
> What I want to do, though, is reference the stylesheets as classpath
> resources. StandardURIResolver claims to be able to handle the "classpath
> URI scheme", so I tried this:
>
> private Document transformDocument(Document document) throws
> TransformerException, FileNotFoundException {
> DOMResult result = new DOMResult();
> TransformerFactory factory = TransformerFactory.newInstance();
> factory.setURIResolver(new StandardURIResolver());
> InputStream is = XmlTest.class.getResourceAsStream("/xsl/juno-driver.xsl");
> Source source = new StreamSource(is, "classpath:/xsl/juno-driver.xsl");
> Transformer transformer = factory.newTransformer(source);
> transformer.transform(new DOMSource(document), result);
> return (Document) result.getNode();
> }
>
> Which results in:
>
> Error
>   XTSE0165: I/O error reported by XML parser processing
>   classpath:xsl/docbook-xsl-1.79.2/fo/docbook.xsl: unknown protocol:
> classpath
> javax.xml.transform.TransformerConfigurationException:
> net.sf.saxon.s9api.SaxonApiException: I/O error reported by XML parser
> processing classpath:xsl/docbook-xsl-1.79.2/fo/docbook.xsl
> at net.sf.saxon.jaxp.SaxonTransformerFactory.newTemplates(
> SaxonTransformerFactory.java:158)
> at net.sf.saxon.jaxp.SaxonTransformerFactory.newTransformer(
> SaxonTransformerFactory.java:112)
> at net.logicsquad.janus.XmlTest.transformDocument(XmlTest.java:142)
>
> If StandardURIResolver can handle classpath URIs, have I just got the
> syntax or other usage wrong somewhere?
>
>
> --
> Paul Hoadley
> https://logicsquad.net/
> https://www.linkedin.com/company/logic-squad/
>
>

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

On 29 Jul 2023, at 13:48, Paul Hoadley  wrote:

> I'll put together a minimal example and see if you can put me in the right 
> direction.

To recap, I'm building a Java project that will encapsulate the DocBook 
stylesheets and some classes to do some transformations, all packaged as a JAR 
to become part of a larger web app. The project uses the standard Maven layout, 
and Saxon-HE 12.3. I've put the XSL in src/main/resources/xsl:

paulh@elmo xsl % pwd
/Users/paulh/Projects/Java/janus/src/main/resources/xsl
paulh@elmo xsl % ls -l
total 688
drwxr-xr-x@ 48 paulh  staff1536 29 Jul  2020 docbook-xsl-1.79.2
-rw-r--r--   1 paulh  staff   16681 24 Jul 10:41 header-footer.xsl
-rw-r--r--   1 paulh  staff7494 28 Jul 14:23 juno-driver.xsl
-rw-r--r--   1 paulh  staff8689 24 Jul 14:33 table.xsl
-rw-r--r--   1 paulh  staff  307717 18 Jul 12:49 titlepage.xsl

juno-driver.xsl is the top-level customisation stylesheet, and it imports the 
others:

  
  
  
  

To be clear, addressing the XSL stylesheets as files on the filesystem works 
just fine. That is, this does exactly what it should:

private Document transformDocument(Document document) throws 
TransformerException, FileNotFoundException {
DOMResult result = new DOMResult();
TransformerFactory factory = TransformerFactory.newInstance();
factory.setURIResolver(new StandardURIResolver());
InputStream is = new FileInputStream(new 
File("/Users/paulh/Projects/Java/janus/src/main/resources/xsl/juno-driver.xsl"));
Source source = new StreamSource(is, 
"file:/Users/paulh/Projects/Java/janus/src/main/resources/xsl/juno-driver.xsl");
Transformer transformer = factory.newTransformer(source);
transformer.transform(new DOMSource(document), result);
return (Document) result.getNode();
}

What I want to do, though, is reference the stylesheets as classpath resources. 
StandardURIResolver claims to be able to handle the "classpath URI scheme", so 
I tried this:

private Document transformDocument(Document document) throws 
TransformerException, FileNotFoundException {
DOMResult result = new DOMResult();
TransformerFactory factory = TransformerFactory.newInstance();
factory.setURIResolver(new StandardURIResolver());
InputStream is = 
XmlTest.class.getResourceAsStream("/xsl/juno-driver.xsl");
Source source = new StreamSource(is, "classpath:/xsl/juno-driver.xsl");
Transformer transformer = factory.newTransformer(source);
transformer.transform(new DOMSource(document), result);
return (Document) result.getNode();
}

Which results in:

Error 
  XTSE0165: I/O error reported by XML parser processing
  classpath:xsl/docbook-xsl-1.79.2/fo/docbook.xsl: unknown protocol: classpath
javax.xml.transform.TransformerConfigurationException: 
net.sf.saxon.s9api.SaxonApiException: I/O error reported by XML parser 
processing classpath:xsl/docbook-xsl-1.79.2/fo/docbook.xsl
at 
net.sf.saxon.jaxp.SaxonTransformerFactory.newTemplates(SaxonTransformerFactory.java:158)
at 
net.sf.saxon.jaxp.SaxonTransformerFactory.newTransformer(SaxonTransformerFactory.java:112)
at net.logicsquad.janus.XmlTest.transformDocument(XmlTest.java:142)

If StandardURIResolver can handle classpath URIs, have I just got the syntax or 
other usage wrong somewhere?


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

On 28 Jul 2023, at 3:10 pm, Norm Tovey-Walsh  wrote:

> Paul Hoadley  writes:
>> I can be more specific about what I've tried, and how it fails, but
>> obviously this isn't a Java mailing list. For now, can anyone (a) tell
>> me whether this is likely to succeed, or whether there's a better
>> approach, or (b) even better, point me at an example of this working
>> in the wild?
> 
> There are a number of needles you have to thread here and without some
> information about how it failed, it’s a bit hard to guess what didn’t
> work.

Yes, understood. I am happy to show some code and stack traces, just didn't 
want to swamp this non-Java list with my very Java problem. I'll put together a 
minimal example and see if you can put me in the right direction.

> The good news is that the xslTNG stylesheets should “just work” the way
> you are hoping:
> 
>  https://xsltng.docbook.org/guide/2.1.6/ch-using.html#java-main

That is good to know—thanks.


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

Re: [docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Norm Tovey-Walsh]

Paul Hoadley  writes:
> I can be more specific about what I've tried, and how it fails, but
> obviously this isn't a Java mailing list. For now, can anyone (a) tell
> me whether this is likely to succeed, or whether there's a better
> approach, or (b) even better, point me at an example of this working
> in the wild?

There are a number of needles you have to thread here and without some
information about how it failed, it’s a bit hard to guess what didn’t
work.

The good news is that the xslTNG stylesheets should “just work” the way
you are hoping:

  https://xsltng.docbook.org/guide/2.1.6/ch-using.html#java-main

If you have any trouble, I’m happy to try to help.

Be seeing you,
  norm

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> In matters of style, swim with the current; in matters of principle,
> stand like a rock.--Thomas Jefferson


signature.asc
Description: PGP signature

[docbook-apps] Embedding DocBook → PDF transformation in a Java web app

[Paul Hoadley]

Hello,

I'm at the proof-of-concept phase of building some DocBook → PDF transformation 
into a web application. Our requirements are quite modest, and I've built a 
customisation layer over the 1.79.2 stylesheets for the moment, though could 
happily use the xslt20 stylesheets if more appropriate.

What I want to do, at least in the first instance, is run this entirely within 
the web app's JVM—that is, no calling out to external tools or services. 
Additionally, I want the stylesheets and customisations to live in a JAR, not 
on any local filesystem. As a quick and dirty test, I've put the custom 
stylesheets in src/main/resources/xsl, and then the entire docbook-xsl-1.79.2 
directory in there as well. I'm just using JUnit 5 (in Eclipse) to run some 
test code against this idea. Using Saxon HE-12.3, I can't get any further than 
loading the top-level customisation stylesheet (by getting an InputStream from 
getResourceAsStream() and wrapping that in a StreamSource). Trying to import 
anything else results in a range of failure modes.

I can be more specific about what I've tried, and how it fails, but obviously 
this isn't a Java mailing list. For now, can anyone (a) tell me whether this is 
likely to succeed, or whether there's a better approach, or (b) even better, 
point me at an example of this working in the wild?


-- 
Paul Hoadley
https://logicsquad.net/
https://www.linkedin.com/company/logic-squad/

[docbook-apps] [ANN] Release of XMLmind XSL-FO Converter v6.4.1

[Hussein Shafie]

Maintenance release:
- updated several software components in XMLmind XSL Utility and XMLmind 
XSL Server;

- official support of Java™ 20.

More information: https://www.xmlmind.com/foconverter/changes.html

-
What is XMLmind XSL-FO Converter?
-

XMLmind XSL-FO Converter is an XSL-FO processor similar to Apache FOP, 
RenderX XEP or Antenna House XSL Formatter, except that it generates 
RTF, WML, ODT and DOCX file formats rather than PDF.


XMLmind XSL-FO Converter is available as a Java™ software component, a 
.NET software component, a desktop application and a server-side 
application (Java Servlet).


The desktop application called "XMLmind XSL Utility" 
(https://www.xmlmind.com/foconverter/xsl_utility.html) makes it easy 
converting DITA, DocBook, XHTML and XSL-FO documents to a variety of 
formats (PDF, RTF, WML, ODT, DOCX, HTML, EPUB, Web Help, etc).


XMLmind XSL Utility also makes it easy customizing the deliverables it 
generates (PDF, DOCX, EPUB, Web Help, etc) and this, without modifying 
configuration files by hand and without prior knowledge of XSLT. See 
https://www.xmlmind.com/foconverter/_distrib/xslutil/doc/help/com.xmlmind.xslutil.ConversionEditor.html#customizing_xslt


Home page: https://www.xmlmind.com/foconverter/

-
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] fo, chapter headings corrupted

[Dave Pawson]

On Fri, 7 Jul 2023 at 10:28, Norm Tovey-Walsh  wrote:
>
> > font-family="ariesSCB,Symbol,ZapfDingbats">
> […]
> > All that shows in the PDF is
> >
> > 9.!
> >
> > I'm tending to look at a font missing problem, except for the two
> > 'present' characters.
>
> Looks like a missing font problem at first glance. If you don’t have
> “ariesSCB” then you’re only getting characters from Symbol and Zapf
> Dingbats.

Quite right Norm.
   Aries - correct
   aries - incorrect.

Thanks.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-----
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] fo, chapter headings corrupted

[Norm Tovey-Walsh]

> font-family="ariesSCB,Symbol,ZapfDingbats">
[…]
> All that shows in the PDF is
>
> 9.!
>
> I'm tending to look at a font missing problem, except for the two
> 'present' characters.

Looks like a missing font problem at first glance. If you don’t have
“ariesSCB” then you’re only getting characters from Symbol and Zapf
Dingbats.

Symbol contains “9”, “.”, and “!” in the expected places[1]. I guess
modern systems “know” what Unicode characters are in a font and you
don’t get ≅ or ✠ for “A” because neither of those is an “A” even though
it’s ostensibly at code point 0x41 in Symbol and Zapf Dingbats,
respectively.

Be seeing you,
  norm

[1] https://en.wikipedia.org/wiki/Symbol_%28typeface%29

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> Life always comes to a bad end.--Marcel Aymé


signature.asc
Description: PGP signature

[docbook-apps] fo, chapter headings corrupted

[Dave Pawson]

Using xep.


chapter in fo is



Chapter 9. All at
sea!

All that shows in the PDF is

9.!


I'm tending to look at a font missing problem, except for the two
'present' characters.

Any other ideas please?

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] force.blank.pages 0 messes up footers

[Tony Graham]

On 06/07/2023 16:37, Kevin Dunn wrote:

I have been using the default value, 1, for force.blank.pages but
wanted to try setting it to 0 to conserve page count. It works as
expected except that when a chapter starts on a verso page, the page
numbers appear on the inside (binding side) of the page. Is there
another stylesheet parameter that I need to set along with
force.blank.pages to get page numbers to appear consistent on the
outside edge of the page?

I do have double.sided set to 1. Chapters that start on a recto page
 have the page numbers correctly on the outside of the page.


I had the same problem for the Markup UK proceedings, where every paper
() starts on a verso page.

Here's a pull request that you may be able to merge into your local copy
of the stylesheet:

   https://github.com/docbook/xslt10-stylesheets/pull/197

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp

-
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] force.blank.pages 0 messes up footers

[Kevin Dunn]

I have been using the default value, 1, for force.blank.pages but wanted to try 
setting it to 0 to conserve page count. It works as expected except that when a 
chapter starts on a verso page, the page numbers appear on the inside (binding 
side) of the page. Is there another stylesheet parameter that I need to set 
along with force.blank.pages to get page numbers to appear consistent on the 
outside edge of the page?

I do have double.sided set to 1. Chapters that start on a recto page have the 
page numbers correctly on the outside of the page.

[docbook-apps] [ANN] Third public release of XMLmind XML Editor Web Edition

[Hussein Shafie]

Third public release of XMLmind XML Editor Web Edition, version 
1.0.0-beta3, is freely available for testing.


Added features and bug fixes documented in 
https://www.xmlmind.com/xmleditor/_web/doc/manual/changes.html


---
What is XMLmind XML Editor Web Edition?
---

XMLmind XML Editor Web Edition (XXEW for short) is a 100% JavaScript, 
lightweight, streamlined, implementation of XMLmind XML Editor running 
in the web browser, thus not requiring any installation on the user side.


Released version 1.0.0-beta3, which is feature complete, is freely 
available for testing. XXEW will become a commercial product at the end 
of the beta test period.


* Online demo: https://www.xmlmind.com/xmleditor/_web/demo/index.html

* Screencast explaining "the basics" (for those unfamiliar with XMLmind 
XML Editor): 
https://www.xmlmind.com/xmleditor/_screencast/xxew_basics/xxew_basics.html


* More information: https://www.xmlmind.com/xmleditor/web_edition.shtml

-
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] [ANN] Release of XMLmind Word To XML v1.10

[Hussein Shafie]

Release of XMLmind Word To XML v1.10:

- Several bug fixes.
- Web Help output format: now supports the new corporate layout in 
addition to the classic and simple layouts.


More information in https://www.xmlmind.com/w2x/changes.html

-
What is XMLmind Word To XML?
--

XMLmind Word To XML can automatically convert DOCX files to:

- Clean, styled, valid HTML (single page or multi-page HTML, Web Help, 
EPUB) looking very much like the source DOCX file.


- Unstyled, but structured and valid, DITA bookmap, map, topic, DocBook 
(including V5.1 assembly), XHTML (single page or multi-page HTML, Web 
Help, EPUB) or XML conforming to your custom schema.


Home Page: https://www.xmlmind.com/w2x/

Download: https://www.xmlmind.com/w2x/download.shtml

Free online DOCX conversion services: 
https://www.xmlmind.com/w2x/online_w2x.html


-
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] [ANN] Second public release of XMLmind XML Editor Web Edition

[Hussein Shafie]

Second public release of XMLmind XML Editor Web Edition, version 
1.0.0-beta2, is freely available for testing.


Added features and bug fixes documented in 
https://www.xmlmind.com/xmleditor/_web/doc/manual/changes.html


---
What is XMLmind XML Editor Web Edition?
---

XMLmind XML Editor Web Edition (XXEW for short) is a 100% JavaScript, 
lightweight, streamlined, implementation of XMLmind XML Editor running 
in the web browser, thus not requiring any installation on the user side.


Released version 1.0.0-beta2, close to be feature complete, is freely 
available for testing. XXEW will become a commercial product at the end 
of the beta test period.


* Online demo: https://www.xmlmind.com/xmleditor/_web/demo/index.html

* Screencast explaining "the basics" (for those unfamiliar with XMLmind 
XML Editor): 
https://www.xmlmind.com/xmleditor/_screencast/xxew_basics/xxew_basics.html


* More information: https://www.xmlmind.com/xmleditor/web_edition.shtml

-
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] Changing toc parameter values by chapter

[Bob Stayton]

If you are using the XSLT 1 stylesheets, then placing an empty  
element where you want a TOC, and setting the 'process.empty.source.toc' 
stylesheet param to 1 will generate a TOC for that element.  It applies 
to hierarchy elements like chapter and section, but not arbitrary elements.


https://docbook.sourceforge.net/release/xsl/current/doc/fo/process.empty.source.toc.html

Changing the behavior of each TOC would require customization of the 
templates in the DocBook toc.xsl stylesheet module that match on the toc 
element, such as:





so they respond to a processing instruction or attribute setting in the 
way you want.  I would not classify that as an "easy" way, though.


Bob

On 5/24/2023 6:45 AM, Tom Moore wrote:
It appears to me that the parameters that control the placement and 
content of tocs apply at a document level. What I am wondering is if 
it is possible to to set different values for 'generate.toc', 
'toc.section.depth', 'toc.max.dept' etc for different chapters/appendices?


In my document (being output as chunked html) most chapters/appendices 
only need a table of contents at the top of the chapter with 
toc.section.depth=2, toc.max.depth=2. There are some chapters with 
considerable detail that would benefit from also having a table of 
contents inserted at the top sect3 with toc.max.depth=1.  And there is 
one appendix that only needs one toc at the top with a max depth of 1.


Is there an easy way to obtain this variety?  Or am I heading down the 
path to madness?


Thanks,

Tom

Re: [docbook-apps] Changing toc parameter values by chapter

[Norm Tovey-Walsh]

> Is there an easy way to obtain this variety? Or am I heading down the
> path to madness?

The xslTNG stylesheets will put a ToC anywhere that you put an empty
 element. There’s also an m:toc mode that would allow you to
control which elements get a ToC more programmatically:

  https://xsltng.docbook.org/guide/2.1.3/m_toc.html

Be seeing you,
  norm

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> The bitterness of poor quality remains long after the sweetness of
> meeting the schedule has been forgotten.


signature.asc
Description: PGP signature

[docbook-apps] Changing toc parameter values by chapter

[Tom Moore]

It appears to me that the parameters that control the placement and content
of tocs apply at a document level. What I am wondering is if it is possible
to to set different values for 'generate.toc', 'toc.section.depth',
'toc.max.dept' etc for different chapters/appendices?

In my document (being output as chunked html) most chapters/appendices only
need a table of contents at the top of the chapter with
toc.section.depth=2, toc.max.depth=2.  There are some chapters with
considerable detail that would benefit from also having a table of contents
inserted at the top sect3 with toc.max.depth=1.  And there is one appendix
that only needs one toc at the top with a max depth of 1.

Is there an easy way to obtain this variety?  Or am I heading down the path
to madness?

Thanks,

Tom

[docbook-apps] Building xslTNG on Windows

[Norm Tovey-Walsh]

Hello world,

This weekend, I hacked away at the xslTNG stylesheets in an effort to
make them build on Windows. I’ve succeeded. Sort of. It works fine on my
machine (of course), but fails in a GitHub action:

  
https://github.com/ndw/xslTNG/actions/runs/5038739863/jobs/903646#step:8:3750

This looks for all the world like a problem with the encoding,

  https://saxonica.plan.io/issues/6042

but I’ve done everything I can think of to process the files as UTF-8.
Those same mitigations “work for me” locally.

Feedback from other Windows users, most especially someone who can
reproduce the error *and* describe how to fix it (!) most appreciated.

Be seeing you,
  norm

--
Norm Tovey-Walsh 
https://norm.tovey-walsh.com/

> It is said that power corrupts, but actually it's more true that power
> attracts the corruptible. The sane are usually attracted by other
> things than power.--David Brin


signature.asc
Description: PGP signature

[docbook-apps] [ANN] Release of XMLmind XML Editor v10.4

[Hussein Shafie]

Release of XMLmind XML Editor v10.4:

* First public release of XMLmind XML Editor Web Edition

XMLmind XML Editor Web Edition (XXEW for short) is a 100% JavaScript, 
lightweight, streamlined, implementation of XMLmind XML Editor running 
in the web browser, thus not requiring any installation on the user side.


Released version 1.0.0-beta1, almost feature complete, is freely 
available for testing. XXEW will become a commercial product at the end 
of the beta test period.


More information in https://www.xmlmind.com/xmleditor/web_edition.shtml

* Other changes:

- A few minor enhancements and bug fixes.

- Updated most software components (XMLmind DITA Converter, XMLmind 
XSL-FO Converter, XMLmind Word To XML, Saxon, etc).


- Official support of Java™ 20.

More information in https://www.xmlmind.com/xmleditor/changes.html

---
What is XMLmind XML Editor?

XMLmind XML Editor is a strictly validating, near WYSIWYG, XML editor, 
having extensive DITA, DocBook, XHTML and MathML support and industrial 
strength DOCX import and export facilities. Its users are generally 
technical writers, engineers and scholars who use it to write large, 
complex, modular, documents.


Personal Edition is free to use by many persons and organizations.

New Web Edition is a 100% JavaScript, lightweight, streamlined, 
implementation of XMLmind XML Editor running in the web browser, thus 
not requiring any installation on the user side.


Home page: https://www.xmlmind.com/xmleditor/

Download: https://www.xmlmind.com/xmleditor/download.shtml

-
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] [ANN] Oxygen XML Editor version 25.1 has been released!

[Alin Belu]

Hello,

We are incredibly proud to announce that *Oxygen XML Author/Editor 
version 25.1* is now available!


Here is a subset of the released features that might be of interest to 
the DocBook community:


Author Visual Editing
==

* A schema or an Oxygen content completion configuration file may define 
a set of values for an XML element. The content completion mechanism in 
Author mode now allows you to insert any number of values from that set 
by re-triggering the list of content completion proposals and filtering 
out the proposals that were already inserted.


* If an XML document does not specify a DTD or a schema, it is still 
possible for Oxygen to determine a default schema or DTD to use for 
validation and content completion if it is specified by an Oxygen 
framework that matches the respective document. A document framework can 
also be defined with an Oxygen Framework Extension Script file ( 
https://www.oxygenxml.com/doc/versions/25.1/ug-editor/?contextId=framework-customization-script 
) and it is now possible to specify the default schema or DTD for that 
framework directly in these files.


XML Refactoring
==

* XML Refactoring actions in special categories (including the 
DITA-specific ones) are now available to be selected and executed 
directly from the Find Action dialog box.


* You can now use the Move resource and Rename resource actions on both 
files and folders within the Project view's contextual menu (under the 
Refactoring submenu). Previously, these actions were only available for 
files.


Add-ons
==

* Some improvements were made to the Git Client add-on:
- A new options page was added for SSH connections to control SSH agent 
usage.
- The Oxygen project change detection mechanism was improved. It is now 
faster and the Git Staging view no longer needs to be displayed.
- The presentation of the labels associated with a commit in the Git 
History view has been improved to avoid truncating names when it is not 
necessary.
- The commit dot in the Git History graph associated with the head of 
the current branch is now painted differently to make it easier to be seen.

- Various bug fixes and performance improvements were implemented.

* A new Saxon XSLT and XQuery transformer add-on is now available for 
Saxon version 12. The add-on integrates the latest major release of 
Saxon (version 12.0 of the engine).


* A new version for the Saxon XSLT and XQuery transformer 11 add-on is 
now available. The new version integrates Saxon 11.5, the latest 
maintenance release of the Saxon 11 engine.


* The new Live Tutorials add-on allows you to create live tutorials for 
people who want to learn various editing functions for a certain 
vocabulary using the application.


* Various improvements were added to the Terminology Checker add-on:
- The ASD Simplified Technical English Specification (ASD-STE100) Rules 
plugin contributes ASD Simplified Technical English Specification rules 
to the Terminology Checker.
- The MS Writing Style Guide Vale Rules plugin contributes a set of 
Vale-compatible rules based on the Microsoft Writing Style Guide to the 
Terminology Checker.


Scripting
==

* Now you have access to some ready-to-use GitHub project templates and 
GitHub actions that allow you to automate scripts that will be triggered 
every time you push changes to your repository. The following templates 
are available for you to use for inspiration and learning:

- Validate - https://github.com/oxygenxml/oxygen-script-validation-template
- Transform - 
https://github.com/oxygenxml/oxygen-script-transformation-template
- Compare Directories - 
https://github.com/oxygenxml/oxygen-script-comparison-template
- XSD/XSL/WSDL Documentation - 
https://github.com/oxygenxml/oxygen-script-documentation-template


Other
==

* When configuring the content completion proposals at framework level 
using the cc_config.xml configuration file, you can now force an element 
to have a content type imposed. This is done by using the new 
contentType attribute on the elementProposals and its possible values 
are: elementOnly, mixed, and empty.


* When using a Framework Extension Script file to customize a framework, 
relative paths listed in the script file are now automatically resolved 
relative to the location of the script file.


* When processing XML refactoring actions that use the document function 
to load additional resources, the access to schemas that are referenced 
in the loaded documents is now cached to speed up the refactoring process.



For the complete list of features, go to 
https://www.oxygenxml.com/xml_editor/whats_new.html


We hope you will enjoy version 25.1 as much as we enjoyed developing it.
As always, thank you for your support and feedback is welcome!

Best regards,
Alin

--
Alin Belu
Oxygen XML Editor

[docbook-apps] [ANN] Release of XMLmind Word To XML v1.9.1

[Hussein Shafie]

Release of XMLmind Word To XML v1.9.1:

- Maintenance release.
- Updated most software components.
- Official support of macOS Ventura (version 13).

More information in https://www.xmlmind.com/w2x/changes.html

-
What is XMLmind Word To XML?
--

XMLmind Word To XML can automatically convert DOCX files to:

- Clean, styled, valid HTML (single page or multi-page HTML, Web Help, 
EPUB) looking very much like the source DOCX file.


- Unstyled, but structured and valid, DITA bookmap, map, topic, DocBook 
(including V5.1 assembly), XHTML (single page or multi-page HTML, Web 
Help, EPUB) or XML conforming to your custom schema.


Home Page: https://www.xmlmind.com/w2x/

Download: https://www.xmlmind.com/w2x/download.shtml

Free online DOCX conversion services: 
https://www.xmlmind.com/w2x/online_w2x.html


-
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] TOC placement in pdf

[Bob Stayton]

Actually, there's a param for that.  If you insert an empty  
element in your content, and set this param:


process.empty.toc.element=1

and set generate.toc to blank (to turn off the default toc), then the 
stylesheet will generate a toc where that  element is located.  
Apparently this param came after the last edition of my book so it isn't 
covered there, but it is included in the fo parameter reference doc online.


Unfortunately, the content model of article does not allow a toc element 
after normal content, even though the stylesheet doesn't care.  So you 
either have to tolerate a validation error, or insert the empty toc 
element just before processing.


Perhaps a cleaner customization would be to insert a processing 
instruction instead of an empty toc element so it validates, and write 
some XSL to process that PI using the XSL code borrowed and customized 
from the template that starts with





from fo/toc.xsl.  Basically you want to call the template named 
'component.toc' but with the right context.  I haven't tried this, but 
it should work.


Bob

On 2/22/2023 9:15 PM, rohith R wrote:

Hmmm,
 I'll check.
I'd prefer to control it via xsl if that's possible as it provides max 
flexibility.

Not sure if it's possible 樂

On Tue, 21 Feb 2023, 6:17 pm Dave Pawson,  wrote:

Can you use the  element to place it where you want?


HTH

On Tue, 21 Feb 2023 at 06:28, Richard Hamilton
 wrote:
>
> Hello,
>
> The element I’ve used to put things before the toc is
, which allows a lot more elements than you might
expect, including paragraphs and tables.
>
> It is an abuse of the tag, (I’ve used it only for a dedication
in our books), but in a pinch, it might do what you need.
>
> I’m sure others on this list may have some good (probably
better:) ideas, but I’m not sure you can do what you want to do
with any other element, unless you modify the stylesheets.
>
> I hope that helps.
> Dick Hamilton
> ---
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> hamil...@xmlpress.net
>
>
>
> > On Feb 20, 2023, at 23:04, rohith R 
wrote:
> >
> > Hi,
> >
> >
> > I'm using an article style docbook and convert it into pdf.
> >
> > The TOC is getting generated after the title page. I want it
before the section but after the front matter. How can I
accomplish  this?
> >
> > My article structure (docbook5):
> > - title page
> > - other stuff (text and couple of tables)
> > - multiple sections 
> >
> > I want the TOC placed after "other stuff" and before sections.
> >
> > How can I accomplish it?
> > At the moment they get generated after title page when
generating pdf.
> >
> > Regards,
> > R
>
>
>
    -----
> To unsubscribe, e-mail:
docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail:
docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson

XSLT XSL-FO FAQ.
    Docbook FAQ.

-
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] TOC placement in pdf

[Norm Tovey-Walsh]

> I'd prefer to control it via xsl if that's possible as it provides max 
> flexibility.
> Not sure if it's possible 樂 

It’s always possible. but sometimes it’s more work. Find the template
for, let’s say “db:book”, that’s putting the ToC in the “wrong” place.
Override that template in your customization layer so that it doesn’t
produce a ToC.

Find the template that produces the markup that you want the ToC to
proceed or follow, let’s say “db:preface”. Override that template in
your customization layer so that it calls the ToC-template to produce
the ToC in the right place.

Be seeing you,
  norm

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

> Man is made so that he can only find relaxation from one kind of labour
> by taking up another.--Anatole France


signature.asc
Description: PGP signature

Re: [docbook-apps] TOC placement in pdf

[rohith R]

Hmmm,
 I'll check.
I'd prefer to control it via xsl if that's possible as it provides max
flexibility.
Not sure if it's possible 樂

On Tue, 21 Feb 2023, 6:17 pm Dave Pawson,  wrote:

> Can you use the  element to place it where you want?
>
>
> HTH
>
> On Tue, 21 Feb 2023 at 06:28, Richard Hamilton 
> wrote:
> >
> > Hello,
> >
> > The element I’ve used to put things before the toc is ,
> which allows a lot more elements than you might expect, including
> paragraphs and tables.
> >
> > It is an abuse of the tag, (I’ve used it only for a dedication in our
> books), but in a pinch, it might do what you need.
> >
> > I’m sure others on this list may have some good (probably better:)
> ideas, but I’m not sure you can do what you want to do with any other
> element, unless you modify the stylesheets.
> >
> > I hope that helps.
> > Dick Hamilton
> > ---
> > XML Press
> > XML for Technical Communicators
> > http://xmlpress.net
> > hamil...@xmlpress.net
> >
> >
> >
> > > On Feb 20, 2023, at 23:04, rohith R  wrote:
> > >
> > > Hi,
> > >
> > >
> > > I'm using an article style docbook and convert it into pdf.
> > >
> > > The TOC is getting generated after the title page. I want it before
> the section but after the front matter. How can I accomplish  this?
> > >
> > > My article structure (docbook5):
> > > - title page
> > > - other stuff (text and couple of tables)
> > > - multiple sections 
> > >
> > > I want the TOC placed after "other stuff" and before sections.
> > >
> > > How can I accomplish it?
> > > At the moment they get generated after title page when generating pdf.
> > >
> > > Regards,
> > > R
> >
> >
> > ---------
> > To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> > For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> >
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
>
> -
> 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] TOC placement in pdf

[Dave Pawson]

Can you use the  element to place it where you want?


HTH

On Tue, 21 Feb 2023 at 06:28, Richard Hamilton  wrote:
>
> Hello,
>
> The element I’ve used to put things before the toc is , which 
> allows a lot more elements than you might expect, including paragraphs and 
> tables.
>
> It is an abuse of the tag, (I’ve used it only for a dedication in our books), 
> but in a pinch, it might do what you need.
>
> I’m sure others on this list may have some good (probably better:) ideas, but 
> I’m not sure you can do what you want to do with any other element, unless 
> you modify the stylesheets.
>
> I hope that helps.
> Dick Hamilton
> ---
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> hamil...@xmlpress.net
>
>
>
> > On Feb 20, 2023, at 23:04, rohith R  wrote:
> >
> > Hi,
> >
> >
> > I'm using an article style docbook and convert it into pdf.
> >
> > The TOC is getting generated after the title page. I want it before the 
> > section but after the front matter. How can I accomplish  this?
> >
> > My article structure (docbook5):
> > - title page
> > - other stuff (text and couple of tables)
> > - multiple sections 
> >
> > I want the TOC placed after "other stuff" and before sections.
> >
> > How can I accomplish it?
> > At the moment they get generated after title page when generating pdf.
> >
> > Regards,
> > R
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] TOC placement in pdf

[rohith R]

Thank you,
I'm using article as my document  type and can't use the  tag
unfortunately.

I'm happy to change the style sheet but need someone's help here in
figuring out that part.

Regards,
R

On Tue, 21 Feb 2023, 4:58 pm Richard Hamilton, 
wrote:

> Hello,
>
> The element I’ve used to put things before the toc is , which
> allows a lot more elements than you might expect, including paragraphs and
> tables.
>
> It is an abuse of the tag, (I’ve used it only for a dedication in our
> books), but in a pinch, it might do what you need.
>
> I’m sure others on this list may have some good (probably better:) ideas,
> but I’m not sure you can do what you want to do with any other element,
> unless you modify the stylesheets.
>
> I hope that helps.
> Dick Hamilton
> ---
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> hamil...@xmlpress.net
>
>
>
> > On Feb 20, 2023, at 23:04, rohith R  wrote:
> >
> > Hi,
> >
> >
> > I'm using an article style docbook and convert it into pdf.
> >
> > The TOC is getting generated after the title page. I want it before the
> section but after the front matter. How can I accomplish  this?
> >
> > My article structure (docbook5):
> > - title page
> > - other stuff (text and couple of tables)
> > - multiple sections 
> >
> > I want the TOC placed after "other stuff" and before sections.
> >
> > How can I accomplish it?
> > At the moment they get generated after title page when generating pdf.
> >
> > Regards,
> > R
>
>
> -
> 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] TOC placement in pdf

[Richard Hamilton]

Hello,

The element I’ve used to put things before the toc is , which 
allows a lot more elements than you might expect, including paragraphs and 
tables.

It is an abuse of the tag, (I’ve used it only for a dedication in our books), 
but in a pinch, it might do what you need.

I’m sure others on this list may have some good (probably better:) ideas, but 
I’m not sure you can do what you want to do with any other element, unless you 
modify the stylesheets.

I hope that helps.
Dick Hamilton
---
XML Press
XML for Technical Communicators
http://xmlpress.net
hamil...@xmlpress.net



> On Feb 20, 2023, at 23:04, rohith R  wrote:
> 
> Hi,
> 
> 
> I'm using an article style docbook and convert it into pdf.
> 
> The TOC is getting generated after the title page. I want it before the 
> section but after the front matter. How can I accomplish  this?
> 
> My article structure (docbook5):
> - title page
> - other stuff (text and couple of tables)
> - multiple sections 
> 
> I want the TOC placed after "other stuff" and before sections. 
> 
> How can I accomplish it?
> At the moment they get generated after title page when generating pdf.
> 
> Regards,
> R


---------
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] TOC placement in pdf

[rohith R]

Hi,


I'm using an article style docbook and convert it into pdf.

The TOC is getting generated after the title page. I want it before the
section but after the front matter. How can I accomplish  this?

My article structure (docbook5):
- title page
- other stuff (text and couple of tables)
- multiple sections 

I want the TOC placed after "other stuff" and before sections.

How can I accomplish it?
At the moment they get generated after title page when generating pdf.

Regards,
R

[docbook-apps] DocBook xslTNG 2.0.9 released

[Norm Tovey-Walsh]

Hi folks,

This is (I hope) the last pre-release. I just bumped the dependencies
for XML Resolver and the XInclude extension function to the latest
versions.

Feedback welcome.

Be seeing you,
  norm

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

> Worrying is the most natural and spontaneous of all human functions. It
> is time to acknowledge this, perhaps even to learn to do it
> better.--Lewis Thomas


signature.asc
Description: PGP signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

Tony Graham  writes:
> I've just read that part of the XInclude spec [1], and I'm not sure that
> I know what it says, either, but it's clear that the 'language fixup' is
> able to create 'xml:lang=""' in some circumstances.

Yes. I think my XInclude implementation should ad xml:lang="" when the
included file has no in-scope xml:lang. Broader discussion might start
here: http://lists.xml.org/archives/xml-dev/202302/msg00016.html

Be seeing you,
  norm

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

> It does not do harm to the mystery to know a little about it. For far
> more marvelous is the truth than any artists of the past
> imagined!--Richard Feynman


signature.asc
Description: PGP signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

> No localization exists for "" or "". Using default "en".
> Error at xsl:text on line 169 column 19 of functions.xsl:
>   XTMM9000  Processing terminated by xsl:message at line 169 in
>   functions.xsl

Fixed in 2.0.8 just released. The termination was a bug, probably left
over from when I was debugging in earnest. I’ve also patched the
function so that xml:lang="" is an explicit request for the default
language which it selects without raising any warnings.

Be seeing you,
  norm

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

> We have fewer friends than we imagine, but more than we know.--Hugo Von
> Hofmannsthal


signature.asc
Description: PGP signature

[docbook-apps] Misunderstanding Customization

[Michael Urban]

I was trying to add decorations to chapter headings in an epub
document.  After failing to accomplish this purely with CSS, I
resorted to trying to customize the epub stylesheet to emit the
correct HTML with the chapter's .  So I copied the template
verbatim from xhtml/titlepage.xsl into my customization stylesheet:


http://www.w3.org/1999/XSL/Transform; 
version="1.0"
  xmlns:d="http://docbook.org/ns/docbook; 
xmlns="http://www.w3.org/1999/xhtml;>

 




...




And actually, I was able to add the decoration around the 
xhtml block.  But then I noticed that there was no chapter number
in the .  Here is the difference in the epub between a chapter
using my stylesheet, and using the standard one. To be clear, this
is after removing my decoration stuff and using the identical
template in both cases.  In other words, the only thing my customizaton
stylesheet is doing at this point is setting a parameter, and
duplicating the match=d:title template:

12,13c12,13
< 
< Chapter I. First Chapter
---
> http://docbook.org/ns/docbook; class="title">
> First Chapter




The Table of Contents _does_ have the correctly roman-numbered
chapters.  The  element is a child of the  element,
with no  element.

Evidently there is something I am failing to grasp in the way these
pieces fit together.   I hope I have provided enough information
for someone to reproduce the problem.  At present, I am stumped.

Mike

---------
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] DocBook xslTNG prerelease 2.0.7

[Tony Graham]

On 07/02/2023 14:00, Jirka Kosek wrote:

On 07.02.2023 9:53, Norm Tovey-Walsh wrote:

*Blink*. Really? I would not have expected language fixup to do that,
but maybe it does. So xml:lang="" is equivalent to $default-language,
I suppose.


Well, I don't know if this is what XInclude spec says but IIRC there 
were some XInclude processors that did that.


I've just read that part of the XInclude spec [1], and I'm not sure that
I know what it says, either, but it's clear that the 'language fixup' is
able to create 'xml:lang=""' in some circumstances.

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp


[1] https://www.w3.org/TR/xinclude/#language

-
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] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

> As I understand the XML specification, the meaning of an empty
> "xml:lang" attribute is defined as overriding any language inherited
> from the parent element and reverting to the processor default. So it
> might make sense that if no language is indicated in an included file,
> it is taken as unspecified and explicitly marked as such in the larger
> context where it's included.

Righto. A detail that had slipped my memory. I see a 2.0.8 in my future!
Thank you!

Be seeing you,
  norm

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

> We judge ourselves by what we feel capable of doing, while others judge
> us by what we have already done.--Henry Wadsworth Longfellow


signature.asc
Description: PGP signature

RE: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Robert Cavicchio]

Jirka Kosek  wrote:

> On 07.02.2023 9:53, Norm Tovey-Walsh wrote:
> > *Blink*. Really? I would not have expected language fixup to do that, 
> > but maybe it does. So xml:lang="" is equivalent to $default-language, 
> > I suppose.
> 
> Well, I don't know if this is what XInclude spec says but IIRC there were 
> some XInclude processors that did that.


As I understand the XML specification, the meaning of an empty "xml:lang" 
attribute is defined as overriding any language inherited from the parent 
element and reverting to the processor default. So it might make sense that if 
no language is indicated in an included file, it is taken as unspecified and 
explicitly marked as such in the larger context where it's included.

https://www.w3.org/TR/2008/REC-xml-20081126/#sec-lang-tag



Rob Cavicchio
rcavi...@opentext.com

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Thomas Schraitle]

Hi,

On 06.02.23 19:48, Tony Graham wrote:

On 06/02/2023 15:23, Thomas Schraitle wrote:
...

No localization exists for "" or "". Using default "en".
Error at xsl:text on line 169 column 19 of functions.xsl:
   XTMM9000  Processing terminated by xsl:message at line 169 in functions.xsl


Do you have any 'xml:lang=""' in your document(s)?


No, not that I'm aware of it. All xml:lang are set correctly. But thanks for
the suggestion.



[...]




--
Gruß/Regards
  Thomas Schraitle


---------
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] DocBook xslTNG prerelease 2.0.7

[Jirka Kosek]

On 07.02.2023 9:53, Norm Tovey-Walsh wrote:

*Blink*. Really? I would not have expected language fixup to do that,
but maybe it does. So xml:lang="" is equivalent to $default-language,
I suppose.


Well, I don't know if this is what XInclude spec says but IIRC there 
were some XInclude processors that did that.


--
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
 Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--


OpenPGP_signature
Description: OpenPGP digital signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

Jirka Kosek  writes:
> Empty @xml:lang can be result of XInclude when included files do not
> explicitly specify @xml:lang.

*Blink*. Really? I would not have expected language fixup to do that,
but maybe it does. So xml:lang="" is equivalent to $default-language,
I suppose.

Be seeing you,
  norm

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

> A proof tells us where to concentrate our doubts.--Anonymous


signature.asc
Description: PGP signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

Tony Graham  writes:
> On 06/02/2023 18:58, Dave Pawson wrote:
>> On Mon, 6 Feb 2023 at 18:48, Tony Graham  wrote:
> ...
>> Which begs the question, where to set the default language, and should
>> it be reported as a bug if not set?
>> [Guess, $gentext-language will default to 'default language' - does
>> that make sense?]
>
> If you look at line 145, $default-language is used if there's no
> $gentext-language and no @xml:lang.  An empty @xml:lang would be used
> ahead of $default-language and would result in those empty values in the
> error message.

There’s a hierarchy:

1. If you specify $gentext-language, that’s used. End of story. You want
   all the generated text to be in Thai even though the book claims to
   be in German, you got it. Why, I don’t know.
2. Otherwise, if you specify a language, that’s used.
3. Otherwise, the $default-language is used.

If there’s a use case for xml:lang="", I don’t know what it is.

Be seeing you,
  norm

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

> There is only one difference between a madman and me. I am not
> mad.--Salvador Dali


signature.asc
Description: PGP signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

> The 'terminate="yes"' on line 168 does rather contradict the message
> that processing will continue with the default language.

Yeah. That seems like a bug. Perhaps I did that when I was trying to
debug and forgot to take it out.

Be seeing you,
  norm

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

> Of all lies, art is the least untrue.--Flaubert


signature.asc
Description: PGP signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Jirka Kosek]

On 06.02.2023 20:07, Tony Graham wrote:

If you look at line 145, $default-language is used if there's no
$gentext-language and no @xml:lang.  An empty @xml:lang would be used
ahead of $default-language and would result in those empty values in the
error message.


Empty @xml:lang can be result of XInclude when included files do not 
explicitly specify @xml:lang.


--
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
 Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--


OpenPGP_signature
Description: OpenPGP digital signature

Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7

[Tony Graham]

On 06/02/2023 18:58, Dave Pawson wrote:

On Mon, 6 Feb 2023 at 18:48, Tony Graham  wrote:


On 06/02/2023 15:23, Thomas Schraitle wrote:
...

No localization exists for "" or "". Using default "en".
Error at xsl:text on line 169 column 19 of functions.xsl:
XTMM9000  Processing terminated by xsl:message at line 169 in
functions.xsl


Do you have any 'xml:lang=""' in your document(s)?

It looks like the function [1] can really only generate 'No localization
exists for "" or "".' if '$gentext-language' is not set (not that I know
how to set it) and there's an 'xml:lang=""' somewhere in your document.

...

Which begs the question, where to set the default language, and should
it be reported as a bug if not set?
[Guess, $gentext-language will default to 'default language' - does
that make sense?]


If you look at line 145, $default-language is used if there's no
$gentext-language and no @xml:lang.  An empty @xml:lang would be used
ahead of $default-language and would result in those empty values in the
error message.

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp


[1] 
https://github.com/docbook/xslTNG/blob/main/src/main/xslt/modules/functions.xsl#L139


-----
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] DocBook xslTNG prerelease 2.0.7

[Dave Pawson]

On Mon, 6 Feb 2023 at 18:48, Tony Graham  wrote:
>
> On 06/02/2023 15:23, Thomas Schraitle wrote:
> ...
> > No localization exists for "" or "". Using default "en".
> > Error at xsl:text on line 169 column 19 of functions.xsl:
> >XTMM9000  Processing terminated by xsl:message at line 169 in
> > functions.xsl
>
> Do you have any 'xml:lang=""' in your document(s)?
>
> It looks like the function [1] can really only generate 'No localization
> exists for "" or "".' if '$gentext-language' is not set (not that I know
> how to set it) and there's an 'xml:lang=""' somewhere in your document.
>
> The 'terminate="yes"' on line 168 does rather contradict the message
> that processing will continue with the default language.

Which begs the question, where to set the default language, and should
it be reported as a bug if not set?
[Guess, $gentext-language will default to 'default language' - does
that make sense?]

HTH
-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-----
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] DocBook xslTNG prerelease 2.0.7

[Tony Graham]

On 06/02/2023 15:23, Thomas Schraitle wrote:
...

No localization exists for "" or "". Using default "en".
Error at xsl:text on line 169 column 19 of functions.xsl:
   XTMM9000  Processing terminated by xsl:message at line 169 in 
functions.xsl


Do you have any 'xml:lang=""' in your document(s)?

It looks like the function [1] can really only generate 'No localization
exists for "" or "".' if '$gentext-language' is not set (not that I know
how to set it) and there's an 'xml:lang=""' somewhere in your document.

The 'terminate="yes"' on line 168 does rather contradict the message
that processing will continue with the default language.

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp


[1] 
https://github.com/docbook/xslTNG/blob/main/src/main/xslt/modules/functions.xsl#L139


---------
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] DocBook xslTNG prerelease 2.0.7

[Thomas Schraitle]

the result HTML is zero bytes. :)

To help debugging, would it make sense to have an option that the HTML could be
still generated? Even if there are some errors?

Although the HTML might be broken, it could give some hints where the XML
source contains some strange structures.

Thanks!

--
Gruß/Regards
  Thomas Schraitle


---------
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] DocBook xslTNG prerelease 2.0.7

[Norm Tovey-Walsh]

Hi folks,

A few weeks ago, I posted a note about the DocBook xslTNG Stylesheets
then current 2.0.2 prerelease. This morning I posted 2.0.7. The big
change is in handling of media:

  https://xsltng.docbook.org/guide/2.0.7/ch-customizing.html#media

Feedback eagerly solicited.

Be seeing you,
  norm

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

> You must not think me necessarily foolish because I am facetious, nor
> will I consider you necessarily wise because you are grave.--Sydney
> Smith


signature.asc
Description: PGP signature

[docbook-apps] LCCN in ePub metadata

[Richard Hamilton]

Has anyone figured out how to represent an LCCN (Library of Congress Control 
Number) in the metadata of an ePub?

It’s easy enough to represent it in DocBook source, using biblioid with 
class=“libraryofcongress”, and to display it on the ePub copyright page, but I 
can’t find any reference on how to code it as metadata in an ePub, and the 
current stylesheets (up to a relatively recent snapshot) don’t handle that 
class.

If anyone knows the correct way to represent this in an ePub, I’d be glad to 
add code to the ePub stylesheets to implement it and do a pull request.

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




-
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] documentation

[Dave Pawson]

Apols to Bob, I thought this may be of use for other projects.

https://rachelandrew.co.uk/archives/2023/01/28/technical-writing-resources/

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] [ANN] Release of XMLmind XSL-FO Converter v6.4

[Hussein Shafie]

Release of XMLmind XSL-FO Converter v6.4: Highlights:

- XMLmind XSL-FO Converter engine: non-standard extension of XSL-FO 
property text-decoration. In addition to the decoration type (underline, 
overline, line-through, etc), it's now possible to specify the color, 
style (solid, double, dotted, dashed, wavy) and thickness of the text 
decoration.


  The syntax used for extended simple properties is identical to the 
syntax of CSS3 property text-decoration. More information in 
"Non-standard extension of XSL-FO property text-decoration", 
http://www.xmlmind.com/foconverter/_distrib/doc/user/implementation.html#text-decoration.


- Updated most software components in XMLmind XSL Utility and XMLmind 
XSL Server (ditac, Saxon, Batik, FOP, etc).


- Official support of Java™ 19 and macOS Ventura (version 13).

More information in http://www.xmlmind.com/foconverter/changes.html



-
What is XMLmind XSL-FO Converter?
-

XMLmind XSL-FO Converter is an XSL-FO processor similar to Apache FOP, 
RenderX XEP or Antenna House XSL Formatter, except that it generates 
RTF, WML, ODT and DOCX file formats rather than PDF.


More importantly, this commercial product comes with a handy desktop 
application called "XMLmind XSL Utility" 
(http://www.xmlmind.com/foconverter/xsl_utility.html) which makes it 
easy converting DITA, DocBook, XHTML and XSL-FO documents to a variety 
of formats (PDF, RTF, WML, ODT, DOCX, HTML, EPUB, Web Help, etc).


XMLmind XSL Utility also makes it easy customizing the deliverables it 
generates (PDF, DOCX, EPUB, Web Help, etc) and this, without modifying 
configuration files by hand and without prior knowledge of XSLT. See 
http://www.xmlmind.com/foconverter/_distrib/xslutil/doc/help/com.xmlmind.xslutil.ConversionEditor.html#customizing_xslt


Home page: http://www.xmlmind.com/foconverter/

-
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] Testing DocBook xslTNG 2.0.2 with a real world example

[Thomas Schraitle]

Hi,

On 20.01.23 09:44, Norm Tovey-Walsh wrote:

This gave me some errors which I'm not able to interpret. For easier reading,
I've uploaded the messages and the XML source code here:


Thank you! I love a test case :-)


I would have provided one, but I'm not yet familiar with XSpec and XSLT 3.0. ;)
All I can for now is to point out some issues. :))



Will report back after I’ve had a chance to investigate.


Great, many thanks!


--
Gruß/Regards
  Thomas Schraitle


-
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] Testing DocBook xslTNG 2.0.2 with a real world example

[Norm Tovey-Walsh]

> This gave me some errors which I'm not able to interpret. For easier reading,
> I've uploaded the messages and the XML source code here:

Thank you! I love a test case :-)

Will report back after I’ve had a chance to investigate.

Be seeing you,
  norm

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

> Society is immoral and immortal; it can 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


signature.asc
Description: PGP signature

[docbook-apps] Testing DocBook xslTNG 2.0.2 with a real world example

[Thomas Schraitle]

Hi,

thanks for releasing 2.0.2 of the DocBook xslTNG stylesheets! \o/

I was curious and wanted to play with it on a real-world example. :)

The example that I've chosen is our administration guides written in DocBook 5.
It has already been successfully published with the DocBook XSLT 1.0
stylesheets. The source code contains 50.000 lines of fine DocBook XML. So it's
quite massive. ;)

For convenience reasons, I've added all in one directory. So I've downloaded
the ZIP archive from GitHub, unpacked it, and created the admin book as a
single DocBook XML file. As the images are referenced without any paths, I've
linked all the PNG and SVG files to this (temporary) directory.

This is how the directory looks like:

  docbook-xslTNG-2.0.2/
  +-- {bin,docker,libs,resources,samples,xslt}/  # all dirs from the project
  +-- tmp/
  |   +-- book-administration.xml  # my guide
  |   +-- *.png
  |   +-- *.svg
  +-- out/   # output should go here

I run it like this:

  $ cd docbook-xslTNG-2.0.2/
  $ python3 bin/docbook -xsl:xslt/docbook.xsl \
 -s:tmp/book-administration.xml \
 -o:out.html

This gave me some errors which I'm not able to interpret. For easier reading,
I've uploaded the messages and the XML source code here:

  https://gist.github.com/tomschr/01bd34acca30b789456ad5e4ee7b3dab

As a summary, I have these issues:

* Some templates seems not be available and I get this messages:

  No titlepage template for: quote
  No localization for keycap/keycap in en, using "MISSING"
  No localization for keycap/keycap in en, using "MISSING"

* I get errors from the TNG stylesheets itself. For example:
XPTY0004  An empty sequence is not allowed as the first argument of
 array:size()
invoked by xsl:iterate at docbook-xslTNG-2.0.2/xslt/modules/objects.xsl#62

  There are similar issues.

It seems, some of the issues are coming from the stylesheets, right? Or is it a
problem in my source code? It's hard to believe as I've validated it against
DocBook 5.2 and it's valid. :)

Maybe I did something wrong. How I can solve the issues above? Would it help to
open some GH issues?

Many thanks and keep up the great work!


--
Gruß/Regards
  Thomas Schraitle

-
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] DocBook xslTNG prerelease 2.0.2

[Norm Tovey-Walsh]

Hi folks,

I’ve been trying to get a new version of the DocBook xslTNG Stylesheets
finished for a few weeks now. The big (and sometimes backwards
incompatible changes) are:

* The system for dealing with generated text has been completely
  rewritten. We’re back to using templates as described in Chapter 4 of
  the updated reference guide. Most of the parameters, variables, and
  functions associated with gentext have been removed. Properties have
  been removed and all template lookups are now done with XPath
  expressions instead ad hoc string matching.

* It’s likely that there are small changes to the way lists-of-titles
  and cross references are formatted by default in some cases.

* Labels for formal objects may be different, but I think these changes
  actually fix previously unreported bugs.

* In some contexts, for example callouts, labels are now used for the
  links instead of titles.

* The parameters for the t:top-nav and t:bottom-nav templates have
  changed. These templates are now always called, even when chunking is
  not being performed. The new $chunk parameter indicates whether or not
  a chunk is being formatted.

* Fixed a bug where orderedlist numeration was not handled correctly in
  cross-references to list items.

* Made another attempt at sorting out how media object URIs are resolved
  in the source (for reading their properties) and formatted in the
  output. If the $mediaobject-input-base-uri is specified, it is always
  used. Documented some subtleties with respect to the
  $chunk-output-base-uri parameter.

* Added support for ISO 690 bibligraphes.

* Fixed bug where authorgroup wasn’t being processed in biblioentry.

* I reworked the way the persistent ToC is generated. You can now have a
  single, external ToC instead of nesting it in every chunk. The way
  navigation works and the CSS have been improved.

* I removed up arrow from $chunk-nav (issue #170). That will be in 2.0.3
  which hasn’t been pushed to Maven yet.

There are probably other changes as well, fixing localization was a
pretty substantial change.

Many customization layers will need to be updated before they’ll
generate the right output. If you’re having trouble, please open up a
bug report and I’ll try to help.

I have pushed 2.0.2 to Maven for everyone’s convenience.

I’ve reworked The Definitive Guide and a couple of other projects to use
the 2.x stylesheets and it seems to be going well. I’d love feedback
from folks who use the localization support.

I expect if there are no new reports, I’ll wrap it up as 2.1.0 in a week
or so and make it the current official version.

Be seeing you,
  norm

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

> Everything is temporary.


signature.asc
Description: PGP signature

Re: [docbook-apps] Bug fix for xslt stylesheets (manpage format)

[Erik Leunissen]

On 1/3/23 18:13, Bob Stayton wrote:
Thanks for this patch.  I've submitted it as a new issue to the Issue Tracker for the DocBook xslt10 
stylesheets on Github.


Thanks for taking care of that (and all other things related to docbook xsl 
b.t.w.).

Erik Leunissen.
--



Bob Stayton

On 12/21/2022 7:16 AM, Erik Leunissen wrote:
Please find attached a patch for the conversion to manpage format. The patch is based on the 
docbook-xsl-1.79.2 stylesheets distribution.


Explanation:

Hunk 1 corrects a missing newline that caused the man program to not recognize 
a new table section.

Hunk 2 prevents that redundant white space, introduced into in an xml source document by the xml 
editor program[*], is copied verbatim into the text of a manpage table cell, thus compromising 
alignment of the text.


 [*] I'm using XMLmind XML Editor 



-
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] Bug fix for xslt stylesheets (manpage format)

[Bob Stayton]

Thanks for this patch.  I've submitted it as a new issue to the Issue 
Tracker for the DocBook xslt10 stylesheets on Github.


Bob Stayton

On 12/21/2022 7:16 AM, Erik Leunissen wrote:
Please find attached a patch for the conversion to manpage format. The 
patch is based on the docbook-xsl-1.79.2 stylesheets distribution.


Explanation:

Hunk 1 corrects a missing newline that caused the man program to not 
recognize a new table section.


Hunk 2 prevents that redundant white space, introduced into in an xml 
source document by the xml editor program[*], is copied verbatim into 
the text of a manpage table cell, thus compromising alignment of the 
text.


 [*] I'm using XMLmind XML Editor 

Re: [docbook-apps] xslTNG regression and maybe other things

[Norm Tovey-Walsh]

> I see that Eric Streit wrote about a regression in xslTNG back in
> December. I’ll investigate that. In the meantime:

Fixed in 1.11.2 published today.

Be seeing you,
  norm

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

> Time makes more converts than reason.--Tom Paine


signature.asc
Description: PGP signature

[docbook-apps] xslTNG regression and maybe other things

[Norm Tovey-Walsh]

Hello world,

I discovered last week that I was no longer subscribed to docbook-apps.
I didn’t do that on purpose (I don’t think I did it at all!).

I see that Eric Streit wrote about a regression in xslTNG back in
December. I’ll investigate that. In the meantime:

1. If you find a bug in the stylesheets, please open a bug report on the
   repo.
2. If you were hoping I’d reply to anything you sent in the last I don’t
   know how long and I didn’t, feel free to send me an email!

Be seeing you,
  norm

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

> Of all the preposterous assumptions of humanity over humanity, nothing
> exceeds most of the criticisms made on the habits of the poor by the
> well-housed, well-warmed, and well-fed.--Herman Melville


signature.asc
Description: PGP signature

[docbook-apps] Re: ISO 690 bibliographies

[Jirka Kosek]

On 31.12.2022 19:54, Norm Tovey-Walsh wrote:

Back in 2012, there was some discussion of ISO 690 bibliography
formatting. Someone named Jana Dvořáková apparently contributed a
document with some proposed markup and the expected results to the
DocBook wiki.

That’s long lost, but I did manage to find an HTML version of that
document in an email attachment from Jirka.

Is Jana reading this list? Does anyone know how to reach them?


Hi Norm,

Jana was my student, I'm putting her on /cc.


I’d like to put the document back on line, or get a pointer to where
they’ve put it online. If it’s possible to get the DocBook source for
that document, that would be nice too.


I'm attaching file that I have found on my machine. It's from 2006, I'm 
not sure if there were some changes since that time that were lost when 
wiki version of doc has been lost.



I’m about halfway through the examples from that document. I plan to
support ISO 690 bibliographies in the DocBook xslTNG stylesheets.

Cool! And Happy New Year.

Jirka



--
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
 Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--





Bibliography according to ISO 690 and ISO 690-2 standards

Jana
Dvořáková




Introduction


Examples are adapted from ISO 690 and ISO 690-2 standards.


Elements marked with * are optional,
+ marks mandatory elements for online documents
and optional for others.




Monographs

Non-serial bibliographic item, i.e. an item either complete in one part or complete
(or intended to be completed) in a finite number of separate parts.



ElementExample

Primary responsibilityLOMINADZE, DG.
TitleCyclotron waves in plasma
*Subordinate responsibilityTranslated by AN. Dellis; edited by SM. Hamberger
Edition1st ed.
*Place of publicationOxford
*PublisherPergamon Press
Year of publication1981
*Extent206 p.
*SeriesInternational series in natural philosophy
*NotesTranslation of: Ciklotronnye volny v plasme
Standard numberISBN 0-08-021680-3




DocBook source code






Output according to ISO 690 standard

LOMINADZE, DG. Cyclotron waves in plasma.
Translated by AN. Dellis; edited by SM. Hamberger.
1st ed.
Oxford: Pergamon Press, 1981.
206 p.
International series in natural philosophy.
Translation of: Ciklotronnye volny v plasme.
ISBN 0-08-021680-3.





Serials

Publication, in any medium, issued in successive parts,
usually having numeric or chronological designations,
and intended to be continued indefinitely.



ElementExample

TitleCommunications equipment manufacturers
ResponsibilityManufacturing and Primary Industries Division, Statistics Canada
EditionPreliminary edition
Issue designation (date and/or n°)1970- 
*Place of publicationOttawa
*PublisherStatistics Canada
Year of publication1971- 
*SeriesAnnual census of manufacturers
*NotesText in English and French
Standard numberISSN 0700-0758




DocBook source code






Output according to ISO 690 standard

Communications equipment manufacturers.
Manufacturing and Primary Industries Division, Statistics Canada.
Preliminary edition.
1970- .
Ottawa: Statistics Canada, 1971- .
Annual census of manufacturers.
Text in English and French.
ISSN 0700-0758.





Parts of monographs


ElementExample

Primary responsibilityPARKER, TJ. and HASWELL, WD.
Title of host documentA text-book of zoology
Edition5th ed.
Numeration of the partvol. 1
*Subordinate responsibilityrevised by WD. Lang
*Place of publicationLondon
*PublisherMacmillan
Year of publication1930
Location within hostSection 12, Phylum Mollusca, p. 663-782




DocBook source code






Output according to ISO 690 standard

PARKER, TJ. and HASWELL, WD.
A text-book of zoology.
5th ed.,
vol. 1.
revised by WD. Lang.
London: Macmillan, 1930.
Section 12, Phylum Mollusca, p. 663-782.





Contributions to monographs

Contribution is independent unit forming part of a document.



ElementExample

for contribution:
Primary responsibilityWRIGLEY, EA.
TitleParish registers and the historian

for host:
Primary responsibilitySTEEL, DJ.
TitleNational index of parish registers
Edition
*Place of publicationLondon
*PublisherSociety of Genealogists
Year of publication1968
Location within hostvol. 1, p. 155-167




DocBook source code






Output according to ISO 690 standard

WRIGLEY, EA.
Parish registers and the historian.
In
STEEL, DJ.
National index of parish registers.
London: Society of Genealogists, 1968,
vol. 1, p. 155-167.





Articles, etc., in serials


ElementExample

Primary responsibilityWEAVER, William
TitleThe collectors: command performances

[docbook-apps] Bug fix for xslt stylesheets (manpage format)

[Erik Leunissen]

L.S.

I'm unsure about the development process of the docbook xslt stylesheets, and whether they are 
actively maintained. In case they are:


Please find attached a patch for the conversion to manpage format. The patch is based on the 
docbook-xsl-1.79.2 stylesheets distribution.


Explanation:

Hunk 1 corrects a missing newline that caused the man program to not recognize 
a new table section.

Hunk 2 prevents that redundant white space, introduced into in an xml source document by the xml 
editor program[*], is copied verbatim into the text of a manpage table cell, thus compromising 
alignment of the text.


 [*] I'm using XMLmind XML Editor


Sincerely,

Erik Leunissen
- tbl.xsl.orig	2018-02-19 22:22:59.0 +0100
+++ tbl.xsl.fix	2022-12-21 10:55:34.0 +0100
@@ -56,7 +56,7 @@
   
   
   
-  .TS
+  .TS
   
 
  H
@@ -216,7 +216,7 @@
 
 
 T{
-
+
 T}
   
 

-
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] RE: [External Email] Re: [docbook-apps] UI strings vs manual strings ?

[Riffel, Patrick]

Hi all,

the issue of keeping UI strings and documentation in sync sounds familiar and 
I'd like to let you know how we've been doing it for last 12 years or so - not 
perfect but robust enough to publish several dozen documents with up to 1300 
pages in two (was four) languages as PDF and webhelp.

The software we are writing documentation for is using dozens of XML files for 
its configuration and user interface. Each UI string comes with an ID that is 
more or less unique, and we can therefore reuse it in our documentation. 
However, almost every configuration file has a slightly different content model 
to the one before and therefore we have to pre-process everything before we can 
actually use it.

In this pre-processing step, a script pulls together all the UI strings from 
all the different configurations into a "normalized" xml file. This step also 
pulls in the translated versions of strings. You end up with a rather big xml 
file ("alltext.xml"), in which you have the ID, the original string and 
translations in one place. If a translation is missing, we add a placeholder 
text.

On the Docbook side, we are using guilabel/guimenu/guimenuitem to tag UI text. 
By our convention, each of these elements must have a @remap attribute with its 
value set to one of the IDs you can find in the software configuration files 
(or rather in that big xml file from the previous step). Referencing the ID is 
the important bit for the automation. For readability, the Technical Writer 
would also use the UI string as content for guilabel/guimenu/guimenuitem. 
However, this isn't strictly necessary as the element's content will be 
replaced at a later stage.

Our publishing process is automated via ant/jenkins. Once all xincludes have 
been resolved, we use some XSLT on the resulting temporary file and replace the 
UI strings with the most recent versions from "alltext.xml". And that's more or 
less it - an ID-based lookup and string replacement.

To assist our Technical Writers, we also provide modified versions of the 
software configuration. This configs can be used to run the software in a way 
that will display the internal ID alongside the UI text. By doing this, the 
Technical Writer is provided with sufficient context to find the right ID to be 
used for @remap. It also helps to avoid confusion where the configuration files 
have several copies of the same UI string but with different ID values.

Since the UI strings are translated separately and keep their original ID, the 
remapping also works when we are publishing in other languages (our primary 
language is German, and we translate into English. This process has been used 
in the past to translate into French, Italian and Russian as well).

A word on the authoring process: We are using oXygen XML and have put together 
some schematron rules that will flag up when a remap attribute is missing or 
when the content of a guilabel is different from the current value in the 
lookup file. This was done as a proof-of-concept and isn't required for 
authoring, but we encourage using it. We are also experimenting with schematron 
quickfixes to replace UI strings where necessary - this also is experimental 
and not a feature we are using all the time, but it comes in handy every now 
and then.

We do most of our translation inhouse (we used OmegaT in the past, but not 
anymore, sorry!). The documentation and the UI strings are translated 
separately (by the same Translator) into two separate translation memories. 
When translating the documentation, all guilabel/guimenu/guimenuitem are set to 
be non-translatable. However, our Translator sees the element content and thus 
has all the context information they need. Once they export their files to the 
target language, the UI strings will still be in German. The German text is 
then replaced via a combination of @lang and @remap when publishing to their 
respective output format.

For those cases where UI text does need to be translated/localized, a Technical 
Writer can set a @translate attribute to "yes" on guilabel elements and 
override the replacement. The TMS will unlock those elemetns and the Translator 
can modify the content of those elements.

I am aware that this process might be problematic with certain languages and/or 
if the source material is not well maintained and probably
for many other reasons, too. We had trouble in the past with UI text that was 
split into several individual strings or when placeholders are
being used. With regards to mnemonics and shortcuts - those are indeed 
annoying. Our specific problem is that the software configuration wasn't 
designed to be translation friendly, and we basically have to strip away things 
before going into translation. I do believe that this problem could be solved 
if we put in some effort in redesigning the configuration files. Screenshots 
also matter and need manual updates when the UI text changes.

Bottom line is: We manage to keep our 

Re: [docbook-apps] how to embed youtube videos using docbook 5.1 / xsltproc?

[Shlomi Fish]

On Fri, 16 Dec 2022 16:15:29 + (UTC)
Alemps Florimond  wrote:

>  Hello
> 
> Just overload the template  with the
> expected html code for the iframe.
> https://www.w3schools.com/html/html5_video.asp might be an alternative to
> iframe.
> 

Thanks, mr./ms. Florimond. i'd like to try  out your leads.

> 
> Regards,Florimond
> Le vendredi 16 décembre 2022 à 16:51:37 UTC+1, Shlomi Fish
>  a écrit : 
>  how to embed youtube videos using docbook 5.1 / xsltproc?
> 
> I want "iframe"s similar to this HTML5 page:
> 
> https://www.shlomifish.org/philosophy/culture/case-for-commercial-fan-fiction/
> 



-- 

Shlomi Fish   https://www.shlomifish.org/
My Favourite FOSS - https://www.shlomifish.org/open-source/favourite/

When Chuck Norris disses your product, it’s not good publicity, even though
you can bet he’ll get the name right.
— https://www.shlomifish.org/humour/bits/facts/Chuck-Norris/

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

Re: [docbook-apps] how to embed youtube videos using docbook 5.1 / xsltproc?

[Alemps Florimond]

 Hello

Just overload the template  with the expected 
html code for the iframe.
https://www.w3schools.com/html/html5_video.asp might be an alternative to 
iframe.


Regards,Florimond
Le vendredi 16 décembre 2022 à 16:51:37 UTC+1, Shlomi Fish 
 a écrit :  
 
 how to embed youtube videos using docbook 5.1 / xsltproc?

I want "iframe"s similar to this HTML5 page:

https://www.shlomifish.org/philosophy/culture/case-for-commercial-fan-fiction/

-- 

Shlomi Fish      https://www.shlomifish.org/
List of Graphics Apps - https://shlom.in/graphics

Real programmers don’t write workarounds. They tell their users to upgrade
their software.
    — https://www.shlomifish.org/humour.html

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

  

Re: [docbook-apps] How to migrate DocBook XSLT 1.0 stylesheets to 3.0?

[Thomas Schraitle]

Hi,

On 15.12.22 21:03, Thomas Schraitle wrote:

[...]


I took the liberty to open a new issue:

  https://github.com/docbook/xslTNG/issues/212

If you have further ideas, suggestions etc. let us know and add it here or in
the above issue.

Many thanks!


--
Gruß/Regards
  Thomas Schraitle


-
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] UI strings vs manual strings ?

[Jean-Christophe Helary]

> On Dec 13, 2022, at 19:28, Tony Graham  wrote:
> 
> What result are you looking for?

I am looking for an authoring process where software UI strings can 
easily be handled in the documentation.

I'm imagining that there would be an editor that uses a UI strings 
"library" as reference and calls its contents when required in the doc 
during the build process.

What would be the best way to achieve that in a DocBook centered process?

> Are you treating one language (say, English) as the main language (which
> has empty elements for value lookups) and the other languages as end
> products (which have all text filled in), where you'd use OmegaT's
> translation memory to keep translations consistent across revisions?

I'm not sure I understand the above question, even though I've been 
using OmegaT almost daily for the past 20 years.

> Or do you want the other languages to be structurally equivalent to the
> main version (apart from inline elements moved around because of
> sentence structure), where elements containing text are turned back into
> empty elements?

I don't understand the second part "where elements containing text are 
turned back into empty elements?".

Jean-Christophe 

> 
> Regards,
> 
> 
> Tony Graham.
> -- 
> Senior Architect
> XML Division
> Antenna House, Inc.
> 
> Skerries, Ireland
> tgra...@antenna.co.jp
> 
> -----
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 

-- 
Jean-Christophe Helary @jchel...@emacs.ch
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/


-----
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] How to migrate DocBook XSLT 1.0 stylesheets to 3.0?

[Thomas Schraitle]

Hi,

the DocBook XSLT 1.0 stylesheets served us very well over the years. However,
as more and more features are implemented in DocBook 5, the more difficult
becomes it to add them into the XSLT 1.0 code base.

As far as I see, the new XSLT 3.0 stylesheets[1] tries to create the foundation
for this. Luckily, Norman provided a very detailed documentation[2] how to use
them. I'm very grateful for this and it's very helpful. Thank you very much!

I played a bit around with them. However, I'm more interested in how to
_migrate_ from the older XSLT 1.0 stylesheets to the new ones. If I'm not
mistaken, there is no such documentation yet, right? I hope this question could
serve as a starting point to collect some ideas and to amend the documentation.

Currently, we use an extensive customization layer of the DocBook XSLT 1.0
stylesheets which support HTML and PDF through XSL-FO. We use xsltproc to
transform them. We even created a tool chain to help us with profiling etc.
This works quite well and we are happy with this.

However, as XSLT 1.0 has some limitations and needs workarounds, I'm searching
for a way if this code base could be migrated somehow. Therefor I'm looking for
some tips and tricks, best practices, or recommendations.

How would you proceed with this? I suppose it isn't easy and needs a complete
rewrite?

Before I start that task, I have some specific questions which hopefully helps
me to understand this better:

1. Compatibility mode in Saxon11?
   As we currently use xsltproc, would it make sense to gradually replace the
   XSLT processor with Saxon 11 and still using the XSLT 1.0 stylesheets?
   Just to get some experiences etc.
   I suppose Saxon 11 has a compatibility mode for XSLT 1.0. However, some
   extension functions and elements in the XSLT 1.0 stylesheets could be
   problematic as they don't exist in Saxon 11, right?

2. Speed?
   When we tried Saxon 6, we measured it is ~3x slower than xsltproc.
   This is probably not a surprise (Java versus C).

   We have quite an extensive DocBook code base. To build all product
   documentation for HTML and PDF takes a long time. If we multiply it by
   a factor N it takes even longer. So that's an important point for us.

   I've read somewhere that the slower start up time is due to the Java
   engine. Once it is started it is more or less comparable with xsltproc.
   Is it correct?

   Can we start Saxon 11 in a kind of "background mode" where it waits
   and listens to some transformation requests? Would that be possible?

3. How to deal with XSL-FO?
   Currently, the xslTNG stylesheets don't support XSL-FO (yet).
   Nowadays it's recommended to use some (print) CSS to create PDF.
   There are commercial offerings for this task, but we are looking
   for an open source solution. Would a browser engine sufficient too?
   Or are there any other tools recommendations?

   The other option would be to implement XSL-FO. However, I think, that
   would be quite a big task, wouldn't it? Is it planned to implement
   it?

   What would you use to provide PDF?

4. Recommendations? Best practices?
   Are there any recommendation to follow, traps to avoid etc.?


Thanks for all your ideas and thoughts! :-)


--- References
[1] https://github.com/docbook/xslTNG
[2] https://xsltng.docbook.org/

--
Gruß/Regards
  Thomas Schraitle

-
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] UI strings vs manual strings ?

[Tony Graham]

What result are you looking for?

Are you treating one language (say, English) as the main language (which
has empty elements for value lookups) and the other languages as end
products (which have all text filled in), where you'd use OmegaT's
translation memory to keep translations consistent across revisions?

Or do you want the other languages to be structurally equivalent to the
main version (apart from inline elements moved around because of
sentence structure), where elements containing text are turned back into
empty elements?

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp

-
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] [ANN] Release of XMLmind XML Editor v10.3

[Hussein Shafie]

Release of XMLmind XML Editor v10.3 (December 12, 2022): Highlights:

- Minor enhancements related to the support of helper applications.

- A couple of bug fixes.

- Updated almost all software components (XMLmind DITA Converter, 
XMLmind XSL-FO Converter, XMLmind Word To XML, Saxon, Apache FOP, etc).


- Official support of Java™ 19 and macOS Ventura (version 13).

More information in http://www.xmlmind.com/xmleditor/changes.html

---
What is XMLmind XML Editor?

Home page: http://www.xmlmind.com/xmleditor/

Personal Edition is free to use by many persons and organizations. Download:

http://www.xmlmind.com/xmleditor/download.shtml

-
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] UI strings vs manual strings ?

[Jean-Christophe Helary]

nkend endterm) is not optimal because the 
link contents/target is not available for inflected modifications required in 
some languages. (And I also happen to be a translation company, so I understand 
those issues quite well, but it was my first time on the DocBook authoring 
side, the last time I wrote the manual it was in HTML.)

As mentioned above in the reply to Tony, the issue with some strings is that 
they must be explicitly available for translation because some languages need 
to modify them (grammatical inflections, etc.)

> I've seen an interesting approach where any guilabel had a dedicated
> attribute storing a termbase ID. While a guilabel value was present, it was
> just informative (for the author, to understand the context). The actual
> value was taken from the termbase during generating outputs.
> 
> So if GUI labels are linked to the same termbase, this system ensures your
> document will never diverge. Moreover, it is ensured also to all translated
> documents. 

I'm not sure I understand how the termbase is linked to the document.

> The hardest step is consolidating such a termbase and establishing processes
> on DEV and DOC sides so both departments use the termbase as a single source
> of truth.

:-)



-- 
Jean-Christophe Helary @jchel...@emacs.ch
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/


-
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] UI strings vs manual strings ?

[Jan Tosovsky]

On 05/12/2022 23:05, Jean-Christophe Helary wrote:
> What's the best way in a DocBook centered process to ensure that the 
> list of terms used in a software UI is (semi-automatically?) taken 
> into account in the DocBook sources that describe that software?

In your document you can use  and other 

Re: [docbook-apps] UI strings vs manual strings ?

[Alemps Florimond]

 Hello,
I would transform the bundle.properties in a document (article, book or section 
whatever)Each line of the file corresponds to somethine like :
My message
One element simpara for one guilabel is useless : it is just to make it 
readable in a DocBook parse.

In the document, you include the message - something like :You should see 
 after clicking 
on the button.
The French, English, German version of the document will take advantage of the 
corresponding translated version of bundle.properties.xml

As far as no id message starts with a number (NC Name for xml:id) you are 
ok.With an XSLT 2.0 processor, it might even be possible to transform the 
bundle.properties in XML.

Regards,Florimond
Le mardi 6 décembre 2022 à 00:05:49 UTC+1, Jean-Christophe Helary 
 a écrit :  
 
 What's the best way in a DocBook centered process to ensure that the list of 
terms used in a software UI is (semi-automatically?) taken into account in the 
DocBook sources that describe that software?

Problem at hand:

- a Java application with ~2k UI strings (not all users facing), in a 
Bundle.properties file
- a ~80K words DocBook manual

It is not trivial to keep track of the whole string set (searches, etc.)

Also, the l10n process takes place on the DocBook sources, not on the HTML 
output, so tricks like  don't work because translators 
don't see the target terms.

I'm left with having to rewrite the strings explicitly and that's a pain, and 
also adds risks of mistakes in translations.

-- 
Jean-Christophe Helary @jchel...@emacs.ch
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/


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