[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[help-texinfo] IXIN 1.4 available

From: Thien-Thi Nguyen
Subject: [help-texinfo] IXIN 1.4 available
Date: Sat, 22 Dec 2012 20:00:14 +0100

release notes:

  Big news is the spec moved from README to spec/ixin.texi (w/ logo!);
  please consider sending suggested changes as a diff against that.


README excerpts:

  IXIN is an EXPERIMENTAL distribution of EXPERIMENTAL code and
  some pre-built IXIN files.  IXIN stands for "indexed texinfo".

  All code is under GPLv3+.  All (.xml) docs are under GFDL.


  It defines a documentation file format and provides two simple
  tools to write and read, respectively, files in that format.

NEWS excerpt:

  - 1.4 | 2012-12-22

    - retrieve reads ‘coding’, as well

        Previously, this was ignored.  Now it is read and displayed
        (but otherwise still ignored, thereafter :-D).

    - specification moved from README into its own document

        Sometimes it's impossible to resist the urge to bloviate...
        Relatedly, you can "make check" there, too.  See subdir spec/.

        Probably, over time, more of README will follow.

        The spec document includes a new section "Terminology", not in
        the original README, for general terms.  It also doesn't mention
        anymore the "input SXML", as mkixin design/implementation has
        nothing to do w/ the file format proper.  On the other hand,
        "vetting gaps" (where mkixin is lacking) are now footnoted.

    - META ‘xid’ includes LANG

        Derived from address@hidden, this is either a symbol, such
        as ‘en’ or a list of two symbols, such as ‘(en US)’, which also
        happens to be the default value if unspecified.

    - automagic processing specified for three old-style txi* vars

        These address@hidden/@clear VAR’ are converted to address@hidden 

        txicodequoteundirected     codequoteundirected
        txicodequotebacktick       codequotebacktick
        txideftypefnnl             deftypefnnewline

        For example, see d/serveez.ixin META.

    - new table in SETTINGS

        This used to be README "groupings", refined a bit.  The group
        designation is now called the "context", one of ‘O’ or ‘A’.
        There are new entries: ‘everyheading’, ‘everyfooting’.

    - META ‘titlepage’ now uses SXML ‘insertcopying’

        Previously, the "link" was the string "@insertcopying".
        Now, it is the SXML ‘(insertcopying (@))’.

    - META last element now TOC

        This used to be the "remaining SXML after ‘titlepage’".  Now it
        is a list of symbols in the set: ‘contents’, ‘shortcontents’,

    - out w/ "two-letter indices", in w/ "document-term sets"

        This de-emphasizes the two-letter nature, and bumps out the word
        "index" (already very heavily used), to reduce confusion.  As a
        bonus, the string length of both old and new terms and their
        acronyms remain the same (18 and 3, respectively) -- woo hoo!

    - DTS "default font" and "inverse default font" specifiable

        Each (non-empty) DTS now has an initial form that includes
        "default font" (a symbol, ‘r’ or ‘code’).  An entry now may
        specify "inverse default font" with the symbol ‘-’ (hyphen)
        in its first position.

        Concurrently, DTS-INDEX now omits DTS-COUNT, as that has moved
        into the DTS initial form.

    - new specification / support for "float sets"

        The new "floset" (‘float’ and ‘listoffloat’) handling is
        analogous to that of "dts" (‘indexterm’ and ‘printindex’).

    - TWEAKS specified for NODE-INDEX elements

        The form is now: (NAME LENGTH NEXT PREV UP [TWEAKS]),
        where TWEAKS is a list of (NAME VALUE), like SETTINGS.

    - S-TREE moved forward, immediately after NODE-INDEX

        We want to move the optional portions (DTS) later, such that
        future addition of new portions can be more uniform (via "tail
        stretching").  This is a design-aesthetic, upward-compatability,
        hand-wavy, out-of-our-gourd reason, admittedly...

        Also, this block is now called the "sectioning tree".

    - new specification / support for "image inlining"

        The specification allows for any detectable image type, using
        MIME ‘image/TYPE’.  The tools support, however, is limited to
        mkixin guessing ‘image/png’ or ‘image/jpeg’, based on file
        extension.  Since the data is inlined into node data, retrieve
        does nothing special w/ it.

    - doc d/prob.xml includes combining chars and cyrillic

        Hmmm, is it valid XML to use combining chars when there are
        alternatives?  (See comment in doc.)

tarball, etc, in dir:

atom feed:

Thien-Thi Nguyen ..................................... GPG key: 4C807502
.                  NB: ttn at glug dot org is not me                   .
.                 (and has not been since 2007 or so)                  .
.                        ACCEPT NO SUBSTITUTES                         .
........... please send technical questions to mailing lists ...........

Attachment: pgpeb9y3Knzcy.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]