Ticket #12 (closed in progress: fixed)

Opened 7 years ago

Last modified 5 years ago

Data.ByteString - Unicode layer over Data.ByteString

Reported by: paolo Owned by: none
Priority: not yet rated Keywords:
Cc: Topic: Data.ByteString
Difficulty: unknown Mentor: not-accepted

Description (last modified by paolo) (diff)

Extend the  Data.ByteString interface to support Unicode.

This might be implemented by a UnicodeString layer above ByteString, tagged with encodings of underlying fragments. Other strategies are also possible.

For added bonus, hook one or more of libiconv, librecord, libicu and unify them under ByteString interfaces.

Interested Mentors

  • Don Stewart <dons@…>
  • Audrey Tang <audreyt@…>

Interested Students

  • Spencer Janssen <sjanssen@…>

Change History

Changed 7 years ago by paolo

  • topic changed from misc to Data.ByteString
  • description modified (diff)

Changed 7 years ago by autrijus@…

  • description modified (diff)

Changed 7 years ago by paolo

  • description modified (diff)

Changed 7 years ago by paolo

  • description modified (diff)

Changed 7 years ago by autrijus@…

FYI: After some discussion on #haskell, and to illustrate the idea of Ropes-as-finger-trees better, I did a 10-mins hack at  http://svn.openfoundry.org/pugs/src/Data/ByteString/Seq.hs based on dcoutt's ByteString?.Lazy.

If we swap the underlying P.ByteString? into EncodedString?, then this would fit my usage pattern perfectly.

Changed 5 years ago by duncan

  • priority set to not yet rated

I have a student working on this for his MSc project. I don't think we need a GSoC project for it too.

Changed 5 years ago by duncan

  • status changed from new to closed
  • type changed from proposed-project to in progress
  • resolution set to fixed

Resolving as fixed because it's in progress as an MSc project and we don't want duplication.

Note: See TracTickets for help on using tickets.