Crates.io | onenote_parser |
lib.rs | onenote_parser |
version | 0.3.1 |
source | src |
created_at | 2020-10-16 18:13:32.652038 |
updated_at | 2022-11-19 19:31:04.539113 |
description | A parser for Microsoft OneNote® files |
homepage | |
repository | https://github.com/msiemens/onenote.rs |
max_upload_size | |
id | 300812 |
size | 15,660,766 |
A parser for Microsoft OneNote® files implemented in Rust.
Work in progress. Right now it can parse most of OneNote file contents but only if the files are in the FSSHTTP packaging format [MS-ONESTORE] 2.8. OneNote files as created and stored by the OneNote 2016 desktop application are not yet supported.
The code organization and architecture follows the OneNote file format which is build from several layers of encodings:
fsshttpb/
: This implements the FSSHTTP binary packaging format as specified
in [MS-FSSHTTPB]: Binary Requests for File Synchronization via SOAP Protocol.
This is the lowest level of the file format and specifies how objects and their
relationships are encoded (and decoded) from a binary stream (in our case a file).onestore/
: This implements the OneStore format as specified in
[MS-ONESTORE]: OneNote Revision Store File Format which describes how a
OneNote revision store file (also called OneStore) containing all OneNote objects
is stored in a FSSHTTP binary packaging file. This also includes the file header
([MS-ONESTORE] 2.8) and then how the OneNote revision store is built from the
FSSHTTP objects and revisions ([MS-ONESTORE] 2.7).one/
: This implements the OneNote file format as specified in [MS-ONE]:
OneNote File Format. This specifies how objects in a OneNote file are parsed
from a OneStore revision file.onenote/
: This finally implements an API that provides access to the data
stored in a OneNote file. It parses the FSSHTTPB data, the revision store
data and then constructs the objects contained by the OneNote file. This includes
resolving all references, e.g. looking up page's paragraphs.This project is neither related to nor endorsed by Microsoft in any way. The author does not have any affiliation with Microsoft.