View Single Post
Old 07-23-2014, 08:17 AM   #5
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Unicode Literally Appearing On Gui Display

Kovid,

There was no difference in output on the display screen. The gui still shows the same unicode literal u'N\xe3o-fic\xe7\xe3o' after changing to using mi.set(xxx instead of mi.set_user_metadata(xxx. Both update the custom column perfectly. Identical output. Again, my question is not about how to get it updated in general, but rather how to get it updated so the human being sitting at the Calibre gui does not see "u'N\xe3o-fic\xe7\xe3o', but instead sees the "real" word of Não-ficção. The gui shows the unicode string, not the human-readable string. Is there special syntax to make Calibre show the value in human readable form instead of the original unicode string?

Please see the attached image.
Attached Thumbnails
Click image for larger version

Name:	Capture2.JPG
Views:	512
Size:	19.4 KB
ID:	125723  

Last edited by DaltonST; 07-23-2014 at 08:35 AM. Reason: Added Screen Snippet
DaltonST is offline   Reply With Quote