Does anyone know what charset/encoding the xml response for HMO requests need to be in? I'm running into a encoding display issue with my tivohmo ruby project ( http://ift.tt/11eBn7J ).
The problem I'm seeing is that metadata (specifically description) that I fetch from plex, has some unicode values (specifically U+2019 - which is a apostrophe), and these show up as empty boxes when browsing the item in the tivo HMO browse UI. However, once I transfer it to the tivo, it does show up correctly as an apostrophe in the details for the show in the "My Shows" UI.
I'm doing everything in utf-8, and both the QueryContainer and TVBusQuery responses are in utf-8. I've tried setting Content-Type response header to 'text/xml', 'application/xml', 'text/xml; charset=utf-8', 'application/xml; charset=utf-8', but makes no difference.
The only place I don't use utf-8 is when transferring the file to the tivo - I generate the TVBusQuery xml as utf-8, but dump the raw bytes into the header since it is a binary stream - which may be why it works in the tivo UI, but not the hmo ui ...? http://ift.tt/1vjk3J9
If I manually create a pyTivo metadata file containing that string, the same things happen.
Any ideas?
The problem I'm seeing is that metadata (specifically description) that I fetch from plex, has some unicode values (specifically U+2019 - which is a apostrophe), and these show up as empty boxes when browsing the item in the tivo HMO browse UI. However, once I transfer it to the tivo, it does show up correctly as an apostrophe in the details for the show in the "My Shows" UI.
I'm doing everything in utf-8, and both the QueryContainer and TVBusQuery responses are in utf-8. I've tried setting Content-Type response header to 'text/xml', 'application/xml', 'text/xml; charset=utf-8', 'application/xml; charset=utf-8', but makes no difference.
The only place I don't use utf-8 is when transferring the file to the tivo - I generate the TVBusQuery xml as utf-8, but dump the raw bytes into the header since it is a binary stream - which may be why it works in the tivo UI, but not the hmo ui ...? http://ift.tt/1vjk3J9
If I manually create a pyTivo metadata file containing that string, the same things happen.
Any ideas?
Aucun commentaire:
Enregistrer un commentaire