CSS-injected parentheses before and after indexterm in Author mode
Posted: Mon Jul 11, 2016 12:15 pm
Author mode uses CSS to display parentheses before and after <indexterm> content. (Oxygen XML Author 17.1.)
I'm sure I'll get over it, but I find this behavior disconcerting to the point of being annoying, especially since those CSS-injected parentheses have exactly the same display attributes as the actual, editable content:
For now, I've commented out the display and content properties in the offending CSS:
in
author\frameworks\dita\css\core\-topic-metadata-indexterm.css
Why are these parentheses in Author mode a good idea?
If the answer is related to nesting of indexterm elements, then I'd prefer to see that nesting represented in Author mode by a combination of line break and indent.
Why is it a good idea to display those parentheses in a way that makes them visually indistinguishable from the editable content?
Finally, it occurs to me that this behavior - this CSS - might not be native to Oxygen; it might be a customization. The Oxygen XML Author installation that I am using has been customized to work with third-party software; this might be one of those customizations, so, with apologies, I might be raising this issue in the wrong place, with the wrong people.
I'm sure I'll get over it, but I find this behavior disconcerting to the point of being annoying, especially since those CSS-injected parentheses have exactly the same display attributes as the actual, editable content:
Code: Select all
<indexterm>(the parentheses are not editable content)</indexterm>
Code: Select all
*[class~="topic/indexterm"]:before {
/* content: "(";
width: auto; */
}
author\frameworks\dita\css\core\-topic-metadata-indexterm.css
Why are these parentheses in Author mode a good idea?
If the answer is related to nesting of indexterm elements, then I'd prefer to see that nesting represented in Author mode by a combination of line break and indent.
Why is it a good idea to display those parentheses in a way that makes them visually indistinguishable from the editable content?
Finally, it occurs to me that this behavior - this CSS - might not be native to Oxygen; it might be a customization. The Oxygen XML Author installation that I am using has been customized to work with third-party software; this might be one of those customizations, so, with apologies, I might be raising this issue in the wrong place, with the wrong people.