From d3247a8c8342dab6d4043e497607a77f3493e0c4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Camilla=20L=C3=B6wy?= Date: Mon, 10 Jul 2017 01:28:44 +0200 Subject: [PATCH] Documentation work --- docs/input.dox | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/input.dox b/docs/input.dox index 1dc21715..6d444656 100644 --- a/docs/input.dox +++ b/docs/input.dox @@ -181,12 +181,10 @@ GLFW supports text input in the form of a stream of operating system text input system. Unlike key input, text input obeys keyboard layouts and modifier keys and supports composing characters using [dead keys](https://en.wikipedia.org/wiki/Dead_key). Once received, you can -encode the code points into -[UTF-8](https://en.wikipedia.org/wiki/UTF-8) or any other encoding you prefer. +encode the code points into UTF-8 or any other encoding you prefer. Because an `unsigned int` is 32 bits long on all platforms supported by GLFW, -you can treat the code point argument as native endian -[UTF-32](https://en.wikipedia.org/wiki/UTF-32). +you can treat the code point argument as native endian UTF-32. There are two callbacks for receiving Unicode code points. If you wish to offer regular text input, set a character callback.