The terminologyįiles can be added in the rules folder or organized in subfolders (the TerminologyĬhecker scans the subfolders to identify the terminology files). Oxy-terms-auto-detect inside the rules folder. The contributor add-on should have a marker file named.The following pre-conditions must be fulfilled:Äescriptor file should reference the rules folder in the plugin.xml The contributed terminology files will be loaded and used Terminology Files Contributed from Other Oxygen Add-onsĪny Oxygen add-on can contribute terminology files that will be This willĪpply the associated validation scenario for each topic or map referenced in the Validate and Check for Completeness toolbar action andĬhoose to Batch validate referenced DITA resources. In the DITA Maps Manager view, you can use the.Validate using a specific validation scenario. In the Project view, you can right-click a folder and.The validation scenario can be used in multiple ways: Validation engine field, choose TerminologyĬhecker. Type field, choose XML Document and for the Create a new validation scenario or editĪn existing validation scenario, and add a new validation stage.Right-click a folder in the Project view and choose.Manager view and choose Check terminology. Right-click on the root of the DITA map opened in the DITA Maps.Once installed, the terminology checker add-on can be used to batch-check multiple You can filter problems based on their severity, match, and messageĪnd the toolbar has actions to navigate between problems or to open the for Vale rules, it also displays the name of the Vale rule file The tooltip for each problem displays a custom message and more You can right-click each problem to apply possible fixes or to find out moreÄetails about it. The Terminology Checker side view shows all problems found in theÄocument. Vale rules that aim to automate the Google style guide.Vale rules that aim to automate the Microsoft style guide.Vale rules that aim to replicate Grammarly checks.Various checks on the following websites: Resources: You can find already created Vale rules that implement Once the user guide project is open in the Oxygen XML Editor Project view, the add-on will start using those rules to check theĬontent. Oxygen XML Editor user guide has a folder with some of the Microsoft style guide rules. In the current project that is open in the Project view, all theįiles in that folder will also be loaded by the terminology checker. Note: If you have a folder named oxygen-term-checker /elementName1/elementName2/elementName3.A list of comma-separated XPath values can be used.įollowing are examples of how simplified XPath expressions might look like: The elementsĬovered by this simplified XPath will be checked for matches (or the exclusion of a XPath expressions that match specific elements. If present, it provides theÄ®xample: Oxygen XML EditorIf present, its content isÄisplayed in a tooltip when you hover over a highlight. If you want to replace the match with an XML fragment, you can set attribute on the Ä®xample: Oxygen XML Editor Replace all occurrences of product with key reference.Click OK several times to apply the changes and close the.The Options > Preferences > Plugins > Terminology Checker preferences page and set the Additional Terminology If you saved the terminology file in a custom folder path, go to.Oxygen-term-checker located in the current project folder (theĬurrent project opened in the application Project view), or in a Save the newly created terminology rules XML file either in a new subfolder named.Here is an exampleįile: Oxygen Product name should be inside a tag. Click the New button on the toolbar or select File > New and search for the Terminology File template. You get started in the New Document wizard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |