Re: Contest
- Posted by Derek Parnell <ddparnell at bigpond.com> Oct 31, 2004
- 520 views
Patrick Barnes wrote: > > > > > > 10-4 is not a token. > > > > > > True, but why are you converting '10-4' into 10-4 ? > > > > Again, because its = it's. > > > > > The specs do not talk > > > about removing bytes from strings. > > > > And that is confusing. > > Derek, I'd say the principle source of confusion comes from: > "For the purposes of comparison and display, quotes are ignored in any token." Agreed. I'll fix that up tonight. > So, we should compare and display our tokens without quotes, but we > shouldn't remove the quotes byte from tokens when we store it > internally? Why *wouldn't* we? Frankly, I don't care whether you internally remove quotes or not. That could be an implementation strategy. *ALL* I'm saying, and no more than this, is that when you compare strings, disregard any quotes. How you do that is your concern. For example, one might remove quotes *after* determining that you've got a token. Some other people might keep alternate lists... there are many variations on this theme. Some work better than others. As for displaying, I don't care if you display quotes or not really, but don't go and display both variants. > "Thus the tokens Ma'am, maam and 'MAAM' are considered to be the same > 4-character token." So, the quote mark should be ignored, but what... > we should still store a copy of "ma'am" and "maam" separately, but > combine them when we go to calculate statistics? > > You can't specify the internal workings of the entries... only the > external effects. I'm *not* specifying the implementation, just the requirements. I don't care if you store "ma'am" and "maam" seperately or not. What I care about is the results. I expect that every submission will solve these weird and cantankerous rules in their own unique manner. -- Derek Parnell Melbourne, Australia