DITA and XMetaL Discussion
XMetaL Community Forum › DITA and XMetaL Discussion › Cannot adjust line length for "file not found" in "Cross-File Operation
-
akaAnnAdams April 11, 2018 at 4:25 pm
Cannot adjust line length for "file not found" in "Cross-File Operation
April 11, 2018 at 4:25 pmParticipants 0Replies 1Last Activity 4 years, 4 months agoXMetaL 12
When running the Cross-File Operation to validate references – “For each XML document, check for broken references.” against all topics in a ditamap. The results identify broken links, but the actual broken link topic does not display in the results. For example:
t_product_topic.xml
file not found: (fiel:///c:/ / / / Derek Read April 11, 2018 at 7:48 pm
Reply to: Cannot adjust line length for "file not found" in "Cross-File Operation
April 11, 2018 at 7:48 pmThe text for long results is truncated, so that code would actually need to be modified to provide more information to the results list. I believe it is truncated in order to increase the speed at which large numbers of results can be displayed. So, the amount of text here could be increased, but perhaps there are other better options…?
Double clicking on the broken link listed in the Results pane will open the DITA file that contains the broken link, and it will move the selection to the element that has that broken link (which in your case is likely an
). Once you are there you can: 1) Double click on the element to open the properties dialog for it and check the full attribute value you are interested in (assuming the dialog lists it). In the case of an
element for example, the dialog will display the href attribute. You can also right click and select “Properties…” from the context menu (or press the context menu key if your keyboard has one, or Shift+F10).
2) Hover over a start or end tag for the element to see the full attribute value for attributes with values that have been set.
3) Place the insertion point inside the element then open the Attribute Inspector (F6) to check all of the element's attributes.There are some other (possibly less useful) options:
1) Switch to Plain Text view to view theelement's XML source in full.
2) Copy theelement and paste it into another plain text application like Notepad (which is similar to previous option). -
AuthorPosts
- You must be logged in to reply to this topic.