Will that function correctly parse a date entered as 5/1/2007 correctly for both people from the US and people fro Europe? That would be great if it did.
You're missing my point. If you use the ISO 8601 standard, then you can interact with any other program that uses it without having to worry which format they're using, not to mention that the standard actually makes logical sense unlike both the UK and US methods for displaying numerical dates.
Sorry for being thick. Can you please point me to an example? Edit: However, I just looked at the standard and now see what you are talking about. Are you saying that we should require the dates to be entered as YYYY-MM-DD in the gig text file? Then the extension would parse it correctly as long as we knew where the code was being executed. Is there a way to determine whether we are in the US or Europe? That way we could add an "if" check to correctly parse that date.
Errr...no I dont think that would do that jim, but it does mean you can use stuff like '5th January' which is nice. Otherwise how about we just define the date format in the default.php file then everyone can choose what they want?
Comments
Edit: However, I just looked at the standard and now see what you are talking about. Are you saying that we should require the dates to be entered as YYYY-MM-DD in the gig text file? Then the extension would parse it correctly as long as we knew where the code was being executed. Is there a way to determine whether we are in the US or Europe? That way we could add an "if" check to correctly parse that date.
Otherwise how about we just define the date format in the default.php file then everyone can choose what they want?
1)Is there a way to style the output? I'm getting line breaks that don't line up with the event title.
http://www.dciscores.com/forum/
Any idea?