This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[ANNOUNCEMENT] [1.7] Updated: asciidoc-8.4.2-1

Hash: SHA1

A new version of the asciidoc package, asciidoc 8.4.2-1, is now available
for download for those testing cygwin 1.7.  I have left asciidoc 8.3.5-1
as previous for cygwin 1.7 and current for cygwin 1.5.

This is a new upstream release; upstream changes are listed below.  See
also the package documentation in /usr/share/doc/asciidoc/.

AsciiDoc is a text document format for writing short documents, articles,
books and UNIX man pages. AsciiDoc files can be translated to HTML and
DocBook markups using the asciidoc(1) command. AsciiDoc is highly
configurable: both the AsciiDoc source file syntax and the backend output
markups (which can be almost any type of SGML/XML markup) can be
customized and extended by the user.

To update your installation, click on the "Install Cygwin now" link on the web page.  This downloads setup.exe to your system.
Save it and run setup, answer the questions and pick up 'asciidoc' from
the 'Devel' category.

Note that downloads from (aka aren't
allowed due to bandwidth limitations.  This means that you will need to
find a mirror which has this update, please choose the one nearest to you:

If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.

- --
Eric Blake
volunteer cygwin asciidoc maintainer

To unsubscribe to the cygwin-announce mailing list, look at the
"List-Unsubscribe: " tag in the email header of this message.  Send email
to the address specified there.  It will be in the format:

If you need more information on unsubscribing, start reading here:

Please read *all* of the information on unsubscribing that is available
starting at this URL.
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at
Comment: Using GnuPG with Mozilla -

1. Version 8.4.2 (2009-03-19)

   Additions and changes
     * Added [1]testasciidoc, a tool to verify AsciiDoc conformance.
     * A warning is issued if nested inline passthroughs are encountered.
     * asciidocapi: setting an attribute value to None will undefine
       (delete) the attribute (this in addition to the name! attribute
       name format that the asciidoc(1) command uses).

2. Version 8.4.1 (2009-03-10)

   Additions and changes
     * AsciiDoc now has a [2]Python API. The following minimal example
       compiles mydoc.txt to mydoc.html:

       from asciidocapi import AsciiDocAPI
       asciidoc = AsciiDocAPI()

     * Backtick quoting for monospaced text is now implemented as an
       inline literal passthrough. This makes more sense since monospace
       text is usually intended to be rendered literally. See
       [3]Regression issues below for the impact this may have on existing
       documents. Here are some examples that would previously have had to
       be escaped:
  The `++i` and `++j` auto-increments.
  Paths `~/.vim` and `~/docs`.
  The `__init__` method.
  The `{id}` attribute.
     * Added --doctest option to asciidoc(1) command.
     * Added an optional second argument to BlockId element, this sets the
       {reftext} attribute which in turn is used to set the xreflabel
       attribute in DocBook elements.
     * Added lists to --help syntax summary.
     * {infile} and {indir} attributes reflect the current input file
       (previously always referred to the root document).
     * {docfile} (new) and {docdir} (previously deprecated) attributes
       refer to the root document specified on the asciidoc(1)
     * Vim syntax highlighter improvements.
     * Syntax summary command (asciidoc -h syntax) additions.
     * Admonition icons now have transparent backgrounds.
     * Changed yellow W3C badges to blue ones in page footers.

   Bug fixes
     * Dropped asciidoc(1) broken undocumented --profile option.
     * Em dash replacement now recognized at start of block.

  2.1. Regression issues

   Replacing backtick quoting with the inline literal passthrough raises
   two regression scenarios for existing documents:
    1. You have escaped the expansion of enclosed inline elements, for
       example: \{id}. You would need to delete the backslashes: {id} (if
       you don't the backslashes will be printed). Mostly it's just a case
       of interactively finding and replacing of all occurrences of `\.
    2. There are enclosed inline elements, for example: some *bold*
       monospaced. You would need to switch to plus character monospace
       quoting: +some *bold* monospaced+ (if you don't the enclosed
       elements won't be expanded).

   If your existing documents include these cases and you don't want to
   upgrade then use the -a no-inline-literal command-line option,
   alternatively put this in ~/.asciidoc/asciidoc.conf:
Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]