Re: invalid doctype/xml

[Alper Ersoy]

Hello!

Jens Elkner:
> unfortunately makeinfo --docbook produces wrong xml code:

It's Docbook SGML in Texinfo 4.6, we changed it to XML a week ago.

> 4)
> if @documentencoding ISO-8859-1 is use and enabled, makeinfo produces
> invalid xml code by appending \^_ ...
> Instead of that, makeinfo should insert 
> <?xml version="1.0" encoding="enc"?>
> at the top of the document!

This is a very nice idea.  Thanks!

[patch cut]

> Last but not least: RFE wrt. to mapping texinfo commands and to retain as
> as much information as possible:
> =========================================================
> a) map @comment to <!-- ... --> instead of ignoring it entirly

Another nice idea :)

> b) man @env to <env>...</env> instead of <command>...</command>

Yes, this one got fixed a while ago too.

> c) map @example to <example>...</example> instead of <screen>...</screen>

This is not possible.  <example> expects a <title> attribute, and it
can't contain CDATA itself.  You still have to use <screen> or
<programlisting> inside <example>.

I have good news.  Texinfo 4.7 will feature a @float environment that
will influence the elements used in Docbook output.  Here's a quick
table:

  Command        Normal              Inside @float
  =======        ======              =============
  @multitable    <informaltable>     <table>
  @image         <informalfigure>    <figure>
  @example       <screen>            <screen> inside <example>
  @lisp          <programlisting>    <programlisting> inside <example>

Also there is a new @caption{} command for titles.

> d) map @file to <filename>...</filename> instead of <command>...</command>
> e) map @option to <option>...</option> instead of <command>...</command>

These two are fixed too.

> f) map @samp to <userinput>...</userinput> instead of <command>...</command>

Hmm, it seems @samp is currently mapped to literal.  But I guess
userinput is a better choice.  Thanks!

> With the current mapping a lot of information gets lost at least wrt.

I'm very much willing to hear more about these cases.

> and one is unable to extract required information or adjust the view
> (e.g. color when transforming the docbook into [x]html or pdf) 

You can use your customized stylesheets for this.  Otherwise I see no
easy way of doing this from within Texinfo documents.  I have a very
simple dsl file I use when formatting Texinfo documents with Docbook.
Let me know if you are interested.

> Since html does not really provide similar tags, it would probably
> a good idea to use <code class="$texinfo_tag">...</code>.

I'll look into doing this.  Can you please help me sort out a list
of where a class attribute is needed?

> BTW: Are there any hints/tips, how makeinfo works out the appropriate tags?
> I took a quick look at cmds.* and xml.c, however the cm_$something and 
> the arrays are a little bit too confusing for me to provide an appropriate
> patch :(

Things got considerably improved in the last few weeks.  I suggest you
to try the current version from CVS, if possible.  (If not, I can
provide you a bootstrapped package, just let me know.)

If there's more stuff that you think should/can be improved, I'll try to
do so as soon as possible.

Thanks!

-- 
Alper Ersoy