UTF-1 is a method of transforming ISO/IEC 10646/Unicode into a stream of bytes. Its design does not provide self-synchronization, which makes searching for substrings and error recovery difficult. It reuses the ASCII printing characters for multi-byte encodings, making it unsuited for some uses (for instance Unix filenames cannot contain the byte value used for forward slash). UTF-1 is also slow to encode or decode due to its use of division and multiplication by a number which is not a power of 2. Due to these issues, it did not gain acceptance and was quickly replaced by UTF-8.
| Attributes | Values |
|---|
| rdf:type
| |
| rdfs:label
| - UTF-1 (de)
- UTF-1 (ko)
- UTF-1 (pt)
- UTF-1 (en)
- UTF-1 (zh)
|
| rdfs:comment
| - UTF-1 is a method of transforming ISO/IEC 10646/Unicode into a stream of bytes. Its design does not provide self-synchronization, which makes searching for substrings and error recovery difficult. It reuses the ASCII printing characters for multi-byte encodings, making it unsuited for some uses (for instance Unix filenames cannot contain the byte value used for forward slash). UTF-1 is also slow to encode or decode due to its use of division and multiplication by a number which is not a power of 2. Due to these issues, it did not gain acceptance and was quickly replaced by UTF-8. (en)
- UTF-1은 국제 문자 세트/유니코드를 바이트 스트림으로 변환하는 한 방법이다. 설계 상의 이유로, 디코딩이 문자 중간에 시작하면 재동기화가 불가능하며 검색 루틴은 이와 함께 신뢰성있게 사용할 수 없다. UTF-1은 또한 제곱이 아닌 수의 나누기를 사용하기 때문에 상당히 느리다. 이러한 문제로 UTF-1은 폭넓게 채택되지 못했으며 UTF-8로 대체되었다. (ko)
- UTF-1 é um formato de transformação de ISO 10646/Unicode em fluxos de bytes, a fim de serialização. Devido ao seu formato não é possível resincronizar se a decodificação começa no meio dum caractere (o que dificulta o truncamento) e rotinas de busca de caractere não podem ser usadas de forma confiável. Dados tais problemas, esse padrão nunca ganhou grande adoção, sendo quase que completamente substituído pelo UTF-8. (pt)
- UTF-1是一种将ISO 10646 / Unicode转化成字节流的方式。由于其本身的设计问题，如果自中间的一个字符开始解码，UTF-1將無法重新同步（這造成擷取的困難），而且UTF-1也沒辦法進行可靠的字节搜索。又因为UTF-1使用的除数不是2的幂，所以转化得也相当缓慢。由于以上这些问题，UTF-1从来没有得到广泛採用，并已被UTF-8所取代。 (zh)
- UTF-1 war das erste UCS Transformation Format für Unicode und ISO 10646 und wurde 1993 im Anhang G der ursprünglichen Version von ISO 10646 veröffentlicht, ist jedoch heute nicht mehr Teil dieser Norm. UTF-1 ist kompatibel zu ISO 2022. Aufgrund dieses Nachteils wurde später eine andere Kodierung für Unicode entwickelt, welche anfangs „UTF-FSS“ (file system safe) genannt wurde und sich heute unter dem Namen UTF-8 allgemein durchgesetzt hat. (de)
|
| name
| |
| dcterms:subject
| |
| Wikipage page ID
| |
| Wikipage revision ID
| |
| Link from a Wikipage to another Wikipage
| |
| Link from a Wikipage to an external page
| |
| sameAs
| |
| dbp:wikiPageUsesTemplate
| |
| classification
| |
| lang
| |
| mime
| |
| next
| |
| status
| - Obscure, of mainly historical interest. (en)
|
| has abstract
| - UTF-1 war das erste UCS Transformation Format für Unicode und ISO 10646 und wurde 1993 im Anhang G der ursprünglichen Version von ISO 10646 veröffentlicht, ist jedoch heute nicht mehr Teil dieser Norm. UTF-1 ist kompatibel zu ISO 2022. ASCII-Zeichen, C0- und C1-Steuerzeichen werden wie in ISO 8859 unverändert (1:1) kodiert. Andere Zeichen werden – über eine relativ rechenaufwändige Modulo-190-Arithmetik – als Zeichenfolgen von 2, 3 oder 5 Byte Länge kodiert. Dabei können auch ASCII-Zeichen Teil dieser Zeichenfolgen sein. Das hat den Nachteil, dass zum Beispiel der Schrägstrich in so einer Zeichenfolge enthalten sein kann, so dass diese Kodierung nicht für Dateinamen verwendet werden kann. Aufgrund dieses Nachteils wurde später eine andere Kodierung für Unicode entwickelt, welche anfangs „UTF-FSS“ (file system safe) genannt wurde und sich heute unter dem Namen UTF-8 allgemein durchgesetzt hat. (de)
- UTF-1 is a method of transforming ISO/IEC 10646/Unicode into a stream of bytes. Its design does not provide self-synchronization, which makes searching for substrings and error recovery difficult. It reuses the ASCII printing characters for multi-byte encodings, making it unsuited for some uses (for instance Unix filenames cannot contain the byte value used for forward slash). UTF-1 is also slow to encode or decode due to its use of division and multiplication by a number which is not a power of 2. Due to these issues, it did not gain acceptance and was quickly replaced by UTF-8. (en)
- UTF-1은 국제 문자 세트/유니코드를 바이트 스트림으로 변환하는 한 방법이다. 설계 상의 이유로, 디코딩이 문자 중간에 시작하면 재동기화가 불가능하며 검색 루틴은 이와 함께 신뢰성있게 사용할 수 없다. UTF-1은 또한 제곱이 아닌 수의 나누기를 사용하기 때문에 상당히 느리다. 이러한 문제로 UTF-1은 폭넓게 채택되지 못했으며 UTF-8로 대체되었다. (ko)
- UTF-1 é um formato de transformação de ISO 10646/Unicode em fluxos de bytes, a fim de serialização. Devido ao seu formato não é possível resincronizar se a decodificação começa no meio dum caractere (o que dificulta o truncamento) e rotinas de busca de caractere não podem ser usadas de forma confiável. Dados tais problemas, esse padrão nunca ganhou grande adoção, sendo quase que completamente substituído pelo UTF-8. (pt)
- UTF-1是一种将ISO 10646 / Unicode转化成字节流的方式。由于其本身的设计问题，如果自中间的一个字符开始解码，UTF-1將無法重新同步（這造成擷取的困難），而且UTF-1也沒辦法進行可靠的字节搜索。又因为UTF-1使用的除数不是2的幂，所以转化得也相当缓慢。由于以上这些问题，UTF-1从来没有得到广泛採用，并已被UTF-8所取代。 (zh)
|
| encodes
| |
| extends
| |
| gold:hypernym
| |
| prov:wasDerivedFrom
| |
| page length (characters) of wiki page
| |
| foaf:isPrimaryTopicOf
| |
| is Link from a Wikipage to another Wikipage
of | |
| is Wikipage redirect
of | |
| is Wikipage disambiguates
of | |
| is prev
of | |
| is foaf:primaryTopic
of | |
![[RDF Data]](/fct/images/sw-rdf-blue.png)
![[cxml]](/fct/images/cxml_doc.png)
![[csv]](/fct/images/csv_doc.png)
![[text]](/fct/images/ntriples_doc.png)
![[turtle]](/fct/images/n3turtle_doc.png)
![[ld+json]](/fct/images/jsonld_doc.png)
![[rdf+json]](/fct/images/json_doc.png)
![[rdf+xml]](/fct/images/xml_doc.png)
![[atom+xml]](/fct/images/atom_doc.png)
![[html]](/fct/images/html_doc.png)