[sword-devel] TSK sources?

2020-04-16 Thread Tuomas Airaksinen
Hi,

I would like to check if it would be possible to improve quality of popular
TSK module (which is public domain). Where are the sources?

--
Best regards,
Tuomas
___
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

Re: [sword-devel] TSK sources?

2020-04-16 Thread David Haslam
Sure - there are lots of things we could do better in 2020 than we could in 
2008.

What might be the most accurate and full featured PD online source ?

There’s a database in this repo.

Treasury of Scripture Knowledge Command Line Interface
https://github.com/narthur/tsk-cli

GitHub came after 2008 so it’s not what was used for our TSK module.
It might even be the other way round.

Might you be the willing volunteer ?

Best regards

David

Sent from ProtonMail Mobile

On Thu, Apr 16, 2020 at 09:27, Tuomas Airaksinen  
wrote:

> Hi,
>
> I would like to check if it would be possible to improve quality of popular 
> TSK module (which is public domain). Where are the sources?
>
> --
>
> Best regards,
> Tuomas___
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

Re: [sword-devel] TSK sources?

2020-04-16 Thread Tuomas Airaksinen
I would like to get it forward, yes. Though I'm putting full efforts on And
Bible releases these days (and there's a lot of work),
so if someone else does it I'm very grateful. But as I have been starting
to use it, and am suffering from quality problems,
yes, I might be willing to contribute.  Is there OSIS source of existing
module? Is tsk-cli having the same source as our module?

On Thu, Apr 16, 2020 at 11:55 AM David Haslam  wrote:

> Sure - there are lots of things we could do better in 2020 than we could
> in 2008.
>
> What might be the most accurate and full featured PD online source ?
>
> There’s a database in this repo.
>
> Treasury of Scripture Knowledge Command Line Interface
> https://github.com/narthur/tsk-cli
>
> GitHub came after 2008 so it’s not what was used for our TSK module.
> It might even be the other way round.
>
> Might you be the willing volunteer ?
>
> Best regards
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Thu, Apr 16, 2020 at 09:27, Tuomas Airaksinen <
> tuomas.airaksi...@gmail.com> wrote:
>
> Hi,
>
> I would like to check if it would be possible to improve quality of
> popular TSK module (which is public domain). Where are the sources?
>
> --
> Best regards,
> Tuomas
>
>
>
> ___
> 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



-- 
T: Tuomas
___
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

Re: [sword-devel] TSK sources?

2020-04-16 Thread David Haslam
Anything done in 2008 was probably built by Chris Little.
He’s left CrossWire so we can’t ask him where he found the source data.

All we can do is to ask about the provenance of any dataset we discover online 
when it’s not already evident.

Aside: On my PC there’s also a module called TSKe - the letter e being for 
enhanced.
I cannot recall where I installed it from.
It must be quite old. I installed it in 2013.
It’s a RawCom module, and there’s not much more to learn from tske.conf

Best regards,

David

Sent from ProtonMail Mobile

On Thu, Apr 16, 2020 at 10:36, Tuomas Airaksinen  
wrote:

> I would like to get it forward, yes. Though I'm putting full efforts on And 
> Bible releases these days (and there's a lot of work),
> so if someone else does it I'm very grateful. But as I have been starting to 
> use it, and am suffering from quality problems,
> yes, I might be willing to contribute.  Is there OSIS source of existing 
> module? Is tsk-cli having the same source as our module?
>
> On Thu, Apr 16, 2020 at 11:55 AM David Haslam  wrote:
>
>> Sure - there are lots of things we could do better in 2020 than we could in 
>> 2008.
>>
>> What might be the most accurate and full featured PD online source ?
>>
>> There’s a database in this repo.
>>
>> Treasury of Scripture Knowledge Command Line Interface
>> https://github.com/narthur/tsk-cli
>>
>> GitHub came after 2008 so it’s not what was used for our TSK module.
>> It might even be the other way round.
>>
>> Might you be the willing volunteer ?
>>
>> Best regards
>>
>> David
>>
>> Sent from ProtonMail Mobile
>>
>> On Thu, Apr 16, 2020 at 09:27, Tuomas Airaksinen 
>>  wrote:
>>
>>> Hi,
>>>
>>> I would like to check if it would be possible to improve quality of popular 
>>> TSK module (which is public domain). Where are the sources?
>>>
>>> --
>>>
>>> Best regards,
>>> Tuomas
>>
>> ___
>> 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
>
> --
>
> T: Tuomas___
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

Re: [sword-devel] TSK sources?

2020-04-16 Thread John Dudeck


I have an OSIS file of the French version of the TSK that we translated. The OSIS was generated by script from the Logos XML 
version that we created by script from the Online Bible version that we originally did by hand in 2005 or so. Unfurtunately the 
translation is copyrighted and not in the Public Domain. I haven't checked with our director, but I'm pretty sure we don't want to put 
it in the Public Domain.


I can give an excerpt of the OSIS to show how we did it. Somebody who is in the mood could massage the PD English version.


John






Sure - there are lots of things we could do better in 2020 than we could in 2008. 


What might be the most accurate and full featured PD online source ?


There’s a database in this repo. 


Treasury of Scripture Knowledge Command Line Interface

https://github.com/narthur/tsk-cli


GitHub came after 2008 so it’s not what was used for our TSK module. 
It might even be the other way round. 


Might you be the willing volunteer ?


Best regards


David


Sent from ProtonMail Mobile





On Thu, Apr 16, 2020 at 09:27, Tuomas Airaksinen <
tuomas.airaksi...@gmail.com
> wrote:

Hi, 




I would like to check if it would be possible to improve quality of popular TSK module (which is public domain). Where are the 
sources? 




--

Best regards,

Tuomas


John Dudeck
Programmer at Editions Cle Lyon, France
john.dud...@sim.org    j...@editionscle.com
--
"The best time to be alive is when things look the worst." -- Dale Losch
  


___
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

[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  tags alone, as delivered by the Sword engine,
rather than having to obliterate them in a post-delivery hack. To this
end, using suggestions from Nathan Phillip Brink at the time, I've made
this change to the opening stanza of Xiphos' main display widget:

#define HTML_START \
-   " \
+   " \
+ \
+http://www.w3.org/1999/xhtml\";> \
+ \

Notable:
- begins with  line
- includes DOCTYPE (either html or xhtml) (also tried leaving this off
entirely, no diff)
- adds namespace to 
- changes content type to application/xhtml+xml (also tried just xhtml,
no diff)

Result so far is an all around no-joy. I am evidently still getting
WebKit behavior in HTML mode because the self-closing  leads to my
.introMaterial format/color change bleeding through to the end of the
chapter, as most clearly seen in the (technically defunct, but I still
have & use it) ESV2011 module, in every book's 1:1. If I leave the
post-delivery hack in place, the self-closing  is eliminated
entirely, and the .introMaterial section is properly highlighted.

Can anyone offer any further suggestions on how to induce the right sort
of behavior?
___
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

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 the first place. The specific goal is to leave self-closing 
> tags alone, as delivered by the Sword engine, rather than having to
> obliterate them in a post-delivery hack. To this end, using suggestions
> from Nathan Phillip Brink at the time, I've made this change to the opening
> stanza of Xiphos' main display widget:
>
> #define HTML_START \
> -   " content=\"text/html; charset=utf-8\"> \
> +   " \
> + \
>

This line is wrong.  will give you HTML 5, not XHTML. XHTML
would be much wordier:
https://en.wikipedia.org/wiki/Document_type_declaration#XHTML_Basic_DTDs

+http://www.w3.org/1999/xhtml\";
> > \
> + charset=utf-8\"> \
>
> Notable:
> - begins with  line
>

Doesn't seem to be strictly needed by browsers for XHTML rendering, but it
shouldn't hurt, either.

- includes DOCTYPE (either html or xhtml) (also tried leaving this off
> entirely, no diff)
>

You will almost certainly need this to put the browser into XHTML mode

- adds namespace to 
>

That will be needed, for sure.

- changes content type to application/xhtml+xml (also tried just xhtml, no
> diff)
>

That's not necessary to get you into XHTML mode.


> Result so far is an all around no-joy. I am evidently still getting WebKit
> behavior in HTML mode because the self-closing  leads to my
> .introMaterial format/color change bleeding through to the end of the
> chapter, as most clearly seen in the (technically defunct, but I still have
> & use it) ESV2011 module, in every book's 1:1. If I leave the post-delivery
> hack in place, the self-closing  is eliminated entirely, and the
> .introMaterial section is properly highlighted.
>

So here's a thing I've learned:
The moment a browser finds anything that violates the XHTML standards it
will dump you back into HTML 4.01 mode. That seems to be what you're
getting, because  is valid in XHTML but not in HTML 4.01. Secondly,
all browsers ignore the doctype declaration at the top of a file. At least
all modern browsers do. They only thing they care about is the
Content-Type: in the HTTP header. Of course, you don't have an HTTP header,
but surely you have a way to set it to "application/xhtml+xml"?

Relevant:
https://stackoverflow.com/questions/97522/what-are-all-the-valid-self-closing-elements-in-xhtml-as-implemented-by-the-maj

--Greg

>
> Can anyone offer any further suggestions on how to induce the right sort
> of behavior?
> ___
> 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
___
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