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

On 2005.09.04 01:13:51 +0200, rudolf wrote:
| Rui Paulo wrote:
| >On 2005.08.26 23:14:20 +0000, rudolf wrote:
| >| I can't make the html files with the charset=3DISO-8859-2 head, with=
=20
| >| "XML_ENCODING=3D iso-8859-2" in Makefile I achieved only ISO-8859-1 wi=
th=20
| >| the specific czech characters in body as html entities. So the one htm=
l=20
| >| file currently published is generated without "XML_ENCODING=3D iso-885=
9-2"=20
| >| in Makefile and the charset is manually changed. What's the canonical=
=20
| >| way of generating different charset head here, please?
| >
| >Isn't best to use XML entities to display czech characters?
|=20
| IMHO, no.

Why ?

| >| In the chap-intro-applications section is also a todo mark:
| >| <!-- *** TODO *** other emulations -->
| >| Here definitely should be the NetBSD's capabiliy of backward=20
| >| compatibility. I've not seen very much operating systems, but I think=
=20
| >| the NetBSD's smooth way of upgrades makes it really different from the=
m.
| >
| >Err, what has backward compatibility to do with emulations ? I think that
| >comment is there because the next <para> misses some emulations like
| >Darwin, OSF1, Linux, Irix, etc.
| >
| >		-- Rui Paulo
|=20
|=20
| Maybe I am just being confused by the name? Is the in-kernel mechanism=20
| totally different?

A little. What that paragraph means is located in src/sys/compat.

		-- Rui Paulo

--y0ulUmNC+osPPQO6
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFDGjEEZPqyxs9FH4QRArJRAKCqLXx/SRRth9BB0+aoZxahMBOj6gCfUUux
SIgD5m7VBUssJIenXVRB35E=
=XllT
-----END PGP SIGNATURE-----

--y0ulUmNC+osPPQO6--