Point to vmod-iconv, update generated RST

src/vmod_j.man.rst

@@ -241,8 +241,8 @@ JSON does not strictly mandate strings to contain valid UTF-8. `RFC
 however
 
    When all the strings represented in a JSON text are composed
-   entirely of Unicode characters [...] (however escaped), then that
-   JSON text is interoperable [...]
+   entirely of Unicode characters [...], then that JSON text is
+   interoperable [...]
 
 For the most part, this module is not concerned with whether or not
 strings represent valid UTF-8 or Unicode:
@@ -261,6 +261,14 @@ The two exceptions are:
 * `j.unquote()`_ fails if the input is not a valid JSON string or if
   invalid UTF-8 would be produced.
 
+Other character encodings
+-------------------------
+
+.. _vmod-iconv: https://gitlab.com/uplex/varnish/libvmod-iconv
+
+Strings in other encodings should be converted to UTF-8 using
+`vmod-iconv`_ before being used with this VMOD.
+
 VMOD INTERFACE REFERENCE
 ========================
 

src/vmod_j.vcc

@@ -247,6 +247,14 @@ The two exceptions are:
 * `j.unquote()`_ fails if the input is not a valid JSON string or if
   invalid UTF-8 would be produced.
 
+Other character encodings
+-------------------------
+
+.. _vmod-iconv: https://gitlab.com/uplex/varnish/libvmod-iconv
+
+Strings in other encodings should be converted to UTF-8 using
+`vmod-iconv`_ before being used with this VMOD.
+
 VMOD INTERFACE REFERENCE
 ========================