# HG changeset patch # User Kenichi Handa # Date 1043629443 0 # Node ID 5579114f7b97f1033b8329ac170177567d278bf9 # Parent 3fd3c5521557b1f04caed7282a487108ede8fff7 (x_set_name, x_set_title): Add comment about encoding strategy. diff -r 3fd3c5521557 -r 5579114f7b97 src/xfns.c --- a/src/xfns.c Sun Jan 26 23:21:53 2003 +0000 +++ b/src/xfns.c Mon Jan 27 01:04:03 2003 +0000 @@ -2517,6 +2517,20 @@ int bytes, stringp; Lisp_Object coding_system; + /* Note: Encoding strategy + + We encode NAME by compound-text and use "COMPOUND-TEXT" in + text.encoding. But, there are non-internationalized window + managers which don't support that encoding. So, if NAME + contains only ASCII and 8859-1 characters, encode it by + iso-latin-1, and use "STRING" in text.encoding hoping that + such window manager at least analize this format correctly, + i.e. treat 8-bit bytes as 8859-1 characters. + + We may also be able to use "UTF8_STRING" in text.encoding + in the feature which can encode all Unicode characters. + But, for the moment, there's no way to know that the + current window manager supports it or not. */ coding_system = Qcompound_text; text.value = x_encode_text (name, coding_system, 0, &bytes, &stringp); text.encoding = (stringp ? XA_STRING @@ -2530,6 +2544,7 @@ } else { + /* See the above comment "Note: Encoding strategy". */ icon.value = x_encode_text (f->icon_name, coding_system, 0, &bytes, &stringp); icon.encoding = (stringp ? XA_STRING @@ -2630,6 +2645,7 @@ Lisp_Object coding_system; coding_system = Qcompound_text; + /* See the comment "Note: Encoding strategy" in x_set_name. */ text.value = x_encode_text (name, coding_system, 0, &bytes, &stringp); text.encoding = (stringp ? XA_STRING : FRAME_X_DISPLAY_INFO (f)->Xatom_COMPOUND_TEXT); @@ -2642,6 +2658,7 @@ } else { + /* See the comment "Note: Encoding strategy" in x_set_name. */ icon.value = x_encode_text (f->icon_name, coding_system, 0, &bytes, &stringp); icon.encoding = (stringp ? XA_STRING