The ESV uses . Osis2mod converts thes to as
milestoned. This is one of the transformations I mentioned.
the x-preverse is also from Osis2mod.
See the wiki for a complete set of transformations that osis2mod does.
The OSIS 2.1.1 is the latest manual. We maintain in the wiki a set of bug
reports
I think the ESV2011 was created by Tyndale. The Strong’s numbers and morphology
came from the KJV.
> On Dec 30, 2017, at 4:32 PM, Tom Sullivan wrote:
>
> DM, Peter:
>
> Thank you very much. The ESV2011 and KJV use different features and are
> looking to be quite helpful together.
>
> Tom Sul
Yes.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
Great News!
God created you, owns you and gave you commands to obey.
You have disobeyed God - as your conscience very well attests to you.
God's holiness and justice compel Him to punish you in Hell.
Jesus Christ becam
Tom,
Have you visited our wiki yet?
https://crosswire.org/wiki
David
Sent from ProtonMail Mobile
On Sat, Dec 30, 2017 at 22:24, Tom Sullivan wrote:
> Y'all: Now that I am able to examine, briefly so far, some "production" OSIS,
> both incompleteness and discrepancies in the OSIS documentati
Y'all:
Now that I am able to examine, briefly so far, some "production" OSIS,
both incompleteness and discrepancies in the OSIS documentation are very
apparent. I do have the OSIS 2.1.1 manual. Am I missing some documentation?
Examples:
OSIS manual: div and p are not listed as milestonable. ES
DM, Peter:
Thank you very much. The ESV2011 and KJV use different features and are
looking to be quite helpful together.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
Great News!
God created you, owns you and gave you commands to obey.
You have disobeyed God - as yo
We publish the OSIS text of the KJV . It pretty much reflects best standards and has a huge number of features encoded, so can serve probably well as a working examplePeterSent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [swo
It’s there, but hidden. Find desktop.properties (location varies by OS) and set
it in there.
Advanced.ViewSource=true
> On Dec 30, 2017, at 3:56 PM, Tom Sullivan wrote:
>
> Michael:
>
> Thank you. That option is missing from 1.6 and 2.0Beta.
>
> Tom Sullivan
> i...@beforgiven.info
> FAX: 8
Michael:
Thank you. That option is missing from 1.6 and 2.0Beta.
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
Great News!
God created you, owns you and gave you commands to obey.
You have disobeyed God - as your conscience very well attests to you.
God's holiness and
There is a version of BibleDesktop that allows you to 'view source' and see
the osis of each verse or chapter from inside the front-end. it's an older
version, so you might run into issues with newer versifications, but if
using a longstanding versification it's very helpful if you're
troubleshoot
Thank you for the replies. I got an output using -r OSIS, but it does
not look good or useful.
My goal was to look at the OSIS used, for example, for ESV2011 to
improve my understanding of the use of OSIS. Is there any access to that
original OSIS?
Regarding indexes for Hebrew words - is thi
To pick up on one possible misunderstanding by Tom,
Analysis tools such as mod2imp and diatheke take the module name as the main
command line argument.
Not the filename of the .bzz files in the .
i.e. Your command should be given in the context of the sword path as the
current directory.
Best
Dear Tom,
Round trip back conversion is seriously disparaged.
For modules having few OSIS features, being mostly plain text content, mod2imp
followed by imp2vs may get you a module that should be the same as you started
with.
There's no guarantee.
However, the moment you have a module with any
Not really. The osis2mod process is lossy (no verse markers) and transformative
(it is in milestoned form). For that reason, we really don’t recommend it.
Also, many OSIS modules are built from non-OSIS source.
mod2imp expects the module to be installed. Beyond that I’m not sure.
mod2osis shoul
Starting a new thread to pick up the question that DM asked almost as an aside.
How should SWORD index (Hebrew) words containing morpheme segments?
By word or by segment ?
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.__
Y'all:
Is there a way to convert a module in .bzz format back to OSIS.
I tried mod2imp, but the help message does not say how to input a
module. The name of the module fails, as do .bzz files.
Thanks.
--
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
Great News!
God
There is a reason the French texts have not been released yet and that is the current absence of front-end support for 1'8. It will happen . Sent from my mobile. Please forgive shortness, typos and weird autocorrects. Original Message Subject: Re: [sword-devel] Win32 sword utilities
In a separate thread, DM wondered whether
[Docker](https://en.wikipedia.org/wiki/Docker_(software)) might be a way
forward.
I know virtually nothing about it, save what I can read quickly.
Let's hear from developers the pros and cons in the context of what we do in
CrossWire.
Best regards,
D
Thanks Troy,
When the Sword utilities supplied with the Windows edition of Xiphos are more
recent than those provided ad hoc by Greg, then I'd generally use those.
I've already mentioned why I had hoped to obtain a new set, which was to test
out the use of the diatheke -o M command line option.
Hi Tom,
I'm sure that most of us are aware that the MAQAF (U+05BE) has a different
function to morpheme segmentation.
The Unicode character name is HEBREW PUNCTUATION MAQAF.
The openscriptures morphhb team have marked these up accordingly:
42577
The differences in spelling are quite common am
Hi DM,
Oh - indeed - I wholly agree.
The OpenScriptures morphhb team has used the solidus in a manner that goes
against the whole philosophy of OSIS.
It's our job to help steer them back to the right track, as we probably have
more expertise in OSIS than most other organisations put together.
As a general rule, CrossWire develops software. We don't primarily compile that
software and distribute binaries.
My intention is for the software we develop to run on as many platforms as
possible. We have a ton of effort in the cross-platform engine (which does a
large part of the work for ea
Hi Troy,
There are at least two separate reasons why the WLC module is "defective".
They are unrelated to this thread. My use of the adjective was an "aside".
Both issues were reported ages ago in the CrossWire tracker for MOD.
Neither issue has been addressed. Just about par for the course.
i.e
Y'all:
Sometimes, one will see something like:
עַל־פְּנֵי
That upper "hyphen," like the vowel points, is a human interpretation
that does not appear in any MSS. But it is a standard. Unfortunately, it
should not be used to delineate "segments" which, I gather from the
context of the discussion
Agreed. Because a frontend doesn't do something with the entry attributes
created by the filter, or that a chosen render filter doesn't do anything with
the morpheme seg, certainly doesn't mean the WLC module is defective. Frontends
are not always the target of the engine. Research can be done
Dear all,
I wish to propose a new SWORD filter.
The idea is to provide a very simple mechanism in SWORD to hide or display
specified markers.
Example use:
The OSIS files hosted by
[openscripture/morphhb](https://github.com/openscriptures/morphhb) could be
converted to replace each solidus in
I wish you had started with this. I find it more satisfying to know what the
end goal is. I had thought you merely wanted to update the wiki.
I’m wondering how a “morphological segment” should be rendered to an end user.
I presume that it is of value to a student of Hebrew. Is it merely highligh
JSword does it’s own thing. The filter architecture is entirely different from
SWORD’s. It converts Plain, GBF, ThML, TEI, … into OSIS. Then the toggles are
passed to XSLT as parameters. The XSLT converts OSIS to HTML and it does the
toggling.
STEP’s XSLT was based on BibleDesktop’s. As a fork
Just glanced at the render filters for OSIS. They don't look for the it at all.
> On Dec 30, 2017, at 10:02 AM, Karl Kleinpaste wrote:
>
> On 12/30/2017 08:31 AM, DM Smith wrote:
>> The module matches what the filter expects.
>> The filter does something.
>> Third possibility: front end doesn’t
Thanks for the detailed report, Karl.
It's just as I feared.
It also indicates that STEP Bible must do its own thing for such modules.
It displays alternate segments in a different colour.
Best regards, David
Sent from ProtonMail Mobile
On Sat, Dec 30, 2017 at 15:02, Karl Kleinpaste wrote:
On 12/30/2017 08:31 AM, DM Smith wrote:
> The module matches what the filter expects.
> The filter does something.
> Third possibility: front end doesn’t handle the attribute.
I just spent an hour stepping through Xiphos' handling of WLC Gen.1.1
with and without Morpheme Segmentation set.
First,
I’m wondering if using Docker would be a good solution.
— DM Smith
From my phone. Brief. Weird autocorrections.
> On Dec 30, 2017, at 4:05 AM, David Haslam wrote:
>
> Thanks everyone for disparaging those of us using Windows. ;>}
>
> I've been building modules for years with the Win32 tools
The module matches what the filter expects.
The filter does something.
Third possibility: front end doesn’t handle the attribute.
— DM Smith
> On Dec 30, 2017, at 3:54 AM, David Haslam wrote:
>
> My concern is that we have a listed filter that either seems to do nothing
> or that the module[
"But not guaranteed so."
Well nothing produced by CrossWire is ever "guaranteed" !
It sometimes comes over very much (however unintended) that those of us who are
not on Linux are in the "second class" carriages. :(
The Sword utilities built for Win32 environment work fine.
Please do not disco
Y'all:
One more point from a hardcore Linux user: Module developers need to
proofread their work. This requires producing a module, then viewing on
a front-end. Let us please recognize that all Sword related projects
from one end to the other strengthen the usefulness of the whole.
I support
There is nothing disparaging in the previous thread, nor is this about module bugs. It is about being able to rely on current tools as and when they become available instead of having to wait for them and it is about tools being built for Linux, though, happily, working in other environments too. B
Thanks everyone for disparaging those of us using Windows. ;>}
I've been building modules for years with the Win32 tools, and barely
encountered any problems attributable to the utility itself.
Nearly all the problems that arise in module development are due to getting
things wrong in the OSIS
Thanks everyone for each "pearl of wisdom".
It wasn't that I didn't understand what Hebrew morpheme segmentation is.
That's pretty evident from examining the content of the modules concerned.
Nor was it that I am unfamiliar with use of the seg element in OSIS XML.
I've been using OSIS for long en
38 matches
Mail list logo
