Can't type in the input box in Korean. #210
Rótulos
Sem rótulo
1app
2 apps
accessibility
android
before-beta
bug
duplicate
enhancement
first-contact
fixed
help wanted
infrastructure
invalid
low-priority
must-fix
needs testing
nice-to-have
question
tor
user-feedback
wontfix
Sem etapa
3 Participantes
Data de vencimento
Sem data de vencimento definida.
Dependências
Não estão definidas dependências.
Referência: cwtch.im/ui#210
Carregando…
Criar uma nova questão referindo esta
Nenhuma descrição fornecida.
Eliminar o ramo "%!s(<nil>)"
Eliminar um ramo é algo permanente. Embora o ramo eliminado possa continuar a existir por um breve período de tempo antes de ser realmente removido, a operação NÃO PODERÁ ser desfeita na maioria dos casos. Quer continuar?
I tried to chat with one of my friend in Korean but failed to type.
For typing Korean, some special method is used.
In Korean '간' is a combination of 'ㄱ, ㅏ, ㄴ'.
While I type each of 'ㄱ, ㅏ, ㄴ', they must to be held for the combination.
But cwtch.im's input box doesn't.
Letters can be copied from clipboard and can be sent, though.
Because they're already combined.
Thank you for the report.
Just to confirm, the issue is that the input box doesn't allow the combination of the three characters?
Some notes for likely fixing this:
Either way it seems like while this was a bug in qml in the past (https://bugreports.qt.io/browse/QTBUG-52486) it should be fixed in 5.13 so we just have to work out why it's not being supported in our main input box.
Sorry for confusion. That combination is just an example.
I can’t type a single letter of Korean.
Such as 가 = ㄱㅏ, 닮 = ㄷㅏㄹㅁ
It looks like same problem as the link.
I’ll check it with both old and new version of QT by my own.
Thank you for the answer
@kjs104901: would you mind testing this with some of the other text input boxes in the cwtch ui? in particular, if you go to any of the settings panes and change a group/contact name, do the characters input properly in those text boxes? that should tell us whether the problem is our Qt setup, or our custom behaviour on the message typing field.
@sarah someone should test this again, now that we've reverted to a plaintext box