> > > And TextEdit cannot save as UTF-8? > > > > It can. But doing so suffers from "mojibake". > > You mean, it won't read it back in properly? Yes, it won't. > I expect that the localization patches that circulate now will > continue to apply (perhaps with minimal modifications) after stage 1 > is implemented. If the patches are enhanced to do the "right thing" > (i.e. properly take into consideration the declared encoding, to > determine the end of a string), people won't notice the difference > compared to a full stage 2 implementation. You do not need localization patches anymore. I have almost written a sample implementation of "stage2" already. It was so hard that it took 2 days ;-). I will post it to NetNews and python.sf.net in a few days. Yes, I will put it in the public domain. -- SUZUKI Hisao <suzuki@acm.org> <suzuki611@oki.com>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4