Martin Vermeer wrote: > On Thu, 2006-04-27 at 10:26 +0200, Abdelrazak Younes wrote: >> Well, we could well decide to do unicode in 1.6 as I don't see anything >> happening in trunk as of now. My point is that 1.5 is very nice as it is >> and users deserves it. > > If that is really the case, it should be released next under the name > 1.4.2.
Yes. >> It unicode is going to destabilize trunk for a >> year or two, let's postpone it until 1.6. It's not like unicode support >> in 1.5 is written down in god sent tablet, or is it? :-) 1.5 should really have unicode support. It is a requirement for important bug fixes. For example I want support for the euro symbol, but it does not make sense to invent something without unicode. And we have the encoding mess which is not completely solved (the spell chaker does not work in utf8 encodings). >> More seriously, if the aim is to support unicode what not let it happen >> now? Is there some code already? >> >> Disclaimer: I know nothing about unicode... > > Same here. But Lars has a personal tree on this, which looks sort-of > impressive. He even made a list of steps to follow. > Why not just put this into trunk after 1.4.2 is out? How > functional is it? I am all for it. We could as well do this now, that would probably accelerate unciode development. Georg
