From nobody Fri Jun 24 16:51:50 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 9A4EA86DFFE for ; Fri, 24 Jun 2022 16:52:01 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4LV37M6p36z3kWK; Fri, 24 Jun 2022 16:51:59 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-1-85-147.area1b.commufa.jp [123.1.85.147]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 25OGpoJr066689; Sat, 25 Jun 2022 01:51:50 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 25 Jun 2022 01:51:50 +0900 From: Tomoaki AOKI To: Hans Petter Selasky Cc: Ivan Quitschal , "freebsd-current@freebsd.org" , Kurt Jaeger Subject: Re: vt newcons mouse paste issue FIXED Message-Id: <20220625015150.4f57017e7098ea591f57bd2a@dec.sakura.ne.jp> In-Reply-To: <5196d98c-7b3a-55b4-3ef7-227b19b66721@selasky.org> References: <41ef5c38-515f-739a-cb47-7cab0e609526@selasky.org> <20220623014847.067b18a5ba388639cf6009ce@dec.sakura.ne.jp> <790bd76d-890f-cf09-a30d-c2e5fba91ec5@selasky.org> <20220624230215.82e02ac661cd7594624a1845@dec.sakura.ne.jp> <5bd74766-f2f0-3df2-0e8c-adabd110f913@selasky.org> <5196d98c-7b3a-55b4-3ef7-227b19b66721@selasky.org> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LV37M6p36z3kWK X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [0.53 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; HAS_ORG_HEADER(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.1.85.147:received]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.92)[-0.925]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-0.94)[-0.941]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sakura.ne.jp]; AUTH_NA(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_CC(0.00)[hotmail.com,freebsd.org]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Fri, 24 Jun 2022 17:29:26 +0200 Hans Petter Selasky wrote: > Hi Tomoaki, > > On 6/24/22 16:48, Hans Petter Selasky wrote: > > IDEOGRAPHIC (Full-width) SPACE > > According to this page: > > https://jkorpela.fi/chars/spaces.html > > There are multiple uni-code characters which are spaces. Should we > support them all? > > --HPS Nice page! Maybe not all. My guess based on "Sample" and "Width of the character" fields are as below. At the first column, 'Y': Should be treated as space / word separator 'N': Should NOT be treated as space / word separator 'U': Unknown for me. Need native speaker to determine. Maybe someone have objections, but basically I've considered breakable spaces as space characters. See also URL [1] below. Special cases: *Looking sample, U+1680 is shown as dash so considered 'N'. *Treated "QUAD" as just a graphical (non-semantic) use so considered as 'N'. *Considered U+205F as 'N', as I thought, for mathematical usage, unintended line break could cause fatal confusion. Code Name of the character Y U+0020 SPACE N U+00A0 NO-BREAK SPACE N U+1680 OGHAM SPACE MARK Y U+180E MONGOLIAN VOWEL SEPARATOR N U+2000 EN QUAD N U+2001 EM QUAD Y U+2002 EN SPACE (nut) Y U+2003 EM SPACE (mutton) Y U+2004 THREE-PER-EM SPACE (thick space) Y U+2005 FOUR-PER-EM SPACE (mid space) Y U+2006 SIX-PER-EM SPACE N U+2007 FIGURE SPACE Y U+2008 PUNCTUATION SPACE Y U+2009 THIN SPACE Y U+200A HAIR SPACE Y U+200B ZERO WIDTH SPACE N U+202F NARROW NO-BREAK SPACE N U+205F MEDIUM MATHEMATICAL SPACE Y U+3000 IDEOGRAPHIC SPACE N U+FEFF ZERO WIDTH NO-BREAK SPACE Maybe, the best would be looking into how unicode normalization treat them. But we Japanese would want U+3000 treated as space. [1] https://en.wikipedia.org/wiki/Non-breaking_space -- Tomoaki AOKI