|
|
## Keyboards
|
|
|
|
|
|
In a [keyboard button][] the text you set is the same that is eventually sent to the server when you hit the button. This might be inconvenient because it requires you to act on strings that might be translated ecc. and also that you cannot have two buttons with the same label.
|
|
|
|
|
|
To address this issue it should be possible to use Unicode characters `U+200B` (`ZERO WIDTH SPACE`), `U+200C` (`ZERO WIDTH NON-JOINER`) and others (e.g. `U+200D` `ZERO WIDTH JOINER`) which should not introduce any visible modification to the button's label but allow for different *strings* to be set (and then decoded server side).
|
|
|
|
|
|
There is now [an article](http://blog.polettix.it/telegram-keyboard-button-encoding/) on this in the blog.
|
|
|
|
|
|
[keyboard button]: https://core.telegram.org/bots/api/#keyboardbutton |
|
|
\ No newline at end of file |