I am running my anual christmascard cycle again using my nextcloud conctact database.
I noticed this year there are quite a bit of changes in nextcloud. Most of them improvements, but I stumbled upon a couple of setbacks that I want to share before running into bug reporting mode.
#1 Some contact were reported corrupt. but when I tried to fix them (with the popup button at the top) I got a spinning circle that ran forever, eventually crashing my browser. I read in a post about the workaround of opening and saving them in Thunderbird. That worked. one by one I fixed a handfull out of 98 addresses.
#2 When I downloaded the christmascard category for post-processing (I run a python script to set all the LABEL fields wit the correctly formatted postal addres for adress stickers) I ran into an error.
Apperantly the vcfs lack a newline between contacts, resulting in lines with
which my script unfortunately couldn’t handle. I had to do some regexp work in emacs to fix those:-)
#3 I think the encoding of the characters changed. Last year I could read the international characters in a console : François. This years version is Fran�ois
I assume this was a change for the better. But it broke my fgrep counting as well. Took me quite some time to realise that I didn’t miss contacts, but they were simply not counted by fgrep because it skips ‘binary’ lines unless you give the -a option.
If someone can give me the background on this format change, I’d be interested though.
I’m now at the stage where I have all my addresses in correctly formated vcf file with the right LABEL field. But I wanted to share my experience. At least #2 is a real bug I think. #1 is a bug, but I read it is being investigated. #3 is an encoding side effect I assume.
Btw, I would still be interested in automatic filling of the ADR LABEL field for formatted addresses.
This should be filled based on the local address format custom so you can print the label on envelopes for mailings. I have an python script now to do that. But it would be great if that could be integrated in nextcloud contacts.
Ah almost forgot. I upgraded to Nexcloud 17.0.1 while running into the above problems, hoping it would solve part of it. so all I have written is based on that version.