You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
When importing Notion exports (HTML format) into Obsidian using the Importer plugin, the process freezes during the file scanning stage. This only occurs with exports containing Korean filenames.
Cause:
The filenames of the exported Notion pages in Korean were in decomposed Unicode form (NFD), where Korean syllables were split into separate consonants and vowels (e.g., ㅎㅏㄴㄱㅡㄹ instead of 한글). This appears to cause the Importer to freeze.
Workaround:
I batch-renamed the files by normalizing their Unicode to NFC (composed form). After normalization, the import was completed successfully without freezing.
I expect some Korean users who want to migrate their data from Notion to Obsidian might go through a similar problem (since Notion does not provide NFC type export), so it could be beneficial to help them know the issue and the workaround.
The text was updated successfully, but these errors were encountered:
Issue:
When importing Notion exports (HTML format) into Obsidian using the Importer plugin, the process freezes during the file scanning stage. This only occurs with exports containing Korean filenames.
Cause:
The filenames of the exported Notion pages in Korean were in decomposed Unicode form (NFD), where Korean syllables were split into separate consonants and vowels (e.g., ㅎㅏㄴㄱㅡㄹ instead of 한글). This appears to cause the Importer to freeze.
Workaround:
I batch-renamed the files by normalizing their Unicode to NFC (composed form). After normalization, the import was completed successfully without freezing.
I expect some Korean users who want to migrate their data from Notion to Obsidian might go through a similar problem (since Notion does not provide NFC type export), so it could be beneficial to help them know the issue and the workaround.
The text was updated successfully, but these errors were encountered: