View Single Post
Old 06-21-2012, 07:47 AM   #34
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 27,552
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Jellby View Post
But the document could be utf-16 encoded, couldn't it?
The original source could possibly be utf-16, but at the point the entity substitution happens, Sigil seems to have already homogenized everything to utf-8 (that's an assumption based on the presence of the "QString::fromUtf8" function). Still... it could pose a problem if Sigil does (or chooses to in the future) preserve the underlying utf-8/16-ness of a document. Right now, though, it seems that portion of Sigil's code is confidently expecting utf-8. *shrugs*

Last edited by DiapDealer; 06-21-2012 at 07:51 AM.
DiapDealer is offline