You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When users take a picture with the "Scan Document" function and enter the file name, there is a problem with entering Japanese (2-byte characters).
I've written about it in my forum, including the current issues, so please take a look there as well. https://central.owncloud.org/t/support-for-2-byte-characters-in-scan-document/29856
Describe the solution you'd like
I want to use Japanese (2-byte characters) in file names without any problems.
Describe alternatives you've considered
The only way to solve this problem is to use 1-byte characters.
The text was updated successfully, but these errors were encountered:
Bables55
changed the title
[FEATURE REQUEST] Japanese(2-Byte charactor) input support
[FEATURE REQUEST] Japanese(2-Byte character) input support
Mar 4, 2021
* #916 UITextfield: fixed a problem that text cursor jumps to the end of the text after entering a Japanese character
* Calens changelog updated
* StaticTableViewRow: avoid self-triggered/circular update of textfields (user entry in textfield -> set value property -> replace value in textfield)
* Calens changelog updated
Co-authored-by: hosy <[email protected]>
Co-authored-by: Felix Schwarz <[email protected]>
Is your feature request related to a problem? Please describe.
When users take a picture with the "Scan Document" function and enter the file name, there is a problem with entering Japanese (2-byte characters).
I've written about it in my forum, including the current issues, so please take a look there as well.
https://central.owncloud.org/t/support-for-2-byte-characters-in-scan-document/29856
Describe the solution you'd like
I want to use Japanese (2-byte characters) in file names without any problems.
Describe alternatives you've considered
The only way to solve this problem is to use 1-byte characters.
Additional context
1: https://od.lk/s/M18yNDA3ODk3NDdf/oc-flickjapanese.MP4 2
2: https://od.lk/s/M18yNDA3ODg4ODNf/oc-qwertyjapanese.mp4
TASKS
PR
The text was updated successfully, but these errors were encountered: