Skip to content

Comments

Windows: Fixes #13549: Importing from OneNote: Fix badly encoded accents in notebook titles#14037

Merged
laurent22 merged 4 commits intolaurent22:devfrom
personalizedrefrigerator:pr/desktop/onenote-import/fix-import-badly-encoded-accents
Jan 7, 2026
Merged

Windows: Fixes #13549: Importing from OneNote: Fix badly encoded accents in notebook titles#14037
laurent22 merged 4 commits intolaurent22:devfrom
personalizedrefrigerator:pr/desktop/onenote-import/fix-import-badly-encoded-accents

Conversation

@personalizedrefrigerator
Copy link
Collaborator

@personalizedrefrigerator personalizedrefrigerator commented Jan 6, 2026

Summary

When importing from a .onepkg file, Joplin uses EXPAND.EXE to extract .one files from .onepkg files. EXPAND.EXE seems to decode filenames within the .onepkg file as latin1, even though the filenames were originally encoded with UTF-8.

This pull request adds a post-processing step when importing .onepkg files on Windows that re-decodes filenames as utf-8.

Partially fixes #13549.

Testing plan

Windows 11:

  1. Create a OneNote notebook titled "tést", containing a single section named "Tést".
  2. Export the notebook as .onepkg.
  3. Import the .onepkg file from Joplin.
  4. Verify that notebook "tést" and sub-notebook "Tést" have been imported successfully.
  5. Import Carnet de test migration Joplin - 2025-10-21.onepkg from the Archive.zip file provided in Fix issues with import of OneNote files #13549.
  6. Verify that the "Procédures" subnotebook is imported as "Procédures" (and not "Procédures").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

desktop All desktop platforms import Related to importing files such as ENEX, JEX, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix issues with import of OneNote files

2 participants