On 04/13/2013 05:35 PM, Peter von Kaehne wrote:
Can I try and summarise what I think is going on here?
Basis of problem:
1) CrossWire has a whitespace/title/poetry problem which has been
discussed at nauseam for many years. But it has neither been thoroughly
resolved nor even isolated. Various
On 04/14/2013 04:39 AM, Matěj Cepl wrote:
On 13/04/13 03:54, John Austin wrote:
It says right on the tag: "indent". So anyone at anytime, who knows some
English, will know exactly what to do with this tag in any situation. It
is ideal really. Please note that this would NOT be the case if IBT
On 13/04/13 03:54, John Austin wrote:
It says right on the tag: "indent". So anyone at anytime, who knows some
English, will know exactly what to do with this tag in any situation. It
is ideal really. Please note that this would NOT be the case if IBT is
required to encode these all as
Exc
On 13/04/13 14:23, Arthur Bolstad wrote:
On the other hand, if experience says a particular language should
prohibit/demand certain presentation characteristics then those should
be programmable. The key for OSIS is that those characteristics should
be semantic and described as such, not in term
On Saturday, April 13, 2013 04:33:16 PM John Austin wrote:
> It has been demonstrated through such comprehension testing, that
indeed
> indents are important to achieving the best comprehension. For
instance,
> in one major language of the region, it was discovered that when a
quote
> margin
On 4/13/2013 3:33 AM, John Austin wrote:
It has been demonstrated through such comprehension testing, that
indeed indents are important to achieving the best comprehension.
Presentation is often chosen to increase comprehension. Does that make
it content?
Whatever you call it, the translat
On Apr 13, 2013, at 9:24 AM, Nic Carter wrote:
>
> On 13/04/2013, at 11:09 PM, DM Smith wrote:
>
>> I would add that the new HTML filter is a work in progress. It is moving to
>> class attributes as a way to abstract presentation out of the filter.
>>
>> This is goodness. I'd recommend that
On 13/04/2013, at 11:09 PM, DM Smith wrote:
> I would add that the new HTML filter is a work in progress. It is moving to
> class attributes as a way to abstract presentation out of the filter.
>
> This is goodness. I'd recommend that we take the OSIS spec and create a
> mapping of each eleme
I would add that the new HTML filter is a work in progress. It is moving to
class attributes as a way to abstract presentation out of the filter.
This is goodness. I'd recommend that we take the OSIS spec and create a mapping
of each element to the corresponding HTML element and class variables
On Apr 12, 2013, at 11:37 PM, Chris Little wrote:
> On 4/12/2013 12:12 PM, DM Smith wrote:
>> Regarding paragraph formats, the element does not define any.
>> There is no notion of "justified", "indented", "line-spacing",
>> "centering", that most word processors provide. These have to
>>
As a one time Bible translator and present adviser on translation, I
notice that there is a linguistic clash going on here. Languages not
only have phoneme level meaning (spelling) and what is normally called
"grammar" (word order and sentence structure) but also higher level
grammar items - p
Can I try and summarise what I think is going on here?
Basis of problem:
1) CrossWire has a whitespace/title/poetry problem which has been
discussed at nauseam for many years. But it has neither been thoroughly
resolved nor even isolated. Various parties have blamed each other -
module makers, os
On 04/13/2013 03:06 PM, Chris Little wrote:
On 4/12/2013 9:42 PM, John Austin wrote:
I still can't see the argument for requiring that everyone call these
questionable instances paragraphs, and require that they must always be
marked up as such. Why not give the publisher the option of calling
On 13 Apr 2013, at 11:33, John Austin wrote:
> It has been demonstrated through such comprehension testing, that indeed
> indents are important to achieving the best comprehension.
I would want to see that "demonstration". There are more factors to
comprehension of printed text than how paragr
On 04/13/2013 03:06 PM, Chris Little wrote:
On 4/12/2013 9:42 PM, John Austin wrote:
I still can't see the argument for requiring that everyone call these
questionable instances paragraphs, and require that they must always be
marked up as such. Why not give the publisher the option of calling
On 04/13/2013 01:47 PM, Troy A. Griffitts wrote:
John,
I'm trying to sympathize with you, but I'm having a hard time. I still
have no clue WHAT the translator is trying to convey to the reader with
the indent. Can you explain?
Yes, essentially the translator works very hard to make their text
On 4/12/2013 9:42 PM, John Austin wrote:
I still can't see the argument for requiring that everyone call these
questionable instances paragraphs, and require that they must always be
marked up as such. Why not give the publisher the option of calling it a
paragraph if they consider it a paragraph
On Sat, 2013-04-13 at 10:42 +0600, John Austin wrote:
> I've worked with many, many SFM texts, and they often do not follow SFM
> rules or play nice in a variety of ways.
And İ think this is the crux here. USFM attempts to separate content
from presentation, albeit not as effectively and
John,
I'm trying to sympathize with you, but I'm having a hard time. I still have no
clue WHAT the translator is trying to convey to the reader with the indent. Can
you explain?
John Austin wrote:
>
>
>On 04/13/2013 09:24 AM, Chris Little wrote:
>> On 4/12/2013 11:18 AM, John Austin wrote:
19 matches
Mail list logo
