[albatross-users] A better page system

[Dave Cole]

>>>>> "Andrew" == Andrew McNamara <andrewm at object-craft.com.au> writes:

Michael> Ps.  How close is that fabled new version of albatross? =)
>>  The code has been ready for some time.  I need to keep plugging
>> away at the documentation.  I don't really have much against an
>> interim/pre release that is followed up with a real release once I
>> finish updating the documentation.
>> 
>> What are your thoughts Andrew?

Andrew> Yes, I think a pre-release would be a good thing. It probably
Andrew> shouldn't be announced on the python-* list.

Yes.

Andrew> Do we want to roll the unicode support into the next release?

That might be a good idea.  I am in two minds though.  On one hand we
want to get the new code out there, while on the other, the Unicode
support has received limited testing.

How many people are interested in trying and using the Unicode
support?

Should we merge it in now or later?

Andrew> When you need unicode support, you really need unicode
Andrew> support. The biggest gotchya is the template output is cast to
Andrew> unicode strings, which means that the 'ascii' decoder is
Andrew> applied to all your traditional string output - the 'ascii'
Andrew> decoder will throw an exception if it's input is not 7-bit
Andrew> clean.

Andrew> Put another way, if your application only uses characters in
Andrew> the range 0-127, the unicode version of albatross works
Andrew> identically to the old version. However, if you are using
Andrew> foreign character sets (accented characters, etc) with
Andrew> characters in the range 128-255, your application will need to
Andrew> be changed (but the results are much cleaner).

You probably need to provide an example here.

- Dave

-- 
http://www.object-craft.com.au