I was about to mention the appInfo element to a fellow Freedict developer, in the hope that he would be able to look at the spec and move from there, when the cute fragment <ptr target="#P1"/> caught my eye.
OK, this is explained in the text of the section, but in the brief spec description the pointer is completely unintuitive. I thought at first that it targeted a description of the tool elsewhere in the header.
I would like to suggest a more thorough description in the spec, and perhaps also including <ref> as an alternative to <ptr>, especially if more than one part is affected and they may be meaningfully labelled.
Another thing I wondered about is the interpretation of <application> in the absence of any pointing element inside. I understand that in such cases, it applies to the entire document (pre- or post-inclusion?), but it may be worth mentioning in the description as well.
Definitely a low-priority issue but worth raising, I thought. HTH
I was about to mention the appInfo element to a fellow Freedict developer, in the hope that he would be able to look at the spec and move from there, when the cute fragment
<ptr target="#P1"/>caught my eye.OK, this is explained in the text of the section, but in the brief spec description the pointer is completely unintuitive. I thought at first that it targeted a description of the tool elsewhere in the header.
I would like to suggest a more thorough description in the spec, and perhaps also including
<ref>as an alternative to<ptr>, especially if more than one part is affected and they may be meaningfully labelled.Another thing I wondered about is the interpretation of
<application>in the absence of any pointing element inside. I understand that in such cases, it applies to the entire document (pre- or post-inclusion?), but it may be worth mentioning in the description as well.Definitely a low-priority issue but worth raising, I thought. HTH