> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/ida-9.3/ida-actions/setstrlitstyle.md).

# SetStrlitStyle

## Description

Setup string literal style. With this dialog you can setup string styles and also create a new string immediately at the current location.

The following string styles are defined:

* C-style (zero-terminated)
* DOS style ($ terminated)
* Pascal style (one byte length prefix)
* Wide pascal (two-byte length prefix)
* Delphi (four-byte length prefix)
* Unicode (UTF-16)
* Unicode pascal style (two-byte length prefix)
* Unicode wide pascal style (four-byte length prefix)
* Character terminated

If you select "character terminated" string style then you may specify up to 2 termination characters. The string will be terminated by any of these characters. If the second character is equal to 0, then it is ignored. In IDA Qt you can also set a specific encoding to be used to display the string, or change the defaults for all strings.

### String encodings

IDA Qt can display program strings using different encodings. You can specify default encodings for all strings or override the encoding of a specific string.

The following encodings can be used:

* `<default>` - the default encoding for this string type (8-bit or 16-bit)
* `<no conversion>` - the string bytes are printed using the current system encoding (after translating with XlatAsciiOutput array in the configuration file).
* Windows codepages (e.g., 866, CP932, windows-1251)
* Charset names (e.g., Shift-JIS, UTF-8, Big5)

You can add new encodings to the list using the context menu item Insert (Ins hotkey).

On Linux/OS X, you can run "iconv -l" to see the available encodings. Please note that some encodings are not supported on all systems.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hex-rays.com/ida-9.3/ida-actions/setstrlitstyle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.