Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

uniname(1) [debian man page]

uniname(1)						      General Commands Manual							uniname(1)

NAME
uniname - Name the characters in a Unicode text file SYNOPSIS
uniname ([option flags]) (<file name>) If no input file name is supplied, uniname reads from the standard input. DESCRIPTION
uniname names the characters in a Unicode text file. For each character, uniname defaults to printing the character offset, the byte off- set, the hexadecimal UTF-32 character code, the encoding as a sequence of hex byte values, the glyph, and the character's Unicode name. Command line flags allow undesired information to be suppressed. Glyphs that do not display nicely, such as control characters and spaces, are not displayed. For the Latin-1 control characters, whose official Unicode name is "control", the real name is given. Character and byte offsets both start from 0. Where a character does not have a unique Unicode name, as is the case with Chinese characters, the character is identified as "character in such-and-such a range". However, if the character is a Chinese character listed in Nelson's dictionary, the Nelson number is supplied. By default, input is expected to be UTF-8. Native order UTF-32 may be specified via the command line flag If invalid UTF8 is encountered, an explanation is printed as to why it is invalid. -q. COMMAND LINE FLAGS
-A Skip ASCII whitespace characters. -a Skip ASCII characters. -B Skip characters within the Basic Multilingual Plane. -b Suppress printing of byte offset. -c Suppress printing of character offset. -e Suppress printing of encoding. -g Suppress printing of glyph. -h Print usage information. -l Print line number. -n Suppress printing of Unicode name. -p Suppress printing of headers every screenfull. -q Input is native order UTF-32. -r Print Unicode range. The ranges reported include both official Unicode ranges and the constructed language ranges within the Pri- vate Use Areas registered with the Conscript Unicode Registry (http://www.evertype.com/standards/csur/). -s <character offset> Skip to specified character offset. -S <byte offset> Skip to specified byte offset. Note that even if the file consists of well-formed Unicode there is no guarantee that the byte sequence beginning at an arbitrary byte will be valid Unicode. This option is provided for use where other programs generate only byte offsets or where it is necessary to skip over damaged Unicode. In most circumstances use of a character offset will be more apprpriate. If a byte offset is used, the character offsets shown are with respect to the beginning of the section of the file exam- ined rather than the beginning of the file. -u Suppress printing of UTF32 code. -V Validate the input. In this case, nothing is done other than determine whether the input is valid UTF-8 Unicode. If it is, no output is produced and the program exits with status 0. If invalid UTF-8 is encountered, the program reports the location of the first invalid UTF-8 encountered, explains why it is invalid, and exits with status 1. -v Print version information. SEE ALSO
unidesc REFERENCES
Unicode Standard, version 5.1 AUTHOR
Bill Poser billposer@alum.mit.edu LICENSE
GNU General Public License February, 2009 uniname(1)

Check Out this Related Man Page

UTF(6)								   Games Manual 							    UTF(6)

NAME
UTF, Unicode, ASCII, rune - character set and format DESCRIPTION
The Plan 9 character set and representation are based on the Unicode Standard and on the ISO multibyte UTF-8 encoding (Universal Character Set Transformation Format, 8 bits wide). The Unicode Standard represents its characters in 16 bits; UTF-8 represents such values in an 8-bit byte stream. Throughout this manual, UTF-8 is shortened to UTF. In Plan 9, a rune is a 16-bit quantity representing a Unicode character. Internally, programs may store characters as runes. However, any external manifestation of textual information, in files or at the interface between programs, uses a machine-independent, byte-stream encoding called UTF. UTF is designed so the 7-bit ASCII set (values hexadecimal 00 to 7F), appear only as themselves in the encoding. Runes with values above 7F appear as sequences of two or more bytes with values only from 80 to FF. The UTF encoding of the Unicode Standard is backward compatible with ASCII: programs presented only with ASCII work on Plan 9 even if not written to deal with UTF, as do programs that deal with uninterpreted byte streams. However, programs that perform semantic processing on ASCII graphic characters must convert from UTF to runes in order to work properly with non-ASCII input. See rune(2). Letting numbers be binary, a rune x is converted to a multibyte UTF sequence as follows: 01. x in [00000000.0bbbbbbb] -> 0bbbbbbb 10. x in [00000bbb.bbbbbbbb] -> 110bbbbb, 10bbbbbb 11. x in [bbbbbbbb.bbbbbbbb] -> 1110bbbb, 10bbbbbb, 10bbbbbb Conversion 01 provides a one-byte sequence that spans the ASCII character set in a compatible way. Conversions 10 and 11 represent higher- valued characters as sequences of two or three bytes with the high bit set. Plan 9 does not support the 4, 5, and 6 byte sequences pro- posed by X-Open. When there are multiple ways to encode a value, for example rune 0, the shortest encoding is used. In the inverse mapping, any sequence except those described above is incorrect and is converted to rune hexadecimal 0080. FILES
/lib/unicode table of characters and descriptions, suitable for look(1). SEE ALSO
ascii(1), tcs(1), rune(2), keyboard(6), The Unicode Standard. UTF(6)
Man Page