Re: Bug in capitalize ... ?
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 53483
interpreted = N
texte = Or, if it's something that will occur a lot in the one place, say a 'surname' coming from a database, you could do this: [capitalize][GetChars start=3D1&end=3D1][surname][/GetChars][/capitalize][!] [/!][GetChars start=3D2][surname][/GetChars] Regards, Tim > From: Brian Fries
> Reply-To: (WebDNA Talk) > Date: Fri, 17 Oct 2003 09:02:40 -0700 > To: (WebDNA Talk) > Subject: Re: Bug in capitalize ... ? >=20 > HTML entities won't help Ken's problem... >=20 > [capitalize]peña[/capitalize] >=20 > shows up as Pe=D1A, as the "n" in ñ gets capitalized, resulting in > Ñ >=20 > The fix would be for WebDNA to support a delimiters param to > [capitalize]. >=20 > In the meantime, you could play with listwords, specifying the > delimiter, then capitalizing only the first character. >=20 > - brian >=20 > On Friday, October 17, 2003, at 07:04 AM, John Peacock wrote: >=20 >> Kenneth Grome wrote: >>=20 >>> Why does webdna make the letter 'a' uppercase when I put a >>> [capitalize] context around this word? >>> Pe=F1A >>> The =F1 is definitely not the last letter in the word, which means >>> [capitalize] should make it lowercase, not uppercase. >>=20 >> Letters in Latin-1 are limited to a-zA-Z. "=F1" is an extended ASCII >> character in the Latin-1 character set, and hence fouls up the logic >> of [capitalize]. It is a bug only in the sense that it doesn't do >> what _you_ expected it to do. It is not a bug in the sense that >> anyone who expects extended ASCII characters to be handled >> consistently by all browsers is going to be massively mistaken. >>=20 >> Don't use extended ASCII; always use HTML entities (in this case >> ñ). >>=20 >> John >>=20 >> --=20 >> John Peacock >>=20 > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com > -- >=20 >=20 > ------------------------------------------------------------- > 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/ ------------------------------------------------------------- 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:
Or, if it's something that will occur a lot in the one place, say a 'surname' coming from a database, you could do this: [capitalize][GetChars start=3D1&end=3D1][surname][/GetChars][/capitalize][!] [/!][GetChars start=3D2][surname][/GetChars] Regards, Tim > From: Brian Fries > Reply-To: (WebDNA Talk) > Date: Fri, 17 Oct 2003 09:02:40 -0700 > To: (WebDNA Talk) > Subject: Re: Bug in capitalize ... ? >=20 > HTML entities won't help Ken's problem... >=20 > [capitalize]peña[/capitalize] >=20 > shows up as Pe=D1A, as the "n" in ñ gets capitalized, resulting in > Ñ >=20 > The fix would be for WebDNA to support a delimiters param to > [capitalize]. >=20 > In the meantime, you could play with listwords, specifying the > delimiter, then capitalizing only the first character. >=20 > - brian >=20 > On Friday, October 17, 2003, at 07:04 AM, John Peacock wrote: >=20 >> Kenneth Grome wrote: >>=20 >>> Why does webdna make the letter 'a' uppercase when I put a >>> [capitalize] context around this word? >>> Pe=F1A >>> The =F1 is definitely not the last letter in the word, which means >>> [capitalize] should make it lowercase, not uppercase. >>=20 >> Letters in Latin-1 are limited to a-zA-Z. "=F1" is an extended ASCII >> character in the Latin-1 character set, and hence fouls up the logic >> of [capitalize]. It is a bug only in the sense that it doesn't do >> what _you_ expected it to do. It is not a bug in the sense that >> anyone who expects extended ASCII characters to be handled >> consistently by all browsers is going to be massively mistaken. >>=20 >> Don't use extended ASCII; always use HTML entities (in this case >> ñ). >>=20 >> John >>=20 >> --=20 >> John Peacock >>=20 > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com > -- >=20 >=20 > ------------------------------------------------------------- > 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/ ------------------------------------------------------------- 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/
Tim Robinson
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:
BUG in WebCatalog 4.0.1 on Mac OSX (2000)
Count regular expressions in a file (2007)
WebCat Ad! (2000)
webcat feature request (1997)
two unique banners on one page (1997)
Loss in form (1998)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
problems with 2 tags (1997)
[WriteFile] problems (1997)
Webcat2, WebCommerce, Mod 10 etc. (1997)
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
Search the same field twice? (2004)
Single Link browsing (1997)
[isfile] ? (1997)
Questions To Answer (1997)
Extended [ConvertChars] (1997)
WebDNA Writer Needed (1997)
Wanted: More Math Functions (or, Can You Solve This?) (1997)
Sending emails (went[ot] ) (2002)
Error handling for accountNum (1997)