Closed scanny closed 4 months ago
Ah, okay, writing this gave me an idea and I figured it out from the source:
LIBPFF_FILE_CONTENT_TYPE_PAB = (int) 'a', LIBPFF_FILE_CONTENT_TYPE_PST = (int) 'p', LIBPFF_FILE_CONTENT_TYPE_OST = (int) 'o'
Sorry to bother you and thanks for the library! :)
Summary In
pypff
,file.content_type
produces unexpected integer value112
. Expectedb'SM'
.To reproduce
I do note that
asc(112)
is'p'
and it occurred to me that might be short for PST or something, but based on the documentation of the file format I was expecting thebytes
valueb'SM'
. https://github.com/libyal/libpff/blob/main/documentation/Personal%20Folder%20File%20(PFF)%20format.asciidoc#21-content-typesCan you advise whether this is a bug or whether I just missed the documentation for how
file.content_type
is encoded?