Notices tagged with unicode

  1. @mcscx Yeah I got it on IRC earlier. gnome-terminal wouldn't make it clickable. Feature or bug? ;)

    Nevertheless, unicode spoofing issues is old news. Everyone know about the crap it endues. I think I've had a rant before about # being a tool of cultural appropration for the west.

    Monday, 24-Apr-17 17:18:22 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context
  2. @gargron Either way, I don't think there would be a problem for !GNUsocial with remote # (non-ASCII) characters. Nicknames are normalised as-is (for example removal of underscores which was another discussion). I don't remember if transliteration of nicknames is done, but we do that for # (which has also sparked controversy due to incompatibility with farsi).

    My desire is to implement unicode support for nicknames. I don't know about the best strategy for homoglyph attacks etc, but I bet the !xmpp community has lots to share there. There you can have at least a large set of Unicode in your user part of the XMPP ID. Maybe # developer @zash knows more about unicode in XMPP usernames etc?

    cc: @munin @nightpool

    Monday, 24-Apr-17 05:55:33 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E
  3. @archaeme A lot of older software incorrectly or incompletely implemented # And I still see the charsets Windows-1252 or Latin-1 / Latin-15 in most office suite documents.

    I'd like to see some "we made a mistake, and we're willing to break backwards compatibility to fix it" posts on corporate software blogs. Oracle, LibreOffice / OpenOffice, Microsoft, IBM, are you all listening?

    Saturday, 08-Apr-17 22:00:43 UTC from nu.federati.net in context Repeated by archaeme
  4. @archaeme A lot of older software incorrectly or incompletely implemented # And I still see the charsets Windows-1252 or Latin-1 / Latin-15 in most office suite documents.

    I'd like to see some "we made a mistake, and we're willing to break backwards compatibility to fix it" posts on corporate software blogs. Oracle, LibreOffice / OpenOffice, Microsoft, IBM, are you all listening?

    Saturday, 08-Apr-17 22:00:43 UTC from nu.federati.net in context
  5. Our proposal to get the #CC logo and icons into #Unicode
    https://creativecommons.org/2016/10/31/cc-logo-icons-unicode/ would be nice...

    Sunday, 06-Nov-16 20:44:53 UTC from joindiaspora.com Repeated by kuro
  6. Our proposal to get the #CC logo and icons into #Unicode
    https://creativecommons.org/2016/10/31/cc-logo-icons-unicode/ would be nice...

    Sunday, 06-Nov-16 20:44:53 UTC from joindiaspora.com Repeated by kzimmermann
  7. Our proposal to get the #CC logo and icons into #Unicode
    https://creativecommons.org/2016/10/31/cc-logo-icons-unicode/ would be nice...

    Sunday, 06-Nov-16 20:44:53 UTC from joindiaspora.com
  8. I joked about # being oppressive and imperialistic, but it actually is. Inclusion/exclusion is a political process: https://Fluffle Puffposter.club/notice/485548

    Monday, 20-Jun-16 15:28:18 UTC from shitposter.club in context
  9. Apparently, !python 3.3+ does strange stuff with # http://goo.gl/KhRFBp

    Thursday, 17-Mar-16 14:37:07 UTC from gs.kawa-kun.com
  10. There's already been a discussion about skin colour in # When will the discussion on gender stereotypes arise? Example from http://unicode.org/emoji/charts/emoji-candidates.html

    U+1F935 MAN IN TUXEDO
    • see BRIDE WITH VEIL

    »Where is "Man with veil" and "Woman in tuxedo"?» ... GO!

    Friday, 11-Mar-16 13:20:25 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context
  11. @mk that was weird: posting the video's title in # it *disappeared* and made cursor position inaccurate; I tried anyway, and it came out OK... a new manifestation of the old # problems in identicurse.

    Thursday, 24-Sep-15 08:52:01 UTC from oracle.skilledtests.com in context
  12. # ☯ ☘ ☮ ☹ ☺ ♡ ⚜

    Wednesday, 30-Jul-14 11:43:12 UTC from bti in context
  13. Nice: # does # without any hickup (at least with gfortran): print *, "type values for a, b, c in ax² + bx + c = 0"

    Tuesday, 09-Jul-13 06:59:33 UTC from identi.ca at 49°10'1"N 8°29'32"E
  14. Those # errors appear always when you least expect them.

    Tuesday, 29-Jan-13 19:08:18 UTC from identi.ca at 60°12'18"N 24°39'7"E
  15. @lnxwalt Like, say, "ustdio.h" or "stduio.h" for # -compliant versions of "stdio.h"'s funcs, where relevant, and so on.

    Sunday, 20-Jan-13 15:25:11 UTC from micro.fragdev.com
  16. @lnxwalt I can understand not adding # support to the existing stdlib, but that shouldn't preclude adding explicitly # libs.

    Sunday, 20-Jan-13 15:23:50 UTC from micro.fragdev.com
  17. Cutest # character ever!

    Thursday, 20-Sep-12 11:29:52 UTC from identi.ca in context