Norman Walsh | 24 May 16:25 2016
Gravatar

Balisage: The Markup Conference

FYI: (Hope to see you there!)

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

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

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

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

If you are interested in open information, reusable documents, and
vendor and application independence, then you need descriptive markup,
and Balisage is the conference you should attend. Balisage brings
together document architects, librarians, archivists, computer
scientists, XML practitioners, XSLT and XQuery programmers, implementers of
(Continue reading)

Bob Stayton | 23 May 16:06 2016
Picon

DocBook Technical Committee Meeting Agenda: 25 May 2016

DocBook Technical Committee Meeting Agenda: 25 May 2016
=============================================================

The DocBook Technical Committee will meet on Wednesday,
25 May 2016 at 2:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
  Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 15 June 2016
4. Review of the agenda.
5. Review of open action items

    a. Norm to review the non-normative XML Schema version of 5.1
       to make sure it has all the latest changes.
(Continue reading)

Thomas Schraitle | 19 May 09:03 2016
Picon

DocBook Transclusion: Allow "prefix" in trans:idfixup?

Hi,

the "DocBook Transclusion" paper[1] defines some attributes
(trans:idfixup, trans:suffix, and trans:linkscope) which are used for
ID fixup in an (x)included XML document.

The trans:idfixup can only have one of the values "none", "suffix", or
"auto" (see B.5 "Manually assigned suffix"[2] for a more exhaustive
example).

That's all nice and dandy. ;) However, the keyword of "suffix" place the
value of trans:suffix *after*. For example:

  <xi:include href="x.xml" 
              trans:idfixup="suffix"
              trans:suffix="_bar_"/>

With the above trans attributes, a former ID "foo" is rewritten as
"foo_bar_". However, I would like to get the opposite ("_bar_foo").

I guess there is no solution with the current spec, right?

Can we extend the spec to allow the value "prefix" in trans:suffix?

-------
[1] http://docbook.org/docs/transclusion/
[2] http://docbook.org/docs/transclusion/#ex.9

--

-- 
Gruß/Regards,
(Continue reading)

Bob Stayton | 16 May 19:16 2016
Picon

DocBook Technical Committee Meeting Agenda: 18 May 2016

DocBook Technical Committee Meeting Agenda: 18 May 2016
=============================================================

The DocBook Technical Committee will meet on Wednesday,
18 May 2016 at 2:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
  Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 15 June 2016
4. Review of the agenda.
5. Review of open action items

    a. Norm to review the non-normative XML Schema version of 5.1
       to make sure it has all the latest changes.
(Continue reading)

aceone | 10 May 15:46 2016
Picon

Fw: new message

Hello!

 

You have a new message, please read http://www.fuarkatalog.com/chain.php

 

aceone <at> mail.ru

Imsieke, Gerrit, le-tex | 8 May 21:52 2016
Picon
Gravatar

et al. in biblioentry

It has been asked before [1,2], but I haven’t seen a useful 
recommendation yet for capturing “more authors” in a structured 
bibliographic entry, that is, an entry that does not permit untagged 
prose within.

I am tasked with marking up the following reference in DocBook 5.0:

[9] Tim Berners-Lee et al. Uniform Resource Identifier (URI): Generic 
Syntax. The Internet Society. https://www.ietf.org/rfc/rfc3986.txt

What I have so far:

<biblioentry xml:id="RFC3986" xreflabel="[9]">
   <authorgroup>
     <author>
       <personname>
         <firstname>Tim</firstname>
         <surname>Berners-Lee</surname>
       </personname>
     </author>
   </authorgroup>
   <title>Uniform Resource Identifier (URI): Generic Syntax</title>
   <publishername>The Internet Society</publishername>
   <biblioid class="uri">https://www.ietf.org/rfc/rfc3986.txt</biblioid>
</biblioentry>

What is missing in the markup: “et al.”.

Let’s assume that I don’t have a complete list of authors and I can’t 
find it out. Or that I’m unwilling to look them up and code them 
manually. Or that I’m an automatic converter that is not smart enough to 
look them up at the given URI. Or that there are just too many authors 
to type them all.

I can’t imagine that DocBook does not have an element like JATS’s etal [3]

[1] http://markmail.org/message/owvosoqcjxl6xzbd
[2] http://markmail.org/message/u3ij3ble7bmxz35c
[3] http://jats.nlm.nih.gov/archiving/tag-library/1.1/element/etal.html

Any recommendations? Am I missing something obvious?

Gerrit

--

-- 
Gerrit Imsieke
Geschäftsführer / Managing Director
le-tex publishing services GmbH
Weissenfelser Str. 84, 04229 Leipzig, Germany
Phone +49 341 355356 110, Fax +49 341 355356 510
gerrit.imsieke <at> le-tex.de, http://www.le-tex.de

Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930

