If I include the .jar files with the 4.3 functionality in an add-on package for 
the version 4.2 that the users are currently running, will it inherit the new 
functionality? We'll be asking the users to uninstall and reinstall when the 
imageport functionality is available, and I'd rather not ask them repeatedly, 
rapid-fire to go through the hassle. There are few things grumpier than an 
overworked engineer.

Cheers,
Jeff.



----- Original Message ----
> From: Hussein Shafie <hussein at xmlmind.com>
> To: Jeff Hooker <jeff at itwriting.ca>
> Cc: "xmleditor-support at xmlmind.com" <xmleditor-support at xmlmind.com>
> Sent: Thu, October 29, 2009 12:58:07 AM
> Subject: Re: [XXE] db5.tableEdit command
> 
> Jeff Hooker wrote:
> > 
> > In PMC's docbook 5 and DITA implimentations, we've standardized on every 
> > entry 
> element in a row having a para element. Tweaking the schemas for this is 
> simple, 
> but tweaking the tableEdit commands have been more challenging. When I look 
> in 
> the commands guide, I can see that the the cell= parameter allows me to 
> define 
> the elements that qualify as a cell, but I cannot define two elements as 
> being a 
> single requirement (cell = entry/para). At least, if I can, I can't make it 
> work.
> > 
> > I would have expected to be able to override the standard parameters for 
> db5.tableEdit.tableSpecification by including my own in the local config 
> file, 
> but I can't. At least, it seems that I can't.
> > 
> > As it stands, even though the schema now forbids the existance of entry 
> elements without at child para element, the insert columns/insert rows 
> command 
> will still insert them, which is a surprise, and leds to believe that this 
> must 
> be template-driven somehow, because it isn't taking its cues from the schema.
> > 
> 
> * The CALS table editor is not parametrized by a user-specified table
> specification. Only the "generic, parametrizable, table editor" command
> is (see
> http://www.xmlmind.com/xmleditor/_distrib/doc/commands/tableEdit.html).
> 
> Instead (not surprisingly) the CALS table specification is hardwired in
> the code of the CALS table editor.
> 
> * The CALS table editor assumes that an entry may contain text. This
> assumption is always correct in the case of *true* CALS tables.
> 
> * It is overkill to modify the DocBook and DITA grammars to force
> entries to contain paragraphs. Please *remove* *these* *changes* because
> there is a simpler way to do that: element templates
> (http://www.xmlmind.com/xmleditor/_distrib/doc/configure/elementTemplate.html)
> 
> * If you add an element template such as this one to your DocBook 4
> customization, all the editing tools, including the CALS table editor,
> will automatically create entries containing a para.
> 
> DocBook 4 example:
> ---
> 
> ? 
> 
> ---
> Notice attribute selectable="override" which is needed for the table
> editor to automatically use an element template.
> 
> Please use a similar element template for DocBook 5 and DITA.
> 
> Of course, also do not forget to also modify your table element
> templates (if any).
> 
> IMPORTANT: this requires XXE version >= 4.3.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> --
> XMLmind XML Editor Support List
> xmleditor-support at xmlmind.com
> http://www.xmlmind.com/mailman/listinfo/xmleditor-support

Reply via email to