On 10/8/10 6:49 AM, Jacek Kałucki wrote:
> Użytkownik Paul McNett napisał:
>> On 10/8/10 3:19 AM, Jacek Kałucki wrote:
>>
>>>> +def getXMLEncoding():
>>>> + ret = getEncoding()
>>>> + if ret.lower().strip().replace("-", "") == "utf8":
>>>> + return "utf-8"
>>>> + if "1252" in ret:
>>>> + return "windows-1252"
>>>> + return ret
>>>>
>>>>
>>> Maybe it worth while to move above code to getEncoding() function itself?
>>>
>> I don't understand enough of the issues to even know if the above function
>> is a good
>> idea at all - it seems like we are setting ourselves up for a maintenance
>> headache.
>>
>> The only reason I put it in was it seemed that some band-aid needed to be
>> applied for
>> our xml files to be generated correctly again, at least on systems with utf8
>> or 1252
>> encoding.
>>
>
>
> Point is that Python encode/decode methods, they do understand
> both, 'windows-1252' and '1252' encoding naming.
> But IANA naming standard, used in XML, it requires 'windows-1252'.
Python may understand that 'windows-1252' and '1252' are the same, but is it
always
guaranteed to understand that 'some-encoding-x' is the same as 'EncodingX'?
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]