Geschäftsführer: Gerrit Imsieke, Svea Jelonek,
Thomas Schmidt, Dr. Reinhard Vöckler
Thomas Schraitle | 4 May 16:51 2016
Picon

Transclusion and Inherited Suffixes?

Hi,

the DocBook Transclusion draft[1] defines three attributes:
trans:suffix, trans:linkscope, and trans:idfixup.

According to the spec, trans:suffix is definied as:

  suffix

    * Defines a value to be appended to all ID values on the element
      (elements and attributes whose values should be treated as IDs
      are listed in the ID-list property)

    * Default is an empty string

    * Inherited

    * Can be changed by the trans:idfixup and trans:suffix attributes

How does the "inherited" feature is supposed to work? Does anybody have
a short example?

Thanks!

-----
[1] http://docbook.org/docs/transclusion

--

-- 
Gruß/Regards,
    Thomas Schraitle
Thomas Schraitle | 28 Apr 10:15 2016
Picon

Add "danger" to the list of possible admonitions?

Hi,

a DocBook writer asked me why there is no "danger" element in DocBook.

Currently, we have tip, note, important, warning, and caution as
admonition elements. The list is sorted from lowest to highest
"severity".

However, for writers who want to give a warning about deadly
consequences, caution seems to me a bit "tame". ;)

Although I'm a bit hesitant to add new elements to the DocBook schema,
maybe we should consider that. The element danger would also fit better
to the ANSI standard (I think it was Z535, right?).

What do you think?

--

-- 
Gruß/Regards,
    Thomas Schraitle
Hussein Shafie | 22 Apr 17:22 2016

Release of XMLmind XSL-FO Converter v5.4.1

Release of XMLmind XSL-FO Converter v5.4.1.

Highlights:

- XMLmind XSL Utility and XMLmind XSL Server: updated several software 
components Apache FOP 2.1, DocBook XSL stylesheets 1.79.1, XMLmind DITA 
Converter v2.6, etc.

   Latest version of XMLmind DITA Converter adds partial DITA 1.3 
support to XMLmind XSL Utility and XMLmind XSL Server. Full DITA 1.3 
support is planned for year 2016. More information in "About DITA 
support in XMLmind DITA Converter" 
(http://www.xmlmind.com/ditac/_distrib/doc/manual/dita_support.html).

- XMLmind XSL-FO Converter engine: better support of East Asian (CJK) 
fonts. See "Special support for East Asian fonts" 
(http://www.xmlmind.com/foconverter/_distrib/doc/user/implementation.html#east_asian_fonts).

Download Evaluation Edition: 
http://www.xmlmind.com/foconverter/downloadeval.shtml

---------------------------------
What is XMLmind XSL-FO Converter?
---------------------------------

XMLmind XSL-FO Converter (http://www.xmlmind.com/foconverter/) 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 DocBook documents to RTF, WML, ODT, DOCX (and PDF thanks 
to Apache FOP).

XMLmind XSL Utility also makes it easy customizing the output of the 
DocBook XSL stylesheets 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
Bob Stayton | 18 Apr 23:34 2016
Picon

DocBook Technical Committee Meeting Agenda: 20 April 2016

DocBook Technical Committee Meeting Agenda: 20 April 2016
=============================================================

The DocBook Technical Committee will meet on Wednesday,
20 April 2016 at 2:00pm ET for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
  Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 18 May 2016
4. Review of the agenda.
5. Review of open action items

    a. Norm to review the non-normative XML Schema version of 5.1
       to make sure it has all the latest changes.

    b.  Everyone to beat the bushes for SoUs.

    c.  Norm to complete his XInclude implementation.

6.  Publisher's and eLearning subcommittee reports

7.  XInclude 1.1 status.

8.  DocBook 5.1 release

9.  Review of Requests for Enhancement

     To browse a specific RFE, enter the URL (on one line):

       https://sourceforge.net/p/docbook/rfes/300/

     RFEs to revisit for 6.0

     247   1907003  biblioid content model too broad

    RFEs under discussion

    Ticket  Tracker
     260   2820947  Ability to transclude text
     273   3035565  Allow sections at any level
     291   3491860  license tag  (hold for 5.2)
     306            Allow Block Elements inside abstract

     Github Issues
     6              Add buildtarget element
     7              Allow revnumber inline.

  No new RFEs

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Hussein Shafie | 11 Apr 10:49 2016

[ANN] Release of XMLmind XML Editor v6.7

Release of XMLmind XML Editor v6.7

Highlights:

- Enhanced "DocBook v5.1 configuration (Release Candidate)" add-on.

- Improved XInclude 1.1 support in DocBook v5 and v5.1 configurations.

- Partial DITA 1.3 support. Full DITA 1.3 support is planned for year 2016.

- Drag&drop of document tabs and tool tabs.

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

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

Gmane