Searched hist:104828 (Results 1 - 6 of 6) sorted by relevance
/freebsd-10.2-release/lib/libc/locale/ | ||
H A D | utf8.5 | 104828 Thu Oct 10 22:56:18 MDT 2002 tjr Add a UTF-8 encoding method, which will eventually replace the antique "UTF2" method. Although UTF-8 and the old UTF2 encoding are compatible for 16-bit characters, the new UTF-8 implementation is much more strict about rejecting malformed input and also handles the full 31 bit range of characters. |
H A D | multibyte.3 | diff 104828 Thu Oct 10 22:56:18 MDT 2002 tjr Add a UTF-8 encoding method, which will eventually replace the antique "UTF2" method. Although UTF-8 and the old UTF2 encoding are compatible for 16-bit characters, the new UTF-8 implementation is much more strict about rejecting malformed input and also handles the full 31 bit range of characters. |
H A D | setlocale.3 | diff 104828 Thu Oct 10 22:56:18 MDT 2002 tjr Add a UTF-8 encoding method, which will eventually replace the antique "UTF2" method. Although UTF-8 and the old UTF2 encoding are compatible for 16-bit characters, the new UTF-8 implementation is much more strict about rejecting malformed input and also handles the full 31 bit range of characters. |
H A D | utf8.c | 104828 Thu Oct 10 22:56:18 MDT 2002 tjr Add a UTF-8 encoding method, which will eventually replace the antique "UTF2" method. Although UTF-8 and the old UTF2 encoding are compatible for 16-bit characters, the new UTF-8 implementation is much more strict about rejecting malformed input and also handles the full 31 bit range of characters. |
H A D | Makefile.inc | diff 104828 Thu Oct 10 22:56:18 MDT 2002 tjr Add a UTF-8 encoding method, which will eventually replace the antique "UTF2" method. Although UTF-8 and the old UTF2 encoding are compatible for 16-bit characters, the new UTF-8 implementation is much more strict about rejecting malformed input and also handles the full 31 bit range of characters. |
H A D | setrunelocale.c | diff 104828 Thu Oct 10 22:56:18 MDT 2002 tjr Add a UTF-8 encoding method, which will eventually replace the antique "UTF2" method. Although UTF-8 and the old UTF2 encoding are compatible for 16-bit characters, the new UTF-8 implementation is much more strict about rejecting malformed input and also handles the full 31 bit range of characters. |
Completed in 121 milliseconds