Re: [WebDNA] Upper ASCII and charset [OT]

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112772
interpreted = N
texte = 355 Alright, to wrap this up.. PHP has some good tools to handle my exact = problem, namely: Get_HTML_Translation_Table() If anyone is interested, find the paragraph in the article below, = entitled: "Copy-and-Paste =46rom Microsoft Word=AE" http://iconoun.com/articles/collisions/ Another possible fix from that article: utf8_encode() It would sure be handy for WSC to look into replicating those two PHP = functions. If I get time, I may try it myself.=20 Oh, precious time.=20 Cheers, Donovan P.S. that article is a good read in general.=20 On May 20, 2016, at 7:34 AM, Donovan Brooke wrote: > Hi Tom, >=20 > Well that =91splain=92s it.=20 >=20 > Unfortunately I=92m dealing with legacy text (lots of it) that was = copy/pasted from word (most likely) many years ago. Maybe I=92ll find = the time to write > a script to change all of it someday :-/=20 >=20 > Thanks, > D >=20 >=20 >=20 > On May 20, 2016, at 3:18 AM, Tom Duke wrote: >=20 >> Donovan, >>=20 >> Your hex codes are wrong - for UTF8 anyhow: >>=20 >> http://revolutionaries.ie/testspace/test8.tmpl >>=20 >> - Tom >>=20 >>=20 >>=20 >> >> >> >> >> >> >> 
>> Em Dash:>> Donovan's hex: [Unurl]%20%97%20[/Unurl]>> character: =97>> correct hex: [url]=97[/url]>>=20>> Horizontal Ellipsis:>> Donovan's hex: [Unurl]%85[/Unurl]>> character: =85>> correct hex: [url]=85[/url]>>
>> >> >>=20 >>=20 >>=20 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> Digital Revolutionaries >> 1st Floor, Castleriver House >> 14-15 Parliament Street >> Temple Bar,Dublin 2 >> Ireland >> ---------------------------------------------- >> [t]: + 353 1 4403907 >> [e]: >> [w]: >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> On 19 May 2016 at 21:57, Tom Duke wrote: >> Donovan, >>=20 >> Ok - I'll test it tomorrow. But it suggests you may have a = mimeheader problem. >>=20 >> That *should* be working ok. >>=20 >> - Tom >>=20 >>=20 >> Sent from my iPhone >>=20 >>> On 19 May 2016, at 20:43, Donovan Brooke wrote: >>>=20 >>> Unicode UTF-8 / Unix (LF) >>>=20 >>>=20 >>>=20 >>>> On May 19, 2016, at 2:30 PM, Tom Duke = wrote: >>>>=20 >>>> Donovan, >>>>=20 >>>> What encoding is the HTML file saved in? >>>>=20 >>>> - Tom >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> Sent from my iPhone >>>>=20 >>>>> On 19 May 2016, at 20:16, Donovan Brooke wrote: >>>>>=20 >>>>> 500 domains in a database of ascii text ;-) >>>>>=20 >>>>> The temporary solution was simply getting rid of the meta tag.. = but I would rather want to be compliant to today=92s standards. >>>>>=20 >>>>> D >>>>>=20 >>>>>=20 >>>>>> On May 19, 2016, at 1:44 PM, Francisco Hirsch = wrote: >>>>>>=20 >>>>>> Why not use the characters directly? >>>>>>=20 >>>>>> Francisco Hirsch >>>>>> -- >>>>>> Lic. Francisco Hirsch >>>>>> http://www.fiscaldemesa.com.ar >>>>>>=20 >>>>>>> On 19 may 2016, at 13:11, Donovan Brooke = wrote: >>>>>>>=20 >>>>>>> Hello, >>>>>>>=20 >>>>>>> hoping someone can educate me on character sets. >>>>>>>=20 >>>>>>> I=92m using this file, which has some higher ASCII characters: >>>>>>>=20 >>>>>>> ----- >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 
>>>>>>> Em Dash: [Unurl]%20%97%20[/Unurl]>>>>>>>=20>>>>>>> Horizontal Elips: [Unurl]%85[/Unurl]>>>>>>>
>>>>>>> >>>>>>> >>>>>>> =97=97 >>>>>>>=20 >>>>>>> This doesn=92t parse as-is.. but when you take out: , then it parses. >>>>>>>=20 >>>>>>> The problem is that utf-8 is the suggested charset. >>>>>>> https://www.w3.org/International/questions/qa-choosing-encodings >>>>>>>=20 >>>>>>> Any thoughts? >>>>>>>=20 >>>>>>> Donovan >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> 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 >>>>>>> Bug Reporting: support@webdna.us >>>>>> --------------------------------------------------------- >>>>>> 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 >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> 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 >>>>> Bug Reporting: support@webdna.us >>>> --------------------------------------------------------- >>>> 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 >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> 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 >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- 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 Bug Reporting: = support@webdna.us >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us --------------------------------------------------------- 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 Bug Reporting: support@webdna.us . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Upper ASCII and charset [OT] (Donovan Brooke 2016)
  2. Re: [WebDNA] Upper ASCII and charset [OT] (Donovan Brooke 2016)
  3. Re: [WebDNA] Upper ASCII and charset [OT] (Donovan Brooke 2016)
  4. Re: [WebDNA] Upper ASCII and charset [OT] (Tom Duke 2016)
  5. Re: [WebDNA] Upper ASCII and charset [OT] (Tom Duke 2016)
  6. Re: [WebDNA] Upper ASCII and charset [OT] (Donovan Brooke 2016)
  7. Re: [WebDNA] Upper ASCII and charset [OT] (Tom Duke 2016)
  8. Re: [WebDNA] Upper ASCII and charset [OT] (Donovan Brooke 2016)
  9. Re: [WebDNA] Upper ASCII and charset [OT] (Francisco Hirsch 2016)
  10. [WebDNA] Upper ASCII and charset [OT] (Donovan Brooke 2016)
