This is not a bug. Nothing is valid inside <unclear> in EpiDoc, except text and <g/>. The theory being that if a character that is identified as a punctuation mark, or part of a punctuation mark, is ambiguous then that character should be tagged as unclear. (And how we display that is another question, as an underdot beneath a period or a colon, for example, would be pretty confusing.)
If this doesn't cover what you want to do, can you explain your use-case a bit? If, for example, you want to use <pc/> as an empty element to represent a punctuation character that has no unicode encoding (analogous to how we use <g/>) then we need to think about (a) whether this is suitable use, rather than enclosing <g>, and only then potentially (b) changing the schema to allow pc in unclear.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
file showing problematic markup
This is not a bug. Nothing is valid inside <unclear> in EpiDoc, except text and <g/>. The theory being that if a character that is identified as a punctuation mark, or part of a punctuation mark, is ambiguous then that character should be tagged as unclear. (And how we display that is another question, as an underdot beneath a period or a colon, for example, would be pretty confusing.)
If this doesn't cover what you want to do, can you explain your use-case a bit? If, for example, you want to use <pc/> as an empty element to represent a punctuation character that has no unicode encoding (analogous to how we use <g/>) then we need to think about (a) whether this is suitable use, rather than enclosing <g>, and only then potentially (b) changing the schema to allow pc in unclear.