Baike.dev
All toolsAI codingTrendingOpen sourceNewsSubmit
Log in
Back to tool/Back to issues
#10398·notesnook

Web Clipper encodes special characters incorrectly (mojibake) when using "Complete with styles" mode

Author: alihamuhCreated Sep 18, 2026Updated Sep 18, 2026
LabelsPlatform: WebStatus: ConfirmedUnit: Web Clipperplane

What happened?

Describe the bug

When using the Notesnook Web Clipper to clip content using the "Complete with styles" mode, special/accented characters (such as ä, ö, ü, é, á, etc.) are improperly encoded into garbled text (mojibake, e.g., ü instead of ü).

However, clipping the same page using the "Simplified" mode renders special characters correctly.

To Reproduce

Navigate to a web page containing special or accented characters (e.g., German umlauts ä, ö, ü or accented letters é, á).

Open the Notesnook Web Clipper.

Select "Complete with styles" mode and save the clip.

Open the saved clip in Notesnook.

Notice that special characters appear corrupted/garbled (e.g., ü displays as ü).

Expected behavior

Special and accented characters should retain their correct UTF-8 encoding and display properly regardless of whether "Simplified" or "Complete with styles" mode is selected.

Actual behavior

"Complete with styles" mode causes character encoding issues/mojibake on special characters, whereas "Simplified" mode displays them correctly.

Environment / Context

App: Notesnook Web App / Web Clipper

Browser: Brave Browser

OS: Manjaro Linux

Steps to reproduce the problem


Version


Platform/OS

Chrome/Chromium, Firefox

Relevant log output

bash
--

Source: streetwriters/notesnook

View original on GitHubView discussion on GitHub