MICROSOFT EXCEL.
You edit my data.
Did you consider that maybe, MAYBE, 8-16 wasn't a date and that you
shouldn't convert it to August 16th? Or perhaps, not edit the DATA so
that I could choose to reformat the cell to text and get back to
8-16 instead of 42853? Where the HELL did 42853 come from
On Tue, 24 Mar 2009 06:35:48 -0700 (PDT), Ann Barcomb
a...@domaintje.com wrote:
On Tue, 24 Mar 2009, H.Merijn Brand wrote:
OO is IMHO even worse, in that they say they follow the locale pretty
strict, but they only follow $LANG and ignore $LC_*
Set $LANG to en_US.utf8 and LC_PAPER to
On Tue, Mar 24, 2009 at 12:43, Mads Ruben Rennemo madsru...@gmail.com wrote:
Where the HELL did 42853 come from anyways?
Honest question? (Fractional) days since the Excel epoch IIRC.
Also, when I save you as a CSV, I expect a line break inside a cell to
be removed or converted. I don't
2009/3/24 Philip Newton philip.new...@gmail.com:
On Tue, Mar 24, 2009 at 12:43, Mads Ruben Rennemo madsru...@gmail.com wrote:
Where the HELL did 42853 come from anyways?
Honest question? (Fractional) days since the Excel epoch IIRC.
Excel Windows epoch. :-) (It was different on a Mac)
Also,
Philip Newton writes:
On Tue, Mar 24, 2009 at 12:43, Mads Ruben Rennemo madsru...@gmail.com wrote:
Where the HELL did 42853 come from anyways?
Honest question? (Fractional) days since the Excel epoch IIRC.
Normally, yes, except (with day 1 of the Excel epoch being 1/1/1900)
day 42853 would
Philip Newton philip.new...@gmail.com writes:
On Tue, Mar 24, 2009 at 12:43, Mads Ruben Rennemo madsru...@gmail.com wrote:
Also, when I save you as a CSV, I expect a line break inside a cell to
be removed or converted. I don't expect to see two 8-column lines in
my 16-column CSV file.
I
2009/3/24 Dagfinn Ilmari Mannsåker ilm...@ilmari.org:
Philip Newton philip.new...@gmail.com writes:
On Tue, Mar 24, 2009 at 12:43, Mads Ruben Rennemo madsru...@gmail.com wrote:
Also, when I save you as a CSV, I expect a line break inside a cell to
be removed or converted. I don't expect to
On 2009-03-24, at 07:03, Philip Newton wrote:
In Excel's little sub-dialect, for example, quotation marks around a
field escape not only the field delimiter but also the record
delimiter.
As they should.
Another fun little hateful fact about Excel is that CSV is really
locale-specific list
On Tue, 24 Mar 2009 09:07:05 -0500, Peter da Silva pe...@taronga.com
wrote:
On 2009-03-24, at 07:03, Philip Newton wrote:
In Excel's little sub-dialect, for example, quotation marks around a
field escape not only the field delimiter but also the record
delimiter.
As they should.
On Tue, 24 Mar 2009 12:43:08 +0100, Mads Ruben Rennemo
madsru...@gmail.com wrote:
MICROSOFT EXCEL.
You edit my data.
Did you consider that maybe, MAYBE, 8-16 wasn't a date and that you
shouldn't convert it to August 16th?
It is worse even. If you have a value like 20090307, obviously an ISO
I had to recently fight Excel not to convert e.g. postal code numbers
and phone numbers to normal numbers. Here's the stomach-wrenching
way to quote a cell in CSV so that Excel gets it:
=01234
I won't bother explaining the whys because I will start sobbing.
--
There is this special biologist
On 2009-03-24, at 08:28, H.Merijn Brand wrote:
why on earth 2009-03-05 *WITH*
quotes end up as May 03, 2009 - even in the Dutch locale - is way
beyond my level of understanding.
Because double-quotes are part of CSV field layout, and it's legal for
a program to quote ALL strings. In one CSV
On Tue, Mar 24, 2009 at 09:10:51AM -0500, Peter da Silva wrote:
On 2009-03-24, at 08:28, H.Merijn Brand wrote:
why on earth 2009-03-05 *WITH*
quotes end up as May 03, 2009 - even in the Dutch locale - is way
beyond my level of understanding.
Because double-quotes are part of CSV field
Joshua Rodman jrod...@hate.spamportal.net writes:
2009-03-05 is always -MM-DD unless you're a moron.
Ah well you see that's where Excel has one up on you. It is the effort
of an impressive collection of morons all the way from the luser to the
cpu.
Matthew
--
I must take issue with the
On 2009-03-24, at 06:43, Mads Ruben Rennemo wrote:
Also, when I save you as a CSV, I expect a line break inside a cell to
be removed or converted. I don't expect to see two 8-column lines in
my 16-column CSV file.
CSV supports line breaks, if they're quoted. I wrote a CSV parser last
year
On Tue, Mar 24, 2009 at 09:05:05AM -0500, Peter da Silva wrote:
On 2009-03-24, at 06:43, Mads Ruben Rennemo wrote:
Also, when I save you as a CSV, I expect a line break inside a cell to
be removed or converted. I don't expect to see two 8-column lines in
my 16-column CSV file.
CSV supports
Do you remember in the good old days, when Sun had this revolutionary
thing called a Lights-Out Management, which was basically an
overachieving serial console?
One of the really cool things about the LOM was how you could actually
power-cycle the server. You typed the following commands:
17 matches
Mail list logo
