From a126ca8481b41c46231da4b927520c37c7302fc4 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 7 Jul 2017 10:47:46 +0200 Subject: [PATCH] curl_easy_escape.3: mention the (lack of) encoding Fixes #1612 Reported-by: Jeroen Ooms --- docs/libcurl/curl_easy_escape.3 | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/libcurl/curl_easy_escape.3 b/docs/libcurl/curl_easy_escape.3 index d2b6cd2861..c8b7b6a4b1 100644 --- a/docs/libcurl/curl_easy_escape.3 +++ b/docs/libcurl/curl_easy_escape.3 @@ -5,7 +5,7 @@ .\" * | (__| |_| | _ <| |___ .\" * \___|\___/|_| \_\_____| .\" * -.\" * Copyright (C) 1998 - 2014, Daniel Stenberg, , et al. +.\" * Copyright (C) 1998 - 2017, Daniel Stenberg, , et al. .\" * .\" * This software is licensed as described in the file COPYING, which .\" * you should have received as part of this distribution. The terms @@ -39,6 +39,15 @@ If \fIlength\fP is set to 0 (zero), \fIcurl_easy_escape(3)\fP uses strlen() on the input \fIstring\fP to find out the size. You must \fIcurl_free(3)\fP the returned string when you're done with it. +.SH ENCODING +libcurl is typically not aware of, nor does it care about, character +encodings. \fIcurl_easy_escape(3)\fP encodes the data byte-by-byte into the +URL encoded version without knowledge or care for what particular character +encoding the application or the receiving server may assume that the data +uses. + +The caller of \fIcurl_easy_escape(3)\fP must make sure that the data passed in +to the funtion is encoded correctly. .SH AVAILABILITY Added in 7.15.4 and replaces the old \fIcurl_escape(3)\fP function. .SH RETURN VALUE