Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-19 Thread Karl Kleinpaste
On 4/18/20 11:28 PM, Troy A. Griffitts wrote: > I hope this fixes the issue for you. Thank you, yes, that does it. I've committed a re-work patch of Xiphos' handling of intro material on that basis. Of course, this means I'm committed, I can't release a new Xiphos now without a preceding or concurr

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Troy A. Griffitts
OK Karl, I've committed a fix for this.  We handle a bunch of OSIS div types specifically, but we weren't handling type="introduction" which is what the ESV used, so the div was simply passed thru.  I'm now checking div types we don't handle and if they are trojan milestones (they include sID and

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Karl Kleinpaste
On 4/18/20 6:32 PM, Caleb Maclennan wrote: > ESV modules have been pulled from every public SWORD repository Uh-huh. Do you suppose that there aren't several tens of thousands of people who still have it, including Troy? ___ sword-devel mailing list: swor

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Caleb Maclennan
On Sun, Apr 19, 2020 at 1:27 AM Karl Kleinpaste wrote: > On 4/18/20 5:25 PM, Troy A. Griffitts wrote: > > Do you have a module and entry key value I can use for testing? > > ESV2011, intro commentary paragraphs at every book's 1:1. > The ESV modules have been pulled from every public SWORD repos

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Karl Kleinpaste
On 4/18/20 5:25 PM, Troy A. Griffitts wrote: > > Do you have a module and entry key value I can use for testing? > ESV2011, intro commentary paragraphs at every book's 1:1. ___ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/m

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Troy A. Griffitts
Hey Karl, Do you have a module and entry key value I can use for testing? Troy On 4/18/20 2:10 PM, Karl Kleinpaste wrote: > On 4/18/20 2:48 PM, Greg Hellings wrote: >> This is the HTML header. Not the HTTP header. > > I had thought that's what the content=\"application/xhtml+xml; charset=utf-8

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Karl Kleinpaste
On 4/18/20 2:48 PM, Greg Hellings wrote: > This is the HTML header. Not the HTTP header. I had thought that's what the was supposed to give me, for the case of a directly-loaded text blob that didn't arrive via HTTP. Apparently not. > For manually loading the text you don't have an HTTP header, b

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Greg Hellings
On Sat, Apr 18, 2020, 07:09 Karl Kleinpaste 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 X

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Troy A. Griffitts
Karl, I fear that, even if you get this working, as Greg mentioned earlier, if any module sends even the smallest error which causes the content not to strictly validate-- like an open quote which doesn't close at the end of a verse, that the browser may drop out of XHTML mode. I do find it odd

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-18 Thread Karl Kleinpaste
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 "appli

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-17 Thread Greg Hellings
On Fri, Apr 17, 2020 at 6:33 AM Karl Kleinpaste wrote: > On 4/16/20 11:08 PM, Greg Hellings wrote: > > will give you HTML 5, not XHTML. XHTML would be much > wordier: > https://en.wikipedia.org/wiki/Document_type_declaration#XHTML_Basic_DTDs > > > Well... That link itself says: > > In XHTML5

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-17 Thread Karl Kleinpaste
On 4/17/20 8:14 AM, Troy A. Griffitts wrote: > Let me see if I can get the XHTML filters to stop outputting milestone > divs. I wouldn't mind them at all, since they're standards-conformant after all, if I could just convince WebKit not to act stupid. But I'll take either result, honestly, smarter

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-17 Thread Troy A. Griffitts
Let me see if I can get the XHTML filters to stop outputting milestone divs. The XHTML filters were meant to use updated HTML/CSS practices, which at the time was XHTML. Now it would probably be HTML5 so, I chose a poor name for the filters. Anyway, if milestone divs are causing you a world of h

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-17 Thread Karl Kleinpaste
On 4/16/20 11:08 PM, Greg Hellings wrote: > will give you HTML 5, not XHTML. XHTML would be much > wordier: > https://en.wikipedia.org/wiki/Document_type_declaration#XHTML_Basic_DTDs Well... That link itself says: In XHTML5  the |DOCTYPE| must be a c

Re: [sword-devel] trying to get proper xhtml to work in webkit

2020-04-16 Thread Greg Hellings
On Thu, Apr 16, 2020 at 9:31 PM Karl Kleinpaste wrote: > From discussion here in March of last year, I am attempting to get Xiphos > to operate in a proper xhtml mode, rather than its apparent heretofore html > mode, because I honestly wasn't aware that WebKit could operate other than > xhtml in

[sword-devel] trying to get proper xhtml to work in webkit

2020-04-16 Thread Karl Kleinpaste
>From discussion here in March of last year, I am attempting to get Xiphos to operate in a proper xhtml mode, rather than its apparent heretofore html mode, because I honestly wasn't aware that WebKit could operate other than xhtml in the first place. The specific goal is to leave self-closing tag