Re: [WebDNA] Foreign characters (2009)
This WebDNA talk-list message is from 2009
It keeps the original formatting.
numero = 102329
interpreted = N
texte = --Apple-Mail-4-480600466 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable This is all closely related to another problem I have. I'm working on =20= a database of munitions (believe it or not). I need to store the =20 symbols stamped or embossed on the bottom of cartridges. These strings =20= of characters are alphanumeric, but have occasional symbols and =20 decorations outside the usual umlauts and grave marks. Sometimes =20 there's a letter surrounded by the shape of a shield. Some letters are =20= contained in a square box. I need a system to establish what decoration appears and where, and I =20= need that system to still allow users to be able to search those =20 strings of characters as text. The logical necessity is to be able to enter the typable characters in =20= the same order, ignoring any decorations that aren't readily typable. =20= (Typable is my new non-word of the day). Chris, I think your approach would work just right because it allows =20 the string to match, regardless of any decorations, I can create =20 custom decorations, and I can do multiple instances per string: mystring(2sheildSymbol)(6goofytriangle)(7toyboat) The only thing I need to figure out is how to display a special symbol =20= within a string, where there's just a special symbol and no letter: =20 mystringpart1_mystringpart2 where the underscore is something like an =20= inverted triangle. I need something like mystring(3*invertedtriangle) =20= where the asterisk indicates that the symbol appears after the third =20 character, instead of around it. I can't help but thing this is only a logical extension of how grep =20 works, if only I knew grep better. Pat On Apr 1, 2009, at 7:11 PM, christophe.billiottet@webdna.us wrote: > if the database content shows "caf=E9" and your user searches for =20 > "cafe", i see a trick that could save your day: code the accented =20 > caracters the old way, meaning the letter from one side, the accent =20= > on the other: http://www.w3schools.com/tags/ref_entities.asp > > you would have > á for =E1 > è for =E8 > é for =E9 > etc... > > > If you look for caf=E9, make your search form remove the accent in =20 > order to actually search for "cafe" (without accent). Then filter =20 > the db content to remove the "&" and the accent itself (acute; =20 > agrave;...) using [GetChars start=3D2&end=3D2][FindString =20 > Source=3Dcafé&Find=3D\&][/GetChars]. You could also use grep = for =20 > this. > > > Another idea: make your own accent coding in the database, moving =20 > the accent at the end of the word: > > caf=E9 would be cafe(4acute) meaning "acute accent on the fourth =20 > caracter" > marf=EDl would be marfil(5acute) > > Then just remove the accent of the searched word, since it exists =20 > without accent in your db. To show the searching results, you will =20 > have to reconvert your coding method into a readable result. > > And what about the pinyin method? each accent has a number: =E9 is e2, = =20 > =E1 is a2 while =E8 would be e1 and =E0 would be a1. > > Well, there is a number of different ways to solve this. WebDNA is =20 > flexible enough to experiment... ;-) but we cannot include this kind =20= > of very specific features into WebDNA code: the product would become =20= > extremely complicated while we want to keep it simple, with powerful =20= > but unspecialized contexts. > > - chris > > > > On Apr 1, 2009, at 19:26, Cristi=E1n Tapia wrote: > >> Thanks for all the hints! >> >> The solution Chris mentioned works perfectly if you search for =20 >> "caf=E9", because it removes the accented character and also looks =20= >> for the word "cafe". But, as all the words in my client's database =20= >> are properly spelled and you won't find any record with "cafe" but =20= >> "caf=E9" in it, if the user types it incorrectly (without the =20 >> accented character), which happens a lot, it won't return any =20 >> records. >> >> If I try to make Chris's solution to work backwards, it will look =20 >> for c=E1f=E9 or m=E1m=E1 or s=F3l=FAc=ED=F3n (it will put an accent = in every vowel) =20 >> and there's no way I can tell the engine where the accented =20 >> character should go, so I'm stuck again. >> >> I wish future versions of WebDNA could work the same way Google =20 >> handles this kind of issue (search for the word regardless of =20 >> accented characters). Is there any chance? >> >> Regards, >> --------------------------------------------------- >> Cristi=E1n Tapia Smith >> Lemon Internet S.A. >> ctapia@lemongroup.cl >> http://www.lemongroup.cl >> Antonia L=F3pez de Bello 172, Of. 801 >> Fono: +562-7377682 >> Santiago, Chile. >> >> >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list
. >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> old archives: http://dev.webdna.us/TalkListArchive/ > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ --Apple-Mail-4-480600466 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGGTCCAtIw ggI7oAMCAQICEBmvvAg5L6PclE8ruwo/gMYwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDkyNzAxMTg1M1oXDTA5MDkyNzAxMTg1 M1owPjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEbMBkGCSqGSIb3DQEJARYMcG1A d2ViZG5hLnVzMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtb7ZYYJV7sbgqxdgpBU/ qCRsIJYGNIo40L9odKmo6Y/mPBybeSry8KefqmuWoBXxc6xCvSSJDWFcb2sZ+TkedZrdxvtoL1pH NjDZNe2ow+RCNUvJcQd1+ASzh0J4QLHnNyoMY3zuCQwqM6hK5gU4AlpOSITekksSFuGXBdJTjSeI gIpZFTTrd1c/Zv7miT9gO5UmHiyDClKP8oX31YFlb3q9EM2p8WQzb2Ce2M9kokCs8ZnhT+fRNc/Q 9lc4RJtEuf3zynvg0cCbf71pgoC0Zepsop466jrvc08MsxxzRJDmjw20ci/3ltk+iAcD3TchYppw yX4HZhjrrZXcOMBMkQIDAQABoykwJzAXBgNVHREEEDAOgQxwbUB3ZWJkbmEudXMwDAYDVR0TAQH/ BAIwADANBgkqhkiG9w0BAQUFAAOBgQCBMxqOGsLwOxtLQ8YLvOQOym8UQyB0CiF0Dpd0oOA+hjD5 n9A1eileTd8OdkdPIb+der2Kw42N/UKARNSSkmn1hhKrgwTNYLyXFNlB+TJ2YvG13B27d4EaUdSn 2KWKDKG4w14lQSO9y+RTjMSuYi4kbeI50QHLZsTZDO3OhNcKjzCCAz8wggKooAMCAQICAQ0wDQYJ KoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNV BAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRp ZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3 dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjA dQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn 8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sC AwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9j cmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjAp BgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6 GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341Yh eILcIRk13iSx0x1G/11fZU8xggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgSXNzdWluZyBDQQIQGa+8CDkvo9yUTyu7Cj+AxjAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA0MDIwMDQ4NDJaMCMGCSqGSIb3 DQEJBDEWBBQ/8k7yI8JP+V75mSI8pv5k6RS7cTCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQG EwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhh d3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEBmvvAg5L6PclE8ruwo/gMYwgYcGCyqG SIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EC EBmvvAg5L6PclE8ruwo/gMYwDQYJKoZIhvcNAQEBBQAEggEArcsVh+gwdjluJfrbfyJ0KBfY0u1Q L8hz0brZbmJtoCS3KawyYLqzAZxoyE0Sq2wdXI84JYWaRlGa3vT732aIvgSC4daXeE9YG1NXaCJW mIZ7vaYyVQ/KGu8VT7rDmpxgXvQqwED8y4v8qeqPiVDyaWsGI24CEvdr6o0irMBkh/8gWagMDKb5 xnPOd0Vt+DZgC6H5Lapb83Rk7ny4Gb60FQRPvcCIZWC2CLGbg18/BBWbzJ9N0gUzj6B+bIsQJwUU UtyqbvzCetj9DYUW8BvhwsW8R3j93VZEu8ZNoXm+Y4zqAp+u26k7f5j44RZTBhz2BQcpoBe7YRTc ogDz7lFIMAAAAAAAAA== --Apple-Mail-4-480600466--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-4-480600466 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable This is all closely related to another problem I have. I'm working on =20= a database of munitions (believe it or not). I need to store the =20 symbols stamped or embossed on the bottom of cartridges. These strings =20= of characters are alphanumeric, but have occasional symbols and =20 decorations outside the usual umlauts and grave marks. Sometimes =20 there's a letter surrounded by the shape of a shield. Some letters are =20= contained in a square box. I need a system to establish what decoration appears and where, and I =20= need that system to still allow users to be able to search those =20 strings of characters as text. The logical necessity is to be able to enter the typable characters in =20= the same order, ignoring any decorations that aren't readily typable. =20= (Typable is my new non-word of the day). Chris, I think your approach would work just right because it allows =20 the string to match, regardless of any decorations, I can create =20 custom decorations, and I can do multiple instances per string: mystring(2sheildSymbol)(6goofytriangle)(7toyboat) The only thing I need to figure out is how to display a special symbol =20= within a string, where there's just a special symbol and no letter: =20 mystringpart1_mystringpart2 where the underscore is something like an =20= inverted triangle. I need something like mystring(3*invertedtriangle) =20= where the asterisk indicates that the symbol appears after the third =20 character, instead of around it. I can't help but thing this is only a logical extension of how grep =20 works, if only I knew grep better. Pat On Apr 1, 2009, at 7:11 PM, christophe.billiottet@webdna.us wrote: > if the database content shows "caf=E9" and your user searches for =20 > "cafe", i see a trick that could save your day: code the accented =20 > caracters the old way, meaning the letter from one side, the accent =20= > on the other: http://www.w3schools.com/tags/ref_entities.asp > > you would have > á for =E1 > è for =E8 > é for =E9 > etc... > > > If you look for caf=E9, make your search form remove the accent in =20 > order to actually search for "cafe" (without accent). Then filter =20 > the db content to remove the "&" and the accent itself (acute; =20 > agrave;...) using [GetChars start=3D2&end=3D2][FindString =20 > Source=3Dcafé&Find=3D\&][/GetChars]. You could also use grep = for =20 > this. > > > Another idea: make your own accent coding in the database, moving =20 > the accent at the end of the word: > > caf=E9 would be cafe(4acute) meaning "acute accent on the fourth =20 > caracter" > marf=EDl would be marfil(5acute) > > Then just remove the accent of the searched word, since it exists =20 > without accent in your db. To show the searching results, you will =20 > have to reconvert your coding method into a readable result. > > And what about the pinyin method? each accent has a number: =E9 is e2, = =20 > =E1 is a2 while =E8 would be e1 and =E0 would be a1. > > Well, there is a number of different ways to solve this. WebDNA is =20 > flexible enough to experiment... ;-) but we cannot include this kind =20= > of very specific features into WebDNA code: the product would become =20= > extremely complicated while we want to keep it simple, with powerful =20= > but unspecialized contexts. > > - chris > > > > On Apr 1, 2009, at 19:26, Cristi=E1n Tapia wrote: > >> Thanks for all the hints! >> >> The solution Chris mentioned works perfectly if you search for =20 >> "caf=E9", because it removes the accented character and also looks =20= >> for the word "cafe". But, as all the words in my client's database =20= >> are properly spelled and you won't find any record with "cafe" but =20= >> "caf=E9" in it, if the user types it incorrectly (without the =20 >> accented character), which happens a lot, it won't return any =20 >> records. >> >> If I try to make Chris's solution to work backwards, it will look =20 >> for c=E1f=E9 or m=E1m=E1 or s=F3l=FAc=ED=F3n (it will put an accent = in every vowel) =20 >> and there's no way I can tell the engine where the accented =20 >> character should go, so I'm stuck again. >> >> I wish future versions of WebDNA could work the same way Google =20 >> handles this kind of issue (search for the word regardless of =20 >> accented characters). Is there any chance? >> >> Regards, >> --------------------------------------------------- >> Cristi=E1n Tapia Smith >> Lemon Internet S.A. >> ctapia@lemongroup.cl >> http://www.lemongroup.cl >> Antonia L=F3pez de Bello 172, Of. 801 >> Fono: +562-7377682 >> Santiago, Chile. >> >> >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> old archives: http://dev.webdna.us/TalkListArchive/ > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ --Apple-Mail-4-480600466 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGGTCCAtIw ggI7oAMCAQICEBmvvAg5L6PclE8ruwo/gMYwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDkyNzAxMTg1M1oXDTA5MDkyNzAxMTg1 M1owPjEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEbMBkGCSqGSIb3DQEJARYMcG1A d2ViZG5hLnVzMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtb7ZYYJV7sbgqxdgpBU/ qCRsIJYGNIo40L9odKmo6Y/mPBybeSry8KefqmuWoBXxc6xCvSSJDWFcb2sZ+TkedZrdxvtoL1pH NjDZNe2ow+RCNUvJcQd1+ASzh0J4QLHnNyoMY3zuCQwqM6hK5gU4AlpOSITekksSFuGXBdJTjSeI gIpZFTTrd1c/Zv7miT9gO5UmHiyDClKP8oX31YFlb3q9EM2p8WQzb2Ce2M9kokCs8ZnhT+fRNc/Q 9lc4RJtEuf3zynvg0cCbf71pgoC0Zepsop466jrvc08MsxxzRJDmjw20ci/3ltk+iAcD3TchYppw yX4HZhjrrZXcOMBMkQIDAQABoykwJzAXBgNVHREEEDAOgQxwbUB3ZWJkbmEudXMwDAYDVR0TAQH/ BAIwADANBgkqhkiG9w0BAQUFAAOBgQCBMxqOGsLwOxtLQ8YLvOQOym8UQyB0CiF0Dpd0oOA+hjD5 n9A1eileTd8OdkdPIb+der2Kw42N/UKARNSSkmn1hhKrgwTNYLyXFNlB+TJ2YvG13B27d4EaUdSn 2KWKDKG4w14lQSO9y+RTjMSuYi4kbeI50QHLZsTZDO3OhNcKjzCCAz8wggKooAMCAQICAQ0wDQYJ KoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNV BAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRp ZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3 dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjA dQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn 8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sC AwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9j cmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjAp BgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6 GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341Yh eILcIRk13iSx0x1G/11fZU8xggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgSXNzdWluZyBDQQIQGa+8CDkvo9yUTyu7Cj+AxjAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG 9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wOTA0MDIwMDQ4NDJaMCMGCSqGSIb3 DQEJBDEWBBQ/8k7yI8JP+V75mSI8pv5k6RS7cTCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQG EwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhh d3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEBmvvAg5L6PclE8ruwo/gMYwgYcGCyqG SIb3DQEJEAILMXigdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EC EBmvvAg5L6PclE8ruwo/gMYwDQYJKoZIhvcNAQEBBQAEggEArcsVh+gwdjluJfrbfyJ0KBfY0u1Q L8hz0brZbmJtoCS3KawyYLqzAZxoyE0Sq2wdXI84JYWaRlGa3vT732aIvgSC4daXeE9YG1NXaCJW mIZ7vaYyVQ/KGu8VT7rDmpxgXvQqwED8y4v8qeqPiVDyaWsGI24CEvdr6o0irMBkh/8gWagMDKb5 xnPOd0Vt+DZgC6H5Lapb83Rk7ny4Gb60FQRPvcCIZWC2CLGbg18/BBWbzJ9N0gUzj6B+bIsQJwUU UtyqbvzCetj9DYUW8BvhwsW8R3j93VZEu8ZNoXm+Y4zqAp+u26k7f5j44RZTBhz2BQcpoBe7YRTc ogDz7lFIMAAAAAAAAA== --Apple-Mail-4-480600466--
Patrick McCormick
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:
About WebCatalog and iTools 7 (2003)
WebCat with WebTen (1998)
[append] vs. [appendfile] delta + question? (1997)
[WebDNA] Ping....testing....1..2..3.. (2009)
Trouble with formula.db (1997)
[cart] Taxrate - seriously .. (2002)
Upgrade to 4.0 (2001)
beta 6 on OSX wierdness | more (2000)
Line items in table cells (1997)
Newbie Tax Question (1997)
help needed: Non-english characters in WebCatalog (1997)
Include Troubles (1998)
WebCat2 - [format thousands] (1997)
911: testing if the field is empty (2000)
WebCatalog 4.0.1 has been released! (2000)
GD Scumbucket Spammer (2004)
Maybe off topic but how to charge (1997)
Associative lookup style? + bit more (1997)
Summing fields (1997)
Accepting Credit Cards Online (1999)