Difference between revisions of "Talk:Converting SFM Bibles to OSIS"
David Haslam (talk | contribs) (→Paratext export to XML: new section) |
David Haslam (talk | contribs) (→Who May Use Paratext: new section) |
||
| Line 8: | Line 8: | ||
The UBS [http://paratext.ubs-translations.org/Home.html#Home-importexport page] about '''Paratext''' includes this sentence, "Paratext also provides function for exporting text to RTF and XML formats." I have been informed that these XML export formats include OSIS in either the ''milestoned'' form (BSP) or the ''containerized'' form (BCV). Has anyone in CrossWire compared the direct Paratext export XML formats with what we can obtain using either the Snowfall software conversion tool or the CrossWire conversion script? [[User:David Haslam|David Haslam]] 13:07, 5 June 2009 (UTC) | The UBS [http://paratext.ubs-translations.org/Home.html#Home-importexport page] about '''Paratext''' includes this sentence, "Paratext also provides function for exporting text to RTF and XML formats." I have been informed that these XML export formats include OSIS in either the ''milestoned'' form (BSP) or the ''containerized'' form (BCV). Has anyone in CrossWire compared the direct Paratext export XML formats with what we can obtain using either the Snowfall software conversion tool or the CrossWire conversion script? [[User:David Haslam|David Haslam]] 13:07, 5 June 2009 (UTC) | ||
| + | |||
| + | == Who May Use Paratext == | ||
| + | |||
| + | The UBS [http://paratext.ubs-translations.org/Home.html page] also states, | ||
| + | |||
| + | :The Paratext program and its associated text files have been developed by the United Bible Societies for use by its translations project teams. Paratext is also made available for use by other Bible agencies for whom a formal licensing arrangement with UBS has been established. Persons qualified to use Paratext will include translation consultants, translators, reviewers, and those directly engaged in the translation's production. Copyright restrictions, especially those determined by third party copyright holders, require that use and distribution of Paratext be strictly limited to those engaged in Bible translation (as outlined above). | ||
| + | |||
| + | Seeing as CrossWire could be properly classified under "other Bible agencies", has there been any move towards negotiating a formal licensing arrangement for CrossWire members? [[User:David Haslam|David Haslam]] 13:14, 5 June 2009 (UTC) | ||
Revision as of 13:14, 5 June 2009
Paratext USFM stylesheet, version 2.2
There has been an update to the Paratext USFM stylesheet, version 2.2, Updated October 17, 2008. See [1]. This update post-dates the making of Go Bible Creator version 2.3.2 which was the first to provide some support for USFM as source text format. CrossWire programmers who make use of the USFM stylesheet standards will need to take note of the changelog. I have also flagged this to the SWORD Dev mailing list. David Haslam 14:37, 8 December 2008 (UTC)
- I suggest that CrossWire programmers who make reference to external standards make use of the excellent service provided by http://www.changedetection.com/ to be alerted by email when there are changes to websites like this. David Haslam 14:46, 8 December 2008 (UTC)
Paratext export to XML
The UBS page about Paratext includes this sentence, "Paratext also provides function for exporting text to RTF and XML formats." I have been informed that these XML export formats include OSIS in either the milestoned form (BSP) or the containerized form (BCV). Has anyone in CrossWire compared the direct Paratext export XML formats with what we can obtain using either the Snowfall software conversion tool or the CrossWire conversion script? David Haslam 13:07, 5 June 2009 (UTC)
Who May Use Paratext
The UBS page also states,
- The Paratext program and its associated text files have been developed by the United Bible Societies for use by its translations project teams. Paratext is also made available for use by other Bible agencies for whom a formal licensing arrangement with UBS has been established. Persons qualified to use Paratext will include translation consultants, translators, reviewers, and those directly engaged in the translation's production. Copyright restrictions, especially those determined by third party copyright holders, require that use and distribution of Paratext be strictly limited to those engaged in Bible translation (as outlined above).
Seeing as CrossWire could be properly classified under "other Bible agencies", has there been any move towards negotiating a formal licensing arrangement for CrossWire members? David Haslam 13:14, 5 June 2009 (UTC)
