Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Each website can set its own Tags whitelist and blacklist. #826

Open
1 task
vagra opened this issue Apr 13, 2024 · 0 comments
Open
1 task

[Feature] Each website can set its own Tags whitelist and blacklist. #826

vagra opened this issue Apr 13, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@vagra
Copy link

vagra commented Apr 13, 2024

Is your feature request related to a problem? Please describe

The main reason for this is that elements like div.search-title in GitHub search results page, which are the names of code repositories, do not need to be translated. Translating them could actually make them less recognizable.

Describe the solution you'd like

For instance, on GitHub. I might want to translate only the <article> tag or the <span> tag with the .search-match class. In that case, I can simply edit the settings for the website, using the syntax standard of CSS selectors, to add article and span.search-match to the whitelist. Consequently, TWP will only translate page elements that meet these two rules.

If this rule can support full CSS selectors, that would be perfect.

This will also greatly reduce the amount of text that needs to be translated on the page.

Describe alternatives you've considered

No response

Additional context

No response

Did you fill in all the fields correctly?

  • Yes, everything is fine!
@vagra vagra added the enhancement New feature or request label Apr 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant