Comma in "Amount to pay" number

[acronymy]

Describe the bug

When enetering a number with a comma in "Amount to pay", Zeus truncates amount once CONFIRM selected. This issue would arise if one was copying a sats amount from satsconverter.io for example.

Reproduce

Lightning Send Lightning payment request address 85,879 Amount to pay CONFIRM Next screen now shows 85 sats only.

Zeus version

v0.8.0

Node interface

LndHub

Network

Clearnet

Device

Pixel 4a

Device operating system

Android 13 GrapheneOS

Log output

No response

[myxmaster]

Yes, we can definitely improve UI here.

General thoughts: It depends on the currently configured app language how "," and "." should be interpreted, because some languages use "," as thousands separator and "." as decimal separator and some languages do it the other way round. In general a space char is the best option for thousands seperator, as this cannot be misinterpreted as decimal separator, but it still makes it easy to read thousands.

So, what about this (examples are in English with ","=thousands separator and "."=decimal separator):

• If a number with thousands separator is pasted 10,123, the thousands separator gets immediately replaced with a space char 10 123.
• If a number with thousands separator is entered 10,123, the thousands separator gets replaced with a space char when text input lost focus 10 123.
• If a number with decimal separator is pasted or entered 1.5 sats, it will stay like that 1.5 sats unless it is a sub sat amount and current backend does not support this -> in this case Zeus will truncate decimal places 1 sat (again immediately for pasting and after losing focus for entering OR we could directly block decimal separator input).
• If a thousands separator is used incorrectly 10,24 or 0,123, Zeus will display an error.