Hi all, Hussein Shafie a ?crit:
>>Thanks. In fact I wonder whether XXE should *natively* support Docbook's >>processing expectations. I've well understood that XXE is*highly* >>customizable :-) > > XXE supports whatever you want to make it support if you take the time > to customize it. That is *very* clear. >The bundled configurations are simply a starting point. OK. So, I understand that I'll have to develop Docbook's "official" Processing Expectations myself :-) > Currently, command editMenu (which displays the Edit popup menu) is not > contextual. That is, it cannot be parametrized to display a menu which > depends on the node being clicked upon. OK. >>Now, I select the whole sect1 element in order to use the "insert" >>command to create a sect1info element. Unfortunately, this element is >>*not* listed because I think that XXE assumes that the content model is >>valid as it is. > > This content model *is* valid. Definitely. > We are not fully satisfied with current semantics of the "insert into" > command: > * insert an element at caret position (even if an ancestor of ``caret > container'' is explicitly selected); > * OR, only if selected element is empty, add a child to this element. > > We will probably rethink the "insert into" command but not on the short > term. OK. > This being said, we'll fix this minor bug. Thank you... for this and all the rest. Cheers, -- Pierrick Brihaye, informaticien Service r?gional de l'Inventaire DRAC Bretagne mailto:pierrick.brihaye at culture.gouv.fr
