Re: [sword-devel] HTML5 File API and SWORD modules

On 08/05/13 15:30, Troy A. Griffitts wrote: Not sure what you mean by "the web", but there are very few client-side-only (only client-side javascript+html/css) applications on "the web" (none that I can think of, but I've been told they exist). a) I have Geeksphone Peak as my main (and now only

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

Ok, I'm gonna top post and reply to various bits, sorry :) Is there any information that we need to keep in those divs that means we need to include either them or a placeholder for them? I just read that anchor tags don't exist in XHTML like they did in HTML 4.01, but you can have tags with

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

On Wed, 2013-05-08 at 15:15 -0500, Greg Hellings wrote: > Off the cuff here, it seems the issue is the difference in semantics > of between OSIS - where it marks a structural division within a > text which can be of many different levels and layers and in XHTML > where it represents a box of bloc

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

Hi Greg, thanks for the ideas. Have a look at this thread: http://www.crosswire.org/pipermail/sword-devel/2005-April/022109.html But let's please keep this thread pragmatic to solving the problem holding up this release :) Any suggestions for WHAT the output should be? I wasn't thinking of

Re: [sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

Off the cuff here, it seems the issue is the difference in semantics of between OSIS - where it marks a structural division within a text which can be of many different levels and layers and in XHTML where it represents a box of block-style layout which defaults to being the full width of its cont

[sword-devel] XHTML Rendering of OSIS Reference Doc - Whitespace

OK guys, I'm starting work on this. I've setup a test in our testsuite for whitespace against our OSIS reference doc. Here are the links: test: http://crosswire.org/svn/sword/trunk/tests/osistest.cpp (whitespace test added at the end) OSIS Reference Document: http://crosswire.org/svn/sword/tr

Re: [sword-devel] HTML5 File API and SWORD modules

On Wed, May 8, 2013 at 9:45 AM, Stephan wrote: > Greg, > > > A client-side Sword application could do something similar. I had begun >> work on such an app at one point. However, in order to fetch data, a >> native client-side JavaScript implementation would be much better off >> leveraging the

Re: [sword-devel] HTML5 File API and SWORD modules

Greg, A client-side Sword application could do something similar. I had begun work on such an app at one point. However, in order to fetch data, a native client-side JavaScript implementation would be much better off leveraging the existing technologies - like localStorage and IndexedDB - for lo

Re: [sword-devel] HTML5 File API and SWORD modules

On Wed, May 8, 2013 at 9:37 AM, Stephan wrote: > Troy, > > > Now, having said this, I use javascript+html/css all the time and would >> like a more native approach to building SWORD applications in this >> environment, hence a javascript interface via Cordova. >> > > That means you want to write

Re: [sword-devel] HTML5 File API and SWORD modules

Troy, Now, having said this, I use javascript+html/css all the time and would like a more native approach to building SWORD applications in this environment, hence a javascript interface via Cordova. That means you want to write native plugins (sword api wrappers) for every supported plattfor

Re: [sword-devel] HTML5 File API and SWORD modules

On Wed, May 8, 2013 at 8:30 AM, Troy A. Griffitts wrote: > Stephan, > > Firefox OS is the only platform I know that doesn't allow 'native' > binaries to be installed and many other platforms all started with this > same concept and conceded shortly before or after release. I am confident > it wil

Re: [sword-devel] HTML5 File API and SWORD modules

Stephan, Firefox OS is the only platform I know that doesn't allow 'native' binaries to be installed and many other platforms all started with this same concept and conceded shortly before or after release. I am confident it will change or FirefoxOS will be irrelevant (not necessarily relate

Re: [sword-devel] usfm2osis.py

To clarify one item of terminology. *Python* is the name of the programming language. *CPython* is the default byte-code interpreter of Python, which is written in C. CPython is Guido van Rossum's reference version of the Python computing language. It's most often called simply "Python"; speake

Re: [sword-devel] usfm2osis.py

OK - thanks Chris. If I do some edits, feel free to improve or correct any details I get slightly wrong. Best regards, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/usfm2osis-py-tp4652232p4652254.html Sent from the SWORD Dev mailing list archive at Nabble.com.

Re: [sword-devel] usfm2osis.py

On 05/08/2013 12:01 AM, Chris Burrell wrote: I think we should also add hailo to the page. .. We don't, as a rule, link to a lot of non-CrossWire/non-Sword software. Haiola in particular is currently not sufficiently mature to warrant linking to as a solution for USFM to OSIS conversion. It t

Re: [sword-devel] usfm2osis.py

On 05/07/2013 11:45 PM, David Haslam wrote: Hi Chris, Should we edit the wiki page to indicate that usfm2osis.py is released and is now the preferred conversion tool? Sure, feel free. And should we also

Re: [sword-devel] usfm2osis.py

Chris B, Spelling: It's called Haiola . "Haiola is derived from the Hawaiian phrase “ha’i ola”, which means “preach salvation”. " David -- View this message in context: http://sword-dev.350566.n4.nabble.com/usfm2osis-py-tp4652232p4652251.html Sent from the SWORD Dev m

Re: [sword-devel] usfm2osis.py

I think we should also add hailo to the page. .. On 8 May 2013 07:46, "David Haslam" wrote: > Hi Chris, > > Should we edit the wiki page > < > http://crosswire.org/wiki/Converting_SFM_Bibles_to_OSIS#Converting_USFM_files_to_OSIS > > > to indicate that usfm2osis.py is released and is now the pref