Kevin Flynn wrote: > > I should have said so in my first mail, but better late than never: XXE 2 > looks VERY good. I have a few minor gripes about the GUI (still too > mouse-dependent for me), but I imagine that I will be able to get round much > of that with customizations when the more detailed doc turns up. > > I use XXE to edit documents based on our own DTDs, and I'm trying to make > use of the catalog functionality to point to these DTDs. I have the > following questions/comments: > > As far as I can see, if I specify a relative path to a DTD in a catalog > file, then that path is interpreted relative to XXE's config catalog, and > not relative to the actual location of the catalog file. Is that correct?
Correct. This is a very common pratice (and in my opinion a very good one). > It would seem to me to be more useful if it were relative to the catalog > location. I have all my documents and the DTDs they use located in a CVS > tree that is mounted with different paths by different people. If paths were > interpreted relative to the catalog file location, then I could place a > catalog file at the top of this tree. All users then have to do would be to > point XXE to the catalog file. As it is, they will need to have their own > catalog file that specifies absolute paths to each DTD (I think). I think that your documents should reference the ``standard universal DTD location'' (W3C or Oasis or for your custom DTDs, DTDs on a centralized HTTP server). This will work fine if the consumers of your documents use XML catalog enabled software. > What about access to a similarly centralized CSS file (for display in > Ayuda)? Will each user have to set the <cfg:css> element in their XXE config > file themselves, or is there some way of using the catalog for CSS file > references as well? XXE configurations (catalogs, DTDs, XML Schema, css, scripts, etc) can be centralized and downloaded from an HTTP server. And this even includes Java code (i.e. .jar files containing support code or plug-ins). This will be documented in the Power User's Guide. > Or would I be better off ignoring the catalog and config files, and relying > on the fact that the new XXE seems to leave relative paths alone? > > I see that use of schema is restricted in the free version of XXE. Am I > correct in assuming that means that if I want to convert my DTDs to XSDs and > use XXE for editing documents based on them, then I need to buy the > commercial version? > > More generally, it would be nice to know in detail now what the differences > between the free and commercial versions of XXE are going to be, and what > the commercial version is going to cost. I see decision time approaching.... Please be patient with us. All the docs you want will be released with V2.0final, before end of this month.
