once more localizing folders

El Muchacho

@fbartels said in once more localizing folders:

sadly you provide no information which kopano version you are using or in which os you are seeing this.

debian stretch … it’s in initial post ;)
and currently still using kopano 8.6.9

and btw : dry-run looks correct:

root@kopano1:~# python localize-folders.py --u myuser --lang de_DE.UTF-8 --dry-run
Localizing user: myuser
Changing localized folder names to "de_DE.UTF-8"
Running in dry mode no changes will be made
Renaming MAPI Folder "junk" -> From "Spam" To "Spam"
Renaming MAPI Folder "tasks" -> From "Aufgaben" To "Aufgaben"
Renaming MAPI Folder "journal" -> From "Journal" To "Journal"
Renaming MAPI Folder "wastebasket" -> From "Deleted Items" To "Gelöschte Objekte"
Renaming MAPI Folder "inbox" -> From "Inbox" To "Posteingang"
Renaming MAPI Folder "sentmail" -> From "Sent Items" To "Gesendete Objekte"
Renaming MAPI Folder "outbox" -> From "Outbox" To "Postausgang"
Renaming MAPI Folder "calendar" -> From "Calendar" To "Kalender"
Renaming MAPI Folder "rss" -> From "RSS Feeds" To "RSS-Feeds"
Renaming MAPI Folder "drafts" -> From "Drafts" To "Entwürfe"
Renaming MAPI Folder "contacts" -> From "Contacts" To "Kontakte"
Renaming MAPI Folder "notes" -> From "Notes" To "Notizen"
Renaming MAPI Folder "suggested_contacts" -> From "Suggested Contacts" To "Vorgeschlagene Kontakte"

MKral

@El-Muchacho

in /etc/apache2/envvars change:
“export LANG=C”
to
“export LANG=de_DE.UTF-8”

… after that:
/etc/init.d/apache2 restart

micro

I am facing exactly the same issue as reported by El Muchacho by using the script provided here. I am trying to change a mailbox to german language de_DE. The last advice to change the apache2 envvar line and restarting apache2 did not help either. So what is the solution to this? The --dry-run succeeds, but the real run fails with the same error message.

Initially I changed it to english language with

python localize-folders.py -u mmustermann --lang en_GB

and it worked like a charm. Then I tried to change it back to german with:

python localize-folders.py -u mmustermann --lang de_DE

but it failed with error message

Error: de_DE Is not a language pack or is not installed

so I retried with

python localize-folders.py -u mmustermann --lang de_DE.UTF-8

which leads to the initial mentioned error message

Localizing user: mmustermann
Changing localized folder names to “de_DE.UTF-8”
‘ascii’ codec can’t decode byte 0xc3 in position 3: ordinal not in range(128)

the dry-run shows no errors though:

python localize-folders.py -u mmustermann --lang de_DE.UTF-8 --dry-run

Localizing user: mmustermann
Changing localized folder names to “de_DE.UTF-8”
Running in dry mode no changes will be made
Renaming MAPI Folder “junk” -> From “Junk E-Mail” To “Junk E-Mail”
Renaming MAPI Folder “tasks” -> From “Aufgaben” To “Aufgaben”
Renaming MAPI Folder “journal” -> From “Journal” To “Journal”
Renaming MAPI Folder “wastebasket” -> From “Deleted Items” To “Gelöschte Objekte”
Renaming MAPI Folder “inbox” -> From “Inbox” To “Posteingang”
Renaming MAPI Folder “sentmail” -> From “Sent Items” To “Gesendete Objekte”
Renaming MAPI Folder “outbox” -> From “Outbox” To “Postausgang”
Renaming MAPI Folder “calendar” -> From “Calendar” To “Kalender”
Renaming MAPI Folder “rss” -> From “RSS Feeds” To “RSS Feeds”
Renaming MAPI Folder “drafts” -> From “Drafts” To “Entwürfe”
Renaming MAPI Folder “contacts” -> From “Contacts” To “Kontakte”
Renaming MAPI Folder “notes” -> From “Notes” To “Notizen”
Renaming MAPI Folder “suggested_contacts” -> From “Suggested Contacts” To >“Vorgeschlagene Kontakte”

thctlo

Try running : dpkg-reconfigure -plow locales

micro

man dpkg-reconfigure

