Future of Ac... or even of PLD

[Marcin Król]

> Wrong choice.
> Why? Because with every spec that should be ony taged you'll have to do 
> conversion. Which isn't needed...

Well, the day that 'cvs diff -u some.spec' will convert charset
automagically on the fly from UTF to my local encoding I'll accept UTF
in Ac specs. Otherwise I may be even unable to check my changes w/o
redirecting diff to file and doing iconv manually as displaying UTFish
charactes on ISO console causes many weird things like screen being
cleared, cursor moving to some random postion etc. Basically in most
cases it clutters up the screen. And no, switching to UTF console is not
an option here.

I prefer doing conversion in spec for AC-branch than seeing UTF junk on
my screen.

> Every developer will have to prepare his console anyway - we shouldn't 
> care about that. Maybe just write some small tutorial :)

Not every developer :) I'm not going to touch HEAD for at least next few
months so I don't need to configure anything for UTF :)

> But he would have choice and he will do this in good for him moment.

I don't see any difference in doing architecture conversion lets say
half a year from now for Ac 2.1 release or year from now for Th release.
User still will have the choice: stick with old Ac 2.0 or go for Ac
2.1/Th also he still would be able to choose the moment when he will
upgrade.

M.