| Blockland Forums > Modification Help |
| RTB Development |
| << < (173/889) > >> |
| Ephialtes:
\xD6 does not constitute valid UTF-8 encoding. Java will not even interpret \xD6 as anything - that's just invalid. \x does not exist in Java. |
| M:
--- Quote from: Ephialtes on February 02, 2010, 10:39:59 AM ---\xD6 does not constitute valid UTF-8 encoding. Java will not even interpret \xD6 as anything - that's just invalid. \x does not exist in Java. --- End quote --- I am saying to you, to send a backslash. Followed by an X. Followed by the sequence. As individual characters. If you have to, escape the backslash so it's its own character, not part of a sequence. Then, when the Torque client receives this sequence with its individual backslashes and other characters, you can collapse the escape sequences, and voila. Unicode characters, and all you ever sent to the server was backslashes and letters and numbers. No umlauts or accents. |
| Ephialtes:
Then people using other clients like Pidgin or Psi are going to see people with names like "Ge\xD6rge" - that's not acceptable. |
| M:
--- Quote from: Ephialtes on February 02, 2010, 10:47:56 AM ---Then people using other clients like Pidgin or Psi are going to see people with names like "Ge\xD6rge" - that's not acceptable. --- End quote --- And why would these clients not have some way to convert unicode characters as well? I'm sure that any widely-used client has some form of unicode support via XMPP. That is, however, a valid point. |
| Ephialtes:
Because the XMPP specification is for UTF-8 only. There is no "oh but use Unicode or EBCIDIC if you feel like it" clause. --- Quote from: XMPP RFC 3920 ---11.5. Character Encoding Implementations MUST support the UTF-8 (RFC 3629 [UTF-8]) transformation of Universal Character Set (ISO/IEC 10646-1 [UCS2]) characters, as required by RFC 2277 [CHARSET]. Implementations MUST NOT attempt to use any other encoding. --- End quote --- |
| Navigation |
| Message Index |
| Next page |
| Previous page |