Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Jun 2006 11:09:13 -0400
From:      "J.R. Oldroyd" <fbsd@opal.com>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Unicode (was Re: Updating ncurses in base)
Message-ID:  <20060627150913.GD45513@linwhf.opal.com>
In-Reply-To: <20060627131313.2lvy38lg08kwo008@netchild.homeip.net>
References:  <6eb82e0606091906j7d9f69aarcf1f9738c7565677@mail.gmail.com> <20060625221640.GI48766@linwhf.opal.com> <20060626014939.GA74292@over-yonder.net> <20060626160245.GM48766@linwhf.opal.com> <20060627131313.2lvy38lg08kwo008@netchild.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--t0UkRYy7tHLRMCai
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Jun 27, 13:13, Alexander Leidinger wrote:
> >
> >	- we may need to update the base fonts so that more
> >	  iso10646 ones have more complete character support
>=20
> If there's not a BSD licensed replacement with at least the same =20
> quality, this may be the hardest part.
>=20
I believe our 10646 fonts are those developed my Markus Kuhn at
Cambridge, UK and documented here:
	http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html
I'm not sure if ours are up-to-date or not.


> >	- utf-8 will have to be made the default character
> >	  encoding in startup scripts for the various utilities
> >	  and ports that are affected
>=20
> Why? The start scripts are written in english and I doubt we will =20
> start to use translated ones. So all they use is/should be 7-bit =20
> clean. Wy do we need to make UTF-8 the default for them? If someone =20
> wants to use UTF-8, he can set the locale accordingly, but for the =20
> rest of the system I don't see a point in switching.
>=20
Perhaps I wasn't clear with this comment.  What I meant was that
defaults for tools like the apache web server will need to change.
Since apache can serve text and html files which users will edit
with their editor and which will therefore now contain UTF-8-encoded
characters, apache's default will also need to be UTF-8.

Same for things like cups/groff and any other tool/server that
processes files which might contain 8-bit characters and which
care about the encoding.

	-jr

--t0UkRYy7tHLRMCai
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iQDVAwUBRKFKGUkkqUax7f6FAQKtQgX9G2VTZLzwhpojUPsO4scR8D3JzuoorjZH
unF+jxZiJpzMA8jK5rOFTpMt/RuhkqLEyKzFmZgBRME+sHBqSut+LEjwDZqzORG7
8/jWogl0JB554LenHKia9Qrv62j/wcqaMVEVnXq2rcYdtRz1JmPC6gXvw3zq12ui
v8xdREDL6PvVuKDIPRq6Gpqs3V3kQdtImX+OJ+W+QwrNYbRzwUmWr4iTUE40sIvD
ZK9EjmYVNNDcSP3fmSQf+PK0eYymAfBY
=ctah
-----END PGP SIGNATURE-----

--t0UkRYy7tHLRMCai--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060627150913.GD45513>