You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the application uses UTF-8 or UTF-16 encoding for each string, but for embedded devices this sometimes is to large / difficult to implement since you cannot easily create lookup tables to map the characters to bitmaps. So most of the times (to my knowledge) ISO-8859-# encoding is used embedded.
So it could be useful to be able to select the characterset encoding per server connection, or in an application wide setting.
The text was updated successfully, but these errors were encountered:
Currently the application uses UTF-8 or UTF-16 encoding for each string, but for embedded devices this sometimes is to large / difficult to implement since you cannot easily create lookup tables to map the characters to bitmaps. So most of the times (to my knowledge) ISO-8859-# encoding is used embedded.
So it could be useful to be able to select the characterset encoding per server connection, or in an application wide setting.
The text was updated successfully, but these errors were encountered: