Re: Bug in capitalize ... ?
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 53485
interpreted = N
texte = >HTML entities won't help Ken's problem... > >[capitalize]peña[/capitalize] > >shows up as Pe=D1A, as the "n" in ñ gets capitalized, resulting >in Ñ > >The fix would be for WebDNA to support a delimiters param to [capitalize]. > >In the meantime, you could play with listwords, specifying the >delimiter, then capitalizing only the first character. A context like [listchars] might also be helpful in this situation as a work-around. In fact I asked for [listchars] a couple years ago, but the 'powers that be' at SMSI apparently did not value my suggestion, so it's still not in the language -- and therefore we still do not have a simple way of listing all the characters in a particular string of text. Sure, I could mimic the capabilities of listchars by using getchars and loop and listwords in some kind of work-around, but that's a ridiculous amount of coding just to get [capitalize] to do what it should by default ... The fact is, [capitalize] should be programmed to understand and behave as if individual words are *only* separated by spaces - which is the way it is in the English language nearly all the time, right? But that's not how capitalize is programmed to work! Instead, it also makes any letter that follows =F1 into an uppercase character -- and =F1 is certainly NOT a blank space. And if Glenn is right, it also capitalizes letters following ' which of course this suggests that it also capitalizes letters following any number of other non-blank characters (who actually knows what other characters it uses as delimtiers, anyone?) So basically, I believe that the person at SMSI who was given the task of deciding how [capitalize] should work did it wrong ... and we still do not have an optional 'delimiters' parameter so we can fix his/her mistake ... :( Personally I feel that the default behavior should actually work "as expecte= d". Only blank spaces are used to separate words in nearly all situations in our language. And for other situations, an optional 'delimiters' parameter would be a welcome solution to the problem ... -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
>HTML entities won't help Ken's problem... > >[capitalize]peña[/capitalize] > >shows up as Pe=D1A, as the "n" in ñ gets capitalized, resulting >in Ñ > >The fix would be for WebDNA to support a delimiters param to [capitalize]. > >In the meantime, you could play with listwords, specifying the >delimiter, then capitalizing only the first character. A context like [listchars] might also be helpful in this situation as a work-around. In fact I asked for [listchars] a couple years ago, but the 'powers that be' at SMSI apparently did not value my suggestion, so it's still not in the language -- and therefore we still do not have a simple way of listing all the characters in a particular string of text. Sure, I could mimic the capabilities of listchars by using getchars and loop and listwords in some kind of work-around, but that's a ridiculous amount of coding just to get [capitalize] to do what it should by default ... The fact is, [capitalize] should be programmed to understand and behave as if individual words are *only* separated by spaces - which is the way it is in the English language nearly all the time, right? But that's not how capitalize is programmed to work! Instead, it also makes any letter that follows =F1 into an uppercase character -- and =F1 is certainly NOT a blank space. And if Glenn is right, it also capitalizes letters following ' which of course this suggests that it also capitalizes letters following any number of other non-blank characters (who actually knows what other characters it uses as delimtiers, anyone?) So basically, I believe that the person at SMSI who was given the task of deciding how [capitalize] should work did it wrong ... and we still do not have an optional 'delimiters' parameter so we can fix his/her mistake ... :( Personally I feel that the default behavior should actually work "as expecte= d". Only blank spaces are used to separate words in nearly all situations in our language. And for other situations, an optional 'delimiters' parameter would be a welcome solution to the problem ... -- Sincerely, Kenneth Grome ------------------------------------------------------------- Outsource your WebDNA programming for $18 an hour or less! ------------------------------------------------------------- ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/
Kenneth Grome
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:
[ShowNext] (1997)
SSL PROBLEM (1999)
Am I going senile? (Price recalc based on quantity) (1997)
any idea (2004)
[WebDNA] [replace] bug in v7.0? (2010)
2.1b3 --> way slow (1997)
Is grep not working with umlauts? (2002)
Authorize.Net (2003)
ShipTotal Again (1998)
Form Weirdness (2002)
SQL Query with % (2007)
Search in 2 or more catalogs (1997)
Credit card types (1997)
WC2b15 File Corruption (1997)
Spawn not working (1999)
RE: Signal Raised (1997)
Summing fields (1997)
multi-paragraph fields (1997)
Append File help needed (2000)
NewCart+Search with one click ? (1997)