Open glufke opened 3 months ago
Same, I wish there was a dual input, or at least a language selector based on application used to start with. I switch all the time between two languages and it's such a pain...
Dual input would be a blessing!
On Swiftkey I'd always have either English-Portuguese or English-French, as I often use English words in the middle of other-language conversations, and it works really well.
I can't stress the importance of this feature!
Living in a bilingual country, I unfortunately had to uninstall the FUTO keyboard due to the lack of this feature. It is indeed essential.
Yes please, its the 1 thing i need then this would work very well for me and alot of other people i know
Living in a bilingual country, I unfortunately had to uninstall the FUTO keyboard due to the lack of this feature. It is indeed essential.
Every day I'm stressing out because FUTO's keyboard isn't bilingual... I'm constantly switching between Portuguese with family and friends and English for business, and I feel like I'm getting white hairs by the day... It's a shame having to switch to Swiftkey after paying for the FUTO keyboard to help support this great FOSS initiative... but in it's current state I unfortunately cannot use it anymore and can't recommend it either.
I'll keep a close eye and wait for new developments to hopefully come back in the future.
I think that Is a really important feature.
But because it might take some times until it gets implemented. How are we gonna do it ourselves?
According to docs: https://gitlab.futo.org/keyboard/keyboard-wiki/-/wikis/Keyboard-LM-docs
It should be possible to create our own dictionary which is bilingual by default or not? Might totally kill all correct predictions..... Anyone tried before?
Or.... We train our own Transformer model. https://gitlab.futo.org/keyboard/keyboard-wiki/-/wikis/Keyboard-LM-docs#can-you-support-xyz-language-for-transformer-lm
I'm not sure if the automatically "Fine-tune" option in settings works for multiple languages... Probably not...
So do it yourself: https://gitlab.futo.org/keyboard/keyboard-wiki/-/wikis/Keyboard-LM-docs#model-creation
Either train our own custom Model. Or try to create a LORA to the existing model for another language... Not sure how well that might work. Maybe not at all...
Original Topic was futo-org/android-keyboard#683
It should be possible to create our own dictionary which is bilingual by default or not? Might totally kill all correct predictions..... Anyone tried before?
I spent some time trying to make a transformer following the code snippets provided in the docs, but I couldn't get it working. The docs mention:
TODO: Training notebooks
If notebooks were released to make training models trivial, I think that would fix the problem.
It'd be such a dream for the keyboard to automatically switch between languages, it is the only missing piece for me as well. An amazing app without it, but it'd be perfect with.
It would help, when you just have two languages, to change between them by longpressing the spacebar, without the extra dialog for choosing the language.
Very similar to #461 - merged that issue into this one.
It would help, when you just have two languages, to change between them by longpressing the spacebar, without the extra dialog for choosing the language.
FWIW, you can replace the Emoji button with a Language switch key, which allows you to switch languages without long pressing or showing you that dialog. Just go to Keyboard & Typing
> Edit Actions
then place Language switch key
in the Action Key
section and the Emojis
key somewhere else.
@dean-futo FWIW, I believe issue #478 and #461 are different.
@Chinoman10 Great minds… :) Anyway, @dean-futo has re-opened the present ticket. Meanwhile, I believe #461 (closed) is indeed about the same feature as #683 (still open), so I believe all should be good now? (Maybe with the exception of #708 still needing to be closed.)
@Chinoman10 thanks for elaborating. Yes, they are a different UX related to multi-lingual support and ultimately we will need to experiment to see which methods work best. Some languages are easier to implement than others and these multi-lingual support requests will be a slow rollout.
@codethief yes, they should all be consolidated enough at this point to get at the core separate types of requests, all related to multi-lingual support.
Use Cases
It's great. But there's one feature missing: it should automatically change the language according to what I type. Example: I have 2 languages installed. Sometimes I write in English, and sometimes not... The Google keyboard detects what language I'm typing, probably by the first or 2 words I type. And then it sticks with that language. That's the only thing it should be improved in order to ditch forever Google keyboard... Thanks!!!!
Proposal
No response
References
No response