Edit: /etc/nginx/mime.types
Add: "text/markdown; charset=utf-8" md;
(note the quote marks around the string)
Don't forget: service nginx reload
In case anyone else is left wondering how to have #nginx serve markdown .md
files in utf-8, instead of basic ascii.
The grumpy serialisation format
Hey everyone. I must admit, I don't believe I have ever seen someone enter #utf8 #unicode characters on a #computer in a natural way. Which seems weird, because a bunch of languages use them.
I wrote a #commonLisp #asdf package that just looks up a list of symbols in a file that has every non-surrogate unicode codepoint in it, and an #emacs #elisp function that just calls the #lisp one.
https://codeberg.org/tfw/unicode-chars
Multilingual people, what can you tell me about doing this at all?
There are three #UTF8 characters (2 symbols, 1 emoji) for old-stye telephones: , ☏,
.
1. On some systems "black telephone" renders as the "red telephone" emoji instead of as the expected winding/dingbat-style character I was expecting. This seems system- and application-specific.
2. Depending on font, the "white telephone" may not match the height or midline of other letters or even /
. The "black flag" ⚑ is often even worse.
Not huge deals, but created some formatting issues today.
In #UTF8 gitb es das Symbol ⍼.
Es heißt Angzarr, eine Art Ligatur aus einem L und einem Blitz.
Niemand weiß so richtig, warum es in UTF8 enthalten ist, aber in diesem Dok. ist am Ende ein Brief vom AMS-Präsidenten!
https://www.unicode.org/wg2/docs/n2191.pdf
Also wofür steht es??
Wrong answers only
#UserAgent based banning of #textmode browsers is sooooo lame.
$ lynx -useragent= https://[…]
Why does this PHP construct:
normalizer_normalize( $search_string, \Normalizer::FORM_D );
Convert ÖÖÖ to OOO, but keeps ÅÅÅ as ÅÅÅ ... WTF?!
Glyphe surprenant du jour : ₣, symbole monétaire du Franc français (!).
Rendu par "un F majuscule doublement barré, qui a été proposé par Édouard Balladur en 1988, une ligature Fr ou d’autres variantes.
Selon Yannis Haralambous en 2004, ce symbole n’a jamais été utilisé"
https://fr.wikipedia.org/wiki/%E2%82%A3
#typo #UTF8
@fanf it's absolutely fantastic. and if, like me, you want to see for yourself that it actually behaves correctly and in which sense of correct, here's something which might help: https://fosstodon.org/@slink/111019934949852505 #utf8
From 2003, but still very helpful to me: "The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!)" https://www.joelonsoftware.com/2003/10/08/the-absolute-minimum-every-software-developer-absolutely-positively-must-know-about-unicode-and-character-sets-no-excuses/ #programming #utf8 #internationalization
wow i think i actually managed to get utf8 working in my VM? i used `setlocale(LC_ALL, ".UTF8")` and then print the UTF32 char 0x0107 ć from my program. the interpreter uses c32rtomb to convert it to UTF8 and then i fwrite that to stdout
but the character doesn't show up in the windows console cause windows is bad. but i figured out a workaround! i put this in my run.bat file:
set run=./bismuth.exe prog.bst
powershell $OutputEncoding = [Console]::InputEncoding = [Console]::OutputEncoding = New-Object System.Text.UTF8Encoding; %run%
and it runs the VM through powershell with powershell forced to use UTF8 and then it works somehow, yay! more bizarrely, it doesn't show me the powershell prompt but the regular command prompt, but it works anyway? idk why but i'll take the win!
also i have no idea if any of this is the right way to do things so, yanno, don't take this as a tutorial or anything
TIL UTF8 names in the author-email field of Python packages are not supported by warehouse (PyPI), and warehouse waits for the PEP/standard to be clarified before moving forward.
- GitHub issue: https://github.com/pypi/warehouse/issues/16496
- Discussion: https://discuss.python.org/t/core-metadata-email-fields-unicode/7421
•ᴗ• ☞ ⁂ ≠ 𝕏