From d052db8abbf86d01b1b39ef5663a8e24648ef30c Mon Sep 17 00:00:00 2001 From: Martchus Date: Thu, 18 May 2017 17:29:15 +0200 Subject: [PATCH] Add note about encoding --- README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index c381995..a08a476 100644 --- a/README.md +++ b/README.md @@ -217,8 +217,12 @@ Here are some Bash examples which illustrate getting and setting tag information a file has been processed. ## Text encoding / unicode support -1. It is possible to set the preferred encoding used *within* the tags via CLI option ``--encoding`` and - in the GUI settings. +1. It is possible to set the preferred encoding used *within* the tags via CLI option ``--encoding`` + and in the GUI settings. + * However, in the GUI this only affects visible fields. In the CLI only specified fields are + affected. So reencoding all text fields is currently not supported. + * The option is ignored (with a warning) when the specified encoding is not supported by the + tag format. 2. The CLI assumes all arguments to be UTF-8 encoded (no matter which preferred encoding is specified) and file names are just passed as specified. 3. The CLI prints all values in UTF-8 encoding (no matter which encoding is actually used in the tag).