I don’t think I ever managed that, unfortunately.
It has not been a priority since.
man. 16. dec. 2019 kl. 03.20 skrev Paul Wise (Debian) <
1470...@bugs.launchpad.net>:
> Martin Møller: did you manage to report this libpst issue to upstream
> via RedHat?
>
> I've also had
I'll look into that in the near future. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470032
Title:
libpst / readpst incorrectly decodes latin1 contacts, etc.
To manage notifications
That would probably be best, yes. I didn't see how to do so.
ons. 16. sep. 2015 15.31 skrev Sebastien Bacher :
> Thanks, that should probably be subscribed upstream for review...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
Well, I took a stab at the problem, since our client would really like
his contacts restored.
Attached is a very crude patch (as I am not a C programmer and thus I am going
the trials and error route here).
With this patch I seem to get both my Latin1 contacts and the UTF-16 contacts
written
PS:
This is the full commandline I used to get the above result (and all the other
contacts now shown here):
readpst -C iso-8859-1 -cv -tc -o /tmp/TAN/ -d /tmp/TAN/TAN-debug.txt
Postkasse\ -\ Torben\ Andersen.pst
Also, Office 2013 act precisely the same way as libpst seems to do, but
wouldn't
Public bug reported:
After a client of ours moved from Exchange 2003 to Office 365 we had to
get some data out of PST-files, which mostly worked well, but apparently
Contacts and some Tasks have a tendency på be incorrectly decoded into
gibberish.
As far as I can tell, the problem is that the