I've been keeping a list of things I notice. Many of them are small 
configuration tweaks that I can do on my own, but they might as well make their 
way into the distribution. Since you're putting together a user wish list, I 
figured I'd send what I have now :) 

Thanks,
David

* Configuration enhancement: Add "DocBook -> Convert to HTMLHelp" (I know 
you're already planning Eclipse). Convert to HTMLHelp could run hhc.exe 
(assuming htmlhelp workshop is installed and in the PATH) and take them all the 
way to a .chm just like a GUI HAT (Help Authoring Tool). 

* Question: I can't seem to put text in some situations. I can't do this: 

<para>Foo <itemizedlist>....</itemizedlist> I can't put text here, but I should 
be able to.</para>

I have to do this:

<para>Foo </para> <itemizedlist>....</itemizedlist> <para>I can't put text 
here, but I should be able to.</para> 

Maybe I missed something in the help/docs? 

* Comment: Colspecs hard to add in docbook tables (I think I have to select 
thead, then insert before). Anything you can do to make tables easier to deal 
with would be good. Converting an informaltable to a table is hard. Probably 
some macros around tables are in order. I'll have to think about what 
specifically would be useful. 

* Feature idea: Norm Walsh has a docbook diffing tool and a Java version 
exists. It would be very cool if this were integrated into xmlmind: 
http://www.nwalsh.com/java/diffmk/index.html

* Question: When I open a xml document that contains Japanese (utf-8), the 
characters are square boxes. This is not a high priority for me--the 
translation house will use whatever tools they want on the xml, but I thought 
I'd mention it. Maybe I have something configured wrong?

* Someone asked about cvs integration on the list: I'd suggest using the 
Escape+e keybinding (in the supplemental docbook material) to drop into emacs 
and then use emacs' cvs integration. 

* Enhancement: It should be possible to 'copy' or 'cut' from node path bar like 
you can from within the doc using the contextual menu choices.

* Configuration enhancement: In DocBook, procedures and some other constructs 
are also lists, so put them in the addListItem command in common.incl:
  <command name="docb.addListItem">
    <macro>
      <sequence>
         <command name="selectNode" 
           parameter="ancestor[implicitElement] itemizedlist orderedlist 
                      variablelist procedure simplelist segmentedlist qandaset 
calloutlist" />
                                        <!-- 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -->        
        <command name="selectNode" parameter="child" />
        <command name="insertNode" parameter="sameElementAfter" />
      </sequence>
    </macro>
  </command>

Also, bind it to a key by default since it's such a common thing: 

 <binding>
    <keyPressed code="ENTER" modifiers="alt ctrl"/>
    <command name="docb.addListItem" />
  </binding>

* Configuration enhancement: Make xmlmind take you back to your original spot 
when you return from the external editor (i.e. back to where you were in 
xmlmind when you left, not the beginning of the doc. Obviously where you were 
in the external editor would be impossible). I realize that the ESCAPE+e trick 
is part of the docbook extension tutorial thing.

* Bug: DocBook segmentedlist/seg not formatted in editor.

* Bug: DocBook qandaset/answer is buggy in the editor. You can't enter text in 
the 'answer'

* Configuration enhancement: The button "Add orderedlist" should be a dropdown 
that includes procedure, orderedlist, and calloutlist. Variablelist button 
might as well be a dropdown with all other types of lists: simplelist, 
segmentedlist.


Reply via email to