Accented characters in Lacewing

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • This question relates to the thread I started elswhere.
    See Please login to see this link. for all the details.

    Brief breakdown of the issue . . .

    In an ini file we have for example "name=Grégoire"

    The application reads the ini file and populates say a field with the "name".
    When the field receives its name it then uses Lacewing to join a group with that name.
    If using an accented (foreign) character it doesn't connect to the group.

    If I change the ini file to say "name=Gregoire" (note: no accented characters)
    Then it works straight away and connects to the group.

    Thanks for any help.

    Addictive 247 Games - Please login to see this link.

  • Thanks for the response.
    So if Lacewing doesn't have a Unicode version does that mean that someone using a foreign keyboard layout as their default, cannot use any of their accented characters in conjunction with Lacewing. i.e connecting to a group etc?
    I just need to be 100% sure that I understand before I speak to the client.

    Thanks again

    Addictive 247 Games - Please login to see this link.

  • I think it's possible to have a different extension encode the string in binary and have Lacewing send it as a binary message instead, and then translate the received binary back into unicode characters again, but I don't own the Unicode exporter so I don't know which extension(s) can do this. It is definitely possible, though. Just know that Lacewing always treats strings as non-unicode, so there is no way for user names or channel names to have unicode characters.

    Working as fast as I can on Fusion 3

  • madmac, the Please login to see this link. will let you encode Unicode characters - just send each character as shorts.

    I may chuck out an update so you can handle whole Unicode strings.

    Cheers

    Darkwire Software Lead Programmer (C++ & C#)
    Please login to see this link. | Please login to see this link. | Please login to see this link. | Please login to see this link.

  • Now Lacewing Blue is ported to Unicode, once it's released (or you sub on Please login to see this link. for early access) you will now get your accented characters sent over properly regardless of sender or receiver OS language. :D

    Darkwire Software Lead Programmer (C++ & C#)
    Please login to see this link. | Please login to see this link. | Please login to see this link. | Please login to see this link.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!