1. Forum
  2. FidoNet
  3. FIDONET.TELEGRAM

  • an emoji suggestion/solution for Tg->Fido

    From August Abolins@2:460/256 to All on Friday, February 10, 2023 20:55:23
    Hi All...

    an emoji suggestion/solution for Tg->Fido

    How about, instead of trying to transliterate every emoji or allowing them to be "??", display the emojis from Tg as the cryptic hex that represents the UTF character?

    Ciao!
    /|ug
    https://t.me/aabolins

    --- Want fido for iOS/MacOS/Android/Win/Linux? https://shrtco.de/tpJ9yV
    * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
  • From Flavio@2:460/256 to August Abolins on Sunday, February 12, 2023 17:58:48
    an emoji suggestion/solution for Tg->Fido
    How about, instead of trying to transliterate every emoji or allowing them to be "??", display the emojis from Tg as the cryptic hex that represents the UTF character?

    that could be good for mail readers, but bad for humans..

    --- tg BBS v0.7.1
    * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
  • From August Abolins@2:460/256 to Flavio on Sunday, February 12, 2023 18:28:22
    Hi Flavio...

    that could be good for mail readers, but bad for humans..

    true enough. messages filled with U+<code> 's could get just as messy to look at as #hashtags. but the end result is better than just "??". personally, i think emojis are an abomination to language. however, used sparingly, they can be useful and fun.

    Ciao!
    /|ug
    https://t.me/aabolins

    --- Want fido for iOS/MacOS/Android/Win/Linux? https://shrtco.de/tpJ9yV
    * Origin: Fido by Telegram BBS from Stas Mishchenkov (2:460/256)
  • From Carlos Navarro@2:341/234.1 to August Abolins on Sunday, February 12, 2023 20:14:26
    10 Feb 2023 20:55, you wrote to All:

    How about, instead of trying to transliterate every emoji or allowing
    them to be "??", display the emojis from Tg as the cryptic hex that represents the UTF character?

    How about, instead of that, just display everything from TG as UTF-8?

    ...except in echos in which some specific charset is commonly used or required, like CP866 in RU.*, etc., where transliteration may be more convenient.

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234.1)
  • From August Abolins@2:221/1.58 to Carlos Navarro on Sunday, February 12, 2023 17:11:00
    Hello Carlos!

    How about, instead of trying to transliterate every emoji
    or allowing them to be "??", display the emojis from Tg
    as the cryptic hex that represents the UTF character?

    How about, instead of that, just display everything from
    TG as UTF-8?

    How many BBS message systems even support UTF-8 today?


    ...except in echos in which some specific charset is
    commonly used or required, like CP866 in RU.*, etc., where
    transliteration may be more convenient.

    It would need to be managed on an echo by echo basis that
    supports UTF-8, I guess. On second thought I wouldn't
    necessarily want to see primarily ascii-based message areas
    filled with untranslated U+HHHHH codes littering a message
    --
    ../|ug

    --- OpenXP 5.0.57
    * Origin: tg_bbs-> https://t.me/joinchat/TWCQfOZqwwOmweR1 (2:221/1.58)
  • From Carlos Navarro@2:341/234.1 to August Abolins on Tuesday, February 14, 2023 18:35:54
    12 Feb 2023 17:11, you wrote to me:

    How about, instead of that, just display everything from
    TG as UTF-8?

    How many BBS message systems even support UTF-8 today?

    Synchronet and MBSE, I was told. It is planned for BBBS too. Not sure about Mystic.

    As for FTN editors/packages, several have full UTF-8 support, others have some limitations...

    It would need to be managed on an echo by echo basis that
    supports UTF-8, I guess. On second thought I wouldn't
    necessarily want to see primarily ascii-based message areas
    filled with untranslated U+HHHHH codes littering a message

    Well, on second thoughts I think that what you suggest may be fine for Fido. Some usual emojis could be transliterated (to :-) :-D X-D etc.), and those that are not currently supported, to something like [U+1F4A9]. At least we could find out what the user meant ;-) Better than lots of confusing quotation marks...

    What I don't like is transliteration of normal, non-English text characters (those not included in ASCII<127, like accented vocals, umlauts, etc.)

    Carlos

    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: cyberiada (2:341/234.1)