From owner-freebsd-current@FreeBSD.ORG Tue Aug 26 02:04:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 075F21065673 for ; Tue, 26 Aug 2008 02:04:39 +0000 (UTC) (envelope-from tzhuan@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 76F778FC18 for ; Tue, 26 Aug 2008 02:04:38 +0000 (UTC) (envelope-from tzhuan@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1578929fgb.35 for ; Mon, 25 Aug 2008 19:04:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=atDwgqJcQ/YsbGg+uWpL0bDnCo+arT19iWB0uGPN4/w=; b=Cf0QqzVxFJKClzV9gTXE13tgugGgif307Vl/2SnhUwrQ/Y+v81DARQouOkx9vHT8j6 GEE7+ebvH8faritY53wK1W55Sad90htzyo3Ais0k9FJI4EUT/9r37Q1luIE6ey70Qlkc kY9JT/kS/C1IohDA+R/ZP4Bz9UOgQMq6VVaPo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=bXde2c+vCEDmNjHnDqOaEvJTf+SBYL9hRJp8is6BEPYk1yBGXH/kWyi6pmn5RnZ2ua pO2OpatyDuZHg9Lo5sASV49+Zknb39S+eoj7dopc9gipvw1IOehciYOSnv4soYH+12Mi ngFs1P6DRHe3gtFYv2GTr6XR+742LlOWHDOgo= Received: by 10.86.93.19 with SMTP id q19mr1152775fgb.76.1219716277296; Mon, 25 Aug 2008 19:04:37 -0700 (PDT) Received: by 10.86.3.2 with HTTP; Mon, 25 Aug 2008 19:04:37 -0700 (PDT) Message-ID: <6a7033710808251904t37df0733s91fd7eb31beae76f@mail.gmail.com> Date: Tue, 26 Aug 2008 10:04:37 +0800 From: "Tz-Huan Huang" Sender: tzhuan@gmail.com To: "Alexander Churanov" In-Reply-To: <3cb459ed0808241958v552eafejf7841f0f9993928e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cb459ed0808221700w335b0906g6901d8b8bec4dad9@mail.gmail.com> <200808241415.31812.mitchell@wyatt672earp.force9.co.uk> <6a7033710808241239p1cbdc7adwd4f87814b428b10b@mail.gmail.com> <3cb459ed0808241958v552eafejf7841f0f9993928e@mail.gmail.com> X-Google-Sender-Auth: 00207495a842a65a Cc: freebsd-current@freebsd.org, Frank , freebsd-i18n@freebsd.org Subject: Re: Unicode-based FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 26 Aug 2008 02:04:39 -0000 Hi, > Tz-Huan, > > Working with Chinese text is the hard part of my solution (described in full > in freebsd-current@freebsd.org). In brief it's about moving FreeBSD to UTF-8 > completely and making syscons map UTF-8 to selected 8-bit charset for > displaying (a failsafe solution). It seems that this makes syscons somewhat > more usable for some people, but not for from East Asia, am I right? Agree. > I was thinking of how to make working with Chinese filenames possible under > syscons, but the help of a native speaker/writer would help much, because I > know only basic facts about that matter. > > I see two alternatives of displaying unicode code points that do not fit > into selected 8-bit display charset: > > 1) Substituting with some character, like '?'. This is very affordable > solutiuon, but makes inconvenient working with files having names that do > not fit into selected charset. > > 2) Substituting with encoded code point value like "#1234;". This is more > complex solutuon, if correct baskspacing and things like that are required. > I am not ready to implement it. IMHO, both solutions are interesting but they might be not so useful for Chinese users. The current syscons will display the Chinese filename byte by byte, so a Chinese character will be displayed as a sequence of 8-bit ASCII characters. When I see that I just know ``oh, that's a file with Chinese filename'', I don't want to recognize which characters it is because there are thousands of different Chinese characters. In this case, if I see ``???'' or ``#1234#3456'', I still cannot recognize the characters if I have no other computer with desktop environment like X or MS Windows. So, whether the Chinese character is displayed as a sequence of 8-bit ASCII, as '?' or as '#xxxx', they are all probably the same for me. > In any case, it would be nice to have some "magic" implemented: if copying > a text with substitued code points and then pasting it would case the > original UTF-8 sequence to be inserted. Yes it's nice, but I think the chance to copy/paste the text of a Chinese filename in syscons is less. The feature might be not easy to implement and you might waste too many time to implement a feature that is used in very less frequency. Of course that's my case, this feature might be very useful for others or other language. :-) Regards, Tz-Huan