def escape_javascript_string(<EOL>text,<EOL>escape_for_html=True,<EOL>escape_quote_for_html=False,<EOL>escape_CDATA=True,<EOL>escape_script_tag_with_quote='<STR_LIT:">'):
if escape_quote_for_html:<EOL><INDENT>text = text.replace('<STR_LIT:">', '<STR_LIT>')<EOL><DEDENT>if escape_for_html:<EOL><INDENT>text = cgi.escape(text)<EOL><DEDENT>elif escape_CDATA:<EOL><INDENT>text = text.replace('<STR_LIT>', '<STR_LIT>')<EOL><DEDENT>text = json.dumps(text)[<NUM_LIT:1>:-<NUM_LIT:1>].replace("<STR_LIT:'>", "<STR_LIT>")<EOL>if not escape_for_html and escape_script_tag_with_quote:<EOL><INDENT>text = RE_CLOSING_SCRIPT_TAG.sub(<EOL>'''<STR_LIT>''' % {'<STR_LIT:q>': escape_script_tag_with_quote}, text)<EOL><DEDENT>return text<EOL>
Escape text in order to be used as Javascript string in various
    context.

    Examples::
    >>> text = '''"Are you a Munchkin?" asked Dorothy.
"No, but I am their friend"'''
    >>> escape_javascript_string(text)
    >>> \\"&quot;Are you a Munchkin?\\" asked Dorothy.\\n\\"No, but I am their friend\\"'

    The returned string can be enclosed either in single or double
    quotes delimiters.

    THE FUNCTION ASSUME THAT YOU HAVE ALREDADY WASHED THE STRING FROM
    UNSAFE CONTENT, according to the context you plan to use the
    string. The function will just make sure that the string will not
    break you Javascript/HTML code/markup.

    If you plan to include the string inside the body of an HTML page,
    you will probably want to set C{escape_for_html} to True, in order
    to produce XHTML-valid pages when the input string contain
    characters such as < , > and &.

    Furthermore if you plan to include the string as part of a tag
    attribute (for eg. <a href="#" onclick="foo&quot;bar"), you might
    want to set C{escape_quote_for_html} to True.

    If you plan to include the string inside the body of an HTML page,
    enclosed by CDATA delimiters, then you would *not* need to escape
    HTML tags. Using CDATA delimeters enables to include Javascript
    strings meant to refer to HTML tags (eg. in case you would like to
    manipulate the DOM tree to add new nodes to the page), which would
    not be possible when escaping the HTML. For eg.:
        /*<![CDATA[*/
            document.getElementById('foo').innerHTML = '<p>bar</p>'
        /*]]>*/
    In this case you will probably want to set C{escape_CDATA} to True
    in order to produce an XHTML-valid document, in case a closing
    CDATA delimeter is in your input string. Parameter C{escape_CDATA}
    is not considered when C{escape_for_html} is set to True.

    Note that CDATA delimiters might be automatically added by the
    browser, based on the content-type used to serve the page.

    When C{escape_for_html} is set to False, whatever option is chosen
    for C{escape_CDATA}, the string must not contain a '</script>' tag
    (apparently...). The only option to keep this '</script>' tag (if
    you need it) is to split it, which requires to know which quote
    delimiter your plan to use. For eg:

    Examples::
    >>> text = '''foo</script>bar'''
    >>> val = escape_javascript_string(text, escape_for_html=False, escape_script_tag_with_quote='"')
    >>> 'foo</scr"+"ipt>bar'
    >>> mycode = '''alert("%s")''' % val

    C{escape_script_tag_with_quote} is not considered when
    C{escape_for_html} is set to True.

    If you are planning to return the string as part of a pure
    Javascript document, then you should in principle set both
    C{escape_for_html} and C{escape_CDATA} to False, and
    C{escape_script_tag_with_quote} to None.

    @param text: string to be escaped
    @param escape_for_html: if True, also escape input for HTML
    @param escape_CDATA: if True, escape closing CDATA tags (when C{escape_for_html} is False)
    @escape_script_tag_with_quote: which quote will be used to delimit your string, in case you must wash, but keep, C{</script>} tag (when C{escape_for_html} is False)