Mercedes,
If you add this code
<script>
Timeline.DateTime._iso8601DateRegExp = "^(-?)([0-9]{5})(" + [
"(-?([0-9]{2})(-?([0-9]{2}))?)", // -month-dayOfMonth
"(-?([0-9]{3}))", // -dayOfYear
"(-?W([0-9]{2})(-?([1-7]))?)" // -Wweek-dayOfWeek
].join("|") + ")?$";
</script>
after you include timeline-api.js then you can specify all the years in
five digits.
Alternatively, you can use the Date constructor right inside your data
var json_events={
'dateTimeFormat': 'iso8601',
'events' : [
{ 'start': new Date(-16000, 0, 1),
'end': new Date(-8500, 11, 31),
'title': 'Magdaleniense',
'description': ''
}
]
};
Note that in the Date constructor, the month is zero-based, meaning that
January is 0 and December is 11.
David
Mercedes Blázquez Cívico wrote:
> Hi all,
>
>
> I'm trying to represent BC events or periods using json events, but I
> have a problem when the start and end date has a year previous to
> 9999BC, for example, 32000 BC. I'm using iso8601 to represent the
> events in the timeline. Is there a 4 digit restriction on start and
> end dates? I am able to add dates upto -9999
>
> An example is:
>
> var json_events={
> 'dateTimeFormat': 'iso8601',
> 'events' : [
> {'start': '-16000-01-01',
> 'end': '-8500-12-31',
> 'title': 'Magdaleniense',
> 'description': ''
> }
> ]};
>
>
> Best regards,
>
> Mercedes
>
>
>
> --
>
> _________________________________________________
>
> *Mercedes Blázquez Cívico *
>
> Innovation and R&D**
>
> Researcher**
>
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>
> #T +34913349776
>
> #F +34913349799
>
> Edificio Testa C/Pedro de Valdivia, 10 - planta baja
>
> 28006 Madrid
>
> **
>
> * *
>
> *iSOCO *
>
> intelligent software for the networked economy
>
> www.isoco.com <http://www.isoco.com/>
>
> Este mensaje se dirige exclusivamente a su destinatario y puede
> contener información privilegiada o confidencial. Si no es vd. el
> destinatario indicado, queda notificado de que la utilización,
> divulgación y/o copia sin autorización está prohibida en virtud de la
> legislación vigente. Si ha recibido este mensaje por error, le rogamos
> que nos lo comunique inmediatamente por esta misma vía y proceda a su
> destrucción.
>
> This message is intended exclusively for its addressee and may contain
> information that is CONFIDENTIAL and protected by professional
> privilege. If you are not the intended recipient you are hereby
> notified that any dissemination, copy or disclosure of this
> communication is strictly prohibited by law. If this message has been
> received in error, please immediately notify us via e-mail and delete it.
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> General mailing list
> [email protected]
> http://simile.mit.edu/mailman/listinfo/general
>
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
