Matthew Willis wrote: > Ed, > > I work with different encodings of Japanese, and it's a big headache. > The biggest part of the headache is that no one knows what encoding > they are using when they make files. So, you see garbled web pages > because the encoding wasn't specified in headers or was specified > incorrectly, garbled emails because the email client makes assumptions > about encodings, and other mayhem. > > Honestly, I think it's about time the world got to know their encodings. > > I REALLY don't want working with the various formats I work with to > become any harder than it already is. I do not want to sacrifice the > ease of saying 'iso-2022-jp <file-reader>', 'shift-jis <file-reader>', > and all the other adorable encodings japanese people like to use. > > I'd really prefer to have the chance to use this new, promising API > that Dan has come up with. Hi Matthew,
Would you be interested in implementing some of these Japanese encodings? There are 100 million potential Factor hackers waiting for you to take the leap! Now we just need to revive the ARM port and get Factor running on lots of gadgets... the Japanese love gadgets, at least that was the impression I got when I visited Japan 10 years ago :-) Slava ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
