News for hackers. Stuff that matters.
Re:Text Editing Hates You Too by pcr910303 on Tuesday October 29, 2019 @05:27AM (#21385339)
> I've been saying that all text input should go through OS-level IMEs

This is so true, all commercial OSes that take i18n seriously do this, while most open source OSes' community (which communication revolves around English) decided that IMEs are an add-on for CJK people.

It's a pity, and this one reason is enough for Linux to be never adopted for ordinary users in the non-western world.

Re:Text Editing Hates You Too by mikekchar on Tuesday October 29, 2019 @06:56AM (#21385723)
That's not really fair, though. Linux users still overwhelmingly use X windows. There is no standard IME for X. This is just a historical issue. X Windows is OLD -- far older that Windows or Mac (even the old Mac), for instance.

My biggest problem with IMEs in free software land is that we've had groups like Gnome lean on IME developers and push through their vision of how it should work -- even though the people pushing their vision don't use IMEs. I ended up migrating to FCITX just because it was the last hold out not to cave to pressure.

Re:Text Editing Hates You Too by shadowgovt on Tuesday October 29, 2019 @09:17AM (#21386743)
Old really means there's been more time to identify and solve the problem, and the fact it hasn't been cleanly solved is a lot more indicative of priorities than time or tech.

Microsoft and Apple have the incentive of selling to billion-user markets. The open source community, on average, appears to have demonstrated a lack of interest in opening up the user-base further (and expecting that user-base to just roll their own solution creates multiple catch-22 and tragedy of the commons problems).

Why one of the commercial open-source vendors hasn't taken this on as a core challenge, I do not know.

Re:Text Editing Hates You Too by hsivonen on Tuesday October 29, 2019 @10:20AM (#21387443)
> There is no standard IME for X.

Technically true, but for practical purposes IBus is the standard. That's what Fedora and Ubuntu use out of the box. Firefox beta telemetry shows about 89% IBus vs. 11% FCITX.

> My biggest problem with IMEs in free software land is that we've had groups like Gnome lean on IME developers and push through their vision of how it should work -- even though the people pushing their vision don't use IMEs. I ended up migrating to FCITX just because it was the last hold out not to cave to pressure.

What wrong thing did the Gnome folks push for?

Re:Text Editing Hates You Too by mikekchar on Tuesday October 29, 2019 @09:28PM (#21393815)
Insisting that there can only be one input type for the entire session rather than one per window. If you are using multiple languages which each require an IME, Gnome's interpretation is completely broken. I had to stop using IBus because of it. It is possible they have changed their mind since then (several years back), but I haven't followed it. Incidentally, it was also the thing that meant I had to stop using Gnome. Before that I was a happy Gnome Shell user :-(
Re:Text Editing Hates You Too by hsivonen on Wednesday October 30, 2019 @12:45PM (#21399717)
Gnome appears to have fixed this.
Re:Text Editing Hates You Too by efdee on Tuesday October 29, 2019 @08:44AM (#21386475)
That's not really fair either. X Windows might be older, but neither Mac OS nor Windows had anything like this in their older versions.

Some things evolved, some things didn't. O hi X Windows!

Re:Text Editing Hates You Too by rmah on Tuesday October 29, 2019 @01:15PM (#21389575)
MacOS had rather robust internationalization support 25 years ago. Non-standard, but still.
Re:Text Editing Hates You Too by pvg on Tuesday October 29, 2019 @10:00AM (#21387227)
far older that Windows or Mac (even the old Mac)

They are all very nearly the same age.

Re:Text Editing Hates You Too by musicale on Tuesday October 29, 2019 @07:16PM (#21393110)
Pretty much. The W window system for the V distributed system predates the Macintosh (as does the Apple Lisa/1983), and W was ported to Unix in 1983. Their immediate successors - X and the Macintosh - came out in 1984, and Windows 1.0 in 1985.

Windows 1.0 was fairly primitive, but Windows 2.0 supported overlapping windows (!) in 1987, coincidentally the year that X11 was released.

Re:Text Editing Hates You Too by rodgerd on Tuesday October 29, 2019 @03:10PM (#21390925)
> That's not really fair, though

It's completely fair. Most of the developer community just doesn't care.

Re:Text Editing Hates You Too by hsivonen on Tuesday October 29, 2019 @10:12AM (#21387361)
> This is so true, all commercial OSes that take i18n seriously do this,

Does Windows really?

> while most open source OSes' community (which communication revolves around English) decided that IMEs are an add-on for CJK people.

IIRC, Fedora ships an iOS/Android like Latin-script IME with autocomplete. It's not mandatory, though.

> It's a pity, and this one reason is enough for Linux to be never adopted for ordinary users in the non-western world.

The Korean situation doesn't really generalize. Among CJK, AFAICT, the Korean IBus IME on Ubuntu 18.04 is pretty broken but the Japanese IME and the various Chinese IMEs appear to be at least OK. (It's a rather surprising situation considering that the Hangul part of a Korean IME should be much simpler than the Japanese and Chinese IMEs.)

Re:Text Editing Hates You Too by WorldMaker on Tuesday October 29, 2019 @02:43PM (#21390645)
> Does Windows really?

Yes, the signs that even English is passing through Windows' IME infrastructure in Windows 10 is pretty minimal by default (in Desktop mode, Tablet mode immediately turns on a couple more), but at this point Windows 10 makes almost all of it opt-in. Some of it is referred to as accessibility tools from an English perspective, because IMEs are also useful for accessibility.

The "big one" IME for most English users is the Emoji Keyboard accessible with Win+. or Win+; (whichever you prefer). It's really interesting how well emoji have helped Latin script users with further understanding the complexities of Unicode, fixing old ugly bugs in Unicode handling, and even introducing some such users to an IME that they want to use (sometimes every day).

Under Settings > Devices > Typing > Hardware Keyboard you can turn on the IME "Show text suggestions as I type" even on a hardware keyboard in Windows 10, which gives you mobile-style auto-suggestions (you can also turn on mobile-style autocorrect even on a hardware keyboard).

Re:Text Editing Hates You Too by hsivonen on Tuesday October 29, 2019 @02:55PM (#21390754)
> The "big one" IME for most English users is the Emoji Keyboard accessible with Win+. or Win+; (whichever you prefer).

No, API-wise the on-screen keyboard generates keystrokes for emoji (astral keystokes, multiple keystokes for multi-scalar-value emoji) even to an IME-aware app. In contrast, the emoji picker built into the Windows 10 Pinyin IME enters emoji via IME API.

> Under Settings > Devices > Typing > Hardware Keyboard you can turn on the IME "Show text suggestions as I type" even on a hardware keyboard in Windows 10, which gives you mobile-style auto-suggestions (you can also turn on mobile-style autocorrect even on a hardware keyboard).

Thanks!

Re:Text Editing Hates You Too by WorldMaker on Tuesday October 29, 2019 @03:17PM (#21391015)
The emoji keyboard may not be entirely using the IME API, but it does do some IME-like things even in English. The big thing I'm thinking of is the way it works when you type English words to search the emoji. I think it still most often defaults to passing the keys along to the application as well and replaces it with keyboard keystrokes or selection APIs, but I have seen it sometimes do the IME thing that the text you are typing is shown underlined and not sent to the application. Though in mentioning it, I don't recall the exact combination of app and emoji I was trying to find where I saw that happen or know precisely enough why it would vary in order to reproduce it just now, and maybe that was just a difference between early Insider versions of the emoji keyboard and current operations or something similar that I'm misremembering.

That said, even if it isn't using the IME APIs directly in most cases, it's still useful as a teaching tool/analogy tool/example tool to English speakers of what an IME can be like to use, even if a nice-to-have for an English writer versus a necessary required tool for other languages.

Re:Text Editing Hates You Too by munmaek on Tuesday October 29, 2019 @10:51AM (#21387784)
On debian 9/10 ibus works for the Korean IME (both Hangeul and Hanja input).

Windows (10 at least) has native support for these IMEs; setting it up on Windows was much easier than on Linux (which doesn't even have a standard IME). Windows also comes with basic CJK fonts, which different distros may or may not have. On Debian I have to install noto-cjk or Adobe's source han fonts.

I originally tried fcitx but had to switch to ibus. Definitely not a great experience.

Re:Text Editing Hates You Too by hsivonen on Tuesday October 29, 2019 @11:03AM (#21387919)
There isn't a single IME setup experience on Linux.

In my experience, Debian is worse than Fedora, Ubuntu, and openSUSE. Fedora is better than Windows 10 when it comes to IMEs: Fedora installs the IMEs by default. Ubuntu, like Windows 10, installs IMEs when you request the addition of an IME-requiring language. OpenSUSE gives you an IME for the language you use at install time if you install openSUSE using an IME-requiring language.

I haven't tried Debian 10, but when I installed Debian 9 _in Japanese_ with a _Japanese keyboard layout_ chosen, the installer didn't bother to set up a Japanese IME!

Fedora comes with an OK set of Noto CJK fonts by default. Ubuntu comes with a minimal set of Noto CJK fonts by default, but when enabling Chinese, Japanese, or Korean, Ubuntu drops more language-appropriate fonts on the system, like Windows 10.

Re:Text Editing Hates You Too by munmaek on Wednesday October 30, 2019 @12:18AM (#21394662)
I didn't mean to use italics here. Oops.