Glen,
This is a good point.
llefevre,
Can you supply a unit test for this as well (or update the existing unit
test)? We need to get unit tests working for these things in order to
really have any hope of localization. (Then we can get real data back like
happened with the comma vs decimal money issue).
BTW I tried to respond to you about localization but my ISP's mail server
crashed. Basically Localization/Internationalization is a priority for us,
but we need good folks like you to do exactly what youre doing! You'll have
a better understanding of what the non-US/UK/AU version of Excel does we can
only guess. (BTW the US/UK/AU versions of excel are all roughly the same
version from what I've read if anyone was wondering)
As a matter of procedure, best to submit patches into bugzilla so that they
don't get lost, just label them [PATCH]. It will be posted to the list by
bugzilla as well.
Thanks for helping out! I'll apply this shortly if flash-glen doesn't beat
me to it.
-Andy
>On Wed, 13 Mar 2002 19:04:34 0100 =?iso-8859-1?B?TG/vYyBMZWbodnJl?=
<[EMAIL PROTECTED]> wrote.
>--- HSSFCell.java Wed Mar 13 17:53:21 2002
> HSSFCellNew.java Wed Mar 13 17:53:02 2002
>@@ -72,6 72,7 @@
> import org.apache.poi.hssf.record.ExtendedFormatRecord;
>
> import java.util.Date;
> import java.util.Calendar;
>
> /**
> * High level representation of a cell in a row of a spreadsheet.
>@@ -631,6 632,19 @@
> public void setCellValue(Date value)
> {
> setCellValue(HSSFDateUtil.getExcelDate(value));
> }
>
> /**
> * set a date value for the cell. Excel treats dates as numeric so you
>will need to format the cell as
> * a date.
> *
> * @param value the date value to set this cell to. For formulas
>we'll set the
> * precalculated value, for numerics we'll set its value. For
>othertypes we
> * will change the cell to a numeric cell and set its value.
> */
> public void setCellValue(Calendar value)
> {
> setCellValue(value.getTime());
> }
>
> /**
>
