Oxygen XML Forum

• I had opened our project xpr file by lowercase URL path. This caused every single reference to result in a validation error of "...incorrect path capitalization.." or "File not found...". While minor, it results in over 160k validation errors that went away when I opened the xpr with correct case path.

• No way of knowing the batch validation progress, it takes my PC over an hour to run through all our files. I couldn't even detect any logic in the file order it was scanning to guesstimate how much longer it would take. It would be nice if it at least counted the files first and then used that count to indicate the progress bar position.

• After waiting over an hour, I went to try and save the ~200k validation results to text and xml file. Sadly, oXygen kept running out of memory when I tried to do that. After fixing the xpr path issue though, and getting the validation issues under control, it worked. Kinda annoying though the first time not having any way to export the results that took an hour to generate.

• No way to automatically filter and exclude some messages from batch scan. We have a plug-in that has a ValidationProblemsFilter listener for the current editor, but there does not appear to be any way to attach that to the batch validation routine. There are a few errors such as the ones complaining about "-dita-use-conref-target" attribute values that are not issues and should not be filtered.

• I added a ValidationProblemsFilter to the map editor to exclude a few messages. It correctly filters the probables, however the problem view panel automatically opens up and is empty when all messages are filtered.

• When renaming a colname in the colspec of a table in author view, all the references to the old colname in the table are not updated. It would be nice if oXygen automatically updated the colname references in the table as well. I could probably incorporate this into our plug-in but seems like something oXygen would do automatically.

I had opened our project xpr file by lowercase URL path. This caused every single reference to result in a validation error of "...incorrect path capitalization.." or "File not found...". While minor, it results in over 160k validation errors that went away when I opened the xpr with correct case path.

No way of knowing the batch validation progress, it takes my PC over an hour to run through all our files. I couldn't even detect any logic in the file order it was scanning to guesstimate how much longer it would take. It would be nice if it at least counted the files first and then used that count to indicate the progress bar position.

After waiting over an hour, I went to try and save the ~200k validation results to text and xml file. Sadly, oXygen kept running out of memory when I tried to do that. After fixing the xpr path issue though, and getting the validation issues under control, it worked. Kinda annoying though the first time not having any way to export the results that took an hour to generate.

No way to automatically filter and exclude some messages from batch scan. We have a plug-in that has a ValidationProblemsFilter listener for the current editor, but there does not appear to be any way to attach that to the batch validation routine. There are a few errors such as the ones complaining about "-dita-use-conref-target" attribute values that are not issues and should not be filtered.

I added a ValidationProblemsFilter to the map editor to exclude a few messages. It correctly filters the probables, however the problem view panel automatically opens up and is empty when all messages are filtered.

When renaming a colname in the colspec of a table in author view, all the references to the old colname in the table are not updated. It would be nice if oXygen automatically updated the colname references in the table as well. I could probably incorporate this into our plug-in but seems like something oXygen would do automatically.

Radu wrote:I will try to reproduce this on my side. So the project references a folder which contains the DITA resources, right? Why did you not open the main DITA Map in the DITA Maps Manager and use the "Validate and check for completeness" action? It shows more problems than just validating each topic individually...

Radu wrote:We also do not have a good way to know how much this will take. I think that at some point we counted all files and encountered a situation in which someone linked their entire harddrive in the project. So counting all the files lasted a long time... but I understand where you stand and I will add an internal issue, maybe we can better report how long this will take.

Radu wrote: I will add an internal issue to test if our batch validation properly releases memory in the end. So these were mostly DITA topics/maps/concepts and so on right? Were they DTD, XML Schema, or RNG based?

Radu wrote:I see below that you managed to get the filter API working. Could you tell us about those particular issues that Oxygen should not report anymore? Maybe we can avoid reporting them on our side if they are nonsense...

<table conref="file2.dita#ref/table_abc"> 

<title></title> 

<tgroup cols="-dita-use-conref-target"> 

.... 

We don't have a main map and some files may be orphaned. I suppose I could have listed all our DITA files and made a master map and checked that.

Yeah, just topics and maps. i think it properly released the memory and everything, the memory usage indicator in the tray was normal. It just seemed to be the "save as text/xml" routines that were struggling with over 200k results the first time around (mainly due to filename case issue)

Most frequent issue is "Element is not a content reference but has attribute "(cols|status)" with value "-dita-use-conref-target"."

I supose we could just hardcode the col number but not sure what would happen if the source table co num changed.

<table conref="#introduction/tableID">

                <tgroup cols="1">

                    <tbody>

                        <row>

                            <entry/>

                        </row>

                    </tbody>

                </tgroup>

            </table>

I added a ValidationProblemsFilter to the map editor to exclude a few messages. It correctly filters the probables, however the problem view panel automatically opens up and is empty when all messages are filtered.

Radu wrote:So you are using Oxygen 18.1, right?
In the Oxygen Help menu->About dialog there is also a "Build ID" value, something with a pattern like "yyyymmddhh". Could you tell me what that value is on your side?
I constructed a validation problems filter which removes all reported problems but I cannot reproduce this problem on my side, could you give me some Java sample code with what your plugin does?

<?xml version="1.0"?>

<!DOCTYPE map PUBLIC  "-//OASIS//DTD DITA Map//EN" "map.dtd">

<map>

    <topicref href="example.xml#ref/section_2"/>

</map>

...

if(msg.indexOf("Topic references should only be made to topic IDs") > -1)

     iterator.remove();