On 04/03/12 09:20, David Haslam wrote:
> I have added a brief description of haiola to
> http://crosswire.org/wiki/File_Formats#USFX
I have deleted it. There is no need to link to programmes which do
nothing of relevance to any format we are ever likely to encounter.
The page is meant to assist m
On 4.3.2012 03:09, Kahunapule Michael Johnson wrote:
I'm really not trying to sell anything. I make no money on file
formats, and it really doesn't affect me one way or the other if you
use it or not. I'm just trying to share good advice based on my
experience. Take it or leave it.
I am sorry,
On 4.3.2012 02:37, Karl Kleinpaste wrote:
[*] After I wrote that paragraph, it occurred to me: I wonder how many
people today are not even _aware_ that there was a battle over some
years, over what kind of worldwide internetworking should be put to use?
And how many people even in the computer
Thanks Michael,
I have added a brief description of haiola to
http://crosswire.org/wiki/File_Formats#USFX
David
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-Users-Manual-considered-confusing-tp4441335p4443190.html
Sent from the SWORD Dev mailing list archive at Na
On 03/03/2012 02:55 PM, Matěj Cepl wrote:
>
>> Wrt USFX - this is simply a XML-fied form of USFM and adds very little
>> to the discussion. It is essentially a structureless mess, replacing
>> each USFM tag with a XML set of tags. If I did not have OSIS, I would go
>> ThML, but certainly never USFX
On 04/03/12 00:55, Matěj Cepl wrote:
> OK, if I could consider wiki to be the standard, good enough for me. If
> it is wiki and we can improve it, even better.
It is a wiki and it needs improvement. Basically it gets
updated/expanded when there is something tp update/expand, i.e. a real
world curr
DM Smith writes:
> I'm not sure you're wanting a reply or just wanting to rip on OSIS as
> a "standard."
Not at all. Consider: I have a long history in IP communications, whose
RFCs are The Definition Of Interoperability. The idea of ambiguity in
such a field is virtually anathema. In the long
On 4.3.2012 00:40, Peter von Kaehne wrote:
The wiki is indeed the place to look if you want to see how to create an
OSIS text which works well with our software. As one of the main module
makers, I do use the manual, but not often. The Wiki will take
precedence over the handbook any time. For us
On 03/03/12 21:04, Kahunapule Michael Johnson wrote:
>> Should I switch from OSIS to USFX?
>
> I would, if I were doing what you are doing.
If you want your text be used on CrossWire, the answer is simply no.
If you want to edit the text for further translation improvements, get
it into USFM a
On 03/03/12 16:47, Matěj Cepl wrote:
> OK, so duly noted ... there isn't widely held agreement even on this
> list on this (see e.g., I found in the list couple of clear statements
> in the opposite direction ... although, thinking about it, I don't see
> anything more natural on paragraphs which
The wiki is indeed the place to look if you want to see how to create an
OSIS text which works well with our software. As one of the main module
makers, I do use the manual, but not often. The Wiki will take
precedence over the handbook any time. For us at least.
It is fairly irrelevant if there a
On 03/03/2012 09:55 AM, Matěj Cepl wrote:
> On 3.3.2012 20:38, Kahunapule Michael Johnson wrote:
>> Bible formatting that were not shared by my good friends, the Bible
>> translators. That means that either the Bible formatting has to
>
> Tell me about. What I am doing is converting from the docume
On 3.3.2012 19:45, DM Smith wrote:
Do you have a suggestion on what the proper semantic should be? Or
whether the OSIS schema should change to provide an unambiguous
semantic?
My point was that mostly anything goes (well, before element it
belongs to seems like a dumb idea from the parsing po
On 3.3.2012 20:38, Kahunapule Michael Johnson wrote:
Bible formatting that were not shared by my good friends, the Bible
translators. That means that either the Bible formatting has to
Tell me about. What I am doing is converting from the document actually
created as a product of translation,
On 03/03/2012 06:47 AM, Matěj Cepl wrote:
>> Nearly half the OSIS editor body is subscribed to this list, so please,
>> if you have an honest question about the standard, humbly ask and know
>> that there might be an answer you hadn't considered.
>
> I am not sure why I should be humble, when notic
On Mar 3, 2012, at 12:30 PM, Karl Kleinpaste wrote:
> DM Smith writes:
>> There is ambiguity about a title that is before the first verse in a chapter.
>
>> Titles for sections should be within a section div. This solves the
>> ambiguity problem for titles before the first verse.
>
> Shouldn't
DM Smith writes:
> There is ambiguity about a title that is before the first verse in a chapter.
> Titles for sections should be within a section div. This solves the
> ambiguity problem for titles before the first verse.
Shouldn't The Standard have eliminated the ambiguity in the first place,
r
On Mar 3, 2012, at 11:52 AM, Matěj Cepl wrote:
> On 3.3.2012 17:47, Matěj Cepl wrote:
>> OK, so duly noted ... there isn't widely held agreement even on this
>> list on this (see e.g., I found in the list couple of clear statements
>> in the opposite direction ... although, thinking about it, I d
On Mar 3, 2012, at 11:47 AM, Matěj Cepl wrote:
> On 3.3.2012 15:18, Troy A. Griffitts wrote:
>> So, what was your question? :)
>
> There are many, but the one specific to my original post (and yes, one should
> never write email messages in anger) is simple: how should I code chapter
> with it
On 3.3.2012 17:47, Matěj Cepl wrote:
OK, so duly noted ... there isn't widely held agreement even on this
list on this (see e.g., I found in the list couple of clear statements
in the opposite direction ... although, thinking about it, I don't see
anything more natural on paragraphs which are arb
On 3.3.2012 15:18, Troy A. Griffitts wrote:
So, what was your question? :)
There are many, but the one specific to my original post (and yes, one
should never write email messages in anger) is simple: how should I code
chapter with its title?
What I mean, is that I really didn't meant to pe
Corrigendum (space was missing).
The simple ThML needed to successfully make a Go Bible is documented in
http://gobible.jolon.org/developer/ThML/ThML.html
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-Users-Manual-considered-confusing-tp4441335p4441591.html
Sent fr
Just some brief comments about OSIS and Go Bible.
The fact that Go Bible Creator supports only the container version of
chapters & verses (not the milestone version) is historic.
That's how we inherited the project since Jolon Faichney first created and
developed the Go Bible software.
Go Bible i
Hey Matěj,
So, what was your question? :)
Any one of us could have technically designed the OSIS standard better.
Lack of technical expertise did not cause the issues you cite.
Nearly half the OSIS editor body is subscribed to this list, so please,
if you have an honest question about the sta
So, I have at least a little bit working version of CzeCSP and I would
like to eliminate some kinks. One of them is using milestones v.
containers in the text.
So I have a friend who has just Nokia phone with Symbian 60 OS. By
browsing through crosswire.org/wiki I found Go Bible as probably the
o
25 matches
Mail list logo
