• 13 Posts
  • 1.61K Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2024

help-circle
  • There are actually two interpretations of N/A:

    • N/A (not available): There is lost media so it can’t be evaluated.
    • N/A (not applicable): The show is in sign language so evaluating that is outside the scope of this string-matching program.

    Meanwhile, undefined seems to mean the value has not yet been evaluated. Maybe null is really the best.















  • Zalgo generators often have a settable range for the random number of diacritics per letter. If it includes 1 and you’re (un)lucky, you can get oops-all-acutes. Manually, you can copy the combining character alone (not easy, as you can’t usually select it, but you can use web apps or UnicodePad) and paste one after every letter.

    Combining diacritics actually include some overlays (s̸l̸a̸s̸h̸e̸s̸, s̶̶t̶̶r̶̶i̶̶k̶̶e̶̶t̶̶h̶̶r̶̶o̶̶u̶̶g̶̶h̶, not⃠, bo⃞x etc.) and allow for vertical text without newlines (although support for characters except aeioucdhmrtvx is spotty). Great for Kahoot names if the host machine runs Windows and displays them in a column, as opposed to overlaid like on Android.

    ͩͤͭͣͮͥͭͦͫ






  • It’s Zalgo (putting combining diacritics on every letter) but mild and consistent, plus I used native accented characters if available to improve rendering consistency

    àèìǹòùẁỳ
    áćéǵíj́ḱĺḿńóṕŕśúẃýź
    

    You can test if your text renderer adds combining diacritics as overlays or replaces with native glyphs:

    1. ď (d-caron)
    2. ď (d plus combining caron)
    3. ԁ̌ (Cyrillic ԁ aka “komi de” or “lowercase Ԁ” plus combining caron)

    Most renderers will use identical glyphs for #1 and #2 because #3 (using a d-lookalike (hompglyph) to simulate how cheap Czech typewriter users would print lowercase d-caron) is not how d-caron looks in print (the closest ASCII-safe rendition of that, if you still have encoding problems, is d’)