Re: Public beta 6 for WebCatalog 4.0 is now available
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 32730
interpreted = N
texte = If the option was [CAPITALIZE delimiters=.!?;], similar to the listwords context, there would still be times when it wouldn't be perfect, but at least we would know what to expect and what the limitations are. I assume that it would be a non-trivial matter to program an algorithm for the English language. Allowing us to specify the delimiters means it remains in the string comparison realm and doesn't have to 'know' anything about the English language. Is that a fair enough assessment? Is that a useful enough suggestion to merit having Grant implement it?Mike>> I just checked and the [capitalize] context is still too sensitive to >> the apostrophe embedded in the string. For example: > > [EXAMPLE DELETED] > >> If the >> parser performed a lookahead and only capitalized after an apostrophe >> when the second character after is a letter, not whitespace. > > What about word's like they're and I'll or if a multiple > possession ends a sentence (giving you ...the three boys'. New > sentence.)? Ideally, there would be a built in list of words that > are parsed properly, but I imagine that the internal code to account > for that would be a far cry from what it is now. > > But I agree, there should be some extra parsing. Maybe options added > to the [CAPITALIZE] tag ([CAPITALIZE posessive=t&contractions=t]). I > don't know exactly how the options would work, but possessive could > just ignore any apostrophes with an s after it, contractions would > look for 'll, etc. It's not a perfect scheme because it ignore > words like don't and can't, but it's a start. > > Michael > > ############################################################# > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > To switch to the INDEX mode, E-mail to > > Send administrative queries to > ############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
If the option was [CAPITALIZE delimiters=.!?;], similar to the listwords context, there would still be times when it wouldn't be perfect, but at least we would know what to expect and what the limitations are. I assume that it would be a non-trivial matter to program an algorithm for the English language. Allowing us to specify the delimiters means it remains in the string comparison realm and doesn't have to 'know' anything about the English language. Is that a fair enough assessment? Is that a useful enough suggestion to merit having Grant implement it?Mike>> I just checked and the [capitalize] context is still too sensitive to >> the apostrophe embedded in the string. For example: > > [EXAMPLE DELETED] > >> If the >> parser performed a lookahead and only capitalized after an apostrophe >> when the second character after is a letter, not whitespace. > > What about word's like they're and I'll or if a multiple > possession ends a sentence (giving you ...the three boys'. New > sentence.)? Ideally, there would be a built in list of words that > are parsed properly, but I imagine that the internal code to account > for that would be a far cry from what it is now. > > But I agree, there should be some extra parsing. Maybe options added > to the [capitalize] tag ([CAPITALIZE posessive=t&contractions=t]). I > don't know exactly how the options would work, but possessive could > just ignore any apostrophes with an s after it, contractions would > look for 'll, etc. It's not a perfect scheme because it ignore > words like don't and can't, but it's a start. > > Michael > > ############################################################# > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > To switch to the INDEX mode, E-mail to > > Send administrative queries to > ############################################################# This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to To switch to the INDEX mode, E-mail to Send administrative queries to
Mike Davis
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
First postarg not taking in $Commands (1997)
RE: webcat license???? (1997)
X etc.... (1999)
(1997)
Help name our technology! (1997)
Latest version? (2000)
Date on ViewOrders.tpl (1998)
searchable list archive (1997)
ie Posting error (2000)
Webmerchant confirmation hooks? (1997)
Draft Manual, Tutorial, and more (1997)
Port of site from OS X to IIS 6 Help needed. (2004)
Multi-processor Mac info ... (1997)
Why does WebCat do this? (2001)
Taxable Shipping (2003)
WebCat2 several catalogs? (1997)
What is a TAB (2003)
Plugin or CGI or both (1997)
Shopping problems with 2.1b3 acgi (1997)
quantity limit (1998)