Other OutSystems sites...
OutSystems Website
About Agility Blog
OutSystems Network
Login
Signup
Forums
Academy
Forge
Ideas
Forums
›
Technology & Integration
›
EmailAddressCreate encode error
EmailAddressCreate encode error
Carlos Freitas
Rank: #110
Posted on 2012-05-16
thumbs_up_ico
0
thumbs_down_ico
0
reply
post_link_ico
When I use the EmailAddressCreate and in the first parameter I send a string with "special" characters I get an error.
Ex: EmailAddressCreate ("Smith, John", "john.smith@test.com");
Result: "=?utf-8?Q?Smith,=20John?=" <john.smith@test.com>
Should I use somekind of encoding to the first parameter to escape some characters? Which characters are forbidden?
I'm using Platform version 6.0.1.16
Thanks,
Carlos Freitas
João Rosado
Rank: #35
Posted on 2012-05-16
thumbs_up_ico
0
thumbs_down_ico
0
reply
post_link_ico
Hi Carlos,
The ',' should be an acceptable character there, but it looks like it's not being encoded propertly.
I recommend to submit issue.
Regards,
João Rosado
Acácio Porta Nova
Rank: #41
Posted on 2012-06-13
thumbs_up_ico
0
thumbs_down_ico
0
reply
post_link_ico
Carlos Freitas wrote
:
When I use the EmailAddressCreate and in the first parameter I send a string with "special" characters I get an error.
Ex: EmailAddressCreate ("Smith, John", "john.smith@test.com");
Result: "=?utf-8?Q?Smith,=20John?=" <john.smith@test.com>
Should I use somekind of encoding to the first parameter to escape some characters? Which characters are forbidden?
I'm using Platform version 6.0.1.16
Thanks,
Carlos Freitas
Hi Carlos
You are not actually getting an error - you are getting a UTF-8 encoded value for the email. That is the way to encode non-US characters following
RFC2047
, which is also valid for any US characters, though it may seem redundant.
What happens is that the Agile Platform code that does the encoding is currently (6.0.1.18 / 7.0.0.5) being more conservative than expected - if the name contains characters others than non-accented letters, numbers or space, it will fall back to encoding per RFC2047, producing the string you presented.
Both forms are
correct
and
must
present correctly in the destination email clients if they respect norms, so this should not worry you.
Cheers,
Quick Reply
Notify me by email when someone answers to my post
attachment
Choose File
No file chosen
Submit
Login to reply
Something on your mind?
Login to Start a Discussion
Top Forums Posters
Gonçalo Martins
Ricardo Silva
Charles Colaço
Richard Pearson
Davide Marquês
Statler & Waldorf
Justin James
David Chen
JD
Robert Chanphakeo
See leaderboard
Online Training
On-demand video lessons to help you learn at your own pace.
Learn More