From: Michael Smith <smith@xml-doc.org>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: ANN: Emacs WYSIWYG CALS table generator
Date: Mon, 22 Jan 2001 22:42:00 -0000 [thread overview]
Message-ID: <u3deawz16.fsf@openwave.com> (raw)
Message-ID: <20010122224200.0o8APS-QOp18cGZESWAIzZeIROxBL7oPNtkHd0lLs4I@z> (raw)
Just made available: a new release of a WYSIWYG table editor for
GNU Emacs and XEmacs, with support added for generating XML source
compliant with the OASIS Exchange subset of the CALS table model
(used in DocBook and in some other DTDs)[1].
The editor -- v1.5.16 of the Emacs lisp package table.el created by
Takaaki (Tak) Ota <Takaaki.Ota@am.sony.com> -- can be dowloaded at:
http://sourceforge.net/project/showfiles.php?group_id=14137&release_id=21474
Details and screenshots are available at:
http://table.sourceforge.net/
Along with the newly added CALS support, other notable features:
* can generate HTML 3.2-compliant tables too
* also useful for embedding tables in any text document: in comments
in code or e-mail, for example -- not just for XML/SGML/HTML
* like Emacs itself, can be used even in a non-Windowing/GUI
environment (for example, over a Telnet/tty connection)
* support for generating LaTeX tables is in the works
The table.el site also provides a number of supporting Sourceforge
features, including links to table.el mailing lists (for bugs and
requests) and an interface for submitting table.el bug reports.
But not a CALS or HTML rendering/display engine
---------------------------------------------------------------------
Though table.el generates CALS and HTML source, it doesn't render/
display either CALS or HTML tables.
Ota considers source rendering out of scope for table.el, and has no
plans to ever offer integrated rendering. However, he has said he is
very much willing to collaborate with developers working on rendering
packages (such as w3 mode for Emacs) and working with them on package
interoperablity to enable "round tripping" of tables in Emacs.
By the way, though table.el itself contains extensive documentation --
and is easy enough to use that you don't really need the docs much --
I'll be helping to create a Texinfo file for it, so feel free to send
comments or suggestions for the documentation to me.
--Mike Smith
[1] For those familiar with the CALS table model
----------------------------------------------------------------------
The XML source generated by table.el will validate either against the
"full" CALS model or the OASIS Exchange XML subset, as described in
OASIS Technical Memorandum TR9901:1999:
http://www.oasis-open.org/html/tm9901.htm
This means that the XML source generated by table.el:
* specifies horizontal spans by placing namest="" and nameend=""
attributes on <entry> elements, instead of <spanspec> elements
* never contains <tfoot> elements
However, compliant with OASIS Exchange subset, table.el _does_ enable
you to specify how many (zero or more) <row>'s of the generated source
should be wrapped in a <thead> element.
----------------------------------------------------------------------
--
Michael Smith mailto:smith@xml-doc.org
xml-doc http://www.xml-doc.org/
next reply other threads:[~2001-01-22 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 22:49 Michael Smith [this message]
2001-01-22 22:42 ` Michael Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u3deawz16.fsf@openwave.com \
--to=smith@xml-doc.org \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).