Comment 1 for bug 623053

All right,

so one more detail about this one:

the field that create the web-client bug is the ('fiscal_operation_id', 'Opera\xc3\xa7\xc3\xa3o Fiscal', 'many2one') field on the sale.order that is brought by the l10n_br localization.

Actually, the other sale.order fields from the list given here also have accents, but those are brought by the translation layer, and consequently comes as unicode (u'translated_field_name'). That's why they don't cause bugs if l10n_br isn't installed.

The question is whether Openobject should accept accents in field names. Using the same reasoning as for bug https://bugs.launchpad.net/openobject-server/+bug/613721 (OpenERP should truly be RAD), I think we should accept them, at least for the fields manually created in the user interface.

Then I'll propose a patch that will encode in unicode field names that are not unicode inside self.fields_list.sort(lambda x, y: cmp(x[1], y[1]))
May be we should encode all field names at the source, but that choice is up to OpenERP S.A. I guess.