From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Line wrap reconsidered Date: Wed, 27 May 2020 18:20:19 +0300 Message-ID: <83d06ptnf0.fsf@gnu.org> References: <92FF4412-04FB-4521-B6CE-52B08526E4E5@gmail.com> <878shfsq35.fsf@gnus.org> <83imgivjak.fsf@gnu.org> <83lfletr03.fsf@gnu.org> <4895C6EE-5E1F-44BF-93C1-CC5F7C096F73@gmail.com> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="64517"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org To: Yuan Fu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 27 17:21:10 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jdxri-000Gf2-Nl for ged-emacs-devel@m.gmane-mx.org; Wed, 27 May 2020 17:21:10 +0200 Original-Received: from localhost ([::1]:42024 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdxrh-0005B1-Ox for ged-emacs-devel@m.gmane-mx.org; Wed, 27 May 2020 11:21:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48470) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jdxr6-0004Fz-99 for emacs-devel@gnu.org; Wed, 27 May 2020 11:20:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38176) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jdxr5-0007SM-Ue; Wed, 27 May 2020 11:20:31 -0400 Original-Received: from [176.228.60.248] (port=2911 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jdxr4-0006Ol-TA; Wed, 27 May 2020 11:20:31 -0400 In-Reply-To: <4895C6EE-5E1F-44BF-93C1-CC5F7C096F73@gmail.com> (message from Yuan Fu on Tue, 26 May 2020 16:31:36 -0400) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:251504 Archived-At: > From: Yuan Fu > Date: Tue, 26 May 2020 16:31:36 -0400 > Cc: Lars Ingebrigtsen , > emacs-devel@gnu.org > > I saw someone mentioning Line_Break.txt from unicode and looked it up, unicode commission has already marked out all wrap-able code points. IIUC we can add Line_Break.txt to admin/unidat and parse it and put a elisp file under /lisp/international, right? We can categoarize all the marked code points into three categories as I mentioned earlier. Line_Break.txt is a data file, but its use is for implementing the Unicode Line Breaking Algorithm, which is described in UAX#14, the Unicode Standard Annex #14. You can find its URL at the beginning of Line_Break.txt; I suggest to read it. Implementing that algorithm is something we should do, and when we do, we indeed need to import the data in that file into Emacs and use it. I don't see a reason to import the data in Line_Break.txt without implementing the algorithm, or at least most of it.