• Comentário oficial
    Avatar
    Alpert

    Hi

    I'm afraid this is not possible at this moment.

    We've upgraded from 3 languages to 5 at present, and for most people this is far from enough.

    But you're welcome to submit a request.

    Alpert

    Ações de comentário Permalink
  • Avatar
    Permanently deleted user

    Hi Alpert,

    too bad, but thanks for the info. I've switched over to GBoard which doesn't limit the number of languages/keyboards, but I hope to return to SwiftKey sometime in the future, I just like it a lot better ...

    Cheers,
    Olaf

    1
    Ações de comentário Permalink
  • Avatar
    Permanently deleted user

    Hi again,

    I have filed the following two feature requests:

    Cheers,
    Olaf

    0
    Ações de comentário Permalink
  • Avatar
    Alpert

    Olaf, 

    SwiftKey has a different prediction method than Gboard, that's why we limited the number of languages.

    Thanks for the requests, the team will take a look at it.

    Alpert

    0
    Ações de comentário Permalink
  • Avatar
    Permanently deleted user

    Hi Alpert,

    yes, and SwiftKey's method is a whole lot better! :-)

    Cheers,
    Olaf

    1
    Ações de comentário Permalink
  • Avatar
    Ai Lvara (ailvara)

    I understand why you would only have five languages to predict from *actually at the same time* but eg. for Chinese or Japanese you need to switch using the space anyway and I can't see why I couldn't have five languages *not counting* Chinese and Japanese then! I need those five and it's driving me nuts to get deep into the settings twice a day on average. 

    3
    Ações de comentário Permalink
  • Avatar
    Permanently deleted user

    Seconded. While the four European languages I use with Swiftkey (German, English, French, Italian and Dutch) are "mixed", i. e. they share a single keyboard (-layout), Russian requires that I swipe the space key to switch to it. That said, it not only contains a separate keyboard layout, but also its very own set of predictive text, thus limiting the amount of data traveling hence and forth.
    With languages being mixed (for instance, there's quite a few Anglicisms in the German and Dutch languages) it probably does make sense to mix the predictions as well, but only to a certain level, i. e. the common ones. Since I'm using all of the languages above on a daily basis, it often renders the predictions completely useless, i. e. proposing French words when I'm writing Dutch. I'd rather swipe to a different set altogether. Consequently, there shouldn't be much of a problem to offer more than five. For me that would eliminate the need for GBoard (which I detest).

    2
    Ações de comentário Permalink
  • Avatar
    Tomek Darda

    Hi guys, here just to agree with you and strengthen the cause on behalf of me and my multilingual friends. An option to mix/divide the same-alphabeth language would be neat and the cap on the non-latin alphabet languages seems pointless. Currently using English/Polish/German/Spanish plus Hebrew and Ukrainian. And as it is 6 I needed to switch to Gboard, where I don't really like the way to switch between languages, but what to do...

    2
    Ações de comentário Permalink
  • Avatar
    Permanently deleted user

    Thanks for your additions, Tomek. Revisiting my original post I also checked the two feature requests that I opened (see this post). I'm quite astonished to see them flagged as "solved"!?

    0
    Ações de comentário Permalink
  • Avatar
    Tomek Darda

    Hi Olaf! As I open your requests the links don't work.

    Still, the update we're suggesting seems like a simple operation, not involving any new mechanisms really. Please SwiftKey, you can do this!

    0
    Ações de comentário Permalink
  • Avatar
    Permanently deleted user

    Hi Tomek, thanks for the heads-up. Maybe they made my requests private? I can see them when being logged in, but not after having logged off. I can't find my requests by searching them either. Not sure what to think of this ...

    0
    Ações de comentário Permalink
  • Avatar
    Maddie Madwolfie

    It is even more frustrating for Chinese users as the same language has simplified and traditional keyboards; which is considered as 2 different keyboards. If we were to include Cantonese keyboard, it will become a 3rd keyboard. Thus we are effectively left with only 2 other keyboards... which is really a 3 language keyboard for us. 

    2
    Ações de comentário Permalink
  • Avatar
    Alpert

    Chinese users rarely need Simplified, Traditional, and Cantonese at the same time. Different languages are for different regions. 

    It's like English users won't enable English US, UK, and Singapore at the same time.

    0
    Ações de comentário Permalink
  • Avatar
    Maddie Madwolfie

    I suppose not that many people bother doing that. Writing to Chinese in China and Taiwan uses two different sets of characters; simplified and traditional respectively. Cantonese of course is different again. Most Chinese users I noticed however, do prefer using audio when using chat apps. This eliminates the use of typing.

    For English, be it US, UK or Singapore, it is essentially English, difference is only in spelling and usage. I don’t really need 3 keyboards for all 3 regions as it is just a matter of preference ; unlike Chinese characters, where they are very different. So there is an actual need and use for it.

     

     

    1
    Ações de comentário Permalink

Por favor, entrar para comentar.