What do you mean by "changing the name in the DITAMap"? Changing its "title" attribute? Its "id" attribute? Using "File|Save As"? (Did all that, works fine).
>>>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. I don't see how this could happen. May be XXE crashed during "File|Save" or "File|Save As". If this is the case, it has probably something to do with your working environment. You need to run XXE in a console and send us the messages printed on it. In order to run XXE with a console, please open XXE_install_dir/bin/xxe.jstart using notepad and replace "javaw" by "java", save xxe.jstart (normally in UTF-8) then restart XXE. >>>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. 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. No. A DITA map can contain thousands of topicrefs. >>> Figured so, wasn't sure if there was any limitations in the client or not. I'm sorry but I don't see anything wrong with the file you sent me. To me, the hierarchy looks good. See attached screen shot. >>> 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. --> In order to be able to help you, we *must* be able to reproduce all your problems here at our offices. [1] Please tell me, step by step, who I can reproduce the non-closing tag problem. Do not hesitate to send me all needed XML files. [2] Please send me a map containing SVN keywords which XXE fails to open. [3] Tell me more about your platform (version of XXE, OS, Java runtime) you use. >>> I'll try and get all this done for you on the next email. Christopher Green GE Fanuc Intelligent Platforms -----Original Message----- From: Hussein Shafie [mailto:[email protected]] Sent: Friday, April 25, 2008 2:38 AM To: Green, Christopher A (GE EntSol, Intelligent Platforms) Cc: xmleditor-support at xmlmind.com Subject: Re: [XXE] DITAMap corruption Green, Christopher A (GE EntSol, Intelligent Platforms) wrote: > > We've noticed a number of issues when modifying source file names and > updating the ditamap. The first issue we notice with that is upon > changing the name in the DITAMap, What do you mean by "changing the name in the DITAMap"? Changing its "title" attribute? Its "id" attribute? Using "File|Save As"? (Did all that, works fine). > the tag itself for that entry does not close after the change. For > example <topicref> </topicref> just becomes <topicref>. I don't see how this could happen. May be XXE crashed during "File|Save" or "File|Save As". If this is the case, it has probably something to do with your working environment. You need to run XXE in a console and send us the messages printed on it. In order to run XXE with a console, please open XXE_install_dir/bin/xxe.jstart using notepad and replace "javaw" by "java", save xxe.jstart (normally in UTF-8) then restart XXE. > > > Secondly, when using SVN in conjunction with the ditamap, and revision > entries get added to the ditamap for tracking, it causes corruption in > the DITAMap and does not allow you to open the file anymore. Only > resolution is to go into the DITAMap file using a text editor and go > line by line and remove the reference information. 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. > > Lastly, file corruption, we are unable to copy and past a single line > to a single line in the DITAMap, we are forced to manually write out > each line (copy and paste the text for most). This is only an issue > when we currently have over 450 entries into the ditamap and becomes a > very laborious job. > > > > One question we have though, is there a limitation to the number of > topicref's that can be entered into a DITAMap inside of XML Mind? No. A DITA map can contain thousands of topicrefs. > > I've attached the ditamap after I've manually re added topic refs so > we can open it in XML Mind again, but the sequence and hierarchy in > the file is all messed up. I'm sorry but I don't see anything wrong with the file you sent me. To me, the hierarchy looks good. See attached screen shot. --> In order to be able to help you, we *must* be able to reproduce all your problems here at our offices. [1] Please tell me, step by step, who I can reproduce the non-closing tag problem. Do not hesitate to send me all needed XML files. [2] Please send me a map containing SVN keywords which XXE fails to open. [3] Tell me more about your platform (version of XXE, OS, Java runtime) you use.
