Difference between revisions of "Talk:Module Development Collaboration"
From CrossWire Bible Society
David Haslam (talk | contribs) (Go Bible tools) |
David Haslam (talk | contribs) (→Go Bible tools: :As regards nomenclature, to avoid confusion, I try to avoid the word "module" for Go Bible applications. It's preferable to reserve the word for SWORD modules. ~~~~) |
||
| Line 2: | Line 2: | ||
Wrt "ThML for import to Go Bible?", I generally use a TextPipe filter for this purpose. Yet please remember that Go Bible Creator can process USFM files directly as one of the input formats, so ThML is not always required. [[User:David Haslam|David Haslam]] 03:34, 25 June 2012 (MDT) | Wrt "ThML for import to Go Bible?", I generally use a TextPipe filter for this purpose. Yet please remember that Go Bible Creator can process USFM files directly as one of the input formats, so ThML is not always required. [[User:David Haslam|David Haslam]] 03:34, 25 June 2012 (MDT) | ||
| + | |||
| + | :As regards nomenclature, to avoid confusion, I try to avoid the word "module" for Go Bible applications. It's preferable to reserve the word for SWORD modules. [[User:David Haslam|David Haslam]] 03:36, 25 June 2012 (MDT) | ||
Revision as of 09:36, 25 June 2012
Go Bible tools
Wrt "ThML for import to Go Bible?", I generally use a TextPipe filter for this purpose. Yet please remember that Go Bible Creator can process USFM files directly as one of the input formats, so ThML is not always required. David Haslam 03:34, 25 June 2012 (MDT)
- As regards nomenclature, to avoid confusion, I try to avoid the word "module" for Go Bible applications. It's preferable to reserve the word for SWORD modules. David Haslam 03:36, 25 June 2012 (MDT)
