Advance Date +15 Days

I have a script...
-----
<SCRIPT language="JavaS cript" type="text/javascript">
<!--
function makeArray() {
for (i = 0; i<makeArray.arg uments.length; i++)
this[i + 1] = makeArray.argum ents[i];
}

function makeArray0() {
for (i = 0; i<makeArray0.ar guments.length; i++)
this[i] = makeArray0.argu ments[i];
}

function y2k(number) { return (number < 1000) ? number + 1900 : number; }

var months = new
makeArray('Janu ary','February' ,'March','April ','May','June', 'July','August' ,'September','O ctober','Novemb er','December') ;
var days = new
makeArray0('Sun day','Monday',' Tuesday','Wedne sday','Thursday ','Friday','Sat urday');

var today = new Date();
var day = days[today.getDay()];
var date = today.getDate( ) + 15;
var month = today.getMonth( ) + 1;
var year = y2k(today.getYe ar());

document.write( months[month] +' ' + date + ', ' + year);
//-->
</SCRIPT>
---

I need this script to advance the document.write by 15 days, as you can see
I tried adding "+ 15"
after the Var Date = today.getDate( ) that works fin until it started
showing 32 days in June
today. LOL.

Can anyone please assist me? Ro****@BeatToBe at.com

Thank you,
Robert

[David Håsäther]

Michael Winter <m.******@bluey onder.co.invali d> wrote:

All a user agent needs to do once it reads a SCRIPT opening tag is
ignore everything until it encounters </

Pedantry: Actually, "</" followed by a name start character (a-zA-Z),
i.e. ETAGO delmiter-in-context, or NET ("/") if the start tag was NET-
enabling.

--
David Håsäther

[Dr John Stockton]

JRS: In article <d9************ *@news.t-online.com>, dated Tue, 21 Jun
2005 11:26:55, seen in news:comp.lang. javascript, Daniel Kirsch
<Iw************ *****@gmx.de> posted :

Dr John Stockton wrote:

Not good.

If new Date('2005/10/21'); is used, then, since there are 31 days in
October, the answer should be November 5th. However, if executed in the
EU or in much of North America, the result will be in November 4th.

Did you not see that I warned the OP "Ignore any response containing
864e5 or its equivalent;"?

Thanks. Added
if (shrt == "d")
dte.setDate(dte .getDate() + val);

Anything else "not good"?

Well, the RegExp test should perhaps be case-sensitive; and you need to
think about what +3H should do to Sun 2005/10/30 00:00:00. As you have
it, it gives 2 o'clock; but with setHours it would give 3 o'clock.

If the change cannot be done, the date should possibly be set to NaN.

vorz = plusMinus[i].charAt(0) == "+" ? 1 : -1;
or vorz = plusMinus[i].charAt(0) + "1" // ??

Actually, you don't need vorz; RegExp match with
X = fst.match(/([+-]\d+)([SMHdmy])/)
then +X[1] can be used as val and X[2] as the selector.

Note that a minute after 2005/10/30 01:59:30 it is actually 2005/10/30
01:00:30.

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 IE 4 ©
<URL:http://www.jibbering.c om/faq/> JL/RC: FAQ of news:comp.lang. javascript
<URL:http://www.merlyn.demo n.co.uk/js-index.htm> jscr maths, dates, sources.
<URL:http://www.merlyn.demo n.co.uk/> TP/BP/Delphi/jscr/&c, FAQ items, links.

[Daniel Kirsch]

Dr John Stockton wrote:

Well, the RegExp test should perhaps be case-sensitive; and you need to
think about what +3H should do to Sun 2005/10/30 00:00:00. As you have
it, it gives 2 o'clock; but with setHours it would give 3 o'clock.
Of course. But that's pretty theoretical :-)
Actually, you don't need vorz; RegExp match with
X = fst.match(/([+-]\d+)([SMHdmy])/)
then +X[1] can be used as val and X[2] as the selector.
Thanks.

Note that a minute after 2005/10/30 01:59:30 it is actually 2005/10/30
01:00:30.

Works for me. It gives me "2:00:30".

Daniel

[Dr John Stockton]

JRS: In article <d9************ *@news.t-online.com>, dated Wed, 22 Jun
2005 15:19:02, seen in news:comp.lang. javascript, Daniel Kirsch
<Iw************ *****@gmx.de> posted :

Dr John Stockton wrote:

Note that a minute after 2005/10/30 01:59:30 it is actually 2005/10/30
01:00:30.

Works for me. It gives me "2:00:30".

Yes; but you're presumably in Germany. Try it in German time, a clock
hour later.

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 MIME. ©
Web <URL:http://www.merlyn.demo n.co.uk/> - w. FAQish topics, links, acronyms
PAS EXE etc : <URL:http://www.merlyn.demo n.co.uk/programs/> - see 00index.htm
Dates - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm etc.

