5 commits

Author	SHA1	Message	Date
Christoph Oelckers	6caf1f60c6	- added some UTF-8 utilities to FString. ... This deprecated CharAt and CharCodeAt for being unsuitable for text processing and in the case of CharCodeAt also for being buggy. A new replacement, ByteAt has been added that reads a string byte by byte, as well as CodePointCount, which counts the amount of Unicode code points in a string and GetNextCodePoint which reads the string code point by code point. Note that while this woll work as intended with the currently supported languages as a means to read single characters, there is no guarantee that this will remain so if Unicode support gets extended to things which break the "one code point == one character" assumption.	2019-05-14 19:35:21 +02:00
Christoph Oelckers	cf818fbe10	- changed zstrformat to allow %c to emit non-ASCII characters as UTF-8.	2019-05-14 17:38:45 +02:00
Christoph Oelckers	0153a42240	- fixed issues with text entering ... * entering a savegame description did not work anymore * the length check was too restrictive and always underestimated the available space * use the console font for entering a savegame description. This has more characters and better contrast for this content. * the interface to the text enterer used bad measurements. # Conflicts: # wadsrc/static/zscript/ui/menu/optionmenuitems.zs	2019-05-14 17:38:21 +02:00
Christoph Oelckers	f790d48041	- made the menu's text input handler Unicode capable. ... Also make sure that the savegame description remains readable. Unlike in-game text this can be done without double-encoding existing UTF-8.	2019-05-14 17:19:19 +02:00
Christoph Oelckers	961a6fe211	- reorganized the ZScript content in gzdoom.pk3 and changed the files' extensions to something unique for easier syntax highlighting. ... # Conflicts: # wadsrc/static/zscript.txt	2019-04-28 22:14:34 +02:00

Renamed from wadsrc/static/zscript/menu/textentermenu.txt (Browse further)