Skip to main content

mastodon - Link to source

My PR got rejected because apparently everyone else should update their clients instead of the app 😅 It wasn't an amazing fix, but it worked.

Well, that's the beauty of open source, I can just keep working on my fork. Couldn't resist posting an XKCD comic in my response though.

github.com/thelounge/thelounge…

#OpenSource

A screenshot of a GitHub Pull Request: ronilaukkarinen commented 3 minutes ago "This isn't the right approach in my view. The world has moved on, utf8 is the standard and I don't think the complexity is worth it. Any reasonably modern IRC client can emit utf8, those that can't aren't worth catering for." I understand your point, and that's fair. However, IRC is one of the oldest messaging platforms, and we still have users running clients that are over 20 years old and don't have that charset support. I'm just tired of telling everyone to update their clients instead of fixing my open-source client. Reminds me of this: Anyway, I can keep using my fork. Thanks for taking the time to review this PR 👍

Add smart encoding detection for legacy IRC clients by ronilaukkarinen · Pull Request #5019 · thelounge/thelounge

Many older IRC clients (like mIRC) use ISO-8859-1 or ISO-8859-15 encoding instead of UTF-8, causing messages with non-ASCII characters (like Finnish ä, ö, å) to display as garbled text (e.g., �� in...
GitHub
#opensource
in reply to Roni Rolle Laukkarinen

Mathew Storm
mastodon - Link to source
Mathew Storm
• •

'The world has moved on' - lol - the world will 'move on' several more times in the next few years before people realize the problem has already been solved XD

Reminds me of why I write solely in markdown, I don't want to lose all my work when 'the world moves on' f

⇧