-pvalue, --priority=value
Specify the minimum priority of question that will be displayed. dpkg-reconfigure normally shows low priority questions no matter what your default priority is. See debconf(7) for a list.

can you provide more info and background about this command and how it might cure the issue? I don’t want to mess around with my locales on this production environment.

fbartels

@micro an error like ‘ascii’ codec can’t decode byte 0xc3 in position 3: ordinal not in range(128) usually means that your local terminal does not understand utf-8.

You can disregard the apache stuff, as this is not directly relevant for the python script.

micro

alright, but do you have any suggestion to this error which might lead to success ?

thctlo

@micro man locale-gen

This give you the option to (re-)generate the locales.

dpkg-reconfigure -plow locales
Shows all questions and allows you to select other locales to add and you can set a default with it.

fbartels

@micro reconfigure your terminal (not your server) to work with utf-8.

How to do that depends in your terminal emulator, but a quick search should give instructions.

micro

well, I am pretty sure for 100% that I did run “dpkg-reconfigure locales” quite after I installed the OS. This is one of the basic steps I perform on a clean install.

When I now run the mentioned command, I see that my settings
de_DE.UTF-8
en_US.UTF-8

are highlighted with the asterisk [*]. On the next step I see that de_DE.UTF-8 is used for my default system environment and once I confirm all these settings the locales are generated. But as said before, I have done this step already and I already got those locales installed on my system. I am pretty sure this is NOT the culprit.

just for your understanding. I haven’t choose the locale en_GB.UTF-8 in the dpkg-reconfigure step, but running the command

python localize-folders.py -u mmustermann --lang en_GB.UTF-8

or

python localize-folders.py -u mmustermann --lang en_GB

both succeed without errors.

thctlo

Hai, well what you did, is not know for us.
We have to ask/verify these things.

kopano 8.6.9 , then its a python2 to python3 bug.
read : https://forum.kopano.io/topic/777/kopano-localize-folders
same…

micro

locale -a

C
C.UTF-8
de_DE.utf8
en_US.utf8
POSIX

the --verbose switch gives me this result

Localizing user: mmustermann
Changing localized folder names to "de_DE.UTF-8"
Running in verbose mode
Renaming MAPI Folder "junk" -> From "Junk E-Mail" To "Junk E-Mail"
Renaming MAPI Folder "tasks" -> From "Aufgaben" To "Aufgaben"
Renaming MAPI Folder "journal" -> From "Journal" To "Journal"
Renaming MAPI Folder "wastebasket" -> From "Deleted Items" To "Gelöschte Objekte"
'ascii' codec can't decode byte 0xc3 in position 3: ordinal not in range(128)

seems that the script succeeded in renaming the first four folders but fails at the next step. Maybe because of German Umlaut?

thctlo

yeah, that is why i say its a python2 => 3 bug.

I’ve seen dozens of these on the samba bug list.
I just can not debug these myself (sorry), im not a coder.

micro

the user @robing links to an updated version of the script which works fine for the user @sebschremser but I cannot access/download it because I have no Bitbucket account. Can I download this updated script somewhere else from?

thctlo

@micro maybe if we call @fbartels … he might.
Ping Felix help ;-)

fbartels

@micro the script was moved to https://stash.kopano.io/projects/KSC/repos/core-tools/browse/localize-folders

In case you’re not ignoring me did you check that YOUR TERMINAL EMULATOR can support UTF-8?

micro

No, I am not ignoring you. Sorry forgot to give feedback on this.

echo $TERM

xterm

echo $LANG

de_DE.UTF-8

yes, I’m sure my terminal shows correctly UTF-8. I am using a /etc/motd as a check, which shows german umlauts. In case my terminal wouldn’t support UTF-8 I wouldn’t have seen the characters displayed correctly. But I do! :) so UTF-8 support is given

I would appreciate if anyone could download the updated script and post it somewhere so I could download it and try it out.

EDIT: Oh, you said the script moved. So I have already the latest version. Hmmm… strange, doesn’t work on my side then.

thctlo

well, im running out of options here, i can only say two more things
Reboot the server and try again.
and/or upgrade kopano to a later version.

fbartels

@micro said in once more localizing folders:

so UTF-8 support is given

in that case please get into contact with our support so that someone could check directly on your system.