Changes to "Changelog" between 2020-02-17 23:57:54 and 2020-02-18 04:04:56

    51     51   
    52     52   * Added a workaround for a FreeDesktop notifications clown fiesta.
    53     53       * Ripcord will sometimes issue notifications or tray messages like this example: "[CoolTeam] <Alice> hi Bob"
    54     54       * With Slack, the client is supposed to just display whatever the server gives it, like the example above.
    55     55       * Some Linux desktop environments (or rather, some components that constitute some desktop environments, I guess) will interpret "<Alice>" to be the opening tag of an HTML element that has no closing tag.
    56     56       * And then the desktop environment will helpfully display a popup with these contents: "[CoolTeam] "
    57     57       * Thanks.
    58         -    * If Ripcord just replaced '<' and '>' with the HTML entities as text (like `<` ) then some *other* Linux DE components wouldn't display that correctly, either. (Since they aren't interpreting it as HTML, they would just display the HTML entities junk as text.)
           58  +    * If Ripcord just replaced '<' and '>' with the HTML entities as text (like `<` ) then some *other* Linux DE components wouldn't display that correctly, either. (Since they aren't interpreting it as HTML, they would just display the HTML entities junk as text.)
    59     59       * There's no API or way to query to see what system or listener Qt ends up sending the notification messages to.
    60     60       * Even if there were, I don't want to maintain a list of specific FreeDesktop-ish dbus things in Ripcord with specific behaviors for each version that Ripcord should follow.
    61     61       * Solution: replace '< and '>' with 'ᐸ' and 'ᐳ' from the Unicode Canadian Aboriginal Syllabics block.
    62     62       * Computer.
    63     63   
    64     64   Ripcord version 0.4.22 (2020-1-18)
    65     65   ----------------------------------