Phillip Shelton a écrit :
Another obvious possibility is to let the stylesheet take care of
the collation.
You need someway of marking up the difference between 1990-2000 and
1990,2000
Hi all,
This is precisely why I think leaving the markup as it is is just OK.
Knowing that
Given the legal question raised, wouldn't it be better to distinguish in
case there are legal implications?
copyright
range
from1990/from
to2000/to
/range
/copyright
or
copyright
year1999/year
year2000/year
/copyright
!ELEMENT copyright (range | year)+
!ELEMENT range (from,
/ Matthew Braun [EMAIL PROTECTED] was heard to say:
| Norman Walsh [EMAIL PROTECTED] writes
| Yann Dirson suggests that a yearrange element be added to copyright.
| [...] what have other people elected to do when faced with this problem?
|
| Another obvious possibility is to let the
On Tue, Sep 25, 2001 at 07:57:35AM -0400, Norman Walsh wrote:
year1999/year
year2000/year
year2001/year
will be rendered as 1999-2001.
Well, I guess it will address most uses, but my initial proposal
(explicit range) was also intended to avoid the need to specify each
year individually.
In some contexts (e.g. library records), I track multiple years for a
publication separately, so I have an inclination towards more explicit
markup in this area. And that might be an issue if we wanted to add, say a
Library of Congress Cataloging in Publication data set to the
metadata. But
/ Yann Dirson [EMAIL PROTECTED] was heard to say:
| From your description of the feature I infer it just merges
| consecutive years, so that the following can be produced - right ?
|
|Copyright (C) 1956, 1962, 1998-2001
Yes. Either by enabling make.year.ranges and specifying:
copyright
On Tue, Sep 25, 2001 at 06:13:12AM -0700, M. Wroth wrote:
But for ordinary use, I don't see a need for explicit markup of
the various combinations --- when the occasion has come up, I've used
year1996, 1998, 1999, 2000/year
Sure, it works. But it probably creates more pain when you need to
Norm,
http://sourceforge.net/tracker/index.php?func=detailaid=456174group_id=21935atid=384107
When you ask a question here like this, do you want followups to go
to the list? Or to the SourceForge bug? I am just sending this to the
list, but will add it to SF if that is where you want it.
/ Dan York [EMAIL PROTECTED] was heard to say:
| Norm,
|
|
|http://sourceforge.net/tracker/index.php?func=detailaid=456174group_id=21935atid=384107
|
| When you ask a question here like this, do you want followups to go
| to the list? Or to the SourceForge bug? I am just sending this to the
Another obvious possibility is to let the stylesheet take care of
the collation.
You need someway of marking up the difference between 1990-2000 and
1990,2000
Phill
To subscribe or unsubscribe from this elist use the
From: Norman Walsh [EMAIL PROTECTED]
In
http://sourceforge.net/tracker/index.php?func=detailaid=456174group_id=21935atid=384107
Yann Dirson suggests that a yearrange element be added to copyright.
The TC considered this and admitted to a certain amount of fudging in
practice, using
Norman Walsh [EMAIL PROTECTED] writes
Yann Dirson suggests that a yearrange element be added to copyright.
[...] what have other people elected to do when faced with this problem?
Another obvious possibility is to let the stylesheet take care of
the collation.
This would make it
12 matches
Mail list logo
