Here is the link I am using to test: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=vincenkwen#gmail.com¤cy_code=USD¬ify_url=https://mysidte.org/testPaypal.php&item_name=问飞&item_number=0338&custom=打的费
As you can see I set item_name and custom to be Chinese characters. However, in my IPN listener, all these characters are received back as \u001as, though on the checkout page the item_name was correctly displayed.
Go to More Options under Language Encoding
Related
I am testing some HTML emails that I will be sending out to customers, and I have hit a problem when it comes to the images in Gmail.
The image I'm including in the email is sourced from the live website. All other email clients are loading up the images, but Gmail is giving me broken images.
I've worked out that the problem is due to the spacing in the image filenames. Gmail is converting the spaces to a "+".
e.g
https://www.test.com/files/a product image.jpg ---> https://www.test.com/files/a+product+image.jpg
I have tried to replace the image link spaces with %20 but gmail is still converting these to "+" and therefore breaking the image.
I understand that images ideally shouldn't have spaces in them, but the website contains thousands of products, and changing the filenames is not an option in this case.
Does anybody know the reason why Gmail would change a space to a + ? Or even better, a way to fix this problem?
Thanks
Luke
URL cannot contain spaces, those need to be encoded as + or %20. See RFC 1738
The space character is unsafe
and
All unsafe characters must always be encoded within a URL
I stumbled across this question due to an email marketing campaign that had been sent out by a client. Some of the images embedded in the email had spaces in the filenames and consequently, some email providers did not render them correctly in the email campaign. The client asked if I could somehow retrospectively fix it so they did not have to resend (a large recipient list)
So while this is a (very) late answer, it's still relevant
Interestingly Gmail adds a "+" sign, while other email providers (Outlook) allow the space and simply add the "%20" html percent encoding...
My fix: if you for some reason can't modify the original image file stored on the server to remove spaces, you could simply place a .htaccess rule to redirect the URL (on Apache server) as follows;
redirect 301 /images/staff/john+does.jpg https://example.com/images/staff/john%20does.jpg
When the recipient reloaded the email campaign, the broken images all loaded up :)
I have a GitHub issue comment here (the third comment down) that I'd like to edit so that it looks prettier, by rendering part of it as a code block.
But it doesn't work; the three backticks show up as literal text.
Anyone know why?
GitHub treats comments received via email differently from comments entered in the web UI. If you look at your comments you'll see that the third one displays an envelope icon beside your name with mouseover text saying, "This comment left via email reply."
In a blog post, GitHub suggests that Markdown formatting is not permitted in email replies:
We figured out early on in testing that we couldn't expect people to write Markdown. People are going to be dumping code or stacktraces, and will expect them to look nicely.
And later, gives this caveat:
Plain text email is vastly preferred. Essentially, we strip all HTML from HTML emails before formatting.
I can't find a better description of how formatting of emailed issue comments is handled, but I don't think you're going to be able to use Markdown if you reply by email.
I am trying to implement a Facebook messenger bot. I have trouble with the bot replying with a response that contains large amount of words. Is there a limit to the number of words that can be used in a response?
P.S : It works fine otherwise
As described in the doc, text message must be UTF-8 and has a 2000 character limit.
There are other restrictions in template for field title, subtitle & call-to-actions button.
Looks like, the limit has been updated to 2000 characters now.
Source: https://developers.facebook.com/docs/messenger-platform/reference/send-api#request
When I am sending a direct mail newsletter as a test, everything looks fine. But when I am sending a newsletter to users only the content without my wrapping template is being send. The user see´s only the content elements in the newsletter. My html template is missing.
By content, do you mean that users see only plain text? If so, it might be due to subscriptions preferences.
Based on your settings, both fe_users and tt_address may have a flag called "Recieve HTML mails" (can't recall the exact english version) which by default is not set.
Please let us know a bit more about your installation if this doesn't help :)
Can you please help me how to send email in JAVA where the email received should have Voting buttons, for example "Yes" or "No"?
Thanks,
Jemru-Da
Take a look at JTNEF:
Transport-Neutral Encapsulation Format (TNEF) is Microsoft's
non-standard format for encapsulating mail which has any
non-plain-text content or properties (such as rich text, embedded OLE
objects, voting buttons, and sometimes just attachments). Whether or
not a given message is encoded using TNEF is determined by the Outlook
default settings, per-recipient setting, Exchange Server settings, and
message type and content.
Your voting buttons will be the links to a website where actual voting happens. Of course buttons will only be available in the HTML version of the email, the text version should fallback to simple textual links (For YES click here: http://blah...)