Description
When using Chat mode, the Georgian character βαβ (U+10D4) is transmitted as a question mark (?) instead of the correct Unicode character.
This behaviour is reproducible in both directions:
Local β Remote (Chat window)
I type Georgian text locally and send it via Chat.
On the remote side, the character βαβ appears as ?.
Remote β Local (Chat window)
If the character is typed on the remote side and sent back, it is also received as ?.
Remote input test (Notepad)
If I type Georgian text directly in a remote application (e.g., Notepad via VNC session), the character βαβ is also rendered as ?.
All other Georgian characters in the same string are transmitted correctly. Only U+10D4 (GEORGIAN LETTER EN β βαβ) is affected.
Test Procedure
Typed a Georgian string equivalent to 'qwerty' using Georgian keyboard layout.
Sent the text via Chat mode.
Verified the received string using:
https://www.babelstone.co.uk/Unicode/whatisit.html
Observed Results (via Unicode inspection)
When checking the received string on the remote side:
The expected character:
U+10D4 : GEORGIAN LETTER EN (α)
Instead received:
U+003F : QUESTION MARK (?)
All other Georgian characters in the string are correctly transmitted with their proper Unicode code points.
Screenshots attached:
1.png β Chat mode showing ?
2.png β Unicode inspection results
3.png β Comparison of local vs remote input
Expected Behavior
Character βαβ (U+10D4) should be transmitted and displayed correctly in:
Chat mode
Remote keyboard input
Any Unicode-capable text field
Environment
UltraVNC (Viewer + Server)
Windows (both sides)
Georgian keyboard layout
No custom encoding settings enabled
Additional Notes
Since:
Other Georgian characters (U+10D0βU+10FF range) are transmitted correctly,
Only U+10D4 consistently fails,
this may indicate:
A specific encoding/translation issue in Chat mode,
A code page fallback problem,
Or incorrect handling of this specific Unicode code point during transmission.
Please let me know if additional logs or reproduction steps are required.
Description
When using Chat mode, the Georgian character βαβ (U+10D4) is transmitted as a question mark (?) instead of the correct Unicode character.
This behaviour is reproducible in both directions:
Local β Remote (Chat window)
I type Georgian text locally and send it via Chat.
On the remote side, the character βαβ appears as ?.
Remote β Local (Chat window)
If the character is typed on the remote side and sent back, it is also received as ?.
Remote input test (Notepad)
If I type Georgian text directly in a remote application (e.g., Notepad via VNC session), the character βαβ is also rendered as ?.
All other Georgian characters in the same string are transmitted correctly. Only U+10D4 (GEORGIAN LETTER EN β βαβ) is affected.
Test Procedure
Typed a Georgian string equivalent to 'qwerty' using Georgian keyboard layout.
Sent the text via Chat mode.
Verified the received string using:
https://www.babelstone.co.uk/Unicode/whatisit.html
Observed Results (via Unicode inspection)
When checking the received string on the remote side:
The expected character:
U+10D4 : GEORGIAN LETTER EN (α)
Instead received:
U+003F : QUESTION MARK (?)
All other Georgian characters in the string are correctly transmitted with their proper Unicode code points.
Screenshots attached:
1.png β Chat mode showing ?
2.png β Unicode inspection results
3.png β Comparison of local vs remote input
Expected Behavior
Character βαβ (U+10D4) should be transmitted and displayed correctly in:
Chat mode
Remote keyboard input
Any Unicode-capable text field
Environment
UltraVNC (Viewer + Server)
Windows (both sides)
Georgian keyboard layout
No custom encoding settings enabled
Additional Notes
Since:
Other Georgian characters (U+10D0βU+10FF range) are transmitted correctly,
Only U+10D4 consistently fails,
this may indicate:
A specific encoding/translation issue in Chat mode,
A code page fallback problem,
Or incorrect handling of this specific Unicode code point during transmission.
Please let me know if additional logs or reproduction steps are required.