Re: [WebDNA] Chrome 56 character encoding
This WebDNA talk-list message is from 2017
It keeps the original formatting.
numero = 113424
interpreted = N
texte = 1018 --94eb2c14c872405857054926610e Content-Type: text/plain; charset=UTF-8 Diane, Hi - the characters are all %0B and %1D - this is how WebDNA stores line returns and tabs. The best thing is to strip or convert them before they get added to a database. Anyhow your options here from what I can see are to use: [grep search=%0B|%1D&replace=][intro_copy][/grep] or [grep search=%0B|%1D|%0A&replace=][intro_copy][/grep] i.e. change the order of the grep. Not sure why but the %0A messes the grep up on my system anyway. - Tom --94eb2c14c872405857054926610e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
--------------------------------------------------------- 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 --94eb2c14c872405857054926610e-- .
Associated Messages, from the most recent to the oldest:
| |
- Re: [WebDNA] Chrome 56 character encoding (Tom Duke 2017)
|
1018 --94eb2c14c872405857054926610e Content-Type: text/plain; charset=UTF-8 Diane, Hi - the characters are all %0B and %1D - this is how WebDNA stores line returns and tabs. The best thing is to strip or convert them before they get added to a database. Anyhow your options here from what I can see are to use: [grep search=%0B|%1D&replace=][intro_copy][/grep] or [grep search=%0B|%1D|%0A&replace=][intro_copy][/grep] i.e. change the order of the grep. Not sure why but the %0A messes the grep up on my system anyway. - Tom --94eb2c14c872405857054926610e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable