Proposal: Optional Search Term Translation for Non-English Users

[shati89406]

As a Japanese speaker, I find it a bit inconvenient that SmartScan currently only supports English search queries.

Of course, I understand that this is due to limitations of the CLIP model, not a problem with SmartScan itself.

Still, I’d like to suggest adding an optional feature to automatically translate non-English queries into English before running the search.

Here are two possible implementation options:

• Use a Python library such as googletrans

• Or use the Google Translate Endpoint directly

This would help make SmartScan more accessible for users who search in languages other than English.

I hope this idea might be useful. Thanks for reading!

[woheller69]

This would require internet permission even if it is just optional which the app does not need currently...

[shati89406]

You’re absolutely right—I overlooked the permission issue. My apologies for the oversight.

If file size and performance permit, I’d prefer a fully offline translation solution, for example using Argos Translate or a similar local translation library.

[dev-diaries41]

You’re absolutely right—I overlooked the permission issue. My apologies for the oversight.

If file size and performance permit, I’d prefer a fully offline translation solution, for example using Argos Translate or a similar local translation library.

Yes so as @woheller69 explained, though I would want to do this it would sacrifice the fully offline benefit I think most users appreciate.

Using a local model to perform offline translation could work but this would very likely result in APK file size being bloated, its already quite high as is. The alternative would be allowing the user to download model(s) at runtime, meaning the APK size won't change. However, again this would require internet permission, though with clear explanation users may not mind. I will have think about it.

[woheller69]

Users could download models via a separate browser. Then you would only need to import a file.

[dev-diaries41]

This seems like the best middle ground.

[yfdyh000]

Here's a compromise idea: the app outputs the original untranslated English tags, then the user send the tags to a translation tool (offline, online or LLM), then paste the translated content back while keeping the original format (e.g. text, .md or .json). This lets the app map the original to its translations.
The user should be reminded that these tags may contain privacy-related content. This also saves users from installing a large language model, provided they already have a local translation app or trusted translation interface.