> > > > In article
> > > > <bbcollins-767F40.08225912122007@70-3-168-216.area5.spcsdns.net>, Bill
[quoted text clipped - 31 lines]
> types of files. You might want to give them a whirl before trashing
> them.
Okeydokey. Will do.
<snip>
> that said, I only kept my Appleworks because I have a couple of simple
> databases and iWork doesn't do database.
[quoted text clipped - 4 lines]
> types of files. You might want to give them a whirl before trashing
> them.
I've still got a few niggles about Numbers, the primary one for my
existing workflow being that it doesn't offer tab delimited exports, but
I'm getting used to it.
OTOH I've been struggling for several years now to successfully import
and print MS Word documents without having to fiddle around with header
and page sizes to get the correct pagination. I've tried OpenOffice,
NeoOffice, and the other usual suspects, always with something not
coming out quite right.
So far, Pages has got it right every time.

Signature
Paul Sture
Sue's OpenVMS bookmarks:
http://eisner.encompasserve.org/~sture/ovms-bookmarks.html
John Rethorst - 15 Dec 2007 02:58 GMT
> I've still got a few niggles about Numbers, the primary one for my
> existing workflow being that it doesn't offer tab delimited exports, but
> I'm getting used to it.
Ouch. I'm sure they'll fix that soon.

Signature
John Rethorst
jrethorst at post dot com
JCrowe - 15 Dec 2007 17:30 GMT
> I've still got a few niggles about Numbers, the primary one for my
> existing workflow being that it doesn't offer tab delimited exports, but
> I'm getting used to it.
I know this is a little painful, but it's easy to convert the comma
separated export of Numbers into a tab separated file. If you feel
comfortable on the command line, you can use some tools from the
command line that support regular expressions to substitute tabs for
the commas. What you have to be careful about is those instances of
commas inside of text strings, which you would not want to replace.
Of course, the export functionality creates a separate file for each
sheet so if that's a problem, you have other challenges.
> OTOH I've been struggling for several years now to successfully import
> and print MS Word documents without having to fiddle around with header
[quoted text clipped - 3 lines]
>
> So far, Pages has got it right every time.
I've noticed this as well.
P. Sture - 18 Dec 2007 01:53 GMT
> > I've still got a few niggles about Numbers, the primary one for my
> > existing workflow being that it doesn't offer tab delimited exports, but
[quoted text clipped - 8 lines]
> Of course, the export functionality creates a separate file for each
> sheet so if that's a problem, you have other challenges.
It's the possibility of commas within a text field which had me using
tab delimited exports in the first place.
I am comfortable with the command line. Any suggestions as to which
tools to look into? I don't see the point of reinventing the wheel...
> > OTOH I've been struggling for several years now to successfully import
> > and print MS Word documents without having to fiddle around with header
[quoted text clipped - 5 lines]
>
> I've noticed this as well.
Sounds good.

Signature
Paul Sture
Sue's OpenVMS bookmarks:
http://eisner.encompasserve.org/~sture/ovms-bookmarks.html
Gregory Weston - 18 Dec 2007 03:05 GMT
> > > I've still got a few niggles about Numbers, the primary one for my
> > > existing workflow being that it doesn't offer tab delimited exports, but
[quoted text clipped - 11 lines]
> It's the possibility of commas within a text field which had me using
> tab delimited exports in the first place.
That's generally handled by wrapping fields that contain commas in
double-quotes. Any program that claims to be able to handle
comma-delimited input should recognize and support that idiom.
G
P. Sture - 18 Dec 2007 11:50 GMT
> > > > I've still got a few niggles about Numbers, the primary one for my
> > > > existing workflow being that it doesn't offer tab delimited exports,
[quoted text clipped - 16 lines]
> double-quotes. Any program that claims to be able to handle
> comma-delimited input should recognize and support that idiom.
Coincidentally, I've just discovered that SQLITE doesn't ignore commas
within double quoted fields. Go figure.

Signature
Paul Sture
Sue's OpenVMS bookmarks:
http://eisner.encompasserve.org/~sture/ovms-bookmarks.html
Gregory Weston - 18 Dec 2007 12:39 GMT
> > > It's the possibility of commas within a text field which had me using
> > > tab delimited exports in the first place.
[quoted text clipped - 5 lines]
> Coincidentally, I've just discovered that SQLITE doesn't ignore commas
> within double quoted fields. Go figure.
Coincidentally, SQLite doesn't claim to be able to import CSV files. Go
figure.
That's aside from not having been mentioned in this thread before,
AFAICT.
P. Sture - 18 Dec 2007 18:57 GMT
> > > > It's the possibility of commas within a text field which had me using
> > > > tab delimited exports in the first place.
[quoted text clipped - 8 lines]
> Coincidentally, SQLite doesn't claim to be able to import CSV files. Go
> figure.
Apologies, I was fooled there by the fact the help claims to support CSV
as output.
> That's aside from not having been mentioned in this thread before,
> AFAICT.
True, it was red herring :-(

Signature
Paul Sture
Sue's OpenVMS bookmarks:
http://eisner.encompasserve.org/~sture/ovms-bookmarks.html