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\"> 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
