Skip to content

Commit 585acf9

Browse files
authored
Merge pull request #783 from AdguardTeam/update-translations
Update translations
2 parents a7a0e6b + 9fe39a4 commit 585acf9

File tree

175 files changed

+3529
-649
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

175 files changed

+3529
-649
lines changed

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -598,11 +598,9 @@ On Motorola devices, there are four key configurations to ensure that AdGuard wo
598598

599599
1. Allow background usage:
600600

601-
- Go to **Settings → Apps** and find **AdGuard**
602-
- Open **App battery usage**
603-
- Enable **Allow background battery usage**
604-
- Tap the option with the toggle
605-
- Set battery usage to **Unrestricted**
601+
- Stop AdGuard protection and close the AdGuard app
602+
- Go to **Settings → Apps → App battery usage** and find AdGuard
603+
- Enable **Allow background usage** or select **Unrestricted**, depending on your Android version
606604

607605
1. Remove background activity restrictions:
608606

@@ -614,10 +612,24 @@ On Motorola devices, there are four key configurations to ensure that AdGuard wo
614612

615613
1. Manage background apps:
616614

617-
- Go to **Settings**, then type **Managing background apps** in the search bar
618-
- Find **AdGuard** and enable the toggle to allow the app to run in the background
615+
- Go to **Settings → Battery → Background app use**
616+
- Enable the **Manage background apps** option
617+
- In the resulting menu, select the **Apps** tab
618+
- Find **AdGuard** in the list and tap it
619+
- In the **Optimize battery use** dialog, select **Always allow**
620+
621+
![Always allow *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/motorolla-background-app-use.png)
619622

620623
1. Disable Adaptive Battery:
621624

