Thomas Dumm wrote:
> 
> Thank you for your reply! The reason that the element is called "Table" and
> not "table" comes from the fact, that we used to have a own table model in
> our dtd, which suited us better.
> But the own table Model lead to too many problems with xml-editors (by the
> way presently we use Arbortext Editor but we want to change this). People
> did not change the letter T when changing to CALS, as all our elements have
> capital letters. Too late now...

OK, I understand.



> What also prevents us from using the CALS-Table-Editor is a "funny" thing
> that I noticed in XMLMind: We do not allow text modes directly inside
> "entry" in our dtd. This certainly correctly set up in the dtd. But for some
> strange reason, XMLMind still enters text nodes by default in entry, of
> course causing invalid xml. XMLMind realizes this invalidity only when
> saving the document, which is too late. I think when using the
> CALS-Table-Editor-command the dtd-validation is bypassed for a "monent"?
> 

Not exactly. The CALS table editing commands don't use the DTD at all. 
They simply assume that the table being edited fully conforms to the 
CALS table model, and in the CALS table model an entry may contain text.

Well, I suppose that we could improve the flexibility of all our table 
editing commands.







Reply via email to