From: "Diana Shannon" <[EMAIL PROTECTED]> > >> So, I'd like to know what's the correct way of managing such > >> situations. Can > >> I just setup a local catalog and use SYSTEM entities or my editing tool > >> should support catalogs natively? > > > > Either way you would need to set up an OASIS Catalog > > (just use the catalog file that comes with Cocoon). Tools > > such as XMetaL have native support and they still need > > you to configure the catalog file, obviously. > > This is useful documentation content, as a general how-to as well as for > instructions to authors. > > Konstantin, if you develop a workaround/fix for XML Spy, would you make > sure to post it?
Sure. Currently, the workaround is to change the declaration during development to point to the real local location, then switch it back on commit. ;) > > Ok, so right now we have these approaches: > - XMLMetal, with configuration of the catalog file > - Saxon command-line, with -r option > > Any other suggestions? Maybe Xalan also can be configured to use catalog? Konstantin > > Thanks. > > Diana > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]