Tracking issue for IME / composition support

[murarth]

This issue tracks the implementation of IME composition events on each platform, an API initially proposed in #1293. PRs implementing this event should be made against the composition-event branch, which will be merged into master once all implementations are complete.

• Public API implemented (add composition event support #1404)
• API rename (rename CompostionEvent to IMEPreeditEvent #1622)
• Implemented on all platforms
  • Windows (Partially in Windows: implement Window.set_ime_position() with IMM API. #1790, more work required)
  • Mac OS (macOS: Composition Event #2147)
  • Linux X11 (add composition event support #1404)
  • Linux Wayland (Add IME event support for Wayland #2154)
  • iOS
  • Android
  • Web (Composition event on web #2173)
• Document IME
• Add an entry to CHANGELOG.md

[chrisduerr]

As a consumer of winit I'd recommend against naming these events CompositionEvent. Applications that deal with display servers will already know that term in connection with window compositing and it could easily be confused with something related to that.

It also does not fall in line with the existing winit naming of functions like set_ime_position.

I think it would be much better to have a more self descriptive name for this event that cannot be confused with anything else related to the winit project. I'd strongly suggest that IME should at least be part of the name.

[pickfire]

Oh, I thought CompositionEvent means some kind of compose key thing, I never used those and don't even know how to use compose key, I had only used IME to input characters not in the keyboard.

[garasubo]

@pickfire This event naming comes from web specification (Ref: https://developer.mozilla.org/en-US/docs/Web/API/Element/compositionstart_event). And IME will create those composition events.
But as @chrisduerr is pointed out, I agree that calling those events as "composition" is confusing.