[cwdjrxyz]

> Michael Winter <m.win...@bluey onder.co.invali *d> wrote:

Script 'hiding' has been around for so long that many don't know why it

began in the first place, or that it stopped being necessary years ago.

I wonder if you can say the same about multi-line comment tags around
CDATA open and close tags placed in a script in a few years. In xhtml
you are required to surround the script with open and close CDATA tags
to avoid possible conflict with xml, if any is included in the xhtml
page. The problem is that most current browsers do not understand the
xml CDATA tags and completely kill the script, if you use them. The W3C
xhtml 1.0 and 1.1 validators will validate such a page perfectly, if it
has no errors. However if you leave the CDATA tags off, the validators
make a terrible fuss. However if you surround the CDATA open and close
tags with the multi-line javascript tags, everyone is happy. The page
works, and the validators and a proper xhtml delivery see right through
the javascripts to view the XML CDATA tags. I believe I first learned
about this at the Opera forum nearly 2 years ago from a member of the
Opera design team. Of course the easy way out is to use an external
javascript file, which avoids all of this fuss. However, many still
insist on including the script on the main page.

PS The Google beta groups site has been acting up at times for the last
day or two. It sometimes does not put the quoted message in the text
box, and you have to highlight and copy it to the response text box.
Until this problem resolves, some posts made from Google are going to
look strange. Major US ISPs including MSN and AOL have dropped Usenet
groups. I and many others are not interested in newsreaders just to
make a few posts in Usenet. Nearly everyone I know reads NGs online.
Most plans here allow unlimited, or very large, time on line, and many
even with dialup leave the computer on for many hours at a time.

[Michael Winter]

On 23/06/2005 09:40, cw******@yahoo. com wrote:

[snip]

The problem is that most current browsers do not understand the
xml CDATA tags and completely kill the script, if you use them.

The rather blatantly obvious solution is to not serve XHTML(-like)
documents to user agents that don't explicitly state[1] they support it.

There is no benefit in serving XHTML as text/html, and XML tools can
transform their output to HTML so there is no excuse here, either.

[snip]

Mike
[1] IE says it supports anything in its request headers, so you have to
ignore things like that when negotiating XHTML.

--
Michael Winter
Replace ".invalid" with ".uk" to reply by e-mail.

[Dr John Stockton]

JRS: In article <11************ *********@g47g2 000cwa.googlegr oups.com>,
dated Thu, 23 Jun 2005 01:40:20, seen in news:comp.lang. javascript,
cw******@yahoo. com <cw******@yahoo .com> posted :

PS The Google beta groups site has been acting up at times for the last
day or two. It sometimes does not put the quoted message in the text
box, and you have to highlight and copy it to the response text box.
Until this problem resolves, some posts made from Google are going to
look strange. Major US ISPs including MSN and AOL have dropped Usenet
groups. I and many others are not interested in newsreaders just to
make a few posts in Usenet. Nearly everyone I know reads NGs online.
Most plans here allow unlimited, or very large, time on line, and many
even with dialup leave the computer on for many hours at a time.

If providers in your country provide only shoddy services, it is you who
should suffer, not us; you merit no sympathy. Pay for a good service,
and demand it.
If you find that, when you start a News reply, Google does not provide
the previous article in quoted form, note what Keith Thompson wrote in
comp.lang.c, message ID <ln************ @nuthaus.mib.or g> :-
If you want to post a followup via groups.google.c om, don't use
the "Reply" link at the bottom of the article. Click on "show
options" at the top of the article, then click on the "Reply" at
the bottom of the article headers.

Since that is what the experts in this newsgroup prefer to read, it will
be to your advantage to comply.

--
© John Stockton, Surrey, UK. ??*@merlyn.demo n.co.uk Turnpike v4.00 MIME. ©
Web <URL:http://www.merlyn.demo n.co.uk/> - FAQish topics, acronyms, & links.
Check boilerplate spelling -- error is a public sign of incompetence.
Never fully trust an article from a poster who gives no full real name.

[Thomas 'PointedEars' Lahn]

Dr John Stockton wrote:

JRS: In article <d9************ *@news.t-online.com>, dated Wed, 22 Jun
2005 15:19:02, seen in news:comp.lang. javascript, Daniel Kirsch
<Iw************ *****@gmx.de> posted :

Dr John Stockton wrote:

Note that a minute after 2005/10/30 01:59:30 it is actually 2005/10/30
01:00:30.

Works for me. It gives me "2:00:30".

Yes; but you're presumably in Germany. Try it in German time,
a clock hour later.

I am in Germany where next change from Daylight Saving Time to
"normal" time is scheduled on Sunday, 2005-10-30, 03:00:00.000
local (DS)time, using the German time locale.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050610
Firefox/1.0.4 (Debian package 1.0.4-3) Mnenhy/0.7.2.0

shows for `new Date(2005, 9, 30, 1, 59)'
"Sun Oct 30 2005 01:59:00 GMT+0200 (CEST)"
which is correct;

for `new Date(2005, 9, 30, 2, 59)'
"Sun Oct 30 2005 02:59:00 GMT+0100 (CET)"
which is incorrect

and so for `new Date(new Date(2005, 9, 30, 2, 59).getTime() + 3600000)'
"Sun Oct 30 2005 03:59:00 GMT+0100 (CET)"
which is correct according to "common sense".

Apparently, the JavaScript 1.5 engine of my UA is not up to date or not
properly using the locale. The second expression should have given

"Sun Oct 30 2005 02:59:00 GMT+0200 (CEST)"

as change from local DST to local "normal" time is scheduled only a
minute later (ref. <http://zeitumstellung. de/>). Or am I missing
something?
PointedEars

[Thomas 'PointedEars' Lahn]

cw******@yahoo. com wrote:

Michael Winter <m.win...@bluey onder.co.invali *d> wrote:
Script 'hiding' has been around for so long that many don't know why it began in the first place, or that it stopped being necessary years ago.

^^
This quote is borken, although Google Groups may error-correct that for
display. The technical flaws of Google Groups posts are many, especially
in the new version; please avoid using it, use a proper newsreader
application instead.
I wonder if you can say the same about multi-line comment tags around
CDATA open and close tags placed in a script in a few years. In xhtml
you are required to surround the script with open and close CDATA tags
to avoid possible conflict with xml, if any is included in the xhtml
page.

No, you are not. As it is but a PCDATA issue, you may instead escape markup
characters within the PCDATA content that script or style content is in
XHTML, e.g. `&lt;' for `<' (JS: less-than operator; CSS: child selector),
&gt; for `>' (JS: greater-than operator) and so on.

It is only that the UA(s) tested with or targeted, most notably Internet
Explorer, are not capable of processing XHTML and so do not support CDATA
_content declarations_ which is why commenting out those declarations is
necessary; not using the unsupported markup language in the first place
(but sticking to widely, if not always, supported HTML 4.01, Strict DTD
if possible) or including/linking to a script or style file would have
avoided the original problem.
PointedEars

[Dr John Stockton]

JRS: In article <47************ ****@PointedEar s.de>, dated Sun, 3 Jul
2005 19:40:18, seen in news:comp.lang. javascript, Thomas 'PointedEars'
Lahn <Po*********@we b.de> posted :

Dr John Stockton wrote: (about ten days ago)

JRS: In article <d9************ *@news.t-online.com>, dated Wed, 22 Jun
2005 15:19:02, seen in news:comp.lang. javascript, Daniel Kirsch
<Iw************ *****@gmx.de> posted :

Dr John Stockton wrote:
Note that a minute after 2005/10/30 01:59:30 it is actually 2005/10/30
01:00:30.
Works for me. It gives me "2:00:30".

Yes; but you're presumably in Germany. Try it in German time,
a clock hour later.

I am in Germany

Apparently, the JavaScript 1.5 engine of my UA is not up to date or not
properly using the locale. The second expression should have given

"Sun Oct 30 2005 02:59:00 GMT+0200 (CEST)"

as change from local DST to local "normal" time is scheduled only a
minute later (ref. <http://zeitumstellung. de/>). Or am I missing
something?

Probably.

Rather than looking at such as
new Date(2005, 9, 30, 1, 59)
it would be simpler to look at
new Date(2005, 9, 30, 1, 59).getTimezone Offset()
or
new Date("2005/10/30 00:59:00 GMT").getTimezo neOffset()

One can get javascript to determine when the clock change is thought to
occur : <URL:http://www.merlyn.demo n.co.uk/js-clndr.htm#Ctrls > shows it.

Unfortunately, operating systems are often written and configured in a
country which has a considerable reputation for ignorance both about
time and about the rest of the world; so your OS may have incorrect
data.
You wrote :
for `new Date(2005, 9, 30, 2, 59)'
"Sun Oct 30 2005 02:59:00 GMT+0100 (CET)"
which is incorrect
Is it? Local time 02:59 occurs twice, once at the end of Summer and
once at the start of Winter, and ISTM that you see the latter. After
the clock has been put back, it continues going forwards.

Indeed, AIUI, the first version of Windows 95 (cf. ibid. 13,14/19) sets
the clock back whenever it thinks that the clock has reached 2 a.m. on
the day in question, not just on the first occasion.

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 MIME. ©
Web <URL:http://www.merlyn.demo n.co.uk/> - w. FAQish topics, links, acronyms
PAS EXE etc : <URL:http://www.merlyn.demo n.co.uk/programs/> - see 00index.htm
Dates - miscdate.htm moredate.htm js-dates.htm pas-time.htm critdate.htm etc.