View Single Post
Old 09-03-2009, 01:55 PM   #47
ekaser
Opinion Artiste
ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.ekaser has a propeller beanie that spins backward.
 
ekaser's Avatar
 
Posts: 301
Karma: 61464
Join Date: Mar 2009
Location: Albany, OR
Device: Nexus 5, Nexus 7, Kindle Touch, Kindle Fire
Quote:
Originally Posted by ahi View Post
Hmmm... it seems like your suggestions would take me back down the road of (effectively) a pre-calculated database being parsed from the input text. Perhaps that means there is great enough merit to the idea that it is worth the pain of implementation?
That's up to you. I'm just trying to provide a second point-of-view, one that may or may not mesh and/or differ from your own. Ultimately, you're writing the code, so you have to (get to) make the decisions about what will work best for what YOU are trying to accomplish. It just seems to me like there are two primary things: structure and content, with content being further divided into images, text and text formatting. Structure (other than sentence and paragraph massaging) would remain pretty much unchanged, I'd think, and most of the changes your program would make would be to the content. Therefore, separating the two as much as possible, while maintaining the necessary links between structure and content, would be best.

Quote:
Regarding footnotes... the only misunderstanding is that I conceive of a footnote as being always tied to a single character, the "*", "**" or "1" or whatever footnote mark being an output concern and the tied-to character being whatever precedes the footnote mark.
I guess I was seeing footnotes and hyperlinks as being pretty much the same thing. You're going to have to handle hyperlinks, so I figured why not treat the footnotes the same way (in terms of the link itself)? You have to write the code once (for hyperlinks), so if you fold the footnote link into the same mold, you're all done. But YOU'RE the one that has to hold all of this in your head until it's excreted as code, so whatever works best in YOUR head is key...

Quote:
Makes sense? This way, I theoretically ought to be able to loop through all words within all sentences, while still querying "what character is before this word" or "does the sentence previous to this one end with punctuation/the way a proper sentence should".
It's sounding pretty good to me!
ekaser is offline   Reply With Quote