Paul, Sorry. It's been almost 10 years since I did it.
I recall that was from WindowsMe (Japanese ed.) to White old MacBook (Japanese) data transfer. I think it worked then. If I recall correctly, since Mac mail system used ISO2022-JP https://en.wikipedia.org/wiki/ISO/IEC_2022 I may have done further conversion from UTF-8 to ISO2022-JP. Since then, I scrapped my private old Windows machine, old white Macbook died (data was migrated to Silver Macbook which didn't involve pst), I don't think I can help. Please note recent Windows (After Windows 10?) application may use different encoding (UTF-16?) internally. The application in the old English system used to use Windows-1252 or CP-1252. That's when application in the localized Windows used encoding I mentioned such as Shift-JIS. * https://docs.microsoft.com/en-us/windows/win32/intl/international-support * https://en.wikipedia.org/wiki/Unicode_in_Microsoft_Windows * https://en.wikipedia.org/wiki/Windows-1252 Regards, Osamu On Sat, 2021-04-03 at 10:21 +0800, Paul Wise wrote: > Hi Osamu, > > On Tue, 3 Apr 2007 01:47:28 +0900 Osamu Aoki wrote: > > > Thanks for interesting tool. This is helping me to move my wife's > > old > > Windows mail to a diifferent platform. > > > > I realized that old windows (95,98,Me) versions used non-utf-8 > > encodings > > for different countries. So when one extracts the content of pst > > file, > > filenames are encoded in traditional non-utf-8 format (Names like > > Inbox > > are translated into each language in pst). > > I recently adopted readpst and I am now triaging the bug reports. > > Would it be possible for you to attach an example PST file with > non-UTF-8 content, without any private information? > > The two scripts that you attached to the bug report have some coding > issues. I have fixed the issues reported by shellcheck, fixed some > other issues and attached the new versions to this email. > > Would it be possible for you to discuss the scripts with the upstream > maintainer? They don't have time to maintain the project but are > willing to accept patches to the Mercurial repository. > > Carl Byington <c...@five-ten-sg.com> > https://www.five-ten-sg.com/libpst/ > http://hg.five-ten-sg.com/libpst/ >
