On Sat, Jan 19, 2013 at 10:20:30PM +0100, Patrice Dumas wrote:
I'll now take a stab at a first IXIN output implementation. I'll do it
with some abstraction, such that other output format than lisp-like may be
output with the same information structure, for instance XML.
I have done an
On Fri, Jan 18, 2013 at 02:40:42AM +0100, Patrice Dumas wrote:
The node label is missing in the 'node index'.
This is, in fact incorrect, I just had misunderstood the labels part.
It is nt possible for a node not to have a label. It also do not make
much sense to compare the label with the
On Fri, Jan 18, 2013 at 02:40:42AM +0100, Patrice Dumas wrote:
On Fri, Jan 11, 2013 at 10:22:25AM +0100, Thien-Thi Nguyen wrote:
Float should also have a number pre-filled. This is currently missing
in the XML output.
Then to match an index entry in the document to an index entry in the
Other comments
* for lang, why not using a string, taking whatever is the default (in
general en and not en_US), and instead of a list using like en_US,
(or maybe - if there is no language because of an error somewhere,
not sure this may happen)?
* for title, there are 2 possibilities (in
On Fri, Jan 11, 2013 at 10:22:25AM +0100, Thien-Thi Nguyen wrote:
‘spec/ixin.texi’ is The IXIN Chronicles, a document that
defines the file format and provides related info. There
are various output formats, including .info, .pdf and .ixin.
Some more comments on the format.
In the
On Fri, Jan 11, 2013 at 10:22:25AM +0100, Thien-Thi Nguyen wrote:
‘spec/ixin.texi’ is The IXIN Chronicles, a document that
defines the file format and provides related info. There
are various output formats, including .info, .pdf and .ixin.
Another comment, I think it would be better
Hello,
I have added a SXML backend based on the XML one. You can test it with
texi2any --set SXML=1 myfile.texi
There is no header, no comments.
How should comments be handled?
Entities are output as normal elements, like
(textlsquo (@))
There is an extraneous space after string before
() Patrice Dumas pertu...@free.fr
() Tue, 15 Jan 2013 19:52:57 +0100
On Fri, Jan 11, 2013 at 10:22:25AM +0100, Thien-Thi Nguyen wrote:
‘spec/ixin.texi’ is The IXIN Chronicles, a document that
defines the file format and provides related info. There
are various output
On Tue, Jan 15, 2013 at 10:18:51PM +, Karl Berry wrote:
I have added a SXML backend based on the XML one.
texi2any --set SXML=1 myfile.texi
1) maybe the name should be IXIN rather than SXML? I thought SXML is
just a generic name for XML written in sexprs. Or am I wrong?
You
() Patrice Dumas pertu...@free.fr
() Sun, 13 Jan 2013 22:14:19 +0100
I have read the specification, looks good, none of the ??? looked
like stumbling blocks.
Cool, thanks. The SETTINGS representation (re)design will benefit from
scrutiny in the next release, for sure.
Using mime types
release notes:
OK, w/ this release, we've fully explored the incremental access
side of IXIN purpose; now to turn to the runtime-tweakable side.
It looks more and more like TWEAKS in each NODE-INDEX entry is not
going to be sufficient. For example, what if, within a node, some
setting
11 matches
Mail list logo
