Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

engage-api-client and UTF-8 requests #52

Closed
bdbavis opened this issue Mar 15, 2016 · 4 comments
Closed

engage-api-client and UTF-8 requests #52

bdbavis opened this issue Mar 15, 2016 · 4 comments

Comments

@bdbavis
Copy link

bdbavis commented Mar 15, 2016

It seems that the API fails to handle Cyrillic letters when sending them to Engage.

@smitchelus
Copy link
Contributor

@bdbavis, could you provide more detail? Some examples of the calls you are making?

@bdbavis
Copy link
Author

bdbavis commented Mar 15, 2016

@smitchelus
I'm using AddRecipientCommand() to add new contact to my DB on Silverpop,
One of the columns that i'm sending on my request is the name of the customer.
When the name contain Cyrillic letters like чийнбд it appears on DB as ?????.
I think that the problem is that the client API does not use UTF-8 when sending the request to Engage.

@smitchelus
Copy link
Contributor

@bdbavis, if you need to use an encoding other than your JVM's default encoding then you would need to wrap the API command in an EncodedApiCommand and specify the desired encoding in there.

For example:
ApiCommand command = commandFactory.createSaveMailingCommand(mailing);
EncodedApiCommand encodedCommand = new EncodedApiCommand(command, "UTF-8");

@bdbavis
Copy link
Author

bdbavis commented Mar 23, 2016

@smitchelus
thanks... you helped me a lot :-)

@bdbavis bdbavis closed this as completed Mar 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants