Archive for the ‘Mojibake’ Category
Posted by jpluimers on 2025/09/17
Voor mijn link archief: KPN telefooncentrales, waarvan een paar waar familie of ik een aansluiting had:
[Wayback/Archive] Wijkcentrales – VVDSL.robinflikkema.nl
Deze hadden Mojibake met de generic replacement character (“�”):
Let op: de [Wayback/Archive] fourstack KPN UI (toenmalig gebouwd door [Wayback/Archive] FourStack) is sinds 2021 uit de lucht, zie [WaybackSave/ArchiveBad] FPI Fourstack Snelheid DSL – Internet en hosting – GoT , dus de gegevens worden niet meer bijgewerkt.
--jeroen
Posted in ADSL, Development, Encoding, Internet, ISDN, ISP, KPN, Mojibake, Power User, PSTN, Software Development, Telephony | Leave a Comment »
Posted by jpluimers on 2025/06/12
I wrote about Sequoiaview in depth in SequoiaView Homepage, made some research notes in “cushion treemap” delphi – Google Search and touched it slightly in A choco install list.
I never heard back from my request for Sequoiaview source code, and given ever increasing local storage media sizes, the speed of it now has become an issue, so I started looking to see if more alternatives have appeared and what sets them apart.
TL;DR
- There is the open source WinDirStat that runs as non-admin and is about as slow as Sequoiaview
- There is the closed source but free for personal use WizTree that requires admin elevation and is much faster than Sequoiaview and WinDirStat
Neither of them allow for a view that is cushion treemap only.
The reason that WizTree is fast is that it directly uses the NTFS MFT (Master File Table) to read the information from. This requires elevated permissions.
This is the same mechanism used by the Everything search tool, but unlike Everything, WizTree:
Read the rest of this entry »
Posted in C++, Development, Encoding, Mojibake, Software Development, UTF-8, Windows Development | Tagged: include | Leave a Comment »
Posted by jpluimers on 2025/02/10
Inn de basis een door mijn opa gebouwde opwindbare (3 gewichten) Warmink Wuba triple chime – Westminster, St. Michael, Whittington clock.
Die liep nauwelijks meer, en sloeg zowel geen melodie meer, maar ook geen uursignaal meer.
Hieronder links die me hielpen met uitzoeken wat er van dit merk nog bestond en kennis aanwezig is.
Read the rest of this entry »
Posted in About, Development, DIY, Encoding, LifeHacker, Mojibake, Personal, Power User, Software Development | Leave a Comment »
Posted by jpluimers on 2024/12/17
[Wayback/Archive] Jeroen Wiert Pluimers: “LOL, just saw @isotopp changed…” – Mastodon
LOL, just saw @isotopp changed his name to Köhntopp
Well done, Kris. Well done.
https://ftfy.vercel.app/?s=ö
( the history of the iso isotopp handle is so great, that I was glad I captured it from Twitter before that content got deleted; it is now at https://wiert.me/2022/06/09/how-isotopp-became-the-online-handle-of-kristian-kohntopp/ )
This Vercel app cannot be archived in the Wayback Machine properly as it then returns a HTTP 500. The Archive.is save succeeded though: [Wayback/Archive] https://ftfy.vercel.app/?s=ö:
Read the rest of this entry »
Posted in Development, Encoding, ISO-8859, ISO8859, Mojibake, Software Development, Unicode, UTF-8 | Leave a Comment »
Posted by jpluimers on 2022/11/22
I have been into more and more Mojibake example pages like [Wayback] Mojibake: Question Marks, Strange Characters and Other Issues | GPI
Have you ever found strange characters like these ��� when viewing content in applications or websites in other languages?
They made me realise that all these (including the Mojibake examples on my blog) are just artifacts, but the real list of examples is the set of ftfy test cases at [Wayback/Archive.is] python-ftfy/test_cases.json at master · LuminosoInsight/python-ftfy
I got reminded when Waternet moved from paper mail using “Pyreneeën” to email using “Pyreneeën“. Not as bad as Waterschap AGV did earlier: they took it one level further and made “Pyreneeën” out of it, see Last year, a classic Mojibake was introduced when Waterschap Amstel, Gooi en Vecht redesigned their IT systems.
This seems like a trend where newer systems perform worse than older systems. I wonder why that is.
BTW: the trick on the [Wayback/Archive] Python.org shell to run ftfy (which is not installed by default) is first dropping to the shell (see my post How do I drop a bash shell from within Python? – Stack Overflow), then starting python again:
Read the rest of this entry »
Posted in CP850, Development, Encoding, ftfy, ISO-8859, Mojibake, Python, Scripting, Software Development, Unicode, UTF-8, UTF8 | Leave a Comment »
Posted by jpluimers on 2022/03/16
Last year, Waterschap Amstel, Gooi en Vecht sent me a paper letter notifying the yearly water bill was going to be late as they were redesigning their IT systems.
Their letter introduced a classic Mojibake that had not been present in all their older paper letter communication.
- Street name on a letter via the old IT systems is
"Pyreneeën":
- Street name on a letter via the new IT systems is
"Pyreneeën":
Read the rest of this entry »
Posted in Development, Encoding, ftfy, Mojibake, Python, Software Development, Unicode, UTF-8, UTF8 | Leave a Comment »
Posted by jpluimers on 2022/03/10
When writing this, [Wayback/Archive.is] ftfy · PyPI:history indicates ftfy was already at 6.0.3.
It is still my goto tool for figuring out the cause of Mojibake. I remember writing about it the first time in 2016 (see the ftfy category) when it was already at version 3.0, discovering it after a few Mojibake posts.
By now it even understands right-to-left Mojibake garbage: 
[Archive.is] Elia Robyn Speer on Twitter: “ftfy 5.8 is out! … A user reported that Hebrew text wasn’t being fixed, and this made me think about how to expand some of the trickier cases to non-Latin alphabets.”
Mojibake mishaps still happen a lot, so by now I hope I will have done a Mojibake themed Delphi talk at one or more conferences.
Read the rest of this entry »
Posted in !!con (bangbangcon), About, Autistic Spectrum/Autism, Cancer, Conference Topics, Conferences, Development, Encoding, Event, ftfy, Mojibake, Personal, Python, Rectum cancer, Scripting, Software Development, Unicode | Leave a Comment »
Posted by jpluimers on 2022/02/09
Nowadays, some 35 years after the first Unicode ideas got drafted and 30+ years after the Unicode Consortium saw the light, UTF-8 is served my more than 95% of the web as shown in yesterday’s post UTF-8 web adoption is huge, closing 100%, but only soured up since around 2006..
I mentioned this:
It means that nowadays there is a very small chance you will see mangled characters (what Japanese call mojibake) when you’re surfing the web.
Serving UTF8 does not mean no unicode problems.
Below are some issues that happened not too long ago and still happen. I have reported them to all parties involved through web-care, but no response whatsoever, and this is bad: Unicode support beyond basic ASCII for the below systems are still broken even for relatively simple non-ASCII characters based in diacritics decorating a standard ASCII character.
Yes, I know the realm of encoding and code pages is a mess, especially when handling data in multiple layers of an application stack. That’s why I wrote this post in the first place, and have a whole encoding category of blog posts plus a Mojibake subset.
Read the rest of this entry »
Posted in Communications Development, CP850, Dark Pattern, Development, Encoding, ISO-8859, ISO8859, Mojibake, Software Development, Unicode, User Experience (ux), UTF-16, UTF-8, Windows-1252 | Leave a Comment »
Posted by jpluimers on 2019/06/17
I live in a street that has a non-ASCII character in it: Pyreneeën.
I’ve reverted back to entering the street name as plain ASCII for a simple reason:
Too often the ë gets mangled into encoding gibberish, similar to the é example in [WayBack] When Good Characters Go Bad: A Guide to Diagnosing Character Display Problems as these characters are very near both in UTF-8 and in the [WayBack] Unicode Characters in the Latin-1 Supplement Block:
I’ve seen these encodings, where only the top encoding is correct; the degeneration gets worse moving downwards, a classic Mojibake:
| # |
encoded |
UTF-8 (hex.) |
| 0 |
ë |
0xC3 0xAB |
| 1 |
ë |
0xC3 0x83 0xC2 0xAB |
| 2 |
ë |
0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0xAB |
| 3 |
ÃÂë |
0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0x83 0xC3 0x83 0xC2 0x82 0xC3 0x82 0xC2 0xAB |
| 4 |
ÃÂÃÂÃÂë |
0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0x83 0xC3 0x83 0xC2 0x82 0xC3 0x82 0xC2 0x83 0xC3 0x83 0xC2 0x83 0xC3 0x82 0xC2 0x82 0xC3 0x83 0xC2 0x82 0xC3 0x82 0xC2 0xAB |
| 5 |
ë |
0x26 0x65 0x75 0x6d 0x6c 0x3b |
The last one seldomly happens, the first one relatively often, just like [Archive.is] fd.nl did a while on their finanancial pages.
These mistakes become sort of understandable (but not forgivable) when you look at the below table-fragment (the full table is at[WayBack] Unicode/UTF-8-character table – starting from code position 0080).
Read the rest of this entry »
Posted in Development, Encoding, Mojibake, Power User, Software Development, Unicode, Web Browsers | Leave a Comment »
The Wiert Corner - irregular stream of stuff 