![]() I can’t imagine any Quality Control was done on this “feature”. The Shift-JIS implementation is clearly broken in v0.58 and I would not use it in this broken form. We’re working on a Font Editor, but it’s not done yet. Or you need to edit the font and replace the \ character with a Yen symbol instead, which is actually what the standard Shift-JIS character at position 5C is. This poses an even bigger problem, because escaping the Yen symbol will result in a backslash character being show in Nextion Editor… Only ‘out-of-the-box’ solution for the Yen symbol is to use its double wide variant instead: b4.txt="ソ\¥" In JIS X 0201, of which Shift JIS is an extension, the yen sign has the same byte value (0x5C) as the backslash in ASCII. The ¥ character code is also 5C, again the same as a backslash in ASCII: I can put this code in the Touch Press/Release Event code and it works fine: b5.txt="ガス" If you decide to use UTF-8 you need to store the text in that encoding instead of Shift-JIS encoding… There shouldn’t be any issue with storing and sending the bytes over UART, just make sure to escape the byte sequences with the extra slash as needed. Unless you really need official support from Nextion (which is both pricey and worthless at the same time), the only drawback I see is generating the font outside the Nextion Editor…įor the MCU it’s all just byte array’s. UTF-8 encoded Japanese text uses more bytes, as the characters use up to 3 bytes.Is the de-facto encoding used in most modern applications.Supports other languages and scripts, making it more versatile. ![]() Font has to be generated in another program.Doesn’t contain the 5C sequence in multi-byte characters, so doesn’t have the bug.Not officially supported (yet), but in my testing I found it just works fine.Only for Japanese, if you want to support other scripts you need additional fonts with different encoding. ![]() Cannot display ソ in the editor nor any other multi-byte characters that end in 5C like Ы, 噂 and 浬.Font can be generated in nextion Editor.Basically it’s a design choice, so you need to weigh the pro’s and con’s. I will decide if it would be better to have the strings saved in the Nextion or in the MCU memory and send the chosen strings through the UART (more universal).īoth UTF-8 and Shift-JIS can display Katakana characters. This is not good.Īlso I am not sure how to send the japanese characters from the MCU to the Nextion in the future. If I enter ソ\ to the txt field, error message appears but then the compilation is successful and ソ\ is displayed (the backslash is visible). I cannot display the character if I enter this in the Nextion IDE (Attribute). Even if I cannot see it untill I run the simulator :-(. Is good workaround - this is the thing I can work with further. Sorry for the bad link - it was halfwidth version.Īnd here even more useful: (kana)#/Other_representations However I was not able to find workaround or solution. I knew that the problem is related with 0x5C character (\). in a new section or in the slack space of an existing section) and fix up all instructions and pointers pointing to the original string.Yes, other characters have been displayed without problems in Shift-JIS encoding. To translate such strings it is necessary to find them in the binary and either patch them in-place (if it can be done without running out of space), or (especially when there's not enough space) put the translated text somewhere else (e.g. rdata section and are represented by byte sequences in whatever codepage the developer used (in case of Japanese it's usually Shift-JIS). Unfortunately, many developers do not think of or care about localization and put various text strings directly into the code. Resources can be decompiled and edited by tools such as resource editors and easily replaced, usually without affecting functionality of the application. Text in them is usually present in Unicode (UTF-16) encoding. rsrc section and include things like strings, menus, dialogs and some others. ![]() Projects support multi-select and drag and drop. Use Workspaces to easily switch all open files. Use projects to store a list of files in a tree structure for editing. These are stored in a special format in the. Announcing 010 Editor - Version 13.0.2 Introducing 010 Editor v13 with support for Projects and Workspace files. Windows executables can have text in one of two formats:
0 Comments
Leave a Reply. |