Re: [sword-devel] transChange element
On 12/8/23 8:27 AM, Tobias Klein wrote: On 12/7/23 10:34 AM, pinoaffe wrote: I was wondering what are the different types? I did not find an exhaustive list. There's a list on page 122 of the OSIS 2.1.1 User Manual, see below: - *added*: Words added. - *amplified*: More than addition of words to smooth out a translation. - *changed*: Words are changed in the translation, such as modern spellings. - *deleted*: Words that appear in the original but not in the translation. - *moved*: Words that are moved to better represent the meaning of the text being translated from their original order. - *tenseChange*: Indicates a change of the tense from the original to one that occurs in the translation language. also, creators of OSIS documents can of course introduce their own types prefixed with "x-" such as "x-spellingCorrection" or anything else. So there is another element mentioned in the list on page 85 of the OSIS User Manual. The element is /implied/ - what's the meaning of that? The explanation for that element is missing. Best regards, Tobias ___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] transChange element
On 12/7/23 10:34 AM, pinoaffe wrote: I was wondering what are the different types? I did not find an exhaustive list. There's a list on page 122 of the OSIS 2.1.1 User Manual, see below: - *added*: Words added. - *amplified*: More than addition of words to smooth out a translation. - *changed*: Words are changed in the translation, such as modern spellings. - *deleted*: Words that appear in the original but not in the translation. - *moved*: Words that are moved to better represent the meaning of the text being translated from their original order. - *tenseChange*: Indicates a change of the tense from the original to one that occurs in the translation language. also, creators of OSIS documents can of course introduce their own types prefixed with "x-" such as "x-spellingCorrection" or anything else. Thank you! That's very helpful :) Best regards, Tobias ___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Module release: BSB
Thank you for the kind words! My hope is that the BSB module would be useful enough and complete enough to be recommended by SWORD apps, or even (due to its liberal licensing) installed by default. Xiphos should know what Strongs number is associated with each lemma (it draws them in the right place, after all), so in theory it should be possible for clicking on the lemma to look up the associated Strongs number with no change to the module. I'm rather fond of AndBible's approach where clicking a word looks up all the associated metadata (lemmas, Strongs numbers, grammar codes, etc.) in all available dictionaries, since the odds of a Strongs number being a valid grammar code or a grammar code being a valid lemma are extremely low - but that would probably be a bigger change. There's one other piece of data included in the translation table spreadsheet that isn't yet included in the BSB module - grammar codes. The BSB is marked up with somewhat proprietary codes for Hebrew and Greek, while the SWORD Project ecosystem seems to have settled on Open Scriptures Hebrew Bible codes for Hebrew, and Robinson codes for Greek. Since both kinds of Hebrew codes model the same rules of Hebrew grammar, and both kinds of Greek codes model the same rules of Greek grammar, it should be possible to translate between them, it's just a lot of work and although I've had some ideas about how to help automate the process, I've been distracted by other things. The other thing that occurred to me is the possibility of creating a more straightforward interlinear Bible, with the source text as the base and the English as the "gloss". That would allow the source text to be presented in its natural order (instead of following the order of English grammar), but it would *also* be a lot of work and I'm not sure if it would actually be very useful. Timothy. On 8/12/23 08:25, Karl Kleinpaste wrote: On 12/4/23 03:27, dom...@crosswire.org wrote: This is to announce that we have just now uploaded BSB I wanted to mention that the updated BSB has become effectively also BIB, the Berean Interlinear Bible, when viewed in Xiphos with lemmas enabled, where stacked display provides the interlinear view. Screenshot of 1Tim.3 with lemmas enabled: http://karl.kleinpaste.org/.../bsb-interlinear.png The only downside is that lemmas don't link to numeric Strong's entries. But you can enable Strong's as well to get that. Several years ago, I had done initial work to create "draft" Berean Bible modules (BSBdraft, BIBdraft) -- "draft" because the *.xlsx weren't finalized at the time -- but this BSB is much superior, a fine end product. ___ sword-devel mailing list:sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Module release: BSB
On 12/4/23 03:27, dom...@crosswire.org wrote: This is to announce that we have just now uploaded BSB I wanted to mention that the updated BSB has become effectively also BIB, the Berean Interlinear Bible, when viewed in Xiphos with lemmas enabled, where stacked display provides the interlinear view. Screenshot of 1Tim.3 with lemmas enabled: http://karl.kleinpaste.org/.../bsb-interlinear.png The only downside is that lemmas don't link to numeric Strong's entries. But you can enable Strong's as well to get that. Several years ago, I had done initial work to create "draft" Berean Bible modules (BSBdraft, BIBdraft) -- "draft" because the *.xlsx weren't finalized at the time -- but this BSB is much superior, a fine end product.___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] transChange element
Hi, Tobias Klein writes: > I am planning to turn the meta data of the transChange element into > user-readable information (see ezra-bible-app #972). Cool! > I was wondering what are the different types? I did not find an > exhaustive list. There's a list on page 122 of the OSIS 2.1.1 User Manual, see below: - *added*: Words added. - *amplified*: More than addition of words to smooth out a translation. - *changed*: Words are changed in the translation, such as modern spellings. - *deleted*: Words that appear in the original but not in the translation. - *moved*: Words that are moved to better represent the meaning of the text being translated from their original order. - *tenseChange*: Indicates a change of the tense from the original to one that occurs in the translation language. also, creators of OSIS documents can of course introduce their own types prefixed with "x-" such as "x-spellingCorrection" or anything else. > These are the types I discovered: > > - added > - deleted > - tenseChange > > Are there any others? Yup :) Kind regards, pinoaffe ___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
