> I was curious and went back to the 85.0b3 before any of yours or Ping's changes occurred. Sounds like a difficult "post mortem". The initial bug forgot to "propagate" all the API changes from ACString to AUTF8String. Ping added that. Whether the various deficiencies compensated each other is hard to tell. In general, code must be formally correct and also work ;-) > I was able to assigned a non-ascii named folder as trash for a non-UTF8=ACCEPT account and it worked OK. Well, assigning it in the account settings worked, but in the folder tree the it didn't get a trash icon. And the setting was lost after a restart since the flag never got set on the folder. That's what I observed before I fixed it. Let's move on to the next issue from comment #64 :-)
Bug 1687727 Comment 66 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> I was curious and went back to the 85.0b3 before any of yours or Ping's changes occurred. Sounds like a difficult "post mortem". The initial bug forgot to "propagate" all the API changes from ACString to AUTF8String. Ping added that. Whether the various deficiencies compensated each other is hard to tell. In general, code must be formally correct and also work ;-) > I was able to assigned a non-ascii named folder as trash for a non-UTF8=ACCEPT account and it worked OK. Well, assigning it in the account settings worked, but in the folder tree the it didn't get a trash icon. And the setting was lost after a restart since the flag never got set on the folder. That's what I observed before I fixed it (with Ping's patches applied, of course). Let's move on to the next issue from comment #64 :-)