[Enhancement] Inclusion of special characters as accents in the letters for pashphrases about krux HOT 4 OPEN

I've tested this with Sparrow, Seed Tool and Krux create a different fingerprint when scanning á as passphrase from QR code. This is a problem even if Krux can't type these special characters, both Sparrow and Seed Tool show 411905a1 for fingerprint, but Krux show 9325504a

from krux.

Just a thought on this:

• when creating a new bip39 passphrase... device should be strict and only allow keys that are most common to most keyboards, else it could be difficult to recover on different devices/wallets.
• when recovering an existing bip39 passphrase... device should be tolerant in allowing as many keyboards as might have been used to create the original wallet.

Not sure how best to achieve that on a stateless device, but would love to hear others' ideas on this.

I suspect that krux's "tools / create qrcode" might be useful, because maybe it could have many different keyboards, whereas "enter passphrase" is more limited, and the resulting qrcode with full utf support could be used to recover bip39 based wallets by scanning the self-created qrcode during the "scan passphrase" step of loading a wallet.

from krux.

This is a big problem!

from krux.

Incorporating a variety of language glyphs could compromise the user experience and pose risks; therefore, we currently have no plans to implement such a feature.

from krux.