Date: Fri, 29 Aug 2008 10:40:32 -0700 From: "Loren M. Lang" <lorenl@north-winds.org> To: freebsd-i18n@freebsd.org Subject: Re: Unicode-based FreeBSD Message-ID: <1220031632.7224.66.camel@habakkuk.aloha.tallye.com> In-Reply-To: <200808241415.31812.mitchell@wyatt672earp.force9.co.uk> References: <3cb459ed0808221700w335b0906g6901d8b8bec4dad9@mail.gmail.com> <200808241415.31812.mitchell@wyatt672earp.force9.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-ilcSBMzPTU9neE/PAI1a Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hmm, I seem to have sent this from the wrong identity, take two: On Sun, 2008-08-24 at 14:15 +0100, Frank wrote: > Even if you use an English locale with occasional accented letters, you might =20 > want ISO-8859-1 for legacy compatibility. Also I multiboot, sharing a Data=20 > Partition with other Unix flavours using ISO-8859-1. And I need to import=20 > previous tracks during Multisession CD/DVD Archive/Backup operations. And=20 > naturally I have legacy documents in ISO-8859-1, which corresponds to my=20 > old Windows Codepage 1252. As far other Unices, all modern ones support a full Unicode environment and I am just lucky enough that all mine are a recent enough install that I've been able to use UTF-8 since install. The filesystems all use UTF-8 for filenames and documents and are compatible across each other. Any CD-ROM using Microsoft's Joliet extensions for long filenames use Unicode as there internal encoding and FreeBSD has to translate that to the local encoding to display them properly, though, I am not sure if FreeBSD currently supports converting to UTF-8. >=20 > I've heard that Japanese and Chinese users prefer their own coding systems,=20 > because the Unicode Character Set in these languages is limited. Korean also=20 > has Combining Characters, and UTF-8 comes in 3 different Levels depending on=20 > its ability to cope with this. Maybe you need some contacts in other=20 > countries. Actually, China's official character set is GB18030. GB18030 is fully backward compatible to their old character set, GB2312, but contains an identical set of characters as is in Unicode. It's basically their version of UTF-8. >=20 > Faictz Ce Que Vouldras: Frank Mitchell >=20 > On Saturday 23 August 2008 01:00:28 Alexander Churanov wrote: > > > > I am interested in FreeBSD internationalization and unicode support. I > > already spent some time examining the source of syscons. I think that > > syscons is the main problem in bringing full UTF-8 support to FreeBSD out > > of box. It seems that I am ready with the solution. That's why I am writing > > to this list. > > > > 0) Is moving to UTF-8 from 8-bit codepages desired for FreeBSD? > > > _______________________________________________ > freebsd-i18n@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-i18n > To unsubscribe, send any mail to "freebsd-i18n-unsubscribe@freebsd.org" >=20 --=20 Loren M. Lang lorenl@north-winds.org http://www.north-winds.org/ Public Key: ftp://ftp.north-winds.org/pub/lorenl_pubkey.asc Fingerprint: 10A0 7AE2 DAF5 4780 888A 3FA4 DCEE BB39 7654 DE5B --=-ilcSBMzPTU9neE/PAI1a Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIuDSQ3O67OXZU3lsRAkY6AKDA7MkqdnbtFn9McGBtlcT5tMLpWACfd30p hnmw1BeuActPO7cq5ByE0rI= =5rbm -----END PGP SIGNATURE----- --=-ilcSBMzPTU9neE/PAI1a--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1220031632.7224.66.camel>