I agree that mangling the proper spelling of an individual's name is inappropriate, and that a proper solution to this issue would circumvent that option. Perhaps each Boost library could have a copyright file associated with it (<library>.copyright.utf8, or some other naming convention), and the boillerplate within the sources of that Boost library could reference that copyright file (which in turn would reference the Boost License file at the root of the source tree). The high-ASCII text could then be in that external file, avoiding the compiler, and nobody's name gets inappropriately altered. Thoughts? Alternatives? Blessings, Foster On 3/30/06, Peter Dimov <pdimov@mmltd.net> wrote:
Foster Brereton wrote:
I have attached a list to this email (There are 354 in the list as of this writing). I couldn't figure out how to attach the file to the bug report after-the-fact. Note that these are the most likely candidate source files to cause an error when building the Boost sources -- some test cases and example sources were omitted.
Many of these are caused by a name in the copyright clause containing non-ASCII characters. Replacing ö and ø with o (even oe) in people's names doesn't seem very polite to me, and such "rechristening" may have legal implications.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Foster T. Brereton - Computer Scientist Software Technology Lab, Adobe Systems Incorporated fbrereto@adobe.com -- http://opensource.adobe.com