validation-regex

I have DCT which has a textarea item where I need to check for \n and other word smart characters like —. The content creators enter these characters while copying content from word. I have a CGI reading stuff from this DCR and it breaks when it encounters these special characters.

I just started creating a regex validation code for this field which is like
validation-regex="^[^\n\xA0`\x96]*$"

I am using \x96 for mdash but it doesn't work. The validation works fine for first three characters.

Can anyone provide me with the complete list of characters and there escape sequences which I need to escape in here.

Find more posts tagged with

Comments

kaalraa

I have DCT which has a textarea item where I need to check for \n and other word smart characters like —. The content creators enter these characters while copying content from word. I have a CGI reading stuff from this DCR and it breaks when it encounters these special characters.

I just started creating a regex validation code for this field which is like
validation-regex="^[^\n\xA0`\x96]*$"

I am using \x96 for mdash but it doesn't work. The validation works fine for first three characters.

Can anyone provide me with the complete list of characters and there escape sequences which I need to escape in here.

As you are using a CGI for reading the stuff, I suggest to use methods of CGI lite module.

TeamSite::CGI_lite::escape_html_data(string)

TeamSite::CGI_lite::unescape_html_data(string)

DougD

Try the Unicode value for mdash, \u2014

JoshProx

The unicode escape \u2014 does not work with validation-regex..

ISCBorisB

I have DCT which has a textarea item where I need to check for \n and other word smart characters like —. The content creators enter these characters while copying content from word. I have a CGI reading stuff from this DCR and it breaks when it encounters these special characters.

I just started creating a regex validation code for this field which is like
validation-regex="^[^\n\xA0`\x96]*$"

I am using \x96 for mdash but it doesn't work. The validation works fine for first three characters.

Can anyone provide me with the complete list of characters and there escape sequences which I need to escape in here.

Actually, 0x96 (150) is ndash. mdash is 0x97 (151)

JoshProx

It didn't work. Is there any other way of doing it. I think even if we write code on onchange event it will only be regex.

ISCBorisB

It didn't work. Is there any other way of doing it. I think even if we write code on onchange event it will only be regex.

'Paste' operation works differently in different software. mdash translates to 0x97 in the ASCII formatted
receiver. TS encodes DCR in UTF-8. If you open up Saved DCR as XML File, in Editor's Hex mode you will see that
mdash is saved as 3-bytes UTF-8 symbol, 0xE28094 ( I just tried). In *naive* ASCII it looks like â€”.

I think you'd be better off by validating this sort of things in FormAPI. Validation regex attribute is too
primitive for multi-byte character negation. Something like "^[^â€”]*$" is obviously wrong (it'll fail a phrase
"€ 25" for example), "lookaround" assertions are ignored and "^[^\x{E28094}]*$" won't work within DCT.

Adam Stoller

I have DCT which has a textarea item where I need to check for \n and other word smart characters like —. The content creators enter these characters while copying content from word. I have a CGI reading stuff from this DCR and it breaks when it encounters these special characters.

I just started creating a regex validation code for this field which is like
validation-regex="^[^\n\xA0`\x96]*$"

I am using \x96 for mdash but it doesn't work. The validation works fine for first three characters.

Can anyone provide me with the complete list of characters and there escape sequences which I need to escape in here.

Are you trying to prevent these characters from being saved in the DCR - or are you trying to fix your CGI program to interpret them correctly? Or something else?

You've gotten a bunch of information regarding various different possibilities - but as your needs are not clear from this post, it isn't clear that you've gotten the information you were looking for.