windows: add GetKeyboardLayout & ToUnicodeEx

[aymanbagabas]

These are used along with GetForegroundWindow and GetWindowThreadProcessId to determine the current user layout and translate the base key the user has pressed.

[gopherbot]

This PR (HEAD: 8dc39ad) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/574755.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 1: Commit-Queue+1

(4 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-28T07:53:41Z","revision":"737b4a1d29e60a909bcba46a91733836d9388aac"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 1: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 1:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: b22df7f) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/574755.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Ayman Bagabas:

Patch Set 1:

(3 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 2:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: f35ca7f) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/574755.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

This PR (HEAD: 3aa85da) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/574755.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Ayman Bagabas:

Patch Set 3:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 3:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 4: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-05-16T08:00:45Z","revision":"0ce8ebea88050fa3aebcc7b54998cf0727d813f1"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 4: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4:

This CL has failed the run. Reason:

Tryjob golang/try/x_sys-gotip-windows-386 has failed with summary (view all results):

---

FAILURE

• go on master (commit 722d594)
• sys on master (change 574755)

Error: failed to run "test golang.org/x/sys module": exit status 1

Links:

• "test golang.org/x/sys module" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 4:

(4 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: d4d009a) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/574755.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Ayman Bagabas:

Patch Set 4:

(2 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 5:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 7:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 7: Code-Review+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 7:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 7:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[aymanbagabas]

Hey @bcmills, could you take a look when you get a chance?

[gopherbot]

Message from Alex Brainman:

Patch Set 7: Commit-Queue+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 7:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-07-09T10:17:43Z","revision":"234e7b8f82f73600af66b3622a30897b070afbdc"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 7: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 7:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 7: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 7:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 7:

(4 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 2afe997) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/574755.

Important tips:

• Don't comment on this PR. All discussion takes place in Gerrit.
• You need a Gmail or other Google account to log in to Gerrit.
• To change your code in response to feedback:
  • Push a new commit to the branch used by your GitHub PR.
  • A new "patch set" will then appear in Gerrit.
  • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
  • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
  • Multiple commits in the PR will be squashed by GerritBot.
• The title and description of the GitHub PR are used to construct the final commit message.
  • Edit these as needed via the GitHub web interface (not via Gerrit or git).
  • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
• See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

[gopherbot]

Message from Ayman Bagabas:

Patch Set 7: Code-Review+1

(4 comments)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 8: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 8:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-07-14T05:58:50Z","revision":"c7b605b721f33bed62339588dfa8c946b59f37a0"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 8: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 8:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 8: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 8: Code-Review+2

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 8:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Ayman Bagabas:

Patch Set 8: Code-Review+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Alex Brainman:

Patch Set 8:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Cherry Mui:

Patch Set 8: Code-Review+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Than McIntosh:

Patch Set 8: Code-Review+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/574755.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR is being closed because golang.org/cl/574755 has been merged.