> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/9.3-administer/troubleshooting-overview-cp/pentaho-server-issues/report-parameters-that-include-accented-characters.md).

# Report parameters that include accented characters

If you run a report containing parameters with accented characters, you may get an error message which reads, "This parameter value is of an invalid value."

To avoid this error message, modify the Tomcat server to include accented character support. This modification is especially necessary if you plan to use Spanish, French, or any other language that use accented character sets.

The following example shows how to implement accented character set support:

1. Stop the Tomcat service.

   ```
   sudo /etc/init.d/tomcat stop
   ```
2. Open the `/tomcat/server/conf/server.xml` file in a text editor.
3. Locate each `Connector` node (typically, there are four in a default Tomcat configuration).

   Add a **URIEncoding="UTF-8"** parameter to it, as shown in the following sample code block:

   ```xml
   <Connector URIEncoding="UTF-8" port="8080" protocol="HTTP/1.1"
                  connectionTimeout="20000"
                  redirectPort="8443" />
   ```
4. Save and close the file, then restart the Tomcat service.

   ```
   sudo /etc/init.d/tomcat start
   ```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-admin/9.3-administer/troubleshooting-overview-cp/pentaho-server-issues/report-parameters-that-include-accented-characters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
