-
Notifications
You must be signed in to change notification settings - Fork 32
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
Invalid character caused by utf8_encode #117
Comments
I think that this utf8_encode is used because XML encoding is utf8. |
@maisoui if you find, that utf8_encode is breaking the request, then I think we can remove encoding. |
In case of code and passed string is already in unicode, utf8_encode will break the request. |
No need. Because we generating document in the code. Thus we already know it encoding. |
This utf8_encode was added specially for values with umlauts. |
I guess this litlle snippet can do the job.
(will be included in my incoming pull request) Regards |
Better to shift the logic for encoding values into Transfer document builder. |
agree |
fixed in #146 :) Tested with real transactions for all umlauts:
|
Hi,
My xml contains invalid characters due to the use of
utf8_encode
in methodData::getContent()
.Example : "München" becomes "München" and request will be rejected by bank server.
Is it really necessary to use
utf8_encode
?Best regards
The text was updated successfully, but these errors were encountered: