From owner-freebsd-current@freebsd.org Wed Jul 20 14:22:51 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70A21B9E787 for ; Wed, 20 Jul 2016 14:22:51 +0000 (UTC) (envelope-from darkuranium@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E93D91B9C for ; Wed, 20 Jul 2016 14:22:50 +0000 (UTC) (envelope-from darkuranium@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id f93so39511854lfi.2 for ; Wed, 20 Jul 2016 07:22:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=6gl0OTgm667RY6v4gomKNHcq2WglSt/BuojCci5I0iI=; b=IrV80anNz0omvA4mpxteOHGd1kB+X9f/7MrdOkLVlJrJRFC+VJIhPcbxStyTRCR0w4 n78T+u5zO73DXMJpDuJo0EPQ8c3FsAZ5Yd0kk8ENouPIF5PndUHe9L/EF2ykuzIf6ODY Gbffzha5Dp0F/3MYEZaPZV4RSXQIL5saxYitI6lTcm4/oPQ4H2oI651YwPN/l14aM/1o BohwYyh8Clk/5801YJZ9X/8C3EYiQr5qEcezxPj/xeMvxEu4I7UVTE8eqsNHyXUH3UGU fRszUYryPVYeTJ6itylrKUqNCDjHA0pmid8dsJ8sKyF9mFjmsb0gcTJ5B519i3dC4gio Cf4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=6gl0OTgm667RY6v4gomKNHcq2WglSt/BuojCci5I0iI=; b=Mss6MpTmx4Syg247wWwYq/BusGNSNb6u1gHNIhEPfxVRlieOtHgVAGxSFG49rcCMXD bCT1k9iwGr0107Ws1BdJLRuvIT299oeUIb6eN+PH5Z8byPUrYxjdU22egPcK33f0Pvgv dE6k3e7vm6d0qOvbAkq4X00p8B2gF+6fPSV+0tWlzNRRCGL4wIouAzSEMQH/PRw+k7Tv yLhLWYWrwUaTxAIYOyAuBs0W7v+hHfRxWxp1ef0unOUY8s16MR72f2D/F1lHUxrOC/2p akmTrfZJ2YaISFL9dB5Vr59jr48S4SBmZQVMbajmBApUqznTLDc1UwXYiJ8DBHjt+VEL 2Y6g== X-Gm-Message-State: ALyK8tIaQZbA0uWczlUlpRrzHBLF5ZSBOCC7Kt3AkwoQ7YkCVFEiTTbhvtkAURlkXdOaGgU7M8jjh8c/XrbRUA== X-Received: by 10.25.209.195 with SMTP id i186mr23350276lfg.230.1469024568976; Wed, 20 Jul 2016 07:22:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.160.201 with HTTP; Wed, 20 Jul 2016 07:22:48 -0700 (PDT) In-Reply-To: <20160720140741.yi7vfgmmqtg6eprx@ivaldir.etoilebsd.net> References: <20160720140741.yi7vfgmmqtg6eprx@ivaldir.etoilebsd.net> From: =?UTF-8?B?VGltIMSMYXM=?= Date: Wed, 20 Jul 2016 16:22:48 +0200 Message-ID: Subject: Re: UTF-8 by default? To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 14:22:51 -0000 On 20 July 2016 at 16:07, 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: >> >> > 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? >> >> At least according to one of my students (who makes more extensive use o= f >> i18n than I do), enabling UTF-8 by default is pretty straightforward: >> >> https://github.com/musec/freebsd/wiki/Common-setup#utf-8-support > > the LC_COLLATE=3DC is not needed anymore with freebsd 11+ >> >> If there's anything missing there, I'd love to hear about it. >> > > Lot of work has been done during the 11.0 development the following issue= s were > fixed: [SNIP] Yes, these are exactly the kind of issues I'm talking about w.r.t. `3)`. > * medium (minor?) > - login(1) does not handle unicode properly Where does `login(1)` need to handle Unicode, though? I mean, I'm not expecting the OS to allow UTF-8 usernames (that would be ... problematic, to say the last).