# Okapi Framework - Steps ## URI Conversion Step
- Overview - Parameters |
Steps | Developer's Guide | Okapi Framework

If you are using an Okapi Tool after the M9 release, you should be using the wiki online help:
http://www.opentag.com/okapi/wiki/index.php?title=URI_Conversion_Step

## Overview

This step allows you to convert the translatable content of an input document to and from URI escape notation.

Takes: Filter events
Sends: Filter events

## Parameters

Un-escape the URI escape sequences -- Select this option to convert URI escaped sequences into normal text.

Escape content to URI escape sequences -- Select this option to convert normal text into a text where characters are escaped into URI escape sequences. Which characters get escaped is specified by the list below.

List of the characters to escape -- Check each character you want to be escaped. Note that the character '`%`' is always escaped.

Escape all extended characters -- Check this option to convert all non-ASCII characters to URI escape sequences.

All But Marks -- Click this button to reset the list of the characters to escape to all, except the characters specified as "marks" in RFC 2396 (which are: '`-`', '`_`', '`.`', '`!`', '`~`', '`*`','`'`', '`(`', and '`)`').

All But Marks And Reserved -- Click this button to reset the list of the characters to escape to all, except the characters specified as "marks" in RFC 2396 (which are: '`-`', '`_`', '`.`', '`!`', '`~`', '`*`','`'`', '`(`', and '`)`'.), as well as the ones specified as "reserved" (which are: '`;`', '`/`', '`?`', '`:`', '`@`', '`&`', '`=`', '`+`', '`$`', '`,`').