On Jul 23, 2012, at 11:29 PM, Kahunapule Michael Johnson
wrote:
On 07/23/2012 06:26 PM, Chris Little wrote:
is bad because it uses a container element to represent a non-container,
and it abuses the semantics of the element for purely typographic purposes.
is bad because it employs a pr
Thanks DM,
Calming it may be to have someone understand me and carefully explain what's
going on "under the hood",
yet I was making an observation about what seemed to be required for any
paragraphed Bible,
even for one that could (in theory at least) be entirely without "section
divisions" and/or
On Jul 24, 2012, at 5:45 AM, David Haslam wrote:
> Quite so!
>
> Ignoring titles and all other preverse content for the purpose of this
> reply, I still find it strange that the only placement of the paragraph
> elements (in relation to verse eID and sID milestones) that works
> empirically with
Quite so!
Ignoring titles and all other preverse content for the purpose of this
reply, I still find it strange that the only placement of the paragraph
elements (in relation to verse eID and sID milestones) that works
empirically without causing widowed verse tags (in at least one front-end)
is a
Sent from my iPhone
Am 24.07.2012 um 09:58 schrieb Nic Carter :
>
>> True, indeed. However, when a problem tempts people to extend, bend, or
>> disregard the standard to get proper results, it might be wise to at least
>> consider if the standard itself has a problem, either in the mechanics
> True, indeed. However, when a problem tempts people to extend, bend, or
> disregard the standard to get proper results, it might be wise to at least
> consider if the standard itself has a problem, either in the mechanics of it
> or in the documentation and usage.
One cannot help but think o
On 07/23/2012 06:26 PM, Chris Little wrote:
> On 07/23/2012 07:35 PM, Kahunapule Michael Johnson wrote:
>>
>>
>> On 07/23/2012 04:06 PM, Chris Little wrote:
>>> On 07/23/2012 07:09 AM, David Haslam wrote: ...
>>>
>>>
He therefore introduced a new OSIS element >>> type="x-p-indent" />
On 07/23/2012 07:35 PM, Kahunapule Michael Johnson wrote:
On 07/23/2012 04:06 PM, Chris Little wrote:
On 07/23/2012 07:09 AM, David Haslam wrote: ...
He therefore introduced a new OSIS element
It's used to provide a poetry indentation as an alternative to
using line elements with level at
On 07/23/2012 04:06 PM, Chris Little wrote:
> On 07/23/2012 07:09 AM, David Haslam wrote:
> ...
>
>
>> He therefore introduced a new OSIS element
>>
>> It's used to provide a poetry indentation as an alternative to using line
>> elements with level attributes.
>> Currently, deeper indents are
On 07/23/2012 07:09 AM, David Haslam wrote:
To chip in with one additional observation, to add to DM's list of bullet
points
Our esteemed friend who developed *xulsword* abandoned the use of line group
and line elements for poetry.
He came to the conclusion that where chunks of poetry start
On 07/23/2012 01:12 PM, Peter von Kaehne wrote:
Von: DM Smith
Mark titles with x-preverse.
DM, this is exactly what we do at the moment - see
svn/sword-tools/modules/misc_cleanup/titles_cleanup.pl (or some such path,
sorry not at home) Not terribly successful, as it causes all kinds of problem
> Von: DM Smith
> Mark titles with x-preverse.
DM, this is exactly what we do at the moment - see
svn/sword-tools/modules/misc_cleanup/titles_cleanup.pl (or some such path,
sorry not at home) Not terribly successful, as it causes all kinds of problems
with titles which are not preverse, but n
On Jul 23, 2012, at 6:46 AM, Matěj Cepl wrote:
> On 23/07/12 08:57, Peter von Kaehne wrote:
>> Put simply, as a module maker I would prefer if osis2mod would simply
>> stop interfering.
>>
>> Osis2mod should identify chunks of text and put them into the right
>> places and then be done - as litt
As a front-end developer I don't like the special code either. I found that the
problem comes because once a module is in the wild, within reason we need to
support it.
One example the NET module has bugs in it. The original OSIS is not well-formed
xml. However, it is out there and the authors
Let me clear up some misconceptions:
Osis2mod does not re-order anything.
It retains nearly everything. Always, in the original order.
osis2mod's transformations are few, well-defined and documented:
http://www.crosswire.org/wiki/Osis2mod#Transformations
Using a revision prior to 2358 and what yo
Yep!
The USFM files for the New Turkish Bible contained at least one mid-verse
title.
Without looking this up, I vaguely recall that it was a single instance
somewhere in Acts.
Our module TurNTB is an example where our in-house module making process did
let us down.
In saying this, I'm repeating
Peter's considered response has real merit. I echo those sentiments.
Our module making process is over-complicated, ill-defined and prone to
making some things unattainable.
e.g. Even when titles and other preverse material gets placed correctly, we
often see widowed verse tags.
To chip in with o
On 23/07/12 08:57, Peter von Kaehne wrote:
Put simply, as a module maker I would prefer if osis2mod would simply
stop interfering.
Osis2mod should identify chunks of text and put them into the right
places and then be done - as little transformation as possible.
Amen. Preach it, brother!
Matě
Replying with my Front-End developer hat on:
On 23/07/2012, at 4:57 PM, Peter von Kaehne wrote:
> So, my proposal - cut osis2mod into half. Let one part handle reordering
> but then spit the result out as a new osis file. Which can be tested,
> which can be worked upon.
>
> And let the other
Thanks DM,
Forgive for top posting.
Put simply, as a module maker I would prefer if osis2mod would simply
stop interfering.
Osis2mod should identify chunks of text and put them into the right
places and then be done - as little transformation as possible.
At that point it would allow us to do
I had mentioned earlier that I'd send something on this. These thoughts are
from working on a few modules and on osis2mod.
There are several things that play into this:
1) Titles: These use the element for their content. This has been the
focus of much of the discussion. The Show/Hide Heading f
21 matches
Mail list logo
