<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - wl_keyboard and hieroglyphs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94279">bug 94279</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - wl_keyboard and hieroglyphs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94279#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - wl_keyboard and hieroglyphs"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94279">bug 94279</a>
from <span class="vcard"><a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span></b>
<pre>(In reply to gramkueo from <a href="show_bug.cgi?id=94279#c0">comment #0</a>)
<span class="quote">> But did you have to separate these 2 entities: physical and virtual keyboards?</span >
Yes, because otherwise shortcuts don't work.
<span class="quote">> In the first case, the keyboard layout is given to the
> client, in the latter case - the compositor. What about the hieroglyphs?
> Compositor needs a clue, where exactly on the surface entering the symbol to
> displaying a menu select the desired character input via pinyin.</span >
This is handled via input methods on the client (provided for via the text
protocol), because it needs extensive knowledge of client internals.
<span class="quote">> Why initially it was impossible to give layouts to compositor, clients to
> give utf-8 characters and modifiers separately?</span >
Because otherwise you can't do shortcuts, basically.
Keyboards and virtual keyboards are very different, and direct keyboard text
entry vs. complex/compositional text entry are also very different. These
different requirements give us very different semantics.
We did look into trying to make everything work with a text-based protocol, but
it proved impossible. Sorry.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>