There was my proposal to add dash entities to guide.dtd etc. I suggested (erroneously) two options to do that: one was &emdash;, and the other was — That was my mistake. Right (and official) names are at http://www.w3.org/2003/entities/ Later on I found that &emdash or &endash is used rarely, but is confusing instead: all of Xml Docbook/ Dita / XHTML / TEI etc use — and – Xavier said it's irrelevant but it isn't: why introduce more chaos? Anybody using it will have to remember: "Endash here, Ndash there, Mdash there, Ndash here" :-) Hopefully, nobody except myself had time to use that entities in real documents at the moment! PLEASE! Change &emdash to &mdash, and &endash to &ndash ASAP. I'll then take care of forthcoming Russian docs. I'll also found that characher entity declarations differ between DTDs where they shouldn't. It is corrected, too. Patches are encosed.
Created attachment 64415 [details, diff] book.dtd char entities fixed
Created attachment 64416 [details, diff] guide.dtd char entities fixed
Created attachment 64417 [details, diff] inserts.dtd char entities fixed
Created attachment 64418 [details, diff] metadoc.dtd char entities fixed
*** Bug 100441 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > Xavier said it's irrelevant but it isn't: why introduce more chaos? You had stated only ndash was ok in html and that is irrelevant because those entities are replaced and do not appear as an entity in html. If you prefer ndash/mdash. I don't care. I'll change them provided no one else has started using them. > I'll also found that characher entity declarations differ between DTDs where > they shouldn't. It is corrected, too. You shouldn't have. metadoc/inserts do not really need them. They are seldom changed and if you need a "funky char", just type it. As for the "missing' entities, they are not missing. They were introduced into guide.dtd only because they have been used in a few old files and it was more convenient to add them than to hunt for those files and fix them and their invalid xml. Only characters that are really very difficult or impossible to type should be available as an entity. In order: Always use instead of ' ' because you can't 'see' them Use the character itself, or its entity if you really can't ype it Avoid (hexa)decimal entities that make the text difficult to read.
e{m,n}dash replaced by {m,n}dash
Thank you!