Translation not working
See original GitHub issue- Download https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/commit/82355cdb608c4acc5a42ace2079916ddd9b63576 as zip, extract to sd webui’s extension folder
\extensions\tag-complete\
- Create
test.csv
with content below and save with UTF-8 encoding, place it into\extensions\tag-complete\tags\
solo,0,单人
- Change line 24 of
\extensions\tag-complete\tags\config.json
from"extraFile": "",
to"extraFile": "test.csv",
- Launch sd webui and wait for tagcomplete loaded, then type
sol
in prompt textbox
Expected result:
Actual result:
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Fix: Google Translate Is Not Working in Chrome and Android?
What to Do if Google Translate Is Not Working in Chrome? · Upgrade Google Chrome · Disable Extensions in Chrome · Use Incognito...
Read more >How to Fix Google Chrome Translate Not Working - TechPP
8 Ways to Fix Google Chrome Translate Not Working · Fix #1: Update Google Chrome Version · Fix #2: Turn On Translate Prompts...
Read more >How to Fix Google Chrome Translate Not Working Issue in 2022
Fix Google Translate does not work in Chrome Issue · Make sure you have a proper internet connection, which is very important to...
Read more >How to Fix Google Chrome Translate Not Working
There are several reasons as to why Chrome may fail to translate foreign websites. It could be due to improperly configured language settings, ......
Read more >Translate Not Working in Chrome: 5 Quick Ways to Fix it
1. Update Chrome · 2. Delete browsing data · 3. Disable Extensions · 4. Use the Google Translate extension · 5. Reset Chrome...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think I was already able to fix it, at least I don’t see any more cutoff on my side with your test tags. But feel free to reopen this if you find something that still behaves strange with translations.
I changed it to work like in your first suggestion for now. Translations need to be added in a new separate CSV file, not as an extra file anymore. Default is just two columns with English as first and Translation as second, but I also included a config switch for the old extra format with 3 columns if you use one of those files. The translations are currently always visible, and are matched purely based on the tag/alias name. Searching by the translated text still works like before if you leave it true in the config.