The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,152 other subscribers

Archive for February 9th, 2022

In this day and age, web sites with delivery back-ends still have Unicode issues: at least @Woonveilig, @Medireva and @PostNL still have trouble

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 »

rsync backup of your ESXi box: How to make a statically linked rsync binary

Posted by jpluimers on 2022/02/09

As promised mid last year in “fixing” ESXi “rsync error: error allocating core memory buffers (code 22) at util2.c(106) [sender=3.1.2]”, I would follow up on building a static rsync for ESXi one day.

So below a few links on how to do this, roughly in the order I found them (most via [Wayback] vmware rsync “3.1.2” static – Google Search):

Boy I forgot how long ago CentOS 3.9 was: [Wayback] [CentOS-announce] CentOS 3.9 is released for i386 and x86_64

Johnny Hughes johnny at
Thu Jul 26 23:14:02 UTC 2007

The CentOS development team is please to announce the release of CentOS
3.9 for i386 and x86_64.

This is the final minor release for CentOS-3. With this release CentOS-3
has entered its maintenance phase during which time only fixes for
critical functional and security issues will be provided.

CentOS 3.9 is available on all mirrors and via bittorrent.

This release corresponds to the upstream vendor U9 release together with
updates through July 3rd 2007 (depending on architecture).

The serverCD version (1 cdrom) is available for i386 and x86_64.

The work for the other arches is still in progress.

To get CentOS 3.9, use one of these archives (I saved all in the Wayback machine as I know how short downloads can last):

There are actually very few places that still have CentOS-3.9-i386-binDVD.iso on-line. The only place I could find was [Wayback] Index of /operating_system/unix/centos/3.9

[ICO] Name Last modified Size Description

[PARENTDIR] Parent Directory
[TXT] [Wayback] CentOS-3.9-i386-CHECKSUM.txt 2012-10-02 20:09 308
[ ] [Wayback] CentOS-3.9-i386-binDVD.iso 2012-10-02 20:29 1.7G
[ ] [Wayback] CentOS-3.9-server-i386.iso 2012-10-02 20:12 680M
[ ] [Wayback] CentOS-3.9-server-x86_64.iso 2012-10-02 20:14 625M
[TXT] [Wayback] CentOS-3.9-x86_64-CHECKSUM.txt 2012-10-02 20:22 445
[ ] [Wayback] CentOS-3.9-x86_64-binDVD.iso 2012-11-28 23:08 1.9G


Posted in *nix, *nix-tools, CentOS, Development, Linux, Power User, RedHat, Software Development | Leave a Comment »

C# Effective way to find any file’s Encoding – Stack Overflow

Posted by jpluimers on 2022/02/09

Note: notepad cannot correctly guess the encoding, see the “old new thing”: [Wayback] Some files come up strange in Notepad | The Old New Thing (talking about ANSI a.k.a. Windows-1252, UTF-16LE, UTF-16BE, UTF-8, UTF-7 somewith and some without BOM as Notepad does not understand all permutations)

David Cumps discovered that certain text files come up strange in Notepad. The reason is that Notepad has to edit files in a variety of encodings, and when its back against the wall, sometimes it’s forced to guess.

[Wayback] C# Effective way to find any file’s Encoding – Stack Overflow shows how to detect various byte order marks in C#.


Posted in ASCII, Development, Encoding, Software Development, Unicode, UTF-16, UTF-32, UTF-8, UTF16, UTF32, UTF8 | Leave a Comment »

%d bloggers like this: