View Single Post
Old 05-17-2009, 04:07 PM   #33
ahi
Wizard
ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.ahi ought to be getting tired of karma fortunes by now.
 
Posts: 1,790
Karma: 507333
Join Date: May 2009
Device: none
Quote:
Originally Posted by pepak View Post
It is sensible, I am just a bit doubtful about it being realistic :-)

I was thinking along these lines, but really, even with same-source files, there are too many variations so that it's too much effort writing a fully-automatic utility. I just keep a collection of useful regexps (or normal replaces) and in each case decide which one (and in which order) to use.
Well, in a way, a utility could be as simple as a set of regexes, with command-line switches (or heuristics at start-up time) mandating which specific one to use. I do think though that some of the fix-ups that can be addressed using regexes might be addressed more reliable through simpler sequential processing. (Though, as with all things, I could be wrong.)

It definitely is a tall order... but broken down into its components like this might make it more achievable. Like I said, I might try my hands at the quotation stuff in the near future.
ahi is offline   Reply With Quote