doc update

CHANGELOG

@@ -3,6 +3,9 @@ jc changelog
 20220426 v1.18.8
 - Fix UnicodeEncodeError on some systems where LANG=C is set and unicode
   characters are in the output
+- Update history parser: do not drop non-ASCII characters if the system
+  is configured for UTF-8 encoding
+- Enhance "magic syntax" to always use UTF-8 encoding
 
 20220425 v1.18.7
 - Add git log command parser

README.md

@@ -425,6 +425,9 @@ or by exporting to the environment before running commands:
 $ export LANG=C
 ```
 
+On some older systems UTF-8 output will be downgraded to ASCII with `\\u`
+escape sequences if the `C` locale does not support UTF-8 encoding.
+
 #### Timezones
 
 Some parsers have calculated epoch timestamp fields added to the output. Unless

docs/utils.md

@@ -1,6 +1,7 @@
 # Table of Contents
 
 * [jc.utils](#jc.utils)
+  * [asciify](#jc.utils.asciify)
   * [warning\_message](#jc.utils.warning_message)
   * [error\_message](#jc.utils.error_message)
   * [compatibility](#jc.utils.compatibility)
@@ -18,6 +19,17 @@
 
 jc - JSON Convert utils
 
+<a id="jc.utils.asciify"></a>
+
+### asciify
+
+```python
+def asciify(string: str) -> str
+```
+
+Return a string downgraded from Unicode to ASCII with some simple
+conversions.
+
 <a id="jc.utils.warning_message"></a>
 
 ### warning\_message

man/jc.1

@@ -686,6 +686,8 @@ or by exporting to the environment before running commands:
 $ export LANG=C
 .RE
 
+On some older systems UTF-8 output will be downgraded to ASCII with `\\u` escape sequences if the \fBC\fP locale does not support UTF-8 encoding.
+
 \fBTimezones:\fP Some parsers have calculated epoch timestamp fields added to the output. Unless a timestamp field name has a \fB_utc\fP suffix it is considered naive. (i.e. based on the local timezone of the system the \fBjc\fP parser was run on).
 
 If a UTC timezone can be detected in the text of the command output, the timestamp will be timezone aware and have a \fB_utc\fP suffix on the key name. (e.g. \fBepoch_utc\fP) No other timezones are supported for aware timestamps.

templates/manpage_template

@@ -201,6 +201,8 @@ or by exporting to the environment before running commands:
 $ export LANG=C
 .RE
 
+On some older systems UTF-8 output will be downgraded to ASCII with `\\u` escape sequences if the \fBC\fP locale does not support UTF-8 encoding.
+
 \fBTimezones:\fP Some parsers have calculated epoch timestamp fields added to the output. Unless a timestamp field name has a \fB_utc\fP suffix it is considered naive. (i.e. based on the local timezone of the system the \fBjc\fP parser was run on).
 
 If a UTC timezone can be detected in the text of the command output, the timestamp will be timezone aware and have a \fB_utc\fP suffix on the key name. (e.g. \fBepoch_utc\fP) No other timezones are supported for aware timestamps.

templates/readme_template

@@ -328,6 +328,9 @@ or by exporting to the environment before running commands:
 $ export LANG=C
 ```
 
+On some older systems UTF-8 output will be downgraded to ASCII with `\\u`
+escape sequences if the `C` locale does not support UTF-8 encoding.
+
 #### Timezones
 
 Some parsers have calculated epoch timestamp fields added to the output. Unless