Green, Christopher A (GE EntSol, Intelligent Platforms) wrote: > No, I mean exactly what I stated. We change the source file name - > so for example, I open explorer, go to my project directory and rename > file mystuff.xml to mystuff1.xml. After that change is made, I open the > DITAMAP in XMLMind and change the name there as well. After that change > is made, and I click "save" it no longer functions and we end up with > extra closing tags. Errors include "Expected </map> and got > </topicref>" etc.
Still not sure to understand. I did that to attempt to reproduce the problem: [1] Opened mymap.map in XXE. [2] mymap.map has a topicref that points to mystuff.xml [3] Opened mystuff.xml in XXE. [4] Used Windows XP file manager to rename mystuff.xml to mystuff1.xml. [5] Changed the "href" attribute of the topicref from "mystuff.xml" to "mystuff1.xml". [6] Saved mymap.map. [7] Closed mystuff.xml and opened mystuff1.xml in XXE. Also did that with the file locking (Option|Preferences, Open Section, "Lock documents stored on the local filesystem" checkbox. See http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.xmleditapp.dialog.PreferencesEditorDialog.html#openOptions) options turned on. As expected, I have not been able to rename mystuff.xml to mystuff1.xml using Windows XP file manager. All in all, everything worked fine. > The client is not crashing during the save. Since this is happening > to a number of our users, do you suggest having all of them run in > console mode for the time being and collect all of this data until the > problem occurs again? The only fix we've been able to come up with so > far is to remove the DITAMAP and recreate it from scratch. Sorry. ``crashing'' means printing error messages on the console. It does not mean that the window of XMLmind XML Editor disappears. No, I suggest that some of your users keep the console open. Normally nothing is printed on it. When a problem occurs, you should see hard to understand messages (stack traces) printed on the console. > > This has nothing to do with our product. Please specify SVN keywords > (e.g. $Date$) in places which will not cause the XML file to become > non-well-formed and/or invalid after these keywords are substituted by > SVN. > >>>> SVN Keyword is ">>>>>>>>>>.r34902" this is an example of what gets > entered an causes files and the map to no longer function. I guess that ">>>>>>>>>>.r34902" added for example before or after the root element of a document could cause this document to become non-well-formed. Adding ">>>>>>>>>>.r34902" in other places could cause the document to become invalid (red icon at the bottom left or main window). I would suggest to add SVN keywords in an XML comment found before the root element of your documents. Note that you cannot use XMLmind XML Editor to do this. > As I stated, I had to fix the file. Without doing so recreating our > DITAMAP turns into over a day of a persons time to recreate it. I guess > you not knowing the original from what that file looks like does not > help you at all, but the essential issue with it is that many of the > levels get indented a level or two, files are re-organized into a > non-logical order as topref close tags don't match the open tag, etc. I > know we'll have this issue again in the next week or two so I'll send > you the file in the state that we can't open it along with a number of > other files that end up in the same state. > There is no code, logic, anything, in XMLmind XML Editor which could cause the nesting level of topicrefs to be garbled. > I'll try and get all this done for you on the next email. Thanks. I'm really curious and at the same time, I'm pessimistic because I'm sure that hundreds of DITA users are doing everyday things similar to what you do without any problem. Therefore I suspect that you have a really nasty problem.
