Date: Wed, 20 Jul 2016 21:08:41 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Jonathan Anderson <jonathan@FreeBSD.org>, Tim =?utf-8?Q?=C4=8Cas?= <darkuranium@gmail.com>, freebsd-current@freebsd.org Subject: Re: UTF-8 by default? Message-ID: <20160720190841.iuplrbhmdq7sr6br@ivaldir.etoilebsd.net> In-Reply-To: <20160720183814.GA77261@ymer.vnode.se> References: <CANd9X8f5wHvdwN_XZ2y0qsiydYyb=NKLXF0k65S0_TiuWHeGKA@mail.gmail.com> <B68D48ED-66CA-4E5B-8ED2-555B397AC73E@FreeBSD.org> <20160720140741.yi7vfgmmqtg6eprx@ivaldir.etoilebsd.net> <20160720183814.GA77261@ymer.vnode.se>
next in thread | previous in thread | raw e-mail | index | archive | help
--eyp6ncyn5hgcup43 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 20, 2016 at 08:38:14PM +0200, Joel Dahl wrote: > On Wed, Jul 20, 2016 at 04:07:41PM +0200, Baptiste Daroussin wrote: > > On Wed, Jul 20, 2016 at 10:47:45AM -0230, Jonathan Anderson wrote: > > > On 20 Jul 2016, at 9:13, Tim =C4=8Cas wrote: > > >=20 > > > > So, without further ado: > > > > 1) What are the reasons that UTF-8 isn't the default yet? > > > > 2) Would it be possible to make this the default in 11.0? What about > > > > 12.0? > > > > 3) Assuming an effort is started towards making UTF-8 the default, > > > > what changes would be required? > > >=20 > > > At least according to one of my students (who makes more extensive us= e of > > > i18n than I do), enabling UTF-8 by default is pretty straightforward: > > >=20 > > > https://github.com/musec/freebsd/wiki/Common-setup#utf-8-support > >=20 > > the LC_COLLATE=3DC is not needed anymore with freebsd 11+ > > >=20 > > > If there's anything missing there, I'd love to hear about it. > > >=20 > > - unicode support in our old groff is pretty bad, I plan to replace i= t with > > heirloom-doctools which does handle unicode propertly (as far I hav= e tested > > at least) >=20 > I haven't really been paying attention lately so things might have change= d, > but why can't we just remove groff now? We have mdocml, and for people th= at > really need the groff functionality can just install it or heirloom-docto= ols > from ports. The initial plan was to remove groff after we imported mdocml= , but > it was never removed and I lost interest, so again, things might have cha= nged > since then. We have roff documentation in based, plus a lot of people argues that not h= avin a roff toolchain in base is an issue for them. heirloom doctools upstream is friendly, they fixed all the bugs I reported = or merged my fixes if needed, they have a good compatibility so the fallback in man(1) could be done on something in base if mandoc cannot render properly = some manpages. Upstream is CDDL but all new code is BSD licensed. Importing is not hard, just need some motivation to finish all the required makefiles :) Best regards, Bapt --eyp6ncyn5hgcup43 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXj8wwAAoJEGOJi9zxtz5aJPwP/ilpKXKH10yDINtdbTRbPa2O 5js0jeZopx1lu6+0vN8eksOtNyPBNUPnw/XjipDhOGaAdrk70zoCDN4NjR1Ysnsb acnUFcoLJlNO3OUrTzaCvrYIs4JnD5nZ3dgBc+4cZaTCrzehAWgO2GsFA6fxm2CC 5B4T21E1WlLFiqa06U/HUwxLT2ShZjF1r2D57l/YI9et8cCFpAjLaqPguyCmwbPp S61ymbfmBZ0xiKJ9muy1HZj0AsQgfeUzSwJcvZmdsVCcoAHxy4NrjjuAcy0NRil+ E09XAmgMnKHSEO02ptGHK5P6nVnbO5dZ8BmKnfHjJEXUZWzZr+ojlbH4xLVEJ33T 4gGlql1gUDq50/tP+ss5gZxcirglyu0yWFavyIgezHen4HDRceRbtuK+a9NL93Br oP3MTvx/hZhyMQkpp0pXWShpG6ubjxehG6PthEGach3TEAxr1pjj0jM0abQTPlyK xs9YibvLdYh2M8j38kiCkrBW1hvYWmPHd1jtGawEqTp3RT0T32FlBqPZMZT1SukQ 5CmaSKXd5MTBPv7pUOTtuCRHd2XTdtWg061A8+jkTm+3Eh4lGwU+B5vd8SxA8C4T d6bA7ppsIW0LxeuXNoUJ72lXdqULvBNP4s0Iw3zKMIblNNe1wMNP3+bTSbhwNJ0G F1KCnSbl9uWMplCZrDEq =lxQD -----END PGP SIGNATURE----- --eyp6ncyn5hgcup43--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160720190841.iuplrbhmdq7sr6br>