deepl plugin fix: avoid unicode escape characters in the response containing non-ANSI characters #542
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reason for this change is avoiding to get unicode escape characters in response for non-ANSI characters potential fix for issue n3d1117#541
The main aim of this commit is preventing including .env file to image during local docker build. As well added Dockerfile, docker-compose and GitHub Actions that is not reuqurid in the Docker image
yurnov
force-pushed
the
deelp-unicode_escape-fix
branch
from
b0f0ec8 to
a631d26
Compare
yurnov
changed the title
|
Just found that in some cases it doesn't work, will investigate |
yurnov
changed the title
|
Fixed and retested, PR is ready to merge. Besides the main fix for #541 this PR includes a |
yurnov
changed the title
|
Thanks @yurnov |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
reason for this change is to get Unicode escape characters in the response containing non-ANSI characters
potential fix for issue #541
Fix tested on my side, works fine: