# PR Checklist
- [x] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
There was an issue where the autoTranslateCachedOnly option was being
ignored when sending messages. This occurred due to the way the
translated variable was initialized with let translated =
$state(DBState.db.autoTranslate).
# PR Checklist
- [x] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
This PR fixes hypav2 issue where the "search_document: " string is not
truncated correctly.
If the "search_document: " string is not truncated correctly, it will
cause "t: " to remain within the <Past Events Details></Past Events
Details> tag.
Edit: This PR also add memo "supaPrompt" to detect supaMemory model
requests in the plugin
# PR Checklist
- [ ] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
This PR fixes an issue where indentation and whitespace inside the
{{#if_pure}} syntax were being trimmed.
I made an effort to minimize the impact on the parser's existing
behavior.
# PR Checklist
- [x] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
This PR introduces a fix for the issue where the input auto-translation
field ("Enter Message for Translate to English" text displayed when
nothing is entered) was not correctly translating the original text into
English in the LLM-based translation.
Additionally, this update ensures that "Curly Braced Syntaxes {{slot}}"
are translated into the user's native language when the translation
button is pressed, and into English during the input translation,
facilitating more effective translation.
# PR Checklist
- [x] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
This PR introduces a fix for an issue where cache misses occur when
translateBeforeHTMLFormatting is disabled. Previously, the 'Auto
Translate Cached Only' feature only worked when
translateBeforeHTMLFormatting was enabled. This update ensures that
cached translations are used properly even when
translateBeforeHTMLFormatting is disabled.
Thank you for taking the time. This is not an urgent matter, but I would
appreciate it if you could incorporate this PR along with other changes
in the next update.
# PR Checklist
- [x] Did you check if it works normally in all models? *This PR does
not affect models.*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? *This PR only modifies translations.*
- [x] Did you added a type def? *No type definitions were required for
this PR.*
# Description
This PR updates the Traditional Chinese translations to improve
consistency and better align with user preferences.
Key changes include:
- Retained the term "lorebook" as it remains commonly used among
Traditional Chinese users.
- Adjusted some wording, such as changing "頭貼" to "頭像," as "頭像" has been
widely used by Traditional Chinese users since at least 2008. This
change was also confirmed by professional translators as the preferred
term.
- Retained English terms such as "Enable Schema" for technical clarity,
as no established Traditional Chinese translations exist for these
terms.
This PR was created by adapting the translations from the RisuAI `.json`
translation file. The formatting has been carefully reviewed, and I hope
there are no issues.
# PR Checklist
- [x] Did you check if it works normally in all models? *This PR does
not affect models.*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? *This PR only modifies translations.*
- [x] Did you added a type def? *No type definitions were required for
this PR.*
# Description
This PR updates the Simplified Chinese translations to better align with
user preferences.
Key changes include:
- Changed "lorebook" to "世界书," a commonly used term among Simplified
Chinese users.
- Retained English terms such as "Enable Schema" for clarity.
I updated some wording in the Traditional Chinese translations and completed some unfinished translations in this version. This update was completed independently by me.
For "lorebook," I chose to retain the original term, as it is still commonly used among Traditional Chinese users (at least based on my understanding).
I also fine-tuned some phrases, such as changing "頭貼" to "頭像." I discovered that "頭像" has been commonly used by Traditional Chinese users as early as 2008. Professional translators also confirmed that they generally use this translation.
Similar to the Simplified Chinese version, I decided to retain some technical terms like "Enable Schema" in English. Since there are no established Traditional Chinese equivalents for these terms, keeping them in English is considered more intuitive by many users.
This file was created by copying and adapting the translations from the RisuAI .json translation file. I have carefully checked the formatting and hope there are no issues.
Additionally, this is my first time uploading a branch... I didn’t initially realize the importance of preserving version comparisons on GitHub. However, since the previous submissions for both the Traditional and Simplified Chinese translations were also made by me, I believe this won’t cause significant problems.
Extended Description: I have updated the word choices in Simplified Chinese translations to better align with the preferences of Simplified Chinese users. This update also includes some unfinished translations from the previous version.
With the help of several Simplified Chinese-speaking friends, I performed a thorough review of the translations. They pointed out that I occasionally used phrasing that reflects Traditional Chinese grammar habits. However, they confirmed that the current version is still clear and widely acceptable among Simplified Chinese users.
The main correction is translating "lorebook" to "世界书" in most cases, as this is the common term used by the Simplified Chinese community. Additionally, I decided to retain some technical terms, such as "Enable Schema," in English. Since there is no widely accepted Chinese translation for these terms, keeping them in English provides greater clarity and professionalism.
Lastly, this file was created by copying and adapting the translations from the RisuAI .json translation file. I have carefully checked the formatting and hope there are no issues.
# PR Checklist
- [x] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [x] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
Please introduce an autoTranslateCachedOnly option that automatically
translates only previously translated text when enabled.
# Why is this feature needed?
- LLM-based translations can be relatively costly, so end users may not
want new/specific text to be automatically translated.
- End users may prefer not to manually click the translate button when
viewing chat logs that have already been translated.
- By utilizing cached translations more effectively, we can enhance the
overall user experience.
# PR Checklist
- [ ] Did you check if it works normally in all models? *ignore this
when it dosen't uses models*
- [ ] Did you check if it works normally in all of web, local and node
hosted versions? if it dosen't, did you blocked it in those versions?
- [ ] Did you added a type def?
# Description
Current build doesn't have aws key slot.
Thank for your time.
