#163 Allow <pb> and other milestones within listBibl

AMBER
closed
nobody
None
5
2009-02-01
2009-01-15
Lou Burnard
No

> > De : Greg Murray <gpm2a@VIRGINIA.EDU>
> > Date : 28 octobre 2008 15:56:21 GMT+01:00
> > À : TEI-L@listserv.brown.edu
> > Objet : Rép : No pb in listBibl?
> > Répondre à : Greg Murray <gpm2a@VIRGINIA.EDU>
> >
> > Sebastian Rahtz wrote:
>> >> Greg Murray wrote:
>>> >>> In P5, pb is not allowed as a child of listBibl. More generally,
>>> >>> the content model for listBibl does not include model.global. This
>>> >>> appears to be a change from P4, where the content model for
>>> >>> listBibl includes m.Incl. Is this a feature or bug in P5?
>>> >>>
>> >> a feature, probably :-}
>> >> model.global is allowed within <bibl>, so you can
>> >> always put the <pb> there. Is that not sufficiently
>> >> expressive?
> >
> > Well, not really. I am converting P4 documents to P5, and I find
> > that the P4 markup
> >
> > <bibl>...</bibl>
> > <pb/>
> > <bibl>...</bibl>
> >
> > expresses what's in the printed source just fine: the bibliographic
> > entry ends, followed by a page break, followed by another
> > bibliographic entry. I'd prefer to leave the page breaks where they
> > are rather than move them (rather artificially in my view) within
> > one of the bibls. Is there a reason why allowing milestone elements
> > within listBibl would be problematic or ill-advised?
> >
> > Thanks,
> > Greg Murray

Discussion

  • Lou Burnard
    Lou Burnard
    2009-02-01

    • milestone: --> AMBER
     
  • Lou Burnard
    Lou Burnard
    2009-02-01

    At release 1.3, the content model of listBibl includes model.mileStoneLike. This update just missed the cut off date for release 1.2, and I forgot to update the ticket to show its status: apologies!

     
  • Lou Burnard
    Lou Burnard
    2009-02-01

    • status: open --> closed