On Wed, 06 Feb 2008 21:19:26 -0000, mte <[EMAIL PROTECTED]> wrote:
>> A better way would be to decode(sys.stdout.encoding)
>>
>> Either way, you can get around this now by just using the unicode
>> string
>> u'\u010d'.
>
> Yes, I thought sys.stdout.encoding (or sys.stdin.encoding?)
Ah yes, of course :). I can't think of many circumstances where they'd be
different, though.
> would be
> better but didn't know if the relevant encoding info was stored there
> or somewhere else.
> Typing u'\u010d' or even unicode('č', 'utf-8') is a workaround but as
> the tg-admin shell is meant for quick tasks it's just not comfortable
> doing it the slow way.
True, since it works in the normal prompt it ought to work in tg-admin's
spawned prompt too.
> So again, is there any point in posting a new ticket? Is there a
> chance that TG developers would apply this patch?
Not for me to say, but if they like it I don't see why they wouldn't apply
it :)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
