tag:blogger.com,1999:blog-11807812.post116338895218873878..comments2023-05-29T08:58:13.381-04:00Comments on Recycled Knowledge: An annoying ambiguity about which nothing can be done nowJohn Cowanhttp://www.blogger.com/profile/11452247999156925669noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-11807812.post-83578718821056615022007-05-26T17:08:00.000-04:002007-05-26T17:08:00.000-04:00I thought I was the only one irked by that.I thought I was the only one irked by that.Michael Eversonhttps://www.blogger.com/profile/16882679137179765872noreply@blogger.comtag:blogger.com,1999:blog-11807812.post-1163433159946931722006-11-13T10:52:00.000-05:002006-11-13T10:52:00.000-05:00The names of Unicode characters cannot be changed,...The names of Unicode characters cannot be changed, although clarifying information can be added outside the name.John Cowanhttps://www.blogger.com/profile/11452247999156925669noreply@blogger.comtag:blogger.com,1999:blog-11807812.post-1163406677456995742006-11-13T03:31:00.000-05:002006-11-13T03:31:00.000-05:00Would it be possible to keep the codes and charact...Would it be possible to keep the codes and characters and properties but clarify their names? Character names are meant to be displayed to humans, most applications should have no trouble updating them and legacy documentation with obviously similar old names is no big deal.<BR/>For example, COMBINING DOUBLE FOO could be renamed to COMBINING DOUBLE FOO MARK or COMBINING TWIN FOO in your first set of examples and COMBINING WIDTH 2 FOO in the second set.Anonymousnoreply@blogger.com