Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Hebrew folder names recognized as invalid

  • 7 Antworten
  • 1 hat dieses Problem
  • 4 Aufrufe
  • Letzte Antwort von yosefm

more options

So I've migrated my father's thundirbird to a new computer (from win7 to win10 fwiw). I did the usual path of letting thunderbird create a profile and then copy into it the existing profile's content like I always do for him. It seems like the existing mail is found as intended - for english-named folders.

For hebrew folders, the folder name is shown but nothing in or under it. Looking in the Win Explorer, a directory called something like d008c... is created alongside the existing directories. I understand this is what Thunderbird names directories with illegal charachters, but I fail to understand why the Hebrew names would be treated as illegal. It was never a problem before, on the old computer or its predecessors.

I tried closing and deleting msf files, all of them in the entire mail hierarchy. No joy. What am I doing wrong and what might I do to fix this?

Thanks in advance.

So I've migrated my father's thundirbird to a new computer (from win7 to win10 fwiw). I did the usual path of letting thunderbird create a profile and then copy into it the existing profile's content like I always do for him. It seems like the existing mail is found as intended - for english-named folders. For hebrew folders, the folder name is shown but nothing in or under it. Looking in the Win Explorer, a directory called something like d008c... is created alongside the existing directories. I understand this is what Thunderbird names directories with illegal charachters, but I fail to understand why the Hebrew names would be treated as illegal. It was never a problem before, on the old computer or its predecessors. I tried closing and deleting msf files, all of them in the entire mail hierarchy. No joy. What am I doing wrong and what might I do to fix this? Thanks in advance.

Alle Antworten (7)

more options
Looking in the Win Explorer, a directory called something like d008c... is created alongside the existing directories.

Sounds to me like the folder names were already screwed upon being copied over to the new computer. Make sure they will be retained by the copy process.

more options

The folder names are the same on both computers before running Thunderbird. The copy was done over the network (Windows file sharing). Only after running TB, the new mangled names appear alongside. The copy process looks fine. Is there a way for the copy process to create the same names but in an encoding not recognized by TB or some black magic like that?

more options

I assume you have the BiDi add-on installed. just make sure it is functioning. I really do not know what it does. But it might be relevant.

Does the windows 10 machine have a Hebrew character sat to run with? Is the version of Thunderbird the same?

more options

Matt said

I assume you have the BiDi add-on installed. just make sure it is functioning. I really do not know what it does. But it might be relevant. Does the windows 10 machine have a Hebrew character sat to run with? Is the version of Thunderbird the same?

Version is the same, and Windows works with Unicode so it shouldn't be a problem (Hebrew language pack is installed for windows and for Thunderbird, to be sure - I don't know what other things might be installed on top of that to get more Hebrew supprt).

The origin computer has BiDi Mail UI. I don't think having it or not ever affected the ability to read directories, but I'll try just in case.

more options

I mean, I've read through the BiDiMailUi code and nothing there touches the reading of mail directories AFAICT.

more options

Lets try an old version of Thunderbird and see if that is the issue. http://ftp.mozilla.org/pub/thunderbird/releases/38.8.0/win32/he/

more options

Hi again. I only now had a chance to try this and I'm sorry to report that the older version you linked also doesn't work. What else can I do to diagnose the problem?