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

Add Support for Importing Shared Resource Files to Multiple Languages #869

Open
metrixsam opened this issue Nov 24, 2024 · 4 comments
Open
Assignees
Labels
Feature Request Request for a new feature High Complexity Requires a lot of time and effort High Priority Get this done as soon as possible Triaged Ticket assessed and assigned

Comments

@metrixsam
Copy link

metrixsam commented Nov 24, 2024

Use Cases

The ability to select multiple languages and purposes for the same imported resource file can be extremely useful and save redundant storage space. For example, it would eliminate the need to import the same multilingual model repeatedly for individual languages, thus opening the gates for possibilities like intelligent language detection when speaking or typing.

Proposal

Solution:
This feature can be implemented through four simple steps:

  1. Altering the way of handling metadata for different languages to enable using shared resources.
  2. Altering the interface of selecting the target language for the imported resource file shown below to allow selecting multiple target languages and move the left pointing arrows to one common "next" (or arrow) button at the bottom of the screen.
    Screenshot_2024-11-24-18-32-07-26
  3. Adding a third button to resource selection pop up interfaces similar to the one below to allow using an existing resource.
    Screenshot_2024-11-24-18-37-11-50
  4. Adding another option to this menu to manage imported resource files and control whether they are shared or not, their respective language(s), etc.
    Screenshot_2024-11-24-18-41-17-23

Notes:
A similar feature was already implemented in the voiceinput project. The app automatically detects and uses the same downloaded multilingual models when enabling multiple languages. It also has an option to disable the ability to use language-specific models, as shown in the attached picture below.
IMG_20241124_180859
This allowed the app to use the same multilingual models for all languages.

References

No response

@metrixsam metrixsam changed the title Add support for importing resource file to multiple languages Add support for importing shared resource files to multiple languages Nov 24, 2024
@dean-futo dean-futo added Feature Request Request for a new feature Low Priority Get this done when you can High Complexity Requires a lot of time and effort Triaged Ticket assessed and assigned labels Nov 27, 2024
@dean-futo dean-futo changed the title Add support for importing shared resource files to multiple languages Add Support for Importing Shared Resource Files to Multiple Languages Nov 27, 2024
@metrixsam
Copy link
Author

I believe this can open the gates for effectively implementing #683 and all of its duplicate and related issues like #140, #226, #684, #425, #74, #478, #158, etc.

@metrixsam
Copy link
Author

Just wanted to check in on the progress so far (if any) regarding this feature request. I also wanted to point out that since this feature request can make it easier to implement other features involving intelligent multilingual functionality, it would be great if @dean-futo changes the priority of this issue to "high" so it doesn't get discarded over time.

@dean-futo dean-futo added High Priority Get this done as soon as possible and removed Low Priority Get this done when you can labels Dec 14, 2024
@sirenpupil
Copy link

Will this feature get implemented? I have multilingual models that can benefit from it.

@dean-futo
Copy link
Contributor

dean-futo commented Jan 30, 2025

Yes. Multilingual typing is a mid-term priority for us and this will come once that's implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Request for a new feature High Complexity Requires a lot of time and effort High Priority Get this done as soon as possible Triaged Ticket assessed and assigned
Projects
None yet
Development

No branches or pull requests

4 participants