> For the complete documentation index, see [llms.txt](https://docs.vntranslator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vntranslator.com/advanced/regexp/matching.md).

# Matching

{% hint style="info" %}
Starting from Pro version **0.9.1-alpha**, VNTranslator supports writing native JS RegExp using the syntax: `/Regexp/flags.`

The instructions below describe the old syntax, which is still supported for compatibility.
{% endhint %}

## Syntax 

`["Regexp", "Flags"], [...]`

## Parameters

* **Regexp** \
  A regular expression object
* **Flags**\
  Regular expressions have optional flags that allow for functionality like global searching and case-insensitive searching

| Flag | Description                                                                                                                                                                                                                  |
| ---- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `d`  | Generate indices for substring matches                                                                                                                                                                                       |
| `g`  | Find all matches rather than stopping after the first match                                                                                                                                                                  |
| `i`  | If `u` flag is also enabled, use Unicode case folding                                                                                                                                                                        |
| `m`  | Treat beginning and end characters (`^` and `$`) as working over multiple lines. In other words, match the beginning or end of *each* line (delimited by  or ), not only the very beginning or end of the whole input string |
| `s`  | Allows `.` to match newlines                                                                                                                                                                                                 |
| `u`  | Treat `pattern` as a sequence of Unicode code points                                                                                                                                                                         |

## Return Value

All results matching the complete regular expression will be returned

***

## Examples

```
["[0-9]", "g"], ["[a-zA-Z]+", "g"]
["\\p{sc=Latin}", "gu"]
["[^\\x00-\\x7F]+", "g"]
["[^\\u0000-\\u007F]+", "g"]
["[一-龠]+|[ぁ-ゔ]+|[ァ-ヴー]+|[々〆〤]+|[⺀-⿕]+|[、-〿]+|[ㇰ-ㇿ㈠-㉃㊀-㍿]+", "gmu"]
```


---

# 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.vntranslator.com/advanced/regexp/matching.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.