[osis-core] Continuation quotes - add in <milestone type="continuationQuote"/>

[Chris Little]

Patrick,

I can live with adding the cQuote milstone type, but I will point out that
it is an incomplete solution.  I assume this only supports addition of
continuing open quotation marks, as used in English.  It doesn't
facilitate languages like Spanish (as Steve pointed out) that also need
continuing close quotation marks (or at least it doesn't facilitate the
distinction between the two sorts).  Sub-type could be used for that, I 
suppose.

Troy's NASB would also be useless to Lockman if they wanted to do a
paragraph layout version, unless the complications their VP identifies
were worked out.

--Chris


On Sat, 18 Oct 2003, Patrick Durusau wrote:

> Todd,
> 
> Talked to Troy and suggested:
> 
> <milestone type="cQuote"/>
> 
> Works for me, particularly since milestones can go anywhere.
> 
> Hope you are having a great day!
> 
> Patrick
> 
> Todd Tillinghast wrote:
> > Patrick,
> > 
> > Are you talking about rendering or how to encode?
> > 
> > It seems how to render.  I suspect that there are complications in
> > practice as indicated by Troy's post from Lockman.
> > 
> > It is possible to allow for a <milestone type="continuationQuote"/> IN
> > ADDATION TO the normal <q> element that marks the start and end of the
> > quote.  This would cover the case where a single continuous quote starts
> > in one paragraph and ends in a later paragraph or even section.  There
> > is little harm in allowing a type attribute on <milestone>.  It could be
> > ignored and rendered without the continuation quote mark, but it would
> > prevent people from having to implement complex and likely manually
> > determined positioning of continuation quote marks.  For these reasons,
> > I am suggesting that we allow the mechanism.
> > 
> > I would like to stress that I think these milestones SOULD NOT alter in
> > any way the meaning of the <q> element only allow for a mechanism to
> > encode the position of a continuation quote mark.
> > 
> > I would not say that best practice would require the usage of these
> > milestone elements AND that an encoding with them would also be
> > considered best practice.
> > 
> > I would also say that an application would be conformant if it chooses
> > to ignore the continuation quote milestones and did its own thing.
> > 
> > Naturally a continuation quote mark milestone would have to occur within
> > a <q> element and would apply to the <q> element that is its nearest
> > ancestor.  (Sounds like text for the user manual)
> > 
> > This is not intended to handle the case where a quote is interrupted.
> > 
> > Todd
> > 
> > Todd
> > 
> > 
> >>-----Original Message-----
> >>From: osis-core-admin@bibletechnologieswg.org [mailto:osis-core-
> >>admin@bibletechnologieswg.org] On Behalf Of Patrick Durusau
> >>Sent: Friday, October 17, 2003 3:01 PM
> >>To: osis-core@bibletechnologieswg.org
> >>Subject: [osis-core] Continuation quotes
> >>
> >>Guys,
> >>
> >>Talking to Steve on the phone and he had a great idea about the
> >>continuation quote problem.
> >>
> >>This is the case where a quote starts, end paragraph for example, no
> >>close quotation marker, then a new line, a continuation quote marker,
> >>more of the quote and then the closing quote mark (matching the first
> > 
> > one).
> > 
> >>Steve observed that if you have:
> >>
> >><q>
> >><p></p>
> >><p></p>
> >></q>
> >>
> >>The stylesheet should distinguish a <p> in an open quote and then
> > 
> > insert
> > 
> >>the continuation quote marker.
> >>
> >>Don't know if that will work in all cases but thought it was at least
> >>worth thinking about and putting a note in the users manual on dealing
> >>with that case.
> >>
> >>Hope everyone is having a great day!
> >>
> >>Patrick
> >>
> >>--
> >>Patrick Durusau
> >>Director of Research and Development
> >>Society of Biblical Literature
> >>Patrick.Durusau@sbl-site.org
> >>Chair, V1 - Text Processing: Office and Publishing Systems Interface
> >>Co-Editor, ISO 13250, Topic Maps -- Reference Model
> >>
> >>Topic Maps: Human, not artificial, intelligence at work!
> >>
> >>
> >>_______________________________________________
> >>osis-core mailing list
> >>osis-core@bibletechnologieswg.org
> >>http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> > 
> > 
> > _______________________________________________
> > osis-core mailing list
> > osis-core@bibletechnologieswg.org
> > http://www.bibletechnologieswg.org/mailman/listinfo/osis-core
> > 
> 
> 
>