Ask Bjoern Hansen (lists.bootstrap): >1) I'm still worried about having the "central list" turning into > another p5p. The idea of working groups was in part to make the > process more focused and goal oriented. It sucks for generalists > who just wants to follow everything (like me), but I still > believe it can make the environment better for those who wants to > work on getting something done. Granted. Maybe moderate it. >2) A (possibly very short) RFC will be a good place to start the > discussion and will give an author right away who you can assume > will keep track of what's going down and make sure it gets > documented. Having an evolving RFC (and more focused lists) will > also make it much much easier for new contributers to "jump on" I > believe. OK, so an initial RFC would be something like this?: (Off the top of my head! This is not a real call for participation!) (Yes, this is an RFC on an RFC. So sue me. :) ---------------------------------------------------------------------- Hi. I've got a few ideas about Unicode design, and I'd like start a group to discuss this. Name: Simon Cozens Group: Unicode Suggested Mailing List Name: perl6-unicode@perl.org Current targets for discussion: UTF8/UTF16/UTF32/...? My feeling is we should use UTF16 internally, but have the built-in ability to understand UTF8. I think UTF32 should be bolted on later, so we need to leave room for that. (Plus any other encodings that may become popular in the next N years.) Internal representation Storing UTF8 and non-UTF8 data separately has been a nightmare. We want to be lobbying for UTF16 (or whatever we decide) encoding exclusively in scalars. Liaise with variables people about this. libunicode/external libraries? There are a few good Unicode handling libraries out there. Can we use them, maybe try them as a base and improve them, (Hey, we could even send back patches to the maintainer, so everyone gains...) or should we be reinventing our own wheels? If you want to discuss these or any other Unicode issues, talk to me off-list and we'll get something set up. ---------------------------------------------------------------------- -- "I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you." (By Vance Petree, Virginia Power)Thread Previous | Thread Next