Subject: Re: ucat - msg#00044

Previous Message by Date: click to view message preview

posgtres/emacs interface utf-8 enablement

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@xxxxxxxxxxxxxxxxxxxxxxxxxxxx for more info. The attached patch, applied to http://www.chez.com/emarsden/download/pg.el makes it possible to interface to PostgreSQL from Emacs/Mule-UCS using Unicode. Without this patch, the Lisp code crashes. PostgreSQL multibyte characters can also be displayed using psql under the new xterm with option -u8. PostreSQL should be recompiled after ./configure --with-mb=UNICODE. Moreover, I attached a better version of the 'textcoding' scsh program sent here yesterday. If I have time I'd like to try to bind iconvlib into scsh.

Next Message by Date: click to view message preview

Fw: Document Action: UTF-16, an encoding of ISO 10646 to Informational

Hi! JFYI. New RFC for "UTF-16". ( The archive of <ietf-charsets@xxxxxxxx> : http://lists.w3.org/Archives/Public/ietf-charsets/ ) -----Original Message----- From: The IESG <iesg-secretary@xxxxxxxx> To: IETF-Announce: ; <IETF-Announce: ;> Sender: scoya@xxxxxxxxxxxxxxxxx Resent-to: ietf-charsets@xxxxxxxx Cc: RFC Editor <rfc-editor@xxxxxxx>; Internet Architecture Board <iab@xxxxxxx> Date: 23 Jan 2000, 5:08 Subject: Document Action: UTF-16, an encoding of ISO 10646 to Informational The IESG has approved publication of the Internet-Draft 'UTF-16, an encoding of ISO 10646' <draft-hoffman-utf16-05.txt> as an Informational RFC. This has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact persons are Patrik Faltstrom and Keith Moore. Note to RFC Editor: 1. Please add the following IANA consideration section: IANA Considerations IANA is to register the character sets found in Appendixes A.1, A.2, and A.3 according to RFC 2278, using registration templates found in those appendixes. 2. Please change last paragraph of section 1.1 according to the following: --- OLD TEXT The IETF policy on character sets and languages [CHARPOLICY] says that IETF protocols MUST be able to use the UTF-8 character encoding scheme [UTF-8]. Although UTF-8 has many beneficial properties, such as the direct encoding of US-ASCII characters, re-synchronization after loss of octets and immunity to the byte-order issue (see 3.1 below), it is less dense than UTF-16 for characters whose values are between 0x0800 and 0xFFFF. Some products and network standards already specify UTF-16, making it an important encoding for the Internet. --- END --- NEW TEXT The IETF policy on character sets and languages [CHARPOLICY] says that IETF protocols MUST be able to use the UTF-8 character encoding scheme [UTF-8]. Some products and network standards already specify UTF-16, making it an important encoding for the Internet. This document is not an update to the [CHARPOLICY] document, only a description of the UTF-16 encoding. --- END - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/lists/

Previous Message by Thread: click to view message preview

posgtres/emacs interface utf-8 enablement

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@xxxxxxxxxxxxxxxxxxxxxxxxxxxx for more info. The attached patch, applied to http://www.chez.com/emarsden/download/pg.el makes it possible to interface to PostgreSQL from Emacs/Mule-UCS using Unicode. Without this patch, the Lisp code crashes. PostgreSQL multibyte characters can also be displayed using psql under the new xterm with option -u8. PostreSQL should be recompiled after ./configure --with-mb=UNICODE. Moreover, I attached a better version of the 'textcoding' scsh program sent here yesterday. If I have time I'd like to try to bind iconvlib into scsh.

Next Message by Thread: click to view message preview

Re: Progress on xterm with combining characters!

Robert Brady recommended > Once compiled and the ucs-fonts on the fontpath, run it like "./xterm -u8 > -fn 9x18". It should find the corresponding double wide font automatically. but this doesn't work here: $ xterm -u8 -fn 9x18 & unable to open font "9x18", trying "fixed".... My xterm #122 works fine with -u8 and my fonts are there ~$ xlsfonts -fn '*18*iso10646*' -misc-fixed-bold-r-normal--18-120-100-100-c-90-iso10646-1 -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1 -misc-fixed-medium-r-normal-ja-18-120-100-100-c-180-iso10646-1 But I only get either -fn '*9x18*iso10646*' : single width European only or -fn '*ja-18*iso10646*' : double width everything but not a terminal that distinguishes between single and double width.