Expand my Community achievements bar.

We are excited to introduce our latest innovation to enhance the Adobe Campaign user experience — the Adobe Campaign v8 Web User Interface!
SOLVED

French character encoding issue in subject message center

Avatar

Level 2

Hi:

we are passing french characters with accent to the email subject line as variables.

But those characters are not correctly showing up in the email client.

we have tried to use UTF-8 encoding, but it only works in gmail.

for string "Inscription à la facture électronique" we are passing "=?UTF-8?Q?=49=6e=73=63=72=69=70=74=69=6f=6e=20=e0=20=6c=61=20=66=61=63=74=75=72=65=20=e9=6c=65=63=74=72=6f=6e=69=71=75=65?="

any idea how we can fix this issue? we have also tried setting enforce encoding on the template delivery

Thanks

1 Accepted Solution

Avatar

Correct answer by
Level 2

we found out that we are using wrong encoding on our application server, once we change it from ASCII to UTF8, it works now

View solution in original post

4 Replies

Avatar

Level 6

We use French in the subject line without an issue.  But we have run into cases that hidden values got passed in one of the spaces between words and it caused an error that would error out when doing a Test.  You could test it by deleting all the spaces between words and then add them back. Here is our last French Subject Line for an email that went out last week:  Comment pouvons-nous aider à implanter des mouvements partout?

Avatar

Level 2

Hi Johnwwilcoxmba:

thanks for the reply, just curious are you sending the email through the message center or the midsource.

do you send the request via the Adobe soap api? and do you need to convert the message to hexdecimal or just pass something like this"Comment pouvons-nous aider à implanter des mouvements partout"?

Thanks in advance

Avatar

Level 6

We are using Adobe Campaign Standard and we are doing a normal send email and not a transactional email.  We are not using the API.  No we don't have to convert the subject to hexadecimal. 

Avatar

Correct answer by
Level 2

we found out that we are using wrong encoding on our application server, once we change it from ASCII to UTF8, it works now