622625
- Go to **Settings → Battery**
623626
- Turn off the **Adaptive Battery** option
627+
628+
## ZTE
629+
630+
ZTE devices functioning under the MyOS operating system have an aggressive approach to background processes. Follow these steps to prevent AdGuard from being closed automatically by AI control:
631+
632+
- Go to **Settings → Battery → App Management**
633+
- Turn off **AI Control**
634+
- Select **Manual Management**
635+
- Find **AdGuard** in the list and set **Background Work** to **Allow**

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,28 @@ You should remove Shadowsocks app from filtering before setting up the process (
155155
| Proxy host | *127.0.0.1* |
156156
| Proxy port | *7891* |
157157

158+
### How to use AdGuard with WG Tunnel
159+
160+
*The proxy mode was added in version 4.0. We presume that you already have WG Tunnel installed on your device and have added the WireGuard configuration.*
161+
162+
1. Open WG Tunnel and go to **Settings** (the cog wheel at the bottom) → **App Mode****Proxy (experimental)**. This will set WG Tunnel to proxy mode.
163+
164+
1. Open AdGuard and go to **App management**. Choose **WG Tunnel** and disable **Route traffic through AdGuard**. This will eliminate traffic looping.
165+
166+
1. Then go to **Settings****Filtering****Network****Proxy****Proxy server**.
167+
168+
1. Tap **Add proxy server** and fill in the fields:
169+
170+
| Field | Value |
171+
| ---------- | ----------- |
172+
| Proxy type | *SOCKS5* |
173+
| Proxy host | *127.0.0.1* |
174+
| Proxy port | *25344* |
175+
176+
1. Tap **Save and select**.
177+
178+
1. Enable the main proxy switch and AdGuard protection to route your device’s traffic through the proxy.
179+
158180
## Limitations
159181

160182
However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**.

i18n/be/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,14 @@ If your SOCKS5 proxy does not support UDP, connections may fail.
182182

183183
:::
184184

185+
## Per-app AdGuard CLI configuration
186+
187+
Users often need to enable filtering manually for certain browsers. AdGuard for Linux supports **per-app configuration**, allowing you to apply settings or rules individually to each application instead of system-wide.
188+
189+
For details, refer to the `apps` section in `proxy.yaml`.
190+
191+
A set of pre-configured entries for popular web browsers is included by default in `browsers.yaml`.
192+
185193
### Checking the current configuration
186194

187195
To view the current `outbound_proxy` configuration, enter:

i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1369,6 +1369,7 @@ These modifiers are able to completely change the behavior of basic rules.
13691369
| [$removeparam](#removeparam-modifier) |||[*[6]](#removeparam-modifier-limitations) |||||
13701370
| [$replace](#replace-modifier) ||||||||
13711371
| [$urltransform](#urltransform-modifier) ||||||||
1372+
| [$reason](#reason-modifier) ||||||||
13721373
| [noop](#noop-modifier) ||||||||
13731374
| [$empty 👎](#empty-modifier "deprecated") ||||||||
13741375
| [$mp4 👎](#mp4-modifier "deprecated") ||||||||
@@ -2932,6 +2933,41 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad
29322933
29332934
:::
29342935
2936+
#### **`$reason`** {#reason-modifier}
2937+
2938+
The `$reason` modifier allows you to add a custom explanation message that will be displayed on the blocking page when a request is blocked by this rule. This modifier only works with the `$document` content-type modifier.
2939+
2940+
**Character limitations and escaping requirements:**
2941+
2942+
- There is no maximum length limit for the reason text
2943+
- All characters are allowed in the reason text
2944+
- Special characters (such as quotes, commas, and backslashes) must be properly escaped using the backslash (`\`)
2945+
2946+
**Predefined localizable tokens:**
2947+
2948+
Instead of custom text, you can use predefined tokens that will be automatically localized:
2949+
2950+
- `malicious`for malicious content
2951+
- `tracker`for tracking content
2952+
- `disreputable`for disreputable content
2953+
2954+
**Examples**
2955+
2956+
```adblock
2957+
||example.com^$document,reason="Tracker"
2958+
||example.com^$document,reason="Malicious site blocked by security filter"
2959+
||ads.example.com^$document,reason="This site contains tracking scripts"
2960+
||malware.example.com^$document,reason="Site blocked: \"Known malware distributor\""
2961+
||tracking.example.com^$document,reason=disreputable
2962+
||analytics.example.com^$document,reason=tracker
2963+
```
2964+
2965+
:::info Compatibility
2966+
2967+
AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with CoreLibs v1.20 or later support rules with the `$reason` modifier. AdGuard Content Blocker does not support these rules.
2968+
2969+
:::
2970+
29352971
#### **`noop`** {#noop-modifier}
29362972
29372973
`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed.

i18n/be/docusaurus-plugin-content-docs/current/general/extensions.md

Lines changed: 39 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,24 @@ This script removes Google's tracking feature from the links in Google search re
5555

5656
Its source code is [available on GitHub](https://github.com/Rob--W/dont-track-me-google). This userscript can be downloaded from [GreasyFork](https://greasyfork.org/en/scripts/428243-don-t-track-me-google) and installed in any AdGuard CoreLibs-based app.
5757

58+
#### SponsorBlock
59+
60+
SponsorBlock skips sponsored segments in YouTube videos. It saves time by jumping straight to the main content and removes interruptions from ads and self-promotions.
61+
62+
:::info
63+
64+
This userscript runs exclusively on our desktop applications, AdGuard for Windows and AdGuard for Mac.
65+
66+
:::
67+
68+
To try it out:
69+
70+
1. Go to [https://mchangrh.github.io/sb.js/](https://mchangrh.github.io/sb.js/).
71+
2. Click **Generate link**.
72+
3. Copy the link that appears.
73+
4. Open AdGuard and go to **Extensions → Add extension → Import from file or URL**.
74+
5. Paste the copied link and confirm.
75+
5876
#### tinyShield
5977

6078
A userscript for people visiting Korean websites and some international websites. The tinyShield userscript blocks Ad-Shield ads and anti-adblocks. This userscript can be installed in AdGuard CoreLibs-based apps, Violentmonkey, Tampermonkey, and [quoid/userscripts](https://github.com/quoid/userscripts). Learn more about tinyShield and how to install it on [GitHub](https://github.com/List-KR/tinyShield).
@@ -439,30 +457,30 @@ We don’t support userstyles that contain `@var` or `@advanced` in the metadata
439457

440458
3. To create a userstyle, first write the title with metadata, for example
441459

442-
```CSS
443-
/* ==UserStyle==
444-
@name New userstyle
445-
@version 1.0
446-
==/UserStyle== */
447-
```
460+
```CSS
461+
/* ==UserStyle==
462+
@name New userstyle
463+
@version 1.0
464+
==/UserStyle== */
465+
```
448466

449467
4. Write the CSS part after the meta data. AdGuard supports website domain names matching (`@-moz-document domain(…), …`). For example:
450468

451-
```CSS
452-
body {
453-
background: gray;
454-
}
455-
```
456-
457-
Or:
458-
459-
```CSS
460-
@-moz-document domain('example.org'),
461-
domain('example.net'),
462-
domain('example.com') body {
463-
background: gray;
464-
}
465-
```
469+
```CSS
470+
body {
471+
background: gray;
472+
}
473+
```
474+
475+
Or:
476+
477+
```CSS
478+
@-moz-document domain('example.org'),
479+
domain('example.net'),
480+
domain('example.com') body {
481+
background: gray;
482+
}
483+
```
466484

467485
5. Once you’re finished, press _Save and Close_. Your new userstyle has been successfully added to AdGuard
468486

i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -598,11 +598,9 @@ On Motorola devices, there are four key configurations to ensure that AdGuard wo
598598

599599
1. Allow background usage:
600600

601-
- Go to **Settings → Apps** and find **AdGuard**
602-
- Open **App battery usage**
603-
- Enable **Allow background battery usage**
604-
- Tap the option with the toggle
605-
- Set battery usage to **Unrestricted**
601+
- Stop AdGuard protection and close the AdGuard app
602+
- Go to **Settings → Apps → App battery usage** and find AdGuard
603+
- Enable **Allow background usage** or select **Unrestricted**, depending on your Android version
606604

607605
1. Remove background activity restrictions:
608606

@@ -614,10 +612,24 @@ On Motorola devices, there are four key configurations to ensure that AdGuard wo
614612

615613
1. Manage background apps:
616614

617-
- Go to **Settings**, then type **Managing background apps** in the search bar
618-
- Find **AdGuard** and enable the toggle to allow the app to run in the background
615+
- Go to **Settings → Battery → Background app use**
616+
- Enable the **Manage background apps** option
617+
- In the resulting menu, select the **Apps** tab
618+
- Find **AdGuard** in the list and tap it
619+
- In the **Optimize battery use** dialog, select **Always allow**
620+
621+
![Always allow *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/motorolla-background-app-use.png)
619622

620623
1. Disable Adaptive Battery:
621624

622625
- Go to **Settings → Battery**
623626
- Turn off the **Adaptive Battery** option
627+
628+
## ZTE
629+
630+
ZTE devices functioning under the MyOS operating system have an aggressive approach to background processes. Follow these steps to prevent AdGuard from being closed automatically by AI control:
631+
632+
- Go to **Settings → Battery → App Management**
633+
- Turn off **AI Control**
634+
- Select **Manual Management**
635+
- Find **AdGuard** in the list and set **Background Work** to **Allow**

i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,28 @@ You should remove Shadowsocks app from filtering before setting up the process (
155155
| Proxy host | *127.0.0.1* |
156156
| Proxy port | *7891* |
157157

158+
### How to use AdGuard with WG Tunnel
159+
160+
*The proxy mode was added in version 4.0. We presume that you already have WG Tunnel installed on your device and have added the WireGuard configuration.*
161+
162+
1. Open WG Tunnel and go to **Settings** (the cog wheel at the bottom) → **App Mode****Proxy (experimental)**. This will set WG Tunnel to proxy mode.
163+
164+
1. Open AdGuard and go to **App management**. Choose **WG Tunnel** and disable **Route traffic through AdGuard**. This will eliminate traffic looping.
165+
166+
1. Then go to **Settings****Filtering****Network****Proxy****Proxy server**.
167+
168+
1. Tap **Add proxy server** and fill in the fields:
169+
170+
| Field | Value |
171+
| ---------- | ----------- |
172+
| Proxy type | *SOCKS5* |
173+
| Proxy host | *127.0.0.1* |
174+
| Proxy port | *25344* |
175+
176+
1. Tap **Save and select**.
177+
178+
1. Enable the main proxy switch and AdGuard protection to route your device’s traffic through the proxy.
179+
158180
## Limitations
159181

160182
However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**.

i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-linux/settings.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -182,6 +182,14 @@ If your SOCKS5 proxy does not support UDP, connections may fail.
182182

183183
:::
184184

185+
## Per-app AdGuard CLI configuration
186+
187+
Users often need to enable filtering manually for certain browsers. AdGuard for Linux supports **per-app configuration**, allowing you to apply settings or rules individually to each application instead of system-wide.
188+
189+
For details, refer to the `apps` section in `proxy.yaml`.
190+
191+
A set of pre-configured entries for popular web browsers is included by default in `browsers.yaml`.
192+
185193
### Checking the current configuration
186194

187195
To view the current `outbound_proxy` configuration, enter:

i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1369,6 +1369,7 @@ These modifiers are able to completely change the behavior of basic rules.
13691369
| [$removeparam](#removeparam-modifier) |||[*[6]](#removeparam-modifier-limitations) |||||
13701370
| [$replace](#replace-modifier) ||||||||
13711371
| [$urltransform](#urltransform-modifier) ||||||||
1372+
| [$reason](#reason-modifier) ||||||||
13721373
| [noop](#noop-modifier) ||||||||
13731374
| [$empty 👎](#empty-modifier "deprecated") ||||||||
13741375
| [$mp4 👎](#mp4-modifier "deprecated") ||||||||
@@ -2932,6 +2933,41 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad
29322933
29332934
:::
29342935
2936+
#### **`$reason`** {#reason-modifier}
2937+
2938+
The `$reason` modifier allows you to add a custom explanation message that will be displayed on the blocking page when a request is blocked by this rule. This modifier only works with the `$document` content-type modifier.
2939+
2940+
**Character limitations and escaping requirements:**
2941+
2942+
- There is no maximum length limit for the reason text
2943+
- All characters are allowed in the reason text
2944+
- Special characters (such as quotes, commas, and backslashes) must be properly escaped using the backslash (`\`)
2945+
2946+
**Predefined localizable tokens:**
2947+
2948+
Instead of custom text, you can use predefined tokens that will be automatically localized:
2949+
2950+
- `malicious`for malicious content
2951+
- `tracker`for tracking content
2952+
- `disreputable`for disreputable content
2953+
2954+
**Examples**
2955+
2956+
```adblock
2957+
||example.com^$document,reason="Tracker"
2958+
||example.com^$document,reason="Malicious site blocked by security filter"
2959+
||ads.example.com^$document,reason="This site contains tracking scripts"
2960+
||malware.example.com^$document,reason="Site blocked: \"Known malware distributor\""
2961+
||tracking.example.com^$document,reason=disreputable
2962+
||analytics.example.com^$document,reason=tracker
2963+
```
2964+
2965+
:::info Compatibility
2966+
2967+
AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard for Linux with CoreLibs v1.20 or later support rules with the `$reason` modifier. AdGuard Content Blocker does not support these rules.
2968+
2969+
:::
2970+
29352971
#### **`noop`** {#noop-modifier}
29362972
29372973
`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed.

0 commit comments

Comments
 (0)