In function mvccwaddnstr, the output truncation needs to handle the case when output is UTF-8 -- simple byte length truncation is not correct or accurate.
Logged In: YES
There are two issues here. The first issue is that the current byte truncation can leave invalid UTF-8 sequences. The second (and more difficult) issue is that byte truncation is simply not accurate for UTF-8 due to zero-width characters, and something like wcswidth is needed.
Checked in changes to CVS trying to fix first issue.
Add global gui8 flag if display output encoding is UTF-8.
New function zs_chop.
Revised mvccwaddnstr to call find_prev_char to avoid chopping
string into illegal UTF-8 output.