#2 Support for unicode encodings

closed
nobody
None
5
2010-04-16
2009-08-19
No

It would be nice to have support for a few more character encodings, for instance, some of the unicode encodings... this would be particularly useful when creating events that communicate application state which often contains data in the language of the end-user

Discussion

  • Michael Lum

    Michael Lum - 2009-10-29

    +1 on this, and I believe the API and event spec support multiple encodings, just need the time to implement.

     
  • Anthony Molinaro

    This is supported right now, in that the library does not enforce an encoding. There is an enc field added to each event, but it is totally left up to the application developer to define and set that field. So if you want to add unicode, you simple define some integer to mean unicode for you, and set that as the encoding value. Then set strings with unicode and write listeners which get them and treat them as unicode.

    In other works lwes does nothing to your bytes. It up to the application to decide what to do. In fact it may be better to deprecate the 'enc' field and force application writers to set it themselves?

     
  • Michael Lum

    Michael Lum - 2010-04-16

    closing since the encoding of the bytes is entirely up to the caller.

     
  • Michael Lum

    Michael Lum - 2010-04-16
    • status: open --> closed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks