-
Notifications
You must be signed in to change notification settings - Fork 93
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
Temp file encoding of curl payloads #77
Comments
Hi, We have this issue with org-trello and all of non-English users could not use it. @gariepyalex Could you kindly send a PR? |
Hi! Sorry, but your workaround isn't working for me... I changed your code a litle: (setq buffer-file-coding-system 'utf-8)
(insert data)
(decode-coding-region (point-min) (point-max) 'utf-8))) |
Is there an alternative version of the |
Matt Price <notifications@github.com> writes:
@DamienCassou have you thought about sharing your fork?
I don't want to invest time in maintaining a fork right now.
…--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
|
Does #85 fix this issue for you @gariepyalex and @MaksVal ? |
@titaniumbones this is a fine solution! Thanks! |
What is exactly the status of this issue? I have an issue with anki-editor (louietan/anki-editor#51) which seems related to this... (I'm using request 0.3.1, but with master I had the same problem) |
While we still heavy-handedly default the encoding to utf-8, we fall back to no-conversion if that assumption fails (rather than allowing `select-safe-coding-system` to bring up a confusing dialogue). Closes tkf#77
@rogorido We made a backwards incompatible change in release 0.3.1. louietan/anki-editor#53 updates your package to be compatible with 0.3.1. #128 attempts to mitigate other fallouts of this kind. |
Yes, thanks you.
пт, 30 нояб. 2018 г., 3:51 Matt Price <notifications@github.com>:
… Does #85 <#85> fix this issue
for you @gariepyalex <https://github.com/gariepyalex> and @MaksVal
<https://github.com/MaksVal> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#77 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJpVj5aeXt57TFOhogAtY83xKJt0EHn8ks5u0IEmgaJpZM4Nivpa>
.
|
Commit 1562f9c seems to conflate the desire to encode request data in utf8 with also decoding server output. In light of tkf#157 and tkf#158, I am removing utf-8 decoding altogether. The impetus to encode to utf-8 in tkf#77, tkf#85, and github/org-trello/#340 suggest nothing about also decoding in utf-8, so I am crossing my fingers I won't rebreak for them. Also, clean up logging. It was impossible to follow with all the capital letters.
When send an HTTP payload using curl, emacs-request make use of a temp file for the content of the payload. However, when the payloads contains non-ascii characters, the temporary file is encoded in latin1 instead of in utf-8.
The problem seems to come from there:
fb93d11
Changing the code to:
seems to fix the problem. I can open a pull request if you want.
The text was updated successfully, but these errors were encountered: