Fix chat translation escape sequences and message cut-off#249
Merged
RedShyGuy merged 1 commit intoRedShyGuy:release/3.3.0from Mar 24, 2026
Merged
Fix chat translation escape sequences and message cut-off#249RedShyGuy merged 1 commit intoRedShyGuy:release/3.3.0from
RedShyGuy merged 1 commit intoRedShyGuy:release/3.3.0from
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This fixes escape sequences like "\n" and "\u003d" contained in the response string from google translate by unescaping the string. Also, when google translate detects multiple sentences in the request, the sentences will be split up into multiple JSON array elements in the response. These are now handled properly. Previously, only the first element was handled, and thus the message sometimes got cut off.