
	Where results make sense

Topic: UTF

Related Topics

Telephone tapping

Traveling salesman problem

CVR

Swift Boat Veterans for Truth

Lutefisk

Beetle Bailey

XM8

Benedictines

Geometric shape

Japan

Mort Walker

George Dantzig

MPF

In the News (Fri 17 Feb 12)

EXECUTIVE POWER

Iran

ANALYSIS

Pakistan

Family compact

	FAQ - UTF-8, UTF-16, UTF-32 & BOM
		Each UTF is reversible, thus every UTF supports lossless round tripping: mapping from any Unicode coded character sequence S to a sequence of bytes and back will produce S again.
		The SCSU compression method, even though it is reversible, is not a UTF because the same string can map to very many different byte sequences, depending on the particular SCSU compressor.
		The BE form uses big-endian byte serialization (most significant byte first), the LE form uses little-endian byte serialization (least significant byte first) and the unmarked form uses big-endian byte serialization by default, but may include a byte order mark at the beginning to indicate the actual byte serialization used.
	www.unicode.org /faq/utf_bom.html (4895 words)

	ongoing · Characters vs. Bytes
		UTF Along with the characters, Unicode also defines methods for storing them in byte sequences in a computer.
		“UTF” may be explained as standing for Unicode Transformation Format, or UCS Transformation format where “UCS”; stands for Unicode Character Set.
		None of the three UTF approaches (-32, -16, -8) are really better than any of the others.
	www.tbray.org /ongoing/When/200x/2003/04/26/UTF (2663 words)

	UTF - UGAMP Transfer Format (Site not responding. Last check: 2007-10-22)
		This document describes the structure of the UGAMP Transfer File (UTF) intended for use in transferring data between computers, mainly for local plotting of data but with the flexibility to allow more general data transfer.
		UTFs are generated by the UMAP from post-processed files produced from a run of the UGAMP GCM.
		This is the method by which data is plotted from the UGAMP model.
	www.atm.ch.cam.ac.uk /acmsu/utf (171 words)

	RFC 2279 (rfc2279) - UTF-8, a transformation format of ISO 10646 (Site not responding. Last check: 2007-10-22)
		Multi-octet characters, however, are not compatible with many current applications and protocols, and this has led to the development of a few so-called UCS transformation formats (UTF), each with different characteristics.
		UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values.
		This situation has led to the development of so-called UCS transformation formats (UTF), each with different characteristics.
	www.faqs.org /rfcs/rfc2279.html (2449 words)

	[No title]
		We had used the original UTF from ISO 10646 to make Plan 9 support 16-bit characters, but we hated it.
		We were close to shipping the system when, late one afternoon, I received a call from some folks, I think at IBM - I remember them being in Austin - who were in an X/Open committee meeting.
		To: r@google.com Subject: utf digging Date-Sent: Saturday, June 07, 2003 7:46 PM -0400 bootes's /sys/src/libc/port/rune.c changed from the division-heavy old utf on sep 4 1992.
	www.cl.cam.ac.uk /~mgk25/ucs/utf-8-history.txt (2417 words)

	Unicode Transformation Formats
		This UTF shares most of UTF-8's nice and not-so-nice properties inclusive of ASCII and sort-order transparency, disambiguity, self-segregation, and 2/3-byte compactness and adds
		That means that it will not mess up terminals that use the C1 controls and allows UTF strings to be cut and pasted between Latin1 applications.
		Besides that, the UTF representation of Latin1's accented letters contains the original code prefixed by a pound sign (£) which means that it readability is remained in Latin1 applications.
	www.czyborra.com /utf (5676 words)

	Gentoo Linux Documentation -- Using UTF-8 with Gentoo
		Unicode has been mapped in many different ways, but the two most common are UTF (Unicode Transformation Format) and UCS (Universal Character Set).
		A number after UTF indicates the number of bits in one unit, while the number after UCS indicates the number of bytes.
		UTF-8 has become the most widespread means for the interchange of Unicode text as a result of its eight-bit clean nature, and it is the subject of this document.
	www.gentoo.org /doc/en/utf-8.xml (3281 words)

	RFC 2044 (rfc2044)
		Abstract The Unicode Standard, version 1.1, and ISO/IEC 10646-1:1993 jointly define a 16 bit character set which encompasses most of the world's writing systems.
		16-bit characters, however, are not compatible with many current applications and protocols, and this has led to the development of a few so-called UCS transformation formats (UTF), each with different characteristics.
		UTF-8, the object of this memo, has the characteristic of preserving the full US-ASCII range: US-ASCII characters are encoded in one octet having the usual US-ASCII value, and any octet with such a value can only be an US-ASCII character.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc2044.html (1426 words)

	UTF-8 and Unicode FAQ
		Note that in multibyte sequences, the number of leading 1 bits in the first byte is identical to the number of bytes in the entire sequence.
		The official name and spelling of this encoding is UTF-8, where UTF stands for UCS Transformation Format.
		There is an old UTF locale, but it is incomplete and uses the now obsolete
	www.cl.cam.ac.uk /~mgk25/unicode.html (14460 words)

	[No title]
		When an XML MIME entity is encoded in "utf-16le" or "utf-16be", it MUST NOT begin with the BOM but SHOULD contain an encoding declaration.
		Conversion from "utf-16" to "utf- 16be" or "utf-16le" and conversion in the other direction MUST strip or add the BOM, respectively.
		Fragment Identifiers Section 4.1 of [RFC2396] notes that the semantics of a fragment identifier (the part of a URI after a "#") is a property of the data resulting from a retrieval action, and that the format and interpretation of fragment identifiers is dependent on the media type of the retrieval result.
	www.rfc-editor.org /rfc/rfc3023.txt (10079 words)

	[No title]
		In doing so it defines a solution which will still allow the installed base to interoperate with new clients and servers.
		This document enhances the capabilities of the File Transfer Protocol by removing the 7-bit restrictions on pathnames used in client commands and server responses, RECOMMENDs the use of a Universal Character Set (UCS) ISO/IEC 10646 [ISO-10646], RECOMMENDs a UCS transformation format (UTF) UTF-8 [UTF-8], and defines a new command for language negotiation.
		The recommendations made in this document are consistent with the recommendations expressed by the IETF policy related to character sets and languages as defined in RFC 2277 [RFC2277].
	www.rfc-editor.org /rfc/rfc2640.txt (5636 words)

	Perl, Unicode and i18N FAQ (Site not responding. Last check: 2007-10-22)
		Search for utf to see what was broken in the official release of 5.6.0
		Input from files or pipes would be mapped on the fly from the source encoding to Perl's internal encoding, either UTF or OEM
		Here's a simple program that converts from native encodings to various UTFs using the above CPAN modules:
	rf.net /~james/perli18n.html (10570 words)

	Unicode Mutt (Site not responding. Last check: 2007-10-22)
		If the output from the command "locale charmap" is "UTF-8" then you already have one.
		grep -i utf" to see if you have any UTF-8 locales, such as "C@utf-8" or "en_GB.UTF-8".
		If you do, try something like "LANG=en_GB.UTF-8 xterm &" to run a terminal in that locale.
	rano.org /mutt.html (1272 words)

Try your search on: Qwika (all wikis)