You are right, nice find! Contact form as well as Messages view always have the first name before last. Side note: one needs to reboot (or killall voicecall-ui) for name order setting to take effect in Dialer.
I wanted to wait with that patch until the community modifications would have some formal process (ie. QML parts would be put to git).
That suggests you wouldn’t prefer to follow community’s currently existing formal process via NDA:)
We haven’t put a concrete date on open-sourcing QML parts, as I believe licensing would also need to be decided somehow, or other hurdles.
Do I think correctly if we translate these strings properly the contact editor field order will follow it?
Token format strings are only used when importing contacts without clear separation of their name parts. E.g. in a SIM card a contact is stored as “John Doe”, so we need to localise the most common use-case for your language (obviously, all international contacts would get imported wrongly, if you are importing a Hungarian’s address book).
This string does not determine the order UI elements are displayed. I have updated content instructions to reflect each case (2, 3, and 4 name parts) with an example (one English, and one Hungarian, to the best of my knowledge:))
Hmm that sounds interesting. What tool do you consider replacing the pootle? I tried several open alternatives (Zanata, Weblate) but I found pootle the easiest to manage and most powerful.
How would WebLate be inferior to Pootle if you could name a few?
