home.social

#utf — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #utf, aggregated by home.social.

  1. 🆕 blog! “A small collection of text-only websites”

    A couple of years ago, I started serving my blog posts as plain text. Add .txt to the end of any URl and get a deliciously lo-fi, UTF-8, mono[chrome|space] alternative.

    Here's this post in plain text - shkspr.mobi/blog/2025/12/a-sma

    Obviously a webpage…

    👀 Read more: shkspr.mobi/blog/2025/12/a-sma

    #blogging #blogs #text #unicode #utf-8

  2. 🆕 blog! “A small collection of text-only websites”

    A couple of years ago, I started serving my blog posts as plain text. Add .txt to the end of any URl and get a deliciously lo-fi, UTF-8, mono[chrome|space] alternative.

    Here's this post in plain text - shkspr.mobi/blog/2025/12/a-sma

    Obviously a webpage…

    👀 Read more: shkspr.mobi/blog/2025/12/a-sma

    #blogging #blogs #text #unicode #utf-8

  3. 🆕 blog! “A small collection of text-only websites”

    A couple of years ago, I started serving my blog posts as plain text. Add .txt to the end of any URl and get a deliciously lo-fi, UTF-8, mono[chrome|space] alternative.

    Here's this post in plain text - shkspr.mobi/blog/2025/12/a-sma

    Obviously a webpage…

    👀 Read more: shkspr.mobi/blog/2025/12/a-sma

    #blogging #blogs #text #unicode #utf-8

  4. 🆕 blog! “A small collection of text-only websites”

    A couple of years ago, I started serving my blog posts as plain text. Add .txt to the end of any URl and get a deliciously lo-fi, UTF-8, mono[chrome|space] alternative.

    Here's this post in plain text - shkspr.mobi/blog/2025/12/a-sma

    Obviously a webpage…

    👀 Read more: shkspr.mobi/blog/2025/12/a-sma

    #blogging #blogs #text #unicode #utf-8

  5. 🆕 blog! “A small collection of text-only websites”

    A couple of years ago, I started serving my blog posts as plain text. Add .txt to the end of any URl and get a deliciously lo-fi, UTF-8, mono[chrome|space] alternative.

    Here's this post in plain text - shkspr.mobi/blog/2025/12/a-sma

    Obviously a webpage…

    👀 Read more: shkspr.mobi/blog/2025/12/a-sma

    #blogging #blogs #text #unicode #utf-8

  6. Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

    - Mojibake fixes for #UTF-16 (no BOM) encoded fields.
    - Some code cleanups, including warning fixes.
    - Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

    Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

  7. Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

    - Mojibake fixes for #UTF-16 (no BOM) encoded fields.
    - Some code cleanups, including warning fixes.
    - Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

    Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

  8. Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

    - Mojibake fixes for #UTF-16 (no BOM) encoded fields.
    - Some code cleanups, including warning fixes.
    - Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

    Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

  9. Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

    - Mojibake fixes for #UTF-16 (no BOM) encoded fields.
    - Some code cleanups, including warning fixes.
    - Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

    Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

  10. Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:

    - Mojibake fixes for #UTF-16 (no BOM) encoded fields.
    - Some code cleanups, including warning fixes.
    - Compatibility with #CMake > 4.0 (we now require CMake 3.10+)

    Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.

  11. #メモ #文字コード #ANSI #JIS #Shift_JIS
    #UTF-8 で書かれたテキストファイルをShift_JIS に変えたいのだけど、Notepad++でどのようにしたら良いのか分からなかった。「エンコード」の「文字セット」で「日本語 > Shift-JIS」を選ぶと日本語が文字化けしてしまう。
    試しに「エンコード」の「文字セット」で「ANSI に変換」を選んだら文字化けせず、右下の文字コード表示も「ANSI」に変わった。もしかして…と検索して、今日、初めて知った。

    #Windows のbatファイルをNotePad++で作成する際、最初はどうしてもデフォルトのUTF-8で保存してしまって、実行すると文字化けしてて、Shift_JIS で保存しなければいけなかったんだ…と直そうとしても方法が分からなくて、TeraPadの「文字/改行コード指定保存」を使っていたのだけど、NotePad++で「ANSI に変換」の後に保存すれば良かったのだな…と。

  12. #メモ #文字コード #ANSI #JIS #Shift_JIS
    #UTF-8 で書かれたテキストファイルをShift_JIS に変えたいのだけど、Notepad++でどのようにしたら良いのか分からなかった。「エンコード」の「文字セット」で「日本語 > Shift-JIS」を選ぶと日本語が文字化けしてしまう。
    試しに「エンコード」の「文字セット」で「ANSI に変換」を選んだら文字化けせず、右下の文字コード表示も「ANSI」に変わった。もしかして…と検索して、今日、初めて知った。

    #Windows のbatファイルをNotePad++で作成する際、最初はどうしてもデフォルトのUTF-8で保存してしまって、実行すると文字化けしてて、Shift_JIS で保存しなければいけなかったんだ…と直そうとしても方法が分からなくて、TeraPadの「文字/改行コード指定保存」を使っていたのだけど、NotePad++で「ANSI に変換」の後に保存すれば良かったのだな…と。

  13. UTF-8 Is Beautiful - It’s likely that many Hackaday readers will be aware of UTF-8, the mechanism for i... - hackaday.com/2025/09/14/utf-8- #softwarehacks #characterset #utf-8

  14. UTF-8 Is Beautiful - It’s likely that many Hackaday readers will be aware of UTF-8, the mechanism for i... - hackaday.com/2025/09/14/utf-8- #softwarehacks #characterset #utf-8

  15. UTF-8 Is Beautiful - It’s likely that many Hackaday readers will be aware of UTF-8, the mechanism for i... - hackaday.com/2025/09/14/utf-8- #softwarehacks #characterset #utf-8

  16. UTF-8 Is Beautiful - It’s likely that many Hackaday readers will be aware of UTF-8, the mechanism for i... - hackaday.com/2025/09/14/utf-8- #softwarehacks #characterset #utf-8

  17. UTF-8 Is Beautiful - It’s likely that many Hackaday readers will be aware of UTF-8, the mechanism for i... - hackaday.com/2025/09/14/utf-8- #softwarehacks #characterset #utf-8

  18. Very cool, copy-paste UTF text from, e.g., Wikipedia, get Unicode.
    Sanskrit अश्विन्
    can be in your HTML as
    अशिवन्
    r12a.github.io/app-conversion/
    #UTF #Unicode #conversion

  19. Very cool, copy-paste UTF text from, e.g., Wikipedia, get Unicode.
    Sanskrit अश्विन्
    can be in your HTML as
    अशिवन्
    r12a.github.io/app-conversion/
    #UTF #Unicode #conversion

  20. Why does this PHP construct:

    normalizer_normalize( $search_string, \Normalizer::FORM_D );

    Convert ÖÖÖ to OOO, but keeps ÅÅÅ as ÅÅÅ ... WTF?! 🤔

    #programming #php #wtf #utf #utf8

  21. Why does this PHP construct:

    normalizer_normalize( $search_string, \Normalizer::FORM_D );

    Convert ÖÖÖ to OOO, but keeps ÅÅÅ as ÅÅÅ ... WTF?! 🤔

    #programming #php #wtf #utf #utf8

  22. Why does this PHP construct:

    normalizer_normalize( $search_string, \Normalizer::FORM_D );

    Convert ÖÖÖ to OOO, but keeps ÅÅÅ as ÅÅÅ ... WTF?! 🤔

    #programming #php #wtf #utf #utf8

  23. Why does this PHP construct:

    normalizer_normalize( $search_string, \Normalizer::FORM_D );

    Convert ÖÖÖ to OOO, but keeps ÅÅÅ as ÅÅÅ ... WTF?! 🤔

    #programming #php #wtf #utf #utf8

  24. Why does this PHP construct:

    normalizer_normalize( $search_string, \Normalizer::FORM_D );

    Convert ÖÖÖ to OOO, but keeps ÅÅÅ as ÅÅÅ ... WTF?! 🤔

    #programming #php #wtf #utf #utf8

  25. Diese Jahr ging die Weihnachtsspende von @sweetgood an den Umwelttreuhand-Fonds (UTF) (umwelt-treuhandfonds.de/). Dieser finanziert die Anwält:innen von Klimaaktivist:innen, die aktuell massiven Repressionen ausgesetzt sind.

    Weitere 50€ gingen an den KUEÖ e.V., also direkt an die @AufstandLastGen

    #SWEETGOOD #andersGOOD #LetzteGeneration #Klimaschutz #Schutz #UTF #Spende #spenden

  26. Diese Jahr ging die Weihnachtsspende von @sweetgood an den Umwelttreuhand-Fonds (UTF) (umwelt-treuhandfonds.de/). Dieser finanziert die Anwält:innen von Klimaaktivist:innen, die aktuell massiven Repressionen ausgesetzt sind.

    Weitere 50€ gingen an den KUEÖ e.V., also direkt an die @AufstandLastGen

    #SWEETGOOD #andersGOOD #LetzteGeneration #Klimaschutz #Schutz #UTF #Spende #spenden

  27. Diese Jahr ging die Weihnachtsspende von @sweetgood an den Umwelttreuhand-Fonds (UTF) (umwelt-treuhandfonds.de/). Dieser finanziert die Anwält:innen von Klimaaktivist:innen, die aktuell massiven Repressionen ausgesetzt sind.

    Weitere 50€ gingen an den KUEÖ e.V., also direkt an die @AufstandLastGen

    #SWEETGOOD #andersGOOD #LetzteGeneration #Klimaschutz #Schutz #UTF

  28. Just lost 3 hours to the charset encoding inferno: my source code is in UTF-8 but the library I use assume 1 byte per char.
    Add to that, some font have only a subset of char.
    You get a nice mix of UTF-8 char that may render nicely and or not (depending if the first byte is a char present in the font).

    "Sometimes I wonder what's worse between charset encoding and timezones." says the guy who makes clocks and displays...

    #UTF-8 #ISO-8859 #ASCII #Hell

  29. Just lost 3 hours to the charset encoding inferno: my source code is in UTF-8 but the library I use assume 1 byte per char.
    Add to that, some font have only a subset of char.
    You get a nice mix of UTF-8 char that may render nicely and or not (depending if the first byte is a char present in the font).

    "Sometimes I wonder what's worse between charset encoding and timezones." says the guy who makes clocks and displays...

    #UTF-8 #ISO-8859 #ASCII #Hell

  30. Just lost 3 hours to the charset encoding inferno: my source code is in UTF-8 but the library I use assume 1 byte per char.
    Add to that, some font have only a subset of char.
    You get a nice mix of UTF-8 char that may render nicely and or not (depending if the first byte is a char present in the font).

    "Sometimes I wonder what's worse between charset encoding and timezones." says the guy who makes clocks and displays...

    #UTF-8 #ISO-8859 #ASCII #Hell

  31. Just lost 3 hours to the charset encoding inferno: my source code is in UTF-8 but the library I use assume 1 byte per char.
    Add to that, some font have only a subset of char.
    You get a nice mix of UTF-8 char that may render nicely and or not (depending if the first byte is a char present in the font).

    "Sometimes I wonder what's worse between charset encoding and timezones." says the guy who makes clocks and displays...

    #UTF-8 #ISO-8859 #ASCII #Hell

  32. So my former colleague @jstepien is a brillant engineer / speaker / teacher, but the thing he'll be internet famous for is how websites can't handle his name 🤷‍♂️. wtf-8.stępień.com is really funny, though.

    #encoding #utf #fail

  33. So my former colleague @jstepien is a brillant engineer / speaker / teacher, but the thing he'll be internet famous for is how websites can't handle his name 🤷‍♂️. wtf-8.stępień.com is really funny, though.

    #encoding #utf #fail

  34. So my former colleague @jstepien is a brillant engineer / speaker / teacher, but the thing he'll be internet famous for is how websites can't handle his name 🤷‍♂️. wtf-8.stępień.com is really funny, though.

    #encoding #utf #fail

  35. So my former colleague @jstepien is a brillant engineer / speaker / teacher, but the thing he'll be internet famous for is how websites can't handle his name 🤷‍♂️. wtf-8.stępień.com is really funny, though.

    #encoding #utf #fail

  36. So my former colleague @jstepien is a brillant engineer / speaker / teacher, but the thing he'll be internet famous for is how websites can't handle his name 🤷‍♂️. wtf-8.stępień.com is really funny, though.

    #encoding #utf #fail

  37. Did you know that apparently completely different strings are interpreted as identical by some tools?

    This is due to redundant UTF-8 encodings of the same Unicode characters.

    Read more below 🧵

    #InfoSec #CyberSecurity #Hacking #Pentesting #UTF #Unicode