From owner-freebsd-current@FreeBSD.ORG Fri Aug 29 13:36:26 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 3A49F1065670 for ; Fri, 29 Aug 2008 13:36:26 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id B833B8FC21 for ; Fri, 29 Aug 2008 13:36:25 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so262486eyi.7 for ; Fri, 29 Aug 2008 06:36:24 -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:to :subject:in-reply-to:mime-version:content-type:references; bh=sEWTQGiTPOO3WWqU5gBeeHcOtUd2JpceQGu0hxgG4xg=; b=ahRluby4uPPLBd7nu7ywOHOqEWN19VKNYR/h1Z6YRnWsGAMeNuyYp5y8EKOfz5wEVd c/Bj+kOptCt2DwJBDj/3RXrsWmUkIaSl3iVmlYsmGYJE04GDrog7kA/rGwYXITPIApow LZtnLUSqf7Z/CpeHLDFOUA8ZJy9pAsvjVqAy8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=rQlNA7WwB6xjVEgSIu5Va0xL2SEwlqKX7naXwT5782Z0+GetexIC3WO6mGsMOFQWW0 5l3OXWPAU+NWhF0VOWSe0eW18yJm70qwKKWPVb6jJyyhgCJQEpIUXWmfOecRviAmuqWy 6PhR63WO12gk7wjxua9GxpjwXhyEd1epXj844= Received: by 10.210.16.16 with SMTP id 16mr1657997ebp.35.1220016984330; Fri, 29 Aug 2008 06:36:24 -0700 (PDT) Received: by 10.210.130.15 with HTTP; Fri, 29 Aug 2008 06:36:24 -0700 (PDT) Message-ID: <3cb459ed0808290636r5eb389c8y6d4aafae1b8001cf@mail.gmail.com> Date: Fri, 29 Aug 2008 17:36:24 +0400 From: "Alexander Churanov" To: freebsd-current@freebsd.org, "Tz-Huan Huang" , olli@lurza.secnetix.de In-Reply-To: <200808281718.m7SHISGL067492@lurza.secnetix.de> MIME-Version: 1.0 References: <3cb459ed0808250952j572dfc35j2feb852a73de5ace@mail.gmail.com> <200808281718.m7SHISGL067492@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: 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: Fri, 29 Aug 2008 13:36:26 -0000 2008/8/28 Oliver Fromme > Right now, a Chinese sysadmin cannot simply go to a FreeBSD > console, run mutt and read mails from his co-workers that > contain Chinese characters. This *does* work fine with > Linux. This is clearly an area where FreeBSD is lacking. Tz-Huan, Could you comment on this? Does Linux really display and render all Chinese glyphs corectly? Do they have video card compatibility issues? How about top-to-bottom rendering? Is it actually used or useful in China and Taiwan? This would mean that they use graphical mode (and I was already suspecting this) and have complex processing layer. Unicode is not only a large bunch of characters, there are also such things as precomposed-decomposed characters, bidirectional text, etc. As for my project, complex rendering layer is definitely out of scope for now. However, the purpose of this discussion is to gather opinions for possible future projects. I see three possible layers of unicode support in FreeBSD: 1) Syscons in pure text mode. This needs improved Unicode support. 2) Non-X console in graphical mode (like Linux). This is not present in FreeBSD. 3) X and related applciations. From my point of view, this does not require modification for now. Probably, all three solutions should be implemented in ideal. And (1) plain-text console would be used only if running (2) is not possible. However, implementing (2) is a very expensive task. And that's why I'd like to receive comments. Probably, it is worth to discuss and extimate costs for such a project. Alexander Churanov