عن هذه الأداة
Mojibake appears when text saved in one character encoding is read with another — most often UTF-8 bytes decoded as Windows-1252, which turns “é” into “é” and Cyrillic into “Ð…Ñ…” sequences. Because no information is lost, the damage can be reversed. This tool reconstructs the original bytes and re-decodes only valid UTF-8 sequences, so correctly encoded characters in mixed text are left untouched, and it repeats the process for double or triple encoding. In auto mode it also tests legacy encodings — Windows-1251, KOI8-R, Shift-JIS and GBK — and picks the most plausible result. Auto mode tries 19 legacy encodings — Cyrillic (Windows-1251, KOI8-R/U, CP866), Central European (Windows-1250), Turkish, Greek, Hebrew, Arabic (Windows-1256), Baltic, Vietnamese (Windows-1258), Thai (TIS-620), Japanese (Shift-JIS, EUC-JP), Chinese (GBK, Big5) and Korean (EUC-KR) — and keeps the result that reads most like real language.
مثل كل أدوات LanguageHelper، تعمل إصلاح الترميز التالف بالكامل داخل متصفح الويب لديك. لا يُرفَع نصك أو يُخزَّن أو يُستخدم للتدريب أبدًا، لذا فهي آمنة للمستندات السرية وبيانات العملاء والرسائل الشخصية. لا حاجة إلى حساب أو تثبيت، وتستمر الأداة في العمل دون اتصال بعد تحميلها.
كيف تعمل
- Paste the garbled text.
- Keep “Auto-detect” or choose what happened if you know.
- The repaired text appears instantly.
- Copy it, and re-save the source file as UTF-8 to prevent it happening again.
حالات الاستخدام
- Repair CSV files opened with the wrong encoding in Excel.
- Fix garbled names and addresses in databases and CRM exports.
- Recover old e-mails, subtitles and web pages with broken characters.
- Clean scraped text before analysis or translation.
أمثلة
قبل
Café crème
بعد
Café crème
قبل
Привет
بعد
Привет
نصائح لأفضل النتائج
Copy the garbled text exactly as it appears; don’t retype it. If auto mode doesn’t fully fix it, try the specific encodings — Russian files often used Windows-1251 or KOI8-R and Japanese files Shift-JIS. After repairing, save your files as UTF-8 and make sure the program reading them is set to UTF-8 too.
الأسئلة الشائعة
What causes mojibake?
A program reads bytes with the wrong encoding: a CSV exported as UTF-8 opened in Excel as Windows-1252, a database connection with the wrong charset, or an e-mail missing its charset header.
Can every garbled text be fixed?
Text is recoverable when the wrong decoding kept all bytes, which is the usual case. If characters were replaced with “?” or “�” during saving, the original information is gone and cannot be restored.
What is double encoding?
Text that was mis-decoded and re-saved twice, producing sequences like “é”. The fixer repeats the repair up to three times until the text is clean.
Will it damage text that is already correct?
No. Only byte sequences that form valid UTF-8 are re-decoded, and correctly encoded characters such as “naïve” or “—” are preserved.
Which encodings are supported?
UTF-8 misread as Windows-1252 or ISO-8859-1 (including double encoding), plus 19 legacy encodings covering all 20 site languages: Windows-1250, 1251, 1253, 1254, 1255, 1256, 1257, 1258, KOI8-R, KOI8-U, CP866, ISO-8859-2, TIS-620/Windows-874, Shift-JIS, EUC-JP, GBK/GB18030, Big5 and EUC-KR. Choose one explicitly if auto-detection picks the wrong one.
How can I prevent mojibake in the future?
Save files as UTF-8, declare the charset in HTML and e-mail headers, set database connections to utf8mb4, and when opening CSV files in Excel use Data → From Text/CSV with UTF-8 selected.