patch 9.1.1223: wrong translation used for encoding failures

Problem:  wrong translation for encoding failures because of using
          literal "from" and "to" in the resulting error message
          (RestorerZ)
Solution: use separate error messages for errors "from" and "to"
          encoding errors.

fixes: #16898
closes: #16918

Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
Christian Brabandt
2025-03-18 20:55:42 +01:00
parent 8ac0f73eb1
commit d5afc74403
6 changed files with 15 additions and 10 deletions

View File

@ -1311,7 +1311,7 @@ blob2str({blob} [, {options}]) *blob2str()*
encoding. The value is a |String|. See
|encoding-names| for the supported values
(plus the special value "none").
*E1515*
*E1515* *E1516*
When current 'encoding' is "utf-8", an error is given and an
empty List is returned if an invalid byte sequence is
encountered in {blob}. To suppress this validation and get

View File

@ -4589,6 +4589,7 @@ E1512 options.txt /*E1512*
E1513 message.txt /*E1513*
E1514 options.txt /*E1514*
E1515 builtin.txt /*E1515*
E1516 builtin.txt /*E1516*
E152 helphelp.txt /*E152*
E153 helphelp.txt /*E153*
E154 helphelp.txt /*E154*