On Sat, Apr 18, 2020, 07:09 Karl Kleinpaste <k...@kleinpaste.org> wrote:
> On 4/17/20 11:43 AM, Greg Hellings wrote: > > the HTML WG suggests, and apparently all browsers implement, ignoring > those directives and instaead caring only about the Content-Type > header/directive. So if you have that header/directive in Xiphos, then try > updating that to the appropriate "application/xhtml+xml" and see if that > fixes Xiphos/WebKit's behavior? > > As I showed in my original note on this, the opening stanza includes > > <meta http-equiv=\"content-type\" content=\"application/xhtml+xml; > charset=utf-8\"> > This is the HTML header. Not the HTTP header. For manually loading the text you don't have an HTTP header, but you still tell the widget what content type when you call wk_html_open_stream or webkit_web_view_load_string or similar functions. It's this value that is telling Webkit what to do. --Greg > > and it doesn't help. On a whim, I tried Content-Type in the event a > case-sensitive match was required, but that didn't help, either. >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
