On 3/5/24 09:55, Paul Knight wrote:
Hi Norm and all,
It looks like this forwarded message didn't go to the "docbook" list,
but only to the "docbook-tc" list. (That was a non-standard naming of
lists dating back to.. the dawn of DocBook - even before my time with
OAS
Hi Norm and all,
It looks like this forwarded message didn't go to the "docbook" list, but
only to the "docbook-tc" list. (That was a non-standard naming of lists
dating back to.. the dawn of DocBook - even before my time with OASIS!)
So yes, this email list will b
On 05/03/2024 10:28, Norm Tovey-Walsh wrote:
[...]
As part of the ongoing OASIS Open migration from Kavi to Higher Logic
Thrive, the OASIS managed mailing lists will become unavailable for
sending new mail starting sometime in March, 2024. Members can login
at https://groups.oasis-open.org/commun
Apparently, yes. Thanks to those who replied to say they received it.
Apparently, only for the time being, however. Shortly after sending the
message, I also received this:
As part of the ongoing OASIS Open migration from Kavi to Higher Logic Thrive,
the OASIS managed mailing lists will becom
: +33 (0)9 57 80 80 37, www.xmlmind.com
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Hello,
OASIS have rolled out some new software for TC management. I’m just wondering
if the mailing lists still work.
Be seeing you,
norm
--
Norm Tovey-Walsh
https://norm.tovey-walsh.com/
> Some people tell you
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 b
OASIS Members and other interested parties,
OASIS is pleased to announce the publication of its newest OASIS Standard,
approved by the members on 06 February 2024:
The DocBook Schema Version 5.2
OASIS Standard
06 February 2024
Overview:
Almost all computer hardware and software developed
be a and
(which sort of acts already as a form of a title).
--
Gruß/Regards
Thomas Schraitle
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
> Richard Hamilton writes:
> > Currently, the xsl stylesheets support two different display options
> > for variablelist: block and table. Maybe tabs should be a third
> > option.
>
> That’s an interesting idea.
Indeed. Abusing variablelist just a little bit was quite straightforward.
https://nw
Richard Hamilton writes:
> Currently, the xsl stylesheets support two different display options
> for variablelist: block and table. Maybe tabs should be a third
> option.
That’s an interesting idea.
Be seeing you,
g, I guess.
>
> I wonder, he asks with trepidation, if listitems should be allowed to
> have titles?
>
> For the record, working out some proper markup for this seems entirely
> within the scope of DocBook.
>
>Be seeing you,
>
nder, he asks with trepidation, if listitems should be allowed to
have titles?
For the record, working out some proper markup for this seems entirely
within the scope of DocBook.
Be seeing you,
norm
--
Norm T
On 2/5/24 06:31, Norm Tovey-Walsh wrote:
Thomas Schraitle writes:
Not sure if this is the "right" way to do that in DocBook, but I face some
questions:
1. What if I don't need the formalgroup title?
I could use , but that's not the same. Perhaps this goes into
Dave Pawson writes:
> Is this made clear in TDG?
> https://tdg.docbook.org/tdg/5.2/formalgroup No?
Dunno. Will check when I have a moment:
https://github.com/docbook/defguide/issues/110
Be seeing you,
(db.group.paramdef) — A group of parametersV5.1
:-)
--
Gruß/Regards
Thomas Schraitle
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
So we ended up with formalgroup: a group of “formal” objects.
Is this made clear in TDG?
https://tdg.docbook.org/tdg/5.2/formalgroup No?
IMHO that might help (general use of 'formal' in db).
History has its place etc.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
when it
> makes sense. Or when it's not. However, this may not be feasible and perhaps
> too specific for a reference.
Yes. I hadn’t noticed that TDG doesn’t have an example for it. That’s an
oversight: https://github.com/docbook/defguide/issues/109
> After thinking about it... maybe an
plicated.
I could certainly imagine use cases for a , but as you said, it would be a
nightmare. :)
Thanks for the discussion and ideas!
--
Gruß/Regards
Thomas Schraitle
-----
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
> From Norms comments, " ## A group of formal objects, for example subfigures"
> seems a bit off (my view), rather than 'formal objects' (I've a job
> relating to that),
> how about 'related' or 'closely related' then figures / subfigures
&g
On Mon, 5 Feb 2024 at 12:02, Thomas Schraitle wrote:
>
> Hi DocBook users,
>
> DocBook 5.2 contains the element [1] which has this content
> model:
>
>#
>db.formalgroup =
> ## A group of formal objects, for example subfigures
Thomas Schraitle writes:
> Not sure if this is the "right" way to do that in DocBook, but I face some
> questions:
>
> 1. What if I don't need the formalgroup title?
>I could use , but that's not the same. Perhaps this goes into
>the direction of a
Hi DocBook users,
DocBook 5.2 contains the element [1] which has this content model:
#
db.formalgroup =
## A group of formal objects, for example subfigures
element formalgroup {
db.formalgroup.attlist,
db.formalgroup.info,
(db.figure+ | db.table+ | db.example
"John L. Clark" writes:
> It seems that this is an innovation that happened between DocBook 5.1
> and DocBook 5.2, and I am curious to read the discussion around this
> development. Does anyone know where I can read about the work that the
> TC did in coming up with this
I've noticed in The Definitive Guide (and in the schema) for DocBook
5.2 that this version allows "[a]ny attribute in any other explicit
namespace" on any element[0, 1]. I'm excited about this development,
as I think it will be good for expressive extensibility that still
mai
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
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 sign
forms.
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 e
Hi,
Since DocBook 5.1, we can write topic oriented documentation with assemblies.
We use it for some time now in our Smart Docs approach at
https://github.com/SUSE/doc-modular and it works for us.
I'm wondering now about those "effectivity attributes"[1] like os, arch, etc.
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 Techn
On 21/10/2023 22:09, Jirka Kosek wrote:
On 15.09.2023 17:44, Peter Flynn wrote:
In the absence of anything specific, I am temporarily using
docbook
[...]
Alternative to using element is to use
@f...@mastodon.org
Thanks very much. I'm already using it for local usernames,
On 15.09.2023 17:44, Peter Flynn wrote:
In the absence of anything specific, I am temporarily using
docbook
without the "at" sign, and keeping the platform in the role attribute.
Is it worth looking at adding Yet Another Element Type (eg
) with a controlled vocabulary for a
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 i
I will have a requirement to identify the social media "names" of
contributors, eg @f...@mastodon.org or @b...@twitter.com (or perhaps @X)
and others (FaceBook, BlueSky, ad infinitum or perhaps ad nauseam).
In the absence of anything specific, I am temporarily using
docbook
w
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
OASIS Members and other interested parties,
OASIS is pleased to announce that The DocBook Schema Version 5.2 from the
OASIS DocBook TC [1] has been approved as an OASIS Committee Specification.
Almost all computer hardware and software developed around the world needs
some documentation. For the
r):
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-unsubscr...@lists.oasis-open.org
For additiona
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
r):
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-unsubscr...@lists.oasis-open.org
For additiona
The comment period for DocBook version 5.2 Committee Draft Specification
has closed, and there were no comments. We will now proceed to submit
this version as a Committee Specification.
Bob Stayton
, 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
iliar 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-unsubscr...@l
Michael Urban writes:
> What Unicode construct has the best semantics for representing an
One approach is to use “inlinemediaobject” which exists largely for this
purpose. Anywhere you can write text that should be rendered, you can
also insert an inlinemediaobject and use a graphic for the glyph
esentation layer can understand?
HTH
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
---------
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
place the entity by additional markup, if need be.
Klaus
-----
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
7;
> in some way. So, it's just a matter of my curiosity here.
>
> ---------
> To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-h...@li
x27;s inconsequential, since I can do whatever I please--this document
will not be exported to anyone, after all--but I'd like to get it 'right'
in some way. So, it's just a matter of my curiosity here.
-
To unsubscribe,
lines
in the declaration of the entire document. Could you please advice me
how to command docbook to produce the HTML I need i.e. the pure class="programlisting highlight-shell notranslate">? Or maybe there's
another way of marking a programlisting in docbook non-translatable?
> I need that the result should look like the following to turn on
> syntax highlighting and more importantly to prevent automatic
> translation of meaningful strings in the listing (say comments) from
> happening:
>
>
> some program lines
>
Depending on which stylesheets you’re using, you may b
anslate">
some program lines
I don't think this xmlns is required and I'm not even sure it is valid
to place xmlns somewhere other than inside a root element much earlier
in the declaration of the entire document. Could you please advice me
how to command docbook to produce th
?
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
Hello
In https://tdg.docbook.org/tdg/5.1/_emphasis.html , element emphasis can be a
child of element otheradrr
In https://tdg.docbook.org/tdg/5.1/otheraddr.html , element emphasis is not
mentionned as a potential child of otheraddress (while mentionned in
"Ubiquitous inlines")
Document is also
pull request that takes into account the xml:lang attribute:
https://github.com/docbook/xslt10-stylesheets/pull/255
The element is not appropriate because its intended to alter the
behavior of the assembly transformation, not insert additional content. So the
answer to question #1 is that xml
specified in the assembly. Attributes
like role and os should reside in the resource XML file, it seems to
me. Defining those on the fly at assembly time is not a use case I can
imagine.
That said, the DocBook TC could not imagine all the ways that people
might use assemblies. The assembly
Hi,
currently I'm trying to inject language information from a element,
but it doesn't work as expected. Either I'm doing something completely wrong or
this is a bug.
Let's assume I have an assembly structure like this:
http://docbook.org/ns/docbook";
xmlns
>> Thank you, everyone, but the whole thing is predicated on a
>> misunderstanding.
>
> So forget it? Just one media as previously?
Yep. I’m going to fudge a little and let a role of ‘poster’ select the
video’s poster attribute but I’m not going to offer to implement image
fallback for videos in J
one, but the whole thing is predicated on a
> misunderstanding.
So forget it? Just one media as previously?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.
> In other words, I want a license to cheat and say that I can render that
> example above in HTML5 as a video element containing three sources, two
> videos and an image. What say you?
Thank you, everyone, but the whole thing is predicated on a
misunderstanding. I was sure that HTML5 allowed
> rendering system to be the transformation from DocBook to HTML5 *and* the
> browser rendering of that HTML5, then your use case does not seem to violate
> the description because the consumer of the content sees only one version,
> right?
Relies on an odd (rare?) circumstance, de
ng more than one of those to the
> end user would be redundant and annoying. If you consider the whole
> rendering system to be the transformation from DocBook to HTML5 *and* the
> browser rendering of that HTML5, then your use case does not seem to violate
> the description bec
It seems ok to me. The idea of a mediaobject is to contain markup for
one or more versions of the same content. Presenting more than one of
those to the end user would be redundant and annoying. If you consider
the whole rendering system to be the transformation from DocBook to
HTML5 *and
On 05/04/2023 21:46, Thibaut Cuvelier wrote:
On Wed, 5 Apr 2023 at 22:32, Peter Flynn wrote:
On 05/04/2023 17:27, Norm Tovey-Walsh wrote:
The description of mediaobject states:
This element contains a set of alternative “media objects.”
Exactly one object will be selected and rendered. … U
On Wed, 5 Apr 2023 at 22:32, Peter Flynn wrote:
> On 05/04/2023 17:27, Norm Tovey-Walsh wrote:
> > The description of mediaobject states:
> >
> >This element contains a set of alternative “media objects.” Exactly
> >one object will be selected and rendered. … Under no circumstances
> >
On 05/04/2023 17:27, Norm Tovey-Walsh wrote:
The description of mediaobject states:
This element contains a set of alternative “media objects.” Exactly
one object will be selected and rendered. … Under no circumstances
should more than one object in a mediaobject be used or presented at
L and DocBook
content models and semantics.
Jirka
--
--
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
--
Professiona
Hello world,
The description of mediaobject states:
This element contains a set of alternative “media objects.” Exactly
one object will be selected and rendered. … Under no circumstances
should more than one object in a mediaobject be used or presented at
the same time.
Bearing in mind t
OASIS members and other interested parties,
OASIS and the OASIS DocBook TC are pleased to announce that The DocBook
Schema Version 5.2 is now available for public review and comment.
This update continues the evolution of the DocBook XML schema.
The documents and related files are available
?
--
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
On 02/03/2023 08:18, Paul Hoadley wrote:
Hello,
I want to mark up some DocBook articles that will be "dependent on"
resources such as legislation. [...]
>
At the article level, I would presumably use a bibliography—correct?
For a formal reference in the text, yes; then use
Hello,
I want to mark up some DocBook articles that will be "dependent on" resources
such as legislation. As an example, say I have a document whose content is
based in part on Australia's "Spam Act (2003)"—perhaps 2 paragraphs in a 10
paragraph article have someth
Hi folks,
DocBook 5.2CR5 fixes a surprisingly long-standing bug[1] where the
cols attribute on entrytbl was not a required attribute.
Be seeing you,
norm
[1] https://github.com/docbook/docbook/issues/247
? Or are the stylesheets in
> the wrong here?
Looks like a bug to me. It’s not optional in DocBook 4.5, so I think
this is just a previously unnoticed error. Thank you for reporting it!
https://github.com/docbook/docbook/issues/247
to relevant docs.
Blaz
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
han 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, W
> If I understand it correctly, validation is a two step process: first validate
> it with the RNG schema and then validate it against the SCH schema.
> Correct?
That’s the order I usually do it in.
Be seeing you,
n
Hi,
thanks Norm!
On 18.01.23 15:15, Norm Tovey-Walsh wrote:
What do I need to do to enable the embedded Schematron rules in the DocBook RNG
schema with Jing? Or do you use a separate tool for this?
There are now Schematron rules in DocBook that require XPath 2.0 so I
doubt the existing Jing
> What do I need to do to enable the embedded Schematron rules in the DocBook
> RNG
> schema with Jing? Or do you use a separate tool for this?
There are now Schematron rules in DocBook that require XPath 2.0 so I
doubt the existing Jing validator will work. Better to do the
va
Hi,
for validation with DocBook RNG, I use Jing version 20220510. This works quite
well. However, it seems the embedded Schematron rules aren't taken into account.
For example, let's consider this structure:
http://docbook.org/ns/docbook";
xmlns:xlink="http://w
Hi,
I've used Paligo while working for my current and past two companies. If you
search the https://lists.oasis-open.org/archives/docbook-apps/ distribution
list, you'll see that Paligo has been around for a while.
To learn more about their DocBook implementation, see their he
DocBook
and Assembly schemas so that they were compatible with XInclude 1.1.
(And also fixed some inconsistencies in the definitions.)
4. We agreed to fix some minor editorial issues in the documentation.
I’m pleased to report that I’ve applied these changes and published
DocBook 5.2CR4. This will
Hi all,
yes Calenco is proudly DocBook based. After actively using and
contributing to DocBook we developed Calenco with my co-founder Fabian
Mandelbaum.
Aside the CCMS perse, our company NeoDoc created a Web Based "WYSIWYM"
XML editor for DocBook as well as a PDF Studio which
Paligo is docbook-based, but specialized and presented in such a way that one
could easily confuse it with a DITA CCMS. It appears very topic-based, with a
lot of support for reuse, conditionalization, etc.
From: Jean-Christophe Helary
Sent: Wednesday, December
Palingo uses WordPress for their site and Calenco refers to DocBook in their
HTML...
> On Dec 14, 2022, at 19:53, Eric Streit wrote:
>
> you have this too:
>
> https://www.calenco.com/en/index.html
>
> It's a French company; they used to work with docbook;
>
&
you have this too:
https://www.calenco.com/en/index.html
It's a French company; they used to work with docbook;
Eric
Le 14/12/2022 à 11:46, Norm Tovey-Walsh a écrit :
Hi,
Does anyone know anything about Paligo (paligo.net)? I was asked about
it a few days ago, and I’d never heard of
Hi,
Does anyone know anything about Paligo (paligo.net)? I was asked about
it a few days ago, and I’d never heard of it. A quick browse around
their website makes me think it’s a DocBook-powered CMS, which is kind
of cool.
Be seeing you
organizations. Download:
http://www.xmlmind.com/xmleditor/download.shtml
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Hi Norm,
On 09.12.22 08:48, Norm Tovey-Walsh wrote:
Thomas Schraitle writes:
However, when you search for set-xml-id in DocBook 5.2CR3 it's
missing. This attribute isn't available in docbookxi.rn{c,g} at all.
Is this an omission?
Yep.
With the current implementation, the above
Thomas Schraitle writes:
> However, when you search for set-xml-id in DocBook 5.2CR3 it's
> missing. This attribute isn't available in docbookxi.rn{c,g} at all.
> Is this an omission?
Yep.
> With the current implementation, the above mentioned example wouldn't be
&
Hi,
On 08.12.22 21:44, Thomas Schraitle wrote:
[...]
However, when you search for set-xml-id in DocBook 5.2CR3 it's missing. This
attribute isn't available in docbookxi.rn{c,g} at all. Is this an omission?
[...]
I've opened an issue in the DocBook issue tracker on G
ductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
-----
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Hi,
just read Jirka's "DocBook Transclusion"[1] document. In Appendix A. "Using
XInclude 1.1 features for your content" there is Example A.3 "Using set-xml-id
to remove the top-level ID during transclusion".
The set-xml-id attribute is mentioned in the XInc
The only two components that stand out as possible problems are:
> - libxml2 2-2.7.7 ("libxml2-2.7.7")
> http://xmlsoft.org
> - Saxon 6-5-5 ("saxon")
> https://sourceforge.net/projects/saxon/files/saxon6/
That Saxon release is really, really old. It’s so old that it may, in
fact, predate the
> On Dec 8, 2022, at 0:42, Norm Tovey-Walsh wrote:
>
>> https://github.com/omegat-org/omegat/tree/master/doc_src/en
>
> Okay. I grabbed the repo and put DocBook 4.5 in the place it was
> expected. A validating parse fails because of the xi:include elements,
> but do
> https://github.com/omegat-org/omegat/tree/master/doc_src/en
Okay. I grabbed the repo and put DocBook 4.5 in the place it was
expected. A validating parse fails because of the xi:include elements,
but doesn’t complain about any entities. A well-formed parse has no
problems.
If I use Saxon
---------
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
> That is the beginning of OmegaTUsersManual_xinclude full.xml.
>
> line 7 in the error message refers to:
>
>OmegaT &vernb; - User
>Guide
Are you sure there’s a declaration for “vernb” in manualvariables.mod?
Be seeing you,
t; Be indiscrete. Do it continuously.
--
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-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
> When I run the build (ant) I get this error message:
>
> include:
> [exec] en/OmegaTUsersManual_xinclude full.xml:7: parser error : Entity
> 'vernb' not defined
> [exec] OmegaT &vernb; - User
> Guide
> [exec] ^
XIncluded do
(not sure whether the best list to post this is docbook@ or docbook-app@)
I’m using this code to reference an entity:
%manualvariables;]>
OmegaT &vernb; - User Guide
@timestamp@
This document is the official user guide to OmegaT, the free
C
On 12/1/22 12:30 AM, Thomas Schraitle wrote:
>
> You are right, the _DTD_ cannot define a start element and as such every root
> element would be possible. But you miss the point. :-)
>
> The DTD is _not_ not used for DocBook 5 (with the exception of 5.0, but
> that'
1 - 100 of 7817 matches
Mail list logo
