Hi Jose,

On Friday 06 August 2010, Jose Manuel wrote:
> "/usr/lib/python2.5/site-packages/binary_agilo-1.3.0.6_PRO-py2.5.egg/
> agilo/utils/permissions.py",
> line 116, in get_actions_for_custom_types
>     plain_name = str('CREATE_' + typename.upper())
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xd3' in
> position 16: ordinal not in range(128)
> beleg:/var/www/operaciones.andago.com/calidad/trac/db#
> 
> With chain "02-Revisión Entregables" that contains the spanish
> character
> 'á'.
> 
> Changes:
> beleg:~# diff
> /usr/lib/python2.5/site-packages/binary_agilo-1.3.0.6_PRO-py2.5.egg/
> agilo/utils/permissions.original.py
> /usr/lib/python2.5/site-packages/binary_agilo-1.3.0.6_PRO-py2.5.egg/
> agilo/utils/permissions.py
> 116c116
> <           plain_name = str('CREATE_' + typename.upper())
> ---
> 
> >           plain_name = str('CREATE_' +
> >typename.upper().encode('utf-8'))

Thanks for the bug report and patch. Unfortunately, I don't think the 
patch solves the problem completely. It just creates a workaround in one 
place for one setup. The whole idea behind the separation between alias 
and type name is that the alias is a localized, displayed value that can 
contain any type of character, including UTF-8. The alias will be used 
in SQL statements, DB schemas, JSON content and URLs and thus it is a 
lot easier to work with ascii text only. The bug in here, in my opinion, 
is that the admin interface does not restrict the input on this field to 
ascii.


Cheers
Robert

-- 
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
Please support us by reviewing and voting on: 
http://userstories.com/products/8-agilo-for-scrum 
http://ohloh.net/p/agilo-scrum 
http://freshmeat.net/projects/agiloforscrum

You have received this message because you are subscribed to
the "Agilo for Scrum" Google Group. This group is focused on
supporting Agilo for Scrum users and is moderated by
agile42 GmbH <http://www.agile42.com>.

To post to this group, send email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo

Reply via email to