Follow-up Comment #7, bug #64445 (project health):
> 42[Y] 11[M] 9[D]
Going back to this representation, I think is the best approach.
Easy to split and get elements, and it could allow more than 1 char, although
I also think that translation should be kept to 1 character.
Question.. how about non-ascii chars, and non-latin representation? (like in
the case of Chinese..) Can we represent it with a single char?
Today we have the ascii-escaped representation, that would take more than one
char.
We'll go back to the debate on ensure_ascii argument in json.dumps. Let's
explore this more.
Best
Luis
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64445>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
