[katello-devel] Fwd: [Pulp-list] i18n input

[Mike McCune]

comment:

This would be awesome.

I'd much rather see the below vs a worst case scenario of forcing ASCII 
encoding for everything.


On 10/02/2012 01:43 PM, Bryan Kearney wrote:
> Comments?
>
> -- bk
>
>
>
> -------- Original Message --------
> Subject: [Pulp-list] i18n input
> Date: Tue, 2 Oct 2012 14:40:18 -0600
> From: Jason Connor<jconnor at redhat.com>
> To: pulp-list at redhat.com<pulp-list at redhat.com>
>
> Hi All,
>
> Lately we've been struggling with a rash of bugs related to i18n input
> in Pulp. Python 2's unicode support is only so-so and whenever we get
> non-ascii or non-utf-8 encoded strings, we tend to run into trouble (the
> most common is problematic encoding seems to be latin-1). Given that
> Python's str type is really just a byte array with some built in smarts,
> it isn't really possible to guess what the encoding might actually be.
>
> To address this issue, I propose that we make string encoding as utf-8 a
> hard requirement on the server. To enforce this, we'll try to decode all
> strings from utf-8 and any failures will get a 400 server response with
> some sort of standardized message: utf-8 encoded strings only (dummy),
> or something similar.
>
> Any thoughts?
>
> Jason L Connor
> linear on freenode #pulp
> http://pulpproject.org/
> RHCE: 805010912355231
> GPG Fingerprint: 2048R/CC4ED7C1
>
>
>
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
>
> _______________________________________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/katello-devel