To implement keep alive feature for Ejabberd it recommends to send a \n character to server.
I'm using strophe.js as the client library. How do I send neutral character from strophe?
You can try to encode the carriage return (CR) character. That is, you can use its character entity:
Related
I am currently using Lazarus 1.6.4 for a mobile app, and I am making an Indy TIdHTTP.Get() call to a web server, which returns a JSON string in UTF-8 format.
The string contains Unicode characters that I cannot see in Lazarus, where the response is converted with multiple ? characters (one for each Unicode character).
For example, I want to get ["id","code","name"],[2,"100","ΤΕΣΤ"], but I receive ["id","code","name"],[2,"100","????"].
I have an older version of Lazarus, and I don't have any problems with the encoding. I also perform the call from other applications/browsers with no problem.
Any ideas?
I am working on a loadrunner winsocket script.
The buff that should be sent has a special character "~", when loadrunner sends the request it sends it as "~7e".
Request to be sent - FBE442757F3FA860~1cFFFF0222050017200181
Request that is sent to the application - FBE442757F3FA860~7e1cFFFF0222050017200181
How can we accommodate special characters in loadrunner winsocket.
see lr_set_send_buffer() for how you can set the contents of any buffer. I refer to your C programming expertise on construction of the buffer with embedded hex characters.
I'm using the .NET SDK to import customers and transactions from another system that accepts UTF-8 encoding in their data, and am having a lot of trouble with special characters. Is there a comprehensive list of (a) what characters need to be escaped (like apostrophe), and (b) what characters are simply not allowed in QBO (like colon)? All I can find in the online doc is "use backslash to escape special characters like apostrophe". OK, what about ampersand, em dash, en dash, grave accent, acute accent... you get the idea.
This problem affects both queries and inserts which causes all kinds of problems. For example, if we query a customer by name, and the query fails (maybe due to an invalid character), we try to insert the customer in QBO, which of course also fails, either due to the customer existing or invalid characters. True, we can usually figure out if the query failed due to a bad character vs the record not existing, but we need a design-time solution. Any suggestions?
If you use Query endpoint, then please URL encode the query parameters.
For ex -
For the following query
select * from Customer where DisplayName='Aülleünte'
URL request would be
https://quickbooks.api.intuit.com/v3/company/<relamId>/query?query=select+*+from+Customer+where+DisplayName%3D%27A%C3%BClle%C3%BCnte%27
PN - Some QBO textfields(for ex - 'Description/Note' of Customer window) allow to enter control characters which gets returned as part of query response. As some of those characters are not supported in XML, object deserialization fails/shows warning.
You should either remove those characters from UI or you need to use some lib/regex in the client side code to remove those characters programmatically. Ideally it should be handled in the server side.
QBO Global UI supports UTF-8 encoding for sure. But It seems, QBO US UI behaves differently while dealing with special characters.
For ex - In QBO US UI, if you enter '你好嗎' then after saving, it gets converted to '}Î'.
Edit
Here is a list of accepted characters:
•Alpha-numeric (A-Z, a-z, 0-9)
•Comma (,)
•Dot or period (.)
•Question mark (?)
•At symbol (#)
•Ampersand (&)
•Exclamation point (!)
•Number/pound sign (#)
•Single quote (')
•Tilde (~)
•Asterisk (*)
•Space ( )
•Underscore (_)
•Minus sign/hyphen (-)
•Semi-colon (;)
•Plus sign (+)
I have found conflicting information about dot stuffing when transmitting an email.
stuff a dot if the line contains a single dot (to avoid premature termination)
stuff a dot to every line stat starts with a dot
stuff a dot to (1) and to every line part of a quoted-printable message part only
Can anyone clarify?
According to the SMTP standard RFC 5321, section 4.5.2:
https://www.rfc-editor.org/rfc/rfc5321#section-4.5.2
To allow all user composed text to be transmitted transparently, the following procedures are used:
Before sending a line of mail text, the SMTP client checks the first character of the line. If it is a period, one additional period is inserted at the beginning of the line.
When a line of mail text is received by the SMTP server, it checks the line. If the line is composed of a single period, it is treated as the end of mail indicator. If the first character is a period and there are other characters on the line, the first character is deleted.
So, from the three points of your question, the second one is right.
The practical answer: If you're using quoted printable format then always translate a dot to =2E. You can't rely on all smtp servers doing the dot removal correctly.
If you want to assume the whole world is standards compliant then go with answer 2 above.
In SMTP protocol the mail is terminated by a single dot and a newline character(s)
In simple terms something like:
\r\n.\r\n
The characters:
CR LF DOT CR LF
Which corresponds to a single dot at the beginning of a line.
In case the mail data contains a single . At the beginning of line and is followed by a new line character then the SMTP protocol will consider it as mail termination and hence only a part of mail would be delivered.
So the whole idea is to avoid these type of situation by padding an extra dot.
Does IRC support internationalized (UTF-8) room names?
How? A pointer to documentation or a spec would be welcome.
According to RFCs 1459 and 2812, channel names can be made up of any bytes other than \x00 (NUL), \x07 (BELL), \x0A (LF), \x0D (CR), \x20 (space), , and :. How those bytes are interpreted is entirely up to the client. IRC doesn't impose any specific restrictions on the encoding.
No specific character set is specified. The protocol is based on a set of codes which are composed of eight (8) bits, making up an octet. Each message may be composed of any number of these octets; however, some octet values are used for control codes, which act as message delimiters.
You need to use IRCX protocol extensions from Microsoft
Basically you add a '%' character append your UTF-8 string and perform a post-processing on the result replacing characters using this table:
\b " " (blank)
\c ","
\\ "\"
\r CR
\n LF
\t TAB
Here is the link to the specification:
https://datatracker.ietf.org/doc/html/draft-pfenning-irc-extensions-04#page-5