> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/resources/support/translating-web-pages-using-google-chrome.md).

# Translating Web Pages

The following article will explain how we can browse LSports Support Portal in your native language by using Google Chrome, in fact, you can utilize this method over any other page.

\\

Step 1.

Once the webpage is loaded in the Google Chrome browser, Right-Click on your mouse button, and in the menu click on Translate.

![](https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-c0d8562cf2173ca96d4d9863be51c6ee64316021%2Fsupport-chrome-ext-01.png?alt=media)

\*The function will automatically suggest to translate for the last selected language.

Step 2.

Once 'Translate' was clicked, a pop-up window will be shown next to your Address Bar\
![](https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-b1c717d47cec503ef6b7833d5c922edf712ec2e9%2Fsupport-chrome-ext-02.png?alt=media)

Step 3.

Click on the 3 dots on the right and you can select for the page to be translated to any other language.\
![](https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-0fff38fbd8b66d326431726568ab249c1120ff53%2Fsupport-chrome-ext-03.png?alt=media)

Here's a video of the entire process:

\\


---

# 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.lsports.eu/u/resources/support/translating-web-pages-using-google-chrome.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.