diff options
author | Gerald Combs <gerald@wireshark.org> | 2016-11-15 10:30:31 -0800 |
---|---|---|
committer | Gerald Combs <gerald@wireshark.org> | 2016-11-15 19:09:47 +0000 |
commit | 1431b97430d1c7bcf31b9969c5a8f4cabdef71f0 (patch) | |
tree | f5bb24dfd6b15b436a8fef5abb1d6e3e72884a9f /wsutil/utf8_entities.h | |
parent | d84e46ff1004018f88be6011f11f70dce4e3227b (diff) |
Add more information about UTF 8 in our source code.
Change-Id: I81d41fdc1aa66dd904160508c4a2e634337b5ba0
Reviewed-on: https://code.wireshark.org/review/18833
Reviewed-by: Gerald Combs <gerald@wireshark.org>
Diffstat (limited to 'wsutil/utf8_entities.h')
-rw-r--r-- | wsutil/utf8_entities.h | 13 |
1 files changed, 10 insertions, 3 deletions
diff --git a/wsutil/utf8_entities.h b/wsutil/utf8_entities.h index 6cb06e1f86..df1d9dc0f8 100644 --- a/wsutil/utf8_entities.h +++ b/wsutil/utf8_entities.h @@ -30,11 +30,18 @@ * http://www.utf8-chartable.de/ * and other places * - * While many modern systems default to UTF-8 and handle it well, some do - * not. The Windows console is a notable example. When adding a glyph below - * you probably shouldn't stray too far from code page 437 or WGL4: + * Please be conservative when adding code points below. While many modern + * systems default to UTF-8 and handle it well, some do not. The Windows + * console is a notable example. As a general rule you probably shouldn't + * stray too far from code page 437 or WGL4: * https://en.wikipedia.org/wiki/Code_page_437 * https://en.wikipedia.org/wiki/Windows_Glyph_List_4 + * + * Hopefully we can dispense with the sequences below and simply encode our + * files as UTF 8 at some point. For example gcc has supported UTF 8 since + * at least 3.4. Visual C++ on the other hand is much more problematic. + * 2015 and later support /source-charset:utf-8, but prior versions appear + * to require a UTF 8 BOM. */ #define UTF8_DEGREE_SIGN "\xc2\xb0" /* 176 / 0xb0 */ |