Open greskom opened 3 years ago
Hello,
the second problem with contact with edited name self healed and I cannot understand why. I found out on the contact with the name Mumu existed still on the nextcloud server, I deleted it. Then I was going to try to synchronize to the phone, but I found it turned off. After turning on the second issue was gone even without synchronization. Strange both things. Why it was turned off and why it healed itself without sync. I tried reboots before so I do not expect it self healed because of reboot. The only outcome now is that editing of the names is dangerous operation here. In cse of the need of the name editing it is probably better to delete contact and create new one.
Marek
Hello,
is it a so big problem to revert the change? The change was a total non-sense.
Thanks
Marek
Hello,
is it a so big problem to revert the change? The change was a total non-sense.
Thanks
Marek
Hello,
What are you asking ?.What would be to revert ?
I can have a look at the alphabetic order issue
Hello,
this issue has been introduced in some OTA. It was working OK before.
Marek
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, November 21st, 2021 at 20:43, Lionel Duboeuf @.***> wrote:
hello, i don't get
Hello,
is it a so big problem to revert the change? The change was a total non-sense.
Thanks
Marek
Hello,
What are you asking ?.What would be to revert ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
after a quick look, i don't see anything change that could modify that. btw, as new contact backend is coming next, we will need to wait for it before digging to that issue
Maybe two or three OTAs back? The bud report was probably created short time after the issue appeared.
Marek
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, November 22nd, 2021 at 14:08, Lionel Duboeuf @.***> wrote:
after a quick look, i don't see anything change that could modify that. btw, as new contact backend is coming next, we will need to wait for it before digging to that issue
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Well sorry but haven't found anything that could modify the sort order rule since 4 years ;-) . And i'm afraid that it is an external component who is responsible to do that. So can't say much about it.
Could be.
Marek
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, November 22nd, 2021 at 18:18, Lionel Duboeuf @.***> wrote:
Well sorry but haven't found anything that could modify the sort order rule since 4 years ;-) . And i'm afraid that it is an external component who is responsible to do that. So can't say much about it.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.
Steps to reproduce
Open contacts in dial application.
Expected behavior
Contact sorted correctly in Slovak language (L comes before Ľ - always):
L: Lala Lolo Lulu
Ľ: Ľaľa Ľuľu
M: Momo
Actual behavior
Contacts are sorted incorrectly in Slovak localization. I can see (on Volla):
L: Lala
Ľ: Ľaľa
L: Lolo Lulu
Ľ: Ľuľu
M: Momo
Moreover I have contact which name started on M, I edited it to start on L (the Lolo one - was Mumu before). On the original device (Volla) I edited it it is under L as seen before, but on the device I synchronized to (BQ) (using nextcloud and syncevolution) it is like this:
L: Lala
Ľ: Ľaľa
L: Lulu
Ľ: Ľuľu
M: Momo
L: Lolo
So it is placed like it is still Mumu, but the name and label are correct. Where the position comes from? Is it stored somewhere in the contact still? Is it needed to delete and create the contact in case the name changes?