- file name encoding converter
- man page
- command and library to convert character encoding
- Most basic character encoding.
- Most of the modern character encoding is based on this.
- 0x00 to 0x7F
- Shift_JIS table
- Japanese character encoding table
- Shift_JIS and Ku,Ten
- English wikipedia article
- has JIS X 0208 to Shift_JIS converting formula
- Calculation ten and ku
- JIS X 0208
- [0x20 + ku, 0x20 + ten]
- kanji encoding
- JIS X 0201
- ASCII extension with *kana* and japanese symbols
- encoding that can allow JIS X 0208 and JIS X 0201
- was popular until UTF-8 gain status
- ISO/IEC 8859-1(usually "Latin-1")
- codepage 1252
- Shinonome font has the support.
- Accent in ASCII
- unix FAQ
- code page table
- If "_UNICODE" or "UNICODE" isn't defined local code page is used in string passing.
- unicode api has "W" suffix
- code page api has "A" suffix
- to support either of API use <tchar.h>
- mingw main function
- Windows macro
- No wchar_t in Windows
- use to compare unicode string
- has 4 type
- C library for utf-8 normalization.
- supports all 4 normalization
- returned string is allocated with malloc() so needs to be deallocated with free()
- has ruby, posgresql binding
- encoding to use unicode in "const char*" or std::string.
- newer encoding but well used.
- needs little complex decode but is easier to use in conventional string system.
- no duplication with ASCII
- widely used to exchange string.
- screen utf-8 settings
- using UTF-8 in windows
- unix utf-8 filename
- python utf-8 filename
- Mostly used in Windows.
- needs to decode to use as Unicode so use UTF-32 as possible.
- uint32_t array of unicode.
- good for internal use but not good for exchanging.
- endian matters.