1. Forum
  2. FidoNet
  3. Hot Dog Editor Support

  • unicode vs cp437

    From Benny Pedersen@2:230/0 to All on Thu Mar 10 20:44:22 2016
    Hello All!

    if utf-8 is enabled it works with unicode senders, no problem there, its just that it changes default aswell for when senders dont add chrs kludge aswell :/

    so if one use latin-1 in hotdoged, it will display utf-8 postings as cp437 since it cant decode unicode in iconv there

    real bug is imho clients leave out chrs kludge not how hotdoged works


    Regards Benny

    ... there can only be one way of life, and it works :)

    --- Msged/LNX 6.2.0 (Linux/4.4.3-gentoo (i686))
    * Origin: openvpn on its way here (2:230/0)
  • From Sergey Poziturin@2:5020/2141.3 to Benny Pedersen on Fri Mar 11 09:10:26 2016
    Hello, Benny Pedersen.
    On 10.03.16 20:44 you wrote:

    if utf-8 is enabled it works with unicode senders, no problem
    there, its just that it changes default aswell for when senders
    dont add chrs kludge aswell :/ so if one use latin-1 in hotdoged,
    it will display utf-8 postings as cp437 since it cant decode
    unicode in iconv there real bug is imho clients leave out chrs
    kludge not how hotdoged works

    Ftn support realization does not support per-message and per-group encoding right now. That's because of the underlying algorithms used for unpacking pkt files. Actually that's jnode part of code.

    So the only encoding that Hotdoged takes care of at the moment is a codepage in
    server settings.

    I'm looking forward to fix this but it will take too much refactoring.

    --
    Best regards!
    Posted using Hotdoged on Android
    --- Hotdoged/2.12/Android
    * Origin: Android device, Milky Way (2:5020/2141.3)