355 Alright, to wrap this up.. PHP has some good tools to handle my exact = problem, namely: Get_HTML_Translation_Table() If anyone is interested, find the paragraph in the article below, = entitled: "Copy-and-Paste =46rom Microsoft Word=AE" http://iconoun.com/articles/collisions/ Another possible fix from that article: utf8_encode() It would sure be handy for WSC to look into replicating those two PHP = functions. If I get time, I may try it myself.=20 Oh, precious time.=20 Cheers, Donovan P.S. that article is a good read in general.=20 On May 20, 2016, at 7:34 AM, Donovan Brooke wrote: > Hi Tom, >=20 > Well that =91splain=92s it.=20 >=20 > Unfortunately I=92m dealing with legacy text (lots of it) that was = copy/pasted from word (most likely) many years ago. Maybe I=92ll find = the time to write > a script to change all of it someday :-/=20 >=20 > Thanks, > D >=20 >=20 >=20 > On May 20, 2016, at 3:18 AM, Tom Duke wrote: >=20 >> Donovan, >>=20 >> Your hex codes are wrong - for UTF8 anyhow: >>=20 >> http://revolutionaries.ie/testspace/test8.tmpl >>=20 >> - Tom >>=20 >>=20 >>=20 >> >> >> >> >> >> >> 
>> Em Dash:>> Donovan's hex: [unurl]%20%97%20[/Unurl]>> character: =97>> correct hex: [url]=97[/url]>>=20>> Horizontal Ellipsis:>> Donovan's hex: [unurl]%85[/Unurl]>> character: =85>> correct hex: [url]=85[/url]>>
>> >> >>=20 >>=20 >>=20 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> Digital Revolutionaries >> 1st Floor, Castleriver House >> 14-15 Parliament Street >> Temple Bar,Dublin 2 >> Ireland >> ---------------------------------------------- >> [t]: + 353 1 4403907 >> [e]: >> [w]: >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> On 19 May 2016 at 21:57, Tom Duke wrote: >> Donovan, >>=20 >> Ok - I'll test it tomorrow. But it suggests you may have a = mimeheader problem. >>=20 >> That *should* be working ok. >>=20 >> - Tom >>=20 >>=20 >> Sent from my iPhone >>=20 >>> On 19 May 2016, at 20:43, Donovan Brooke wrote: >>>=20 >>> Unicode UTF-8 / Unix (LF) >>>=20 >>>=20 >>>=20 >>>> On May 19, 2016, at 2:30 PM, Tom Duke = wrote: >>>>=20 >>>> Donovan, >>>>=20 >>>> What encoding is the HTML file saved in? >>>>=20 >>>> - Tom >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>> Sent from my iPhone >>>>=20 >>>>> On 19 May 2016, at 20:16, Donovan Brooke wrote: >>>>>=20 >>>>> 500 domains in a database of ascii text ;-) >>>>>=20 >>>>> The temporary solution was simply getting rid of the meta tag.. = but I would rather want to be compliant to today=92s standards. >>>>>=20 >>>>> D >>>>>=20 >>>>>=20 >>>>>> On May 19, 2016, at 1:44 PM, Francisco Hirsch = wrote: >>>>>>=20 >>>>>> Why not use the characters directly? >>>>>>=20 >>>>>> Francisco Hirsch >>>>>> -- >>>>>> Lic. Francisco Hirsch >>>>>> http://www.fiscaldemesa.com.ar >>>>>>=20 >>>>>>> On 19 may 2016, at 13:11, Donovan Brooke = wrote: >>>>>>>=20 >>>>>>> Hello, >>>>>>>=20 >>>>>>> hoping someone can educate me on character sets. >>>>>>>=20 >>>>>>> I=92m using this file, which has some higher ASCII characters: >>>>>>>=20 >>>>>>> ----- >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 
>>>>>>> Em Dash: [unurl]%20%97%20[/Unurl]>>>>>>>=20>>>>>>> Horizontal Elips: [unurl]%85[/Unurl]>>>>>>>
>>>>>>> >>>>>>> >>>>>>> =97=97 >>>>>>>=20 >>>>>>> This doesn=92t parse as-is.. but when you take out: , then it parses. >>>>>>>=20 >>>>>>> The problem is that utf-8 is the suggested charset. >>>>>>> https://www.w3.org/International/questions/qa-choosing-encodings >>>>>>>=20 >>>>>>> Any thoughts? >>>>>>>=20 >>>>>>> Donovan >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> --------------------------------------------------------- >>>>>>> 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 >>>>>>> Bug Reporting: support@webdna.us >>>>>> --------------------------------------------------------- >>>>>> 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 >>>>>> Bug Reporting: support@webdna.us >>>>>=20 >>>>> --------------------------------------------------------- >>>>> 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 >>>>> Bug Reporting: support@webdna.us >>>> --------------------------------------------------------- >>>> 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 >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> 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 >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- 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 Bug Reporting: = support@webdna.us >=20 > --------------------------------------------------------- > 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 > Bug Reporting: support@webdna.us --------------------------------------------------------- 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 Bug Reporting: support@webdna.us . Donovan Brooke

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:

breaking & sorting (2000) Problems getting parameters passed into email. (1997) WebCat2 - Getting to the browser's username/password data (1997) WebCat & WebTen (1997) RE: (OFF TOPIC) System 8.5.1 FINDER ERROR (1999) Multiple Pulldowns (1997) using tcpconnect with ups.com (2001) Secure server question (1997) [WebDNA] Still having problems (2008) GuestBook example (1997) [WebDNA] test (2010) b12 cannot limit records returned and more. (1997) Bug Report, maybe (1997) [WebDNA] WebDNA Development server (2018) WC2b15 File Corruption (1997) PCS Frames (1997) Multipart Form - Ascertain File Type (2007) Squares instead of spaces (2001) upgrade? (1997) Further on formula.db failure to calculate shipCost (1997)