Skip to content

Commit

Permalink
Merge pull request #338 from AdguardTeam/update-translations
Browse files Browse the repository at this point in the history
Update translations
  • Loading branch information
el-termikael authored Oct 5, 2023
2 parents 5644ebf + 92f2852 commit a47a6a0
Show file tree
Hide file tree
Showing 60 changed files with 1,054 additions and 1,055 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -2115,7 +2115,7 @@ In the `$replace` value, two characters must be escaped: comma `,` and dollar si

There are three parts in this rule:

- `regexp` - `(<VAST(.|\s)*?>)(.|\s)*<\/VAST>`;
- `regexp` `(<VAST(.|\s)*?>)(.|\s)*<\/VAST>`;
- `replacement``\$1<\/VAST>` where `$` is escaped;
- `modifiers``i` for insensitive search.

Expand Down Expand Up @@ -2302,7 +2302,7 @@ If there is a `$header` modifier in the rule it adds `50`.

#### `$domain` or `$app` with allowed domains or applications {#priority-category-3}

Specified domains through `$domain` or specified applications through `$app` add `100 + 100 / N`, where `N` is the number of modifier values for example: `||example.com^$domain=example.com|example.org|example.net` will add `100 + 100 / 3 = 134.3 = 135` or `||example.com^$app=org.example.app1|org.example.app2` will add `100 + 100 / 2 = 151` or `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` will add `100 + 100/1` ($domain part) and `100 + 100/2` ($app part) - will add `350` in total.
Specified domains through `$domain` or specified applications through `$app` add `100 + 100 / N`, where `N` is the number of modifier values for example: `||example.com^$domain=example.com|example.org|example.net` will add `100 + 100 / 3 = 134.3 = 135` or `||example.com^$app=org.example.app1|org.example.app2` will add `100 + 100 / 2 = 151` or `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` will add `100 + 100/1` ($domain part) and `100 + 100/2` ($app part), totaling `350`.

Modifier values that are regexps or tld will be interpreted as normal entries of the form `example.com` and counted one by one, for example: `||example.com^$domain=example.*` will add `100 + 100 / 1 = 200` or `||example.com^$domain=example.*|adguard.*` will add `100 + 100 / 2 = 150`.

Expand Down Expand Up @@ -3993,14 +3993,14 @@ Filtering log is an advanced tool that will be helpful mostly to filter develope

Depending on which AdGuard product you are using, Filtering log can be located in different places.

- In **AdGuard for Windows** you will find it inside *Ad Blocker* tab or via the tray menu;
- In **AdGuard for Mac** it is under *Settings → Advanced → Filtering log*;
- In **AdGuard for Android** it is a separate item in the side menu, also filtering log for a specific app or website is accessible from the Assistant.
- In **AdGuard Browser Extension** it is accessible from the *Miscellaneous* settings tab or by right-clicking the extension icon. Only Chromium- and Firefox-based browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs.
- In **AdGuard for Windows**, you can find it in the *Ad Blocker* tab or via the tray menu
- In **AdGuard for Mac**, it is located in *Settings → Advanced → Filtering log*
- In **AdGuard for Android**, you can find it under *Statistics → Recent activity*. *Recent activity* can also be accessed from the *Assistant*
- In **AdGuard Browser Extension**, it is accessible from the *Miscellaneous* settings tab or by right-clicking the extension icon. Only Chromium- and Firefox-based browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs

:::note

In **AdGuard for iOS** and in **AdGuard for Safari** Filtering log does not exist because of the way content blockers are implemented in Safari. AdGuard does not see the web requests and therefore cannot display them.
In **AdGuard for iOS** and **AdGuard for Safari**, Filtering log does not exist because of the way content blockers are implemented in Safari. AdGuard does not see the web requests and therefore cannot display them.

:::

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2115,7 +2115,7 @@ In the `$replace` value, two characters must be escaped: comma `,` and dollar si

There are three parts in this rule:

- `regexp` - `(<VAST(.|\s)*?>)(.|\s)*<\/VAST>`;
- `regexp` `(<VAST(.|\s)*?>)(.|\s)*<\/VAST>`;
- `replacement``\$1<\/VAST>` where `$` is escaped;
- `modifiers``i` for insensitive search.

Expand Down Expand Up @@ -2302,7 +2302,7 @@ If there is a `$header` modifier in the rule it adds `50`.

#### `$domain` or `$app` with allowed domains or applications {#priority-category-3}

Specified domains through `$domain` or specified applications through `$app` add `100 + 100 / N`, where `N` is the number of modifier values for example: `||example.com^$domain=example.com|example.org|example.net` will add `100 + 100 / 3 = 134.3 = 135` or `||example.com^$app=org.example.app1|org.example.app2` will add `100 + 100 / 2 = 151` or `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` will add `100 + 100/1` ($domain part) and `100 + 100/2` ($app part) - will add `350` in total.
Specified domains through `$domain` or specified applications through `$app` add `100 + 100 / N`, where `N` is the number of modifier values for example: `||example.com^$domain=example.com|example.org|example.net` will add `100 + 100 / 3 = 134.3 = 135` or `||example.com^$app=org.example.app1|org.example.app2` will add `100 + 100 / 2 = 151` or `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` will add `100 + 100/1` ($domain part) and `100 + 100/2` ($app part), totaling `350`.

Modifier values that are regexps or tld will be interpreted as normal entries of the form `example.com` and counted one by one, for example: `||example.com^$domain=example.*` will add `100 + 100 / 1 = 200` or `||example.com^$domain=example.*|adguard.*` will add `100 + 100 / 2 = 150`.

Expand Down Expand Up @@ -3993,14 +3993,14 @@ Filtering log is an advanced tool that will be helpful mostly to filter develope

Depending on which AdGuard product you are using, Filtering log can be located in different places.

- In **AdGuard for Windows** you will find it inside *Ad Blocker* tab or via the tray menu;
- In **AdGuard for Mac** it is under *Settings → Advanced → Filtering log*;
- In **AdGuard for Android** it is a separate item in the side menu, also filtering log for a specific app or website is accessible from the Assistant.
- In **AdGuard Browser Extension** it is accessible from the *Miscellaneous* settings tab or by right-clicking the extension icon. Only Chromium- and Firefox-based browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs.
- In **AdGuard for Windows**, you can find it in the *Ad Blocker* tab or via the tray menu
- In **AdGuard for Mac**, it is located in *Settings → Advanced → Filtering log*
- In **AdGuard for Android**, you can find it under *Statistics → Recent activity*. *Recent activity* can also be accessed from the *Assistant*
- In **AdGuard Browser Extension**, it is accessible from the *Miscellaneous* settings tab or by right-clicking the extension icon. Only Chromium- and Firefox-based browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs

:::note

In **AdGuard for iOS** and in **AdGuard for Safari** Filtering log does not exist because of the way content blockers are implemented in Safari. AdGuard does not see the web requests and therefore cannot display them.
In **AdGuard for iOS** and **AdGuard for Safari**, Filtering log does not exist because of the way content blockers are implemented in Safari. AdGuard does not see the web requests and therefore cannot display them.

:::

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -63,4 +63,4 @@ Když povolíte některá rozšíření Safari, můžete si všimnout, že poža

– Pro správnou funkci ručního blokování reklam a pokročilých pravidel blokování je nutný přístup k obsahu webové stránky. – Přístup k historii prohlížení je nutný pro kontrolu stavu ochrany na webových stránkách a určení, která pokročilá pravidla by měla být použita

We do not use this data for any other purpose or share it with anyone. Pro více informací se můžete podívat na naše [Zásady ochrany osobních údajů](https://adguard.com/privacy.html).
Tyto údaje nepoužíváme pro žádné jiné účely a ani je s nikým nesdílíme. Pro více informací se můžete podívat na naše [Zásady ochrany osobních údajů](https://adguard.com/privacy.html).
Loading

0 comments on commit a47a6a0

Please sign in to comment.