Comment 3 for bug 189219
Revision history for this message
| Christopher Yeleighton (giecrilj) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
That does not mean the bug is invalid, it only means the Unicode Standard is at fault ("report upstream"). What do you think?
It is hopeless to try to contact Unicode Consortium as an individual.
The best way this could be handled is to make sure the cross-references are symmetric while the descriptions are extracted during building.