W3C home > Mailing lists > Public > public-i18n-archive@w3.org > April to June 2020

[jlreq] Should Japanese verbs be segmented by morpheme for selection? (#212)

From: r12a via GitHub <sysbot+gh@w3.org>
Date: Fri, 22 May 2020 12:21:29 +0000
To: public-i18n-archive@w3.org
Message-ID: <issues.opened-623169964-1590150088-sysbot+gh@w3.org>
r12a has just created a new issue for https://github.com/w3c/jlreq:

== Should Japanese verbs be segmented by morpheme for selection? ==
I've been exploring the results of double-clicking on Japanese text. See a [summary of the results](https://w3c.github.io/i18n-tests/results/int-grapheme-word-segmentation#japanese) of some exploratory tests. See https://github.com/w3c/character_phrase_tests/issues/30 for a discussion about what happens when clicking inside verbs.

Firefox only selects adjacent rows of characters from the same Unicode block when you double-click in the middle of a sentence.

Chrome and Safari, however, apply some logic to the resulting selection, so that if you click inside the word 歩きました (depending on where you click) the browser highlights one of the following morphological segments, 歩き, ま, or した.

The latter is what ICU does. See the [ICU segmentation demo page](https://icu4c-demos-7hxm2n5zgq-uc.a.run.app/icu-bin/icusegments#1/en).

My question is whether that's what the average Japanese user wants to happen, or not?  Are they happy to be able to select the word root (including incidental hiragana, as in 歩き), or do they get frustrated that they have to constantly extend the selection to get what they want, ie. the whole word?

Please view or discuss this issue at https://github.com/w3c/jlreq/issues/212 using your GitHub account
Received on Friday, 22 May 2020 12:21:31 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 18:09:42 UTC