[nlpharrison]

Hi Severin,

Yes, I've tried both of those things; no dice.  The ditamap and topics open up in XMetal, so it's finding them, and validating them against the correct DTDs, but it's just not finding a file that's definitely in the location where it's looking.  Can you suggest any debugging stuf I might put into build.xml to figure it out?

Nancy

Reply

[nlpharrison]

Hi,

This is on XMetal 6.0, which I can't move from until my clients do.

This problem never went away; no one ever responded to it, and I just worked around it.  But now I'm trying to fix something else, and it's coming up again, so I really need to understand and fix it.

Regards,
Nancy

Reply

[nlpharrison]

Hi Derek,

The check for outputclass=”landscape” is implemented by the custom stylesheet [my client's stylesheet] that I'm using, which is a customization of [and directly imports] the DITA-OT dita2fo-shell.xsl stylesheet.  When it sees that attribute value, it calls its customized version of the landscape page-master template. 

The thing is, I'm using the same stylesheet inside and outside of Astoria – I created a customized version of the DITA-OT folder to use with my local XMetaL when I working with this client's content – and the same source files.  Other than the landscape issues, the stylesheet seems to have the same effect on the source files in terms of formatting and page-, topic-, section-, figure- and table-numbering, whether I invoke it from within XMetaL or from within Astoria.  My client's writers are all using XMetaL to author in, so they've set up their system to coordinate as well as possible.

I'm also discussing this with their Astoria expert, but I just wondered if anyone had ever run into this before.

Thanks,
Nancy

Reply

[nlpharrison]

Hi,

I am currently getting this Microsoft error with XMetal 6.0;

I tried following the suggestions that seemed to work for the original posters of the thread; uninstalling – removing it along with the suggested supplementary folders (Program Files/XMetal 6.0, Program Files/Corel/.., Programs Files/Common Files/XMetal Shared/*, /AppData/Softquad, /Local Settings/Temp/Xmetal/..).  But after doing all this, then rebooting, then reinstalling, the first time I open XMetal and try to create a new document, it opens the new document and then I get this error and it crashes.  I've gone thru the uninstall/reinstall process 3 times, but can't get rid of the problem.  I even used the uninstall utility you'd sent me earlier (xmclean.exe) after the last uninstall; still no joy…

Is there a new version (later than 6.0.1.39) that fixes this problem?  6.0.1 was working for me for about 5 days  before this started happening

Regards,
Nancy

Reply

[nlpharrison]

Well,

I decided that I'd be better off simply uninstalling XMetal Author Enterprise (XMAE) 5.5 and installing XMAE 6.0 instead, so I've done that.  I installed the eval copy of 6.0, specified the 5 specialized DTDs I needed, created a set of templates for the new DTDs, and configured a couple of PDF output options to try and get the publishing to use the customized XSL files required.  I'd added the customized XSL files to all the places I thought they'd need to be.

Then I created a new map from the specialized map DTD that I'd installed, and inserted a bunch of topicrefs for some topics (task, concept, and reference) that I'd previously created against the new topic DTDs.  

In this installation of XMAE 6.0, I do get the 'Generate Output' option from the File menu when I have the map open.  At first, I couldn't get the build script to find the DTD location, but then I realized I needed to update the XMetal 6.0 catalog-dita.* files with the locations of the DTDs. Now the build is progressing, though I'm still working through the build issues.

I'm noticing that if I delete the local (i.e. Docum,ents and Settings//Application Data/SoftQuad/) folder in order to get it to be updated when I update the main (Program Files/Common files/XMetaL Shared/DITA-OT) stylesheet locations, it doesn't always get populated with my updates.  For example, in the DITA-OT/xsl folder, we have 2 customized xtylssheets; micron_topicmerge.xsl and dita2fo-shell_axf.xsl.  When I updated the local version of the DITA-OT, the dita2fo-shell_axf.xsl file was recopied, but the micron_topicmerge.xsl file was not.  Same thing with the catalog-dita.xml file. Until I actually modified the catalog-dita_template.xml file as well as the 'live' version, updates to the SoftQuad folder kept ignoring my updates to the live version.

Reply

[Author]

Posts