Difference between revisions of "Talk:File Formats"
m (→Go Bible & collaboration with CrossWire: big C, big W) |
David Haslam (talk | contribs) (→Go Bible: new section) |
||
| (42 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Talk:File Formats/Archive]] | |
| − | + | == Biblical texts stored in SQlite database format == | |
| − | + | Should you come across a Biblical text stored in [https://en.wikipedia.org/wiki/SQLite SQlite] database format, then this open source program may prove to be useful. | |
| + | : [http://sqlitebrowser.org/ DB Browser for SQLite] | ||
| + | The source files are hosted on github – there are builds available for Windows, Mac OS X, Linux, Arch Linux, Fedora, Ubuntu and Derivatives, and FreeBSD. You can export a table to CSV format, which could be a stepping stone towards making a SWORD module with other utilities. | ||
| + | :[[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 12:34, 16 December 2016 (MST) | ||
| − | == | + | == Deletion == |
| − | I have | + | I am deleting references to all defunct, foreign or otherwise irrelevant formats and their utilities. I also remove references to undocumented utilities. There are a few within the source tree which possibly need removing, but we are not helping this by keeping references here. |
| + | |||
| + | Further, we do not support GBF anymore other than in legacy modules. We also have seen for years (ie.e since I am part of the project) any suggested imports from STEP. I will generally par this page down to be specific to tools currently in use, encouraged and useful. [[User:Refdoc|refdoc]]:[[User_Talk:Refdoc|talk]] 04:11, 8 January 2018 (MST) | ||
| + | :New sections to a talk page should always be added at the bottom. Sections should be in chronological order. --[[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 04:47, 8 January 2018 (MST) | ||
| + | |||
| + | ::As we still accept '''IMP format''', this section should not have been removed. Please re-instate it. [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 16:25, 11 March 2018 (UTC) | ||
| + | :::Found it and added a link to the new page under '''See also'''. [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) | ||
| + | |||
| + | == Go Bible == | ||
| + | |||
| + | I am removing this section from the main page. It has some broken links. Go Bible is no longer being developed. [[User:David Haslam|David Haslam]] ([[User talk:David Haslam|talk]]) 12:30, 28 April 2018 (UTC) | ||
| + | |||
| + | ===Go Bible=== | ||
| + | Following an agreement made in July 2008 with the program's author Jolon Faichney, [[Projects:Go Bible|Go Bible]] was adopted by CrossWire as its Java ME software project. | ||
| + | |||
| + | To achieve the navigation speed and general ease of use on even the simplest of Java mobile phones, Go Bible data is fully indexed, as well as being compressed (as are all JAR files). The format is described in [http://code.google.com/p/gobible/wiki/GoBibleDataFormat Go Bible data format]. Go Bible data is structured as Book | Chapter | Verse text and does not support notes, headings and cross-references, etc. The developer kit [http://gobible.jolon.org/developer/welcome.html Go Bible Creator] can take either USFM, ThML or OSIS as the source text format, but they usually have to be made specially suitable. For example, OSIS files produced by Snowfall Software's SFMToOSIS script are not structured the same. Work has begun to make an [http://en.wikipedia.org/wiki/XSL_Transformations XSLT] script to convert such OSIS XML files to the format suitable for Go Bible. [[Projects:Go Bible/Go Bible Creator|Go Bible Creator]] version 2.3.2 and onwards can take a folder of USFM files as the source text format. | ||
| + | |||
| + | Go Bible source code is now available [https://crosswire.org/svn/gobible/ here] on the CrossWire Repository. ''To access this you will need to have an account''. | ||
| + | |||
| + | GoBibleDataFormat is being extended in the [[Projects:Go Bible/SymScroll|SymScroll]] branch. | ||
Latest revision as of 12:30, 28 April 2018
Biblical texts stored in SQlite database format
Should you come across a Biblical text stored in SQlite database format, then this open source program may prove to be useful.
The source files are hosted on github – there are builds available for Windows, Mac OS X, Linux, Arch Linux, Fedora, Ubuntu and Derivatives, and FreeBSD. You can export a table to CSV format, which could be a stepping stone towards making a SWORD module with other utilities.
- David Haslam (talk) 12:34, 16 December 2016 (MST)
Deletion
I am deleting references to all defunct, foreign or otherwise irrelevant formats and their utilities. I also remove references to undocumented utilities. There are a few within the source tree which possibly need removing, but we are not helping this by keeping references here.
Further, we do not support GBF anymore other than in legacy modules. We also have seen for years (ie.e since I am part of the project) any suggested imports from STEP. I will generally par this page down to be specific to tools currently in use, encouraged and useful. refdoc:talk 04:11, 8 January 2018 (MST)
- New sections to a talk page should always be added at the bottom. Sections should be in chronological order. --David Haslam (talk) 04:47, 8 January 2018 (MST)
- As we still accept IMP format, this section should not have been removed. Please re-instate it. David Haslam (talk) 16:25, 11 March 2018 (UTC)
- Found it and added a link to the new page under See also. David Haslam (talk)
- As we still accept IMP format, this section should not have been removed. Please re-instate it. David Haslam (talk) 16:25, 11 March 2018 (UTC)
Go Bible
I am removing this section from the main page. It has some broken links. Go Bible is no longer being developed. David Haslam (talk) 12:30, 28 April 2018 (UTC)
Go Bible
Following an agreement made in July 2008 with the program's author Jolon Faichney, Go Bible was adopted by CrossWire as its Java ME software project.
To achieve the navigation speed and general ease of use on even the simplest of Java mobile phones, Go Bible data is fully indexed, as well as being compressed (as are all JAR files). The format is described in Go Bible data format. Go Bible data is structured as Book | Chapter | Verse text and does not support notes, headings and cross-references, etc. The developer kit Go Bible Creator can take either USFM, ThML or OSIS as the source text format, but they usually have to be made specially suitable. For example, OSIS files produced by Snowfall Software's SFMToOSIS script are not structured the same. Work has begun to make an XSLT script to convert such OSIS XML files to the format suitable for Go Bible. Go Bible Creator version 2.3.2 and onwards can take a folder of USFM files as the source text format.
Go Bible source code is now available here on the CrossWire Repository. To access this you will need to have an account.
GoBibleDataFormat is being extended in the SymScroll branch.
