"Bryan C. Warnock" wrote:
> I toyed with automatic column detection for a while - (convert any tabs to
> spaces, convert whitespace to 1s, non-whitespace to 0s, and & all the lines
> together. Splitting on /(1+)/ allows determination on each individual
> column width, as well as the space between columns. Then generate the
> appropriate format on the fly, and fill it in with the heavy use of substrs.
> It was supposed to allow table creation in the same vein as "I'll figure out
> what you're trying to do, just do it.", and it worked fairly well for me.
> Couldn't handle multiline entries, was my biggest problem. Then I realized
> that I was doing it all in a fixed width font, and the whole thing was
> worthless in the customer's WYSIWYG environment. But I digress...)
You're not digressing at all. I believe nearly all code editing
is done with fixed width fonts.
--
David Nicol 816.235.1187
"Straight from the docs" doesn't mean "you can cut-and-paste" - it
just means you find the principle explained clearly - without
having to construct it from smaller blocks. -- Abigail
Thread Previous