One.Two becomes One.Two
whereas
One.Two becomes One.Two [after "." it should check the space. If space is not found then this example appears problem]
I think here I need help then. Thanks Rick.
Before a program can be written, we need clearly defined requirements. So far, you seem to be defining your requirements in pieces which causes any program that has been written to have to be revised, sometimes drastically so, in order to handle the "new" requirements. It would be real helpful if you could spell out in clear detail what should be colored and when. I am going to show you several text fragments with one or more characters colored within them... please show us how they should be colored. I noticed you were a little sloppy about doing this earlier, so I am going to ask you to check and then double-check the answers you give us (pay particular attention to whether the
non-alphanumeric characters adjacent to the text with colored letters should be colored or not).
1) check and then double-ch
eck the answers
2) check and then do
uble-check the answers
3) handle the "n
ew" requirements
4) within t
hem... please
5) I bought a new car (To
yota) today
6) pick a size (s
mall/medium/large) for your order
7) pick a size (small/me
dium/large) for your order
8) pick a size (small/medium/la
rge) for your order
9) an apostrophe 'qu
oted' word
I think that covers the bulk of the types of situations that need to be quoted around. Note that we will make "educated guess" about alternates above (for example, what you tell us to do with a dash in the middle of text is what we will do if that dash were a slash instead. Similarly, what you tell us about a word in parentheses is what we will do if the word is surrounded by square or curly brackets instead.