From 3a15109318edaa29e088d062d021cbf3414b83a4 Mon Sep 17 00:00:00 2001 From: puglieri <112409628+puglieri@users.noreply.github.com> Date: Wed, 9 Oct 2024 09:55:01 +0000 Subject: [PATCH 1/2] automatically update translations --- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../compatibility.md | 10 +- .../adguard-browser-extension/mv3-version.md | 66 +- .../solving-problems/debug-rules.md | 50 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 22 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 8 +- .../solving-problems/logcat.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 18 +- .../current/adguard-for-ios/installation.md | 12 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 10 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/ads-not-blocked.md | 2 +- .../solving-problems/filters-after-disable.md | 2 +- .../solving-problems/logs.md | 16 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 6 +- .../adguard-for-windows/installation.md | 2 +- .../solving-problems/adguard-logs.md | 2 +- .../solving-problems/system-logs.md | 2 +- .../current/general/account/features.md | 2 +- .../ad-filtering/create-own-filters.md | 510 ++++----- .../general/ad-filtering/filter-policy.md | 2 +- .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/license/what-is.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/family-link-certificate.md | 2 +- .../current/guides/minidump.md | 4 +- .../current/guides/report-bugs.md | 2 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 4 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../adguard-for-android/installation.md | 52 +- .../adguard-for-android-tv.md | 68 +- .../solving-problems/background-work.md | 16 +- .../solving-problems/battery.md | 44 +- .../solving-problems/compatibility-issues.md | 4 +- .../solving-problems/firefox-certificates.md | 32 +- .../solving-problems/har.md | 26 +- .../multiple-user-profiles.md | 8 +- .../solving-problems/youtube-ads.md | 24 +- .../features/extensions.md | 12 +- .../features/home-screen.md | 2 +- .../adguard-for-windows/features/others.md | 12 +- .../adguard-for-windows/features/settings.md | 12 +- .../adguard-for-windows/installation.md | 12 +- .../current/general/account/features.md | 4 +- .../current/general/account/register.md | 2 +- .../ad-filtering/create-own-filters.md | 23 +- .../general/ad-filtering/filter-policy.md | 4 +- .../what-is-https-filtering.md | 2 +- .../current/general/license/what-is.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 4 +- .../current/guides/take-screenshot.md | 18 +- .../adguard-browser-extension/mv3-version.md | 80 +- .../adguard-for-android/installation.md | 2 +- .../solving-problems/background-work.md | 208 ++-- .../solving-problems/battery.md | 4 +- .../solving-problems/compatibility-issues.md | 14 +- .../solving-problems/har.md | 40 +- .../https-certificate-for-rooted.md | 46 +- .../solving-problems/log.md | 28 +- .../solving-problems/logcat.md | 78 +- .../solving-problems/low-level-settings.md | 150 +-- .../solving-problems/manual-certificate.md | 44 +- .../multiple-user-profiles.md | 4 +- .../solving-problems/outbound-proxy.md | 170 +-- .../samsungpay-with-adguard-in-south-korea.md | 2 +- .../solving-problems/secure-folder.md | 14 +- .../solving-problems/tasker.md | 64 +- .../adguard-for-windows/installation.md | 2 +- .../ad-filtering/create-own-filters.md | 26 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 78 +- .../solving-problems/debug-rules.md | 60 +- .../adguard-for-ios/features/free-vs-full.md | 20 +- .../admins-documentation.md | 46 +- .../adguard-for-windows/browser-assistant.md | 44 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 92 +- .../ad-filtering/create-own-filters.md | 22 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 77 +- .../solving-problems/debug-rules.md | 60 +- .../adguard-for-android/installation.md | 4 +- .../solving-problems/outbound-proxy.md | 2 +- .../adguard-for-ios/features/free-vs-full.md | 20 +- .../admins-documentation.md | 44 +- .../adguard-for-windows/browser-assistant.md | 40 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 94 +- .../ad-filtering/create-own-filters.md | 25 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../solving-problems/log.md | 2 +- .../solving-problems/logcat.md | 2 +- .../solving-problems/low-level-settings.md | 2 +- .../facetime-compatibility-issues.md | 2 +- .../features/browser-assistant.md | 58 +- .../current/adguard-for-mac/features/dns.md | 22 +- .../adguard-for-mac/features/extensions.md | 22 +- .../adguard-for-mac/features/filters.md | 16 +- .../adguard-for-mac/features/general.md | 22 +- .../current/adguard-for-mac/features/main.md | 4 +- .../adguard-for-mac/features/network.md | 22 +- .../adguard-for-mac/features/security.md | 10 +- .../adguard-for-mac/features/stealth.md | 4 +- .../current/adguard-for-mac/installation.md | 38 +- .../solving-problems/advanced-settings.md | 10 +- .../solving-problems/big-sur-issues.md | 10 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 14 +- .../admins-documentation.md | 44 +- .../adguard-for-windows/browser-assistant.md | 44 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 72 +- .../general/ad-filtering/adguard-filters.md | 78 +- .../ad-filtering/create-own-filters.md | 23 +- .../current/general/userscripts.md | 80 +- .../adguard-browser-extension/mv3-version.md | 76 +- .../solving-problems/debug-rules.md | 58 +- .../adguard-for-ios/features/free-vs-full.md | 18 +- .../ad-filtering/create-own-filters.md | 22 +- .../current/intro.md | 12 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 78 +- .../ad-filtering/create-own-filters.md | 22 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 981 +++++++++--------- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../ad-filtering/create-own-filters.md | 117 ++- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- .../adguard-browser-extension/mv3-version.md | 64 +- .../solving-problems/debug-rules.md | 58 +- .../solving-problems/logs.md | 2 +- .../features/advanced-protection.md | 2 +- .../features/safari-protection.md | 2 +- .../general/ad-filtering/adguard-filters.md | 12 +- .../ad-filtering/create-own-filters.md | 21 +- .../general/ad-filtering/filter-policy.md | 8 +- .../ad-filtering/how-ad-blocking-works.md | 54 +- .../general/ad-filtering/search-ads.md | 38 +- .../tracking-filter-statistics.md | 46 +- .../what-is-https-filtering.md | 72 +- .../adguard-browser-extension/mv3-version.md | 2 +- .../ad-filtering/create-own-filters.md | 19 +- 208 files changed, 2876 insertions(+), 2910 deletions(-) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index 7b478df0824..0f476bb766e 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -9,16 +9,16 @@ Tento článek je o Rozšíření prohlížeče AdGuard, které chrání pouze v ::: -While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. +Zatímco rozšíření prohlížeče AdGuard může blokovat reklamy v prohlížečích, [samostatné programy AdGuard](/adguard-browser-extension/comparison-standalone) filtrují veškerý provoz ve vašem zařízení, a to i z prohlížečů a aplikací. -If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. +Pokud se rozhodnete do počítače nainstalovat rozšíření i samostatný program, můžete narazit na problémy s kompatibilitou. Problémem je, že v některých případech se aplikace a rozšíření mohou vzájemně rušit. Některé webové stránky již nebudou chráněny programem pro stolní počítače a budou chráněny pouze rozšířením, které má méně možností. Také filtrování může u některých webových stránek fungovat nesprávně. Proto nedoporučujeme používat rozšíření společně s aplikací. -If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. +Pokud máte v počítači nainstalovanou desktopovou verzi AdGuard, je lepší použít místo rozšíření Asistenta prohlížeče AdGuard. ## AdGuard Asistent prohlížeče ![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). +Asistent prohlížeče AdGuard je rozšíření prohlížeče, které funguje a působí stejně jako rozšíření prohlížeče AdGuard, ale je mnohem lehčí a nezasahuje do aplikací na ploše. Můžete si [přečíst více o programu Asistent prohlížeče pro Windows](/adguard-for-windows/browser-assistant) nebo [Mac](/adguard-for-mac/features/browser-assistant), případně [stáhnout z našich webových stránek](https://adguard.com/adguard-assistant/overview.html). -AdGuard Browser Assistant is available in all major browsers. +AdGuard Asistent prohlížeče je k dispozici ve všech známých prohlížečích. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 5a3ae991259..d69015ea9e2 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -1,76 +1,74 @@ --- -title: AdGuard Browser Extension for Chrome MV3 +title: Rozšíření prohlížeče AdGuard pro Chrome MV3 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +Vzhledem k tomu, že rozšíření MV2 jsou ve webovém obchodě Chrome postupně ukončována, mohou uživatelé prohlížeče Chrome přejít na rozšíření MV3, která jsou kompatibilní s novým Chrome API Manifest V3. Naše úvahy na toto téma jsou podrobně rozebrány na [našem blogu](https://adguard.com/en/blog/tag/manifest-v3.html). -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +Naše rozšíření MV3 účinně blokuje reklamy a slídiče a zároveň bezproblémově spravuje sociální widgety, bannery a videoreklamy. Většina uživatelů nezaznamená žádné provozní rozdíly, ale je třeba si uvědomit některá omezení a změny. -## Where to find our extensions +## Kde najdete naše rozšíření -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +**Verze MV3** nahradila naše staré rozšíření v [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +**Beta verze MV3** bude stále k dispozici v [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +Staré beta rozšíření bude přejmenováno na [**Blokátor reklam AdGuard MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) a bude podporováno, dokud jej společnost Google postupně nezruší. -## Main changes in features and settings +## Hlavní změny funkcí a nastavení -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **Není k dispozici automatická a ruční aktualizace filtrů.** Na kartě _Filtry_ již nejsou k dispozici možnosti _Automatická aktualizace filtrů_ a _Kontrola aktualizace filtrů_. Vzhledem k tomu, že některá pravidla jsou nyní aplikována ve formě DNR, nemůžeme aktualizovat filtry na vyžádání, ale pouze prostřednictvím celého procesu aktualizace rozšíření spolu s přezkumem v obchodech. -- **Filtering log** +- **Záznam filtrování** ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + Vzhledem k omezením DNR nemůžeme přesně ukázat, které pravidlo fungovalo, ale uvedeme "předpokládané pravidlo, které bylo spuštěno" na základě našeho enginu. Chcete-li získat přesné informace, musíte si "rozbalenou" formu rozšíření nainstalovat do prohlížeče sami. Podrobný návod, jak to provést, najdete v [samostatném článku](/adguard-browser-extension/solving-problems/debug-rules/). -- _Tracking protection_ (formerly known as _Stealth mode_) +- _Ochrana před sledováním_ (dříve známá jako _Režim utajení_) ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + Neexistuje sekce _Cookies_ spolu s _Samozničení vlastních cookies_ a _Samozničení cookies třetích stran_, protože nelze nastavit TTL cookies pomocí deklarativních pravidel. -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- _Ochrana proti phishingu a malwaru_ již není v obecném nastavení k dispozici. Chcete-li se chránit před škodlivými webovými stránkami a podvody, zapněte příslušné filtry _Zabezpečení_ na kartě _Filtry_. ![Security \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) ## Omezení -### Maximum number of rules and filters +### Maximální počet pravidel a filtrů -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +Manifest V3 zavádí omezení statických a regexových pravidel na jedno rozšíření. Uživatelé mohou dostávat oznámení o překročení těchto limitů. ![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) ![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +Manifest V3 v zásadě dělí pravidla na statická (vestavěná) a dynamická s přísnými omezeními. -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +**Statická pravidla:** minimálně **30000** pravidel na jedno rozšíření s kumulativním limitem **330000** pro všechna rozšíření nainstalovaná jedním uživatelem. -For regex rules, the limit is set at **1,000 per extension**. +Pro regexová pravidla je nastaven limit **1000 na jedno rozšíření**. -The maximum number of simultaneously enabled filters is **50**. +Maximální počet současně aktivovaných filtrů je **50**. -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +**Dynamická pravidla:** je stanoven přísný limit **5000** pravidel, který zahrnuje maximálně 1000 regexových pravidel. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> **Převedená pravidla** jsou pravidla, která byla převedena do formátu \[DNR] pomocí [deklarativního převodníku][github-declarative-converter]. +> Během tohoto převodu mohou některá pravidla přepsat jiná (`$badfilter`), některá mohou být sloučena (`$removeparam`), takže vznikne seznam pravidel s mírně odlišným pořadím. > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> Z tohoto seznamu převedených pravidel použijeme pouze 5000 pravidel. Ostatní se v editoru zobrazí, ale nepoužijí se. -Here's how a rule with a basic modifier is converted to a declarative rule: +Zde je uveden způsob převodu pravidla se základním modifikátorem na deklarativní pravidlo: ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +je převedeno na ```json [ @@ -94,14 +92,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +Další příklady najdete na [GitHubu][github-declarative-converter-examples]. -### Network rule modifiers +### Modifikátory síťových pravidel -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +Modifikátory síťových pravidel mají svá omezení: některé z nich nelze v MV3 implementovat nebo je lze implementovat pouze s omezeními. -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +Další podrobnosti o omezeních najdete na [GitHubu][github-declarative-converter]. +Další informace o modifikátorech naleznete v naší [Databázi znalostí](/general/ad-filtering/create-own-filters). [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md index e6d6f9291e2..4067a3b49c5 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md @@ -1,98 +1,98 @@ --- -title: How to debug rules in AdGuard for Chrome MV3 +title: Jak ladit pravidla v AdGuardu pro Chrome MV3 sidebar_position: 2 --- -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. +V [AdGuardu pro Chrome MV3](/adguard-browser-extension/mv3-version) se v protokolu filtrování zobrazují pouze přibližná pravidla, která byla použita a která nazýváme "předpokládaná pravidla". Je to proto, že prohlížeč neposkytuje podrobnosti o tom, která konkrétní deklarativní pravidla byla použita, pokud není rozšíření v "rozbaleném" formátu. Chcete-li získat přesné informace, musíte si sami nainstalovat rozbalenou verzi rozšíření do prohlížeče. -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. +Tyto pokyny jsou určeny i pro problematické případy, kdy chcete upravit pravidla, která jsou s rozšířením staticky svázána. Ve většině případů by mělo stačit použití _Uživatelských pravidel_ v rozšíření. -## Prerequisites +## Předpoklady -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) +1. **Git:** [nainstalujte Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) +2. **Node:** [nainstalujte Node.js](https://nodejs.org/en/download/package-manager) -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) +3. **Yarn:** [nainstalujte Yarn](https://classic.yarnpkg.com/lang/en/docs/install) -## How to clone extension +## Jak klonovat rozšíření -1. Clone the repository: +1. Naklonujte repozitář: ```bash git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git ``` -2. Navigate to the directory: +2. Přejděte do adresáře: ```bash cd AdguardBrowserExtension ``` -3. Switch to the `v5.0` branch: +3. Přepněte na větev `v5.0`: ```bash git checkout v5.0 ``` -4. Install dependencies: +4. Nainstalujte závislosti: ```bash yarn install ``` -## How to build extension +## Jak sestavit rozšíření -1. Switch to the `v5.0` branch: +1. Přepněte na větev `v5.0`: ```bash git checkout v5.0 ``` -2. Run the following command in the terminal: +2. V terminálu spusťte následující příkaz: ```bash yarn dev chrome-mv3 ``` -3. The built extension will be located in the directory: +3. Sestavené rozšíření bude umístěno v adresáři: ```bash ./build/dev/chrome-mv3 ``` -## How to install unpacked in the browser +## Jak nainstalovat rozbalené rozšíření v prohlížeči -1. Turn on developer mode: +1. Zapněte režim vývojáře: ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) -2. Click _Load unpacked_: +2. Klikněte na _Načíst rozbalené_: ![Load unpacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) -3. Select the extension directory and click `Select`: +3. Vyberte adresář s rozšířením a klikněte na `Vybrat`: ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) To je vše! -## How to debug rules +## Jak ladit pravidla -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. +1. Najděte a upravte potřebné pravidlo v adresáři `./Extension/filters/chromium-mv3` v souborech `.txt`. -2. Convert the rules from txt to declarative form: +2. Převeďte pravidla z txt do deklarativní formy: ```bash yarn convert-declarative ``` -3. Build the extension again: +3. Sestavte rozšíření znovu: ```bash yarn dev chrome-mv3 ``` -4. Reload the extension in the browser: +4. Znovu načtěte rozšíření v prohlížeči: ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index fe82e0e5d03..993cbd967cc 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ Chcete-li odstranit pravidlo nebo aplikaci v části _Vlastní pravidla_, přeje ### Upozornění -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. Upozornění můžete zapnout a vypnout pro všechny aplikace nebo pro každou aplikaci zvlášť. +Pokud je tato funkce povolena, upozorní vás, když se aplikace pokouší porušit příslušné pravidlo brány firewall, např. se pokouší přistupovat k mobilním datům, která jsou blokována. Upozornění můžete zapnout a vypnout pro všechny aplikace nebo pro každou aplikaci zvlášť. Klepnutím na upozornění získáte přístup k nastavení brány firewall aplikace nebo můžete dočasně zakázat všechna pravidla brány firewall pro danou aplikaci klepnutím na příslušné tlačítko v upozornění. Můžete také ztlumit všechna upozornění brány firewall pro aplikaci klepnutím na tlačítko _Ztlumit_ v upozornění pro danou aplikaci. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 2f3581896ec..46ff9f8ef74 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Zde jsou uvedeny aktivní funkce předkonfigurovaných úrovní: k. _Odstranit X-Client-Data hlavičku_. Tato funkce zabraňuje tomu, aby prohlížeč Google Chrome odesílal informace o své verzi a úpravách do domén společnosti Google (včetně služeb DoubleClick a Google Analytics) -Jednotlivá nastavení můžete upravit v části _Ochrana před sledováním_ a vytvořit si vlastní konfiguraci. Každé nastavení má popis, který vám pomůže pochopit jeho roli. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +Jednotlivá nastavení můžete upravit v části _Ochrana před sledováním_ a vytvořit si vlastní konfiguraci. Každé nastavení má popis, který vám pomůže pochopit jeho roli. [Další informace o tom, co dělají různá nastavení _Ochrany před sledováním_](/general/stealth-mode). Přistupujte k nim opatrně, protože některá mohou narušovat funkčnost webových stránek a rozšíření prohlížeče. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 1fe589a1c9f..7257076ee44 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt Vzhledem k bezpečnostním opatřením OS Android jsou některé funkce AdGuardu dostupné pouze na zařízeních s přístupem root. Zde je jejich seznam: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **Filtrování HTTPS filtrování ve většině aplikací** vyžaduje [instalaci certifikátu CA do systémového úložiště](/adguard-for-android/features/settings#security-certificates), protože většina aplikací nedůvěřuje certifikátům v uživatelském úložišti - [Režim směrování **Automatický proxy**](/adguard-for-android/features/settings#routing-mode) vyžaduje přístup root kvůli omezením systému Android na filtrování provozu v celém systému - [Režim směrování **Ruční proxy**](/adguard-for-android/features/settings#routing-mode) vyžaduje v systému Android 10 a novějším přístup root, protože již není možné určit název aplikace přidružené ke spojení filtrovanému AdGuardem diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 39210156e93..e1f5c14ce1b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ _Automatizace_ vám umožňuje spravovat AdGuard prostřednictvím aplikací Tas _Hlídací pes_ pomáhá chránit AdGuard před vypnutím systémem ([přečtěte si více o úsporném režimu baterie systému Android](/adguard-for-android/solving-problems/background-work/)). Zadaná hodnota bude interval v sekundách mezi kontrolami watchdog. -_Úroveň záznamu_ definuje, jaká data o provozu aplikace by měla být zaznamenána. Ve výchozím nastavení aplikace shromažďuje údaje o vlastních událostech. _Úroveň ladění_ zaznamenává více událostí – povolte ji, pokud o to tým AdGuardu požádá, abyste mu pomohli lépe porozumět problému. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +_Úroveň záznamu_ definuje, jaká data o provozu aplikace by měla být zaznamenána. Ve výchozím nastavení aplikace shromažďuje údaje o vlastních událostech. _Úroveň ladění_ zaznamenává více událostí – povolte ji, pokud o to tým AdGuardu požádá, abyste mu pomohli lépe porozumět problému. [Přečtěte si více o shromažďování a odesílání záznamů](/adguard-for-android/solving-problems/log/) ![Advanced \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ Pokud aktivujete příliš mnoho filtrů, mohou některé webové stránky fungo ### Uživatelské skripty -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. K instalaci uživatelských skriptů potřebujete speciální správce uživatelských skriptů. AdGuard takovou funkci má a umožňuje přidávat uživatelské skripty pomocí URL nebo ze souboru. +Uživatelské skripty jsou miniprogramy napsané v jazyce JavaScript, které rozšiřují funkčnost jedné nebo více webových stránek. K instalaci uživatelských skriptů potřebujete speciální správce uživatelských skriptů. AdGuard takovou funkci má a umožňuje přidávat uživatelské skripty pomocí URL nebo ze souboru. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ V této sekci najdete informace o své licenci a můžete provádět následují - Zakoupit licenci AdGuardu pro aktivaci [funkcí plné verze](/adguard-for-android/features/free-vs-full) - Přihlásit se ke svému AdGuard účtu nebo zadat licenční klíč pro aktivaci licence - Zaregistrovat se a aktivovat si 7denní zkušební dobu, pokud jste ji ještě nevyužili -- Refresh the license status from the three-dots menu (⋮) +- Obnovit stav licence z nabídky se třemi tečkami (⋮) - Otevřít AdGuard účet a spravovat v něm své licence - Resetovat licenci — například pokud jste dosáhli limitu zařízení pro tuto licenci a chcete použít jinou diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index af4d2124190..dcfda4b1230 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Android TV, blokátor reklam, který chrán ::: -Ve většině případů nelze do TV nainstalovat soubor ze standardních prohlížečů, ale můžete si stáhnout prohlížeč z obchodu Google Play, který tuto funkci má. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. Případně můžete použít aplikaci [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader). +Ve většině případů nelze do TV nainstalovat soubor ze standardních prohlížečů, ale můžete si stáhnout prohlížeč z obchodu Google Play, který tuto funkci má. V našem průvodci se budeme zabývat příkladem instalace skrze prohlížeč TV Bro, ale existují i jiné možnosti a vy si můžete vybrat tu, která lépe vyhovuje vašim potřebám. Případně můžete použít aplikaci [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader). ## Instalace aplikace AdGuard pro Android TV z prohlížeče v TV diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c89764c5d53..8926cfaf048 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -29,29 +29,29 @@ Xiaomi (a zejména MIUI) patří mezi nejproblematičtější, pokud jde o prác ### MIUI 13+ a HyperOS -Depending on the MIUI and HyperOS versions, there are two ways to change the battery optimization settings on your phone and block ads more efficiently. +V závislosti na verzi MIUI a HyperOS existují dva způsoby, jak změnit nastavení optimalizace baterie v telefonu a účinněji blokovat reklamy. -Option 1 +1. možnost -1. Go to **Settings** → **Apps** → **Permissions** → **Background autostart** and allow AdGuard to run in the background +1. Přejít do **Nastavení** → **Aplikace** → **Oprávnění** → **Automatické spuštění na pozadí** a umožněte AdGuardu běžet na pozadí -1. Return to **Settings** → **Apps** → **Manage apps** → **AdGuard** and uncheck **Pause app activity if unused** +1. Vraťte se do **Nastavení** → **Aplikace** → **Správa aplikací** → **AdGuard** a zrušte zaškrtnutí políčka **Pozastavit aktivitu aplikace, pokud není používána** -1. Go to **Battery saver** and tap **No restrictions** +1. Přejděte do **Spořiče baterie** a klepněte na **Bez omezení** -Option 2 +2. možnost -1. Go to **Settings** → **Apps** → **Manage apps** → **AdGuard** and enable **Autostart** +1. Přejděte do **Nastavení** → **Aplikace** → **Správa aplikací** → **AdGuard** a povolte **Automatické spouštění** -1. Go to **Battery saver** and tap **No restrictions** +1. Přejděte do **Spořiče baterie** a klepněte na **Bez omezení** -Hotovo! You have successfully set up AdGuard to work in the background. +Hotovo! Úspěšně jste nastavili AdGuard tak, aby pracoval na pozadí. ### MIUI 12.0.8 Chcete-li aplikaci AdGuard úspěšně spustit na pozadí, proveďte následující kroky: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +V **Nastavení** → **Aplikace** → **Spravovat aplikace** → přejděte dolů k **AdGuard**, nastavte **Automatické spuštění** na “Zapnuto“. ![Nastavení Xiaomi *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ V systému Android 11+ je na stejné obrazovce s režimem STAMINA nastavení s n Je také třeba AdGuard vyjmout z funkce úspory energie: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**Nastavení systému** → **Aplikace a Oznámení** → **Rozšířené** → **Přístup ke speciálním aplikacím** → **Funkce úspory energie** → Přepnout AdGuard na **Vynechat** ## Wiko diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 44d75e0334d..918171a75b3 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. Bylo to proto, že AdGuard počítal veškerý provoz, který filtroval z různých aplikací. V důsledku toho byl podíl AdGuardu na celkovém využití dat a baterie nadhodnocen, zatímco podíl ostatních aplikací byl podhodnocen. +Kvůli vestavěným statistickým procesům byla vysoká spotřeba dat a/nebo baterie často připisována AdGuardu v systému Android 6 a dřívějších verzích. Bylo to proto, že AdGuard počítal veškerý provoz, který filtroval z různých aplikací. V důsledku toho byl podíl AdGuardu na celkovém využití dat a baterie nadhodnocen, zatímco podíl ostatních aplikací byl podhodnocen. V Androidu 7 se však tento scénář zlepšil. Nyní se údaje uvedené ve vestavěných statistikách využití dat systému Android velmi blíží skutečnosti, i když v údajích o využití baterie jsou drobné nesrovnalosti. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 3ee6552f3ce..583e1a0c4bd 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Někteří výrobci zařízení nechávají nastavení Soukromých DNS skryté a ### Prohlížeče UC: UC Browser, UC Browser pro x86, UC Mini, UC Browser HD -Aby mohl AdGuard filtrovat přenosy HTTPS, musí uživatel přidat certifikát do důvěryhodných uživatelských certifikátů zařízení. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +Aby mohl AdGuard filtrovat přenosy HTTPS, musí uživatel přidat certifikát do důvěryhodných uživatelských certifikátů zařízení. Prohlížeče UC bohužel nedůvěřují uživatelským certifikátům, takže v nich AdGuard nemůže provádět filtrování HTTPS. - Chcete-li tento problém vyřešit, přesuňte certifikát do [systémového úložiště certifikátů](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 67910bba588..be1c7ee747a 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: Jak generovat soubory HAR sidebar_position: 5 --- @@ -17,11 +17,11 @@ Soubory HAR jsou zpracovávány v souladu se [Zásadami ochrany osobních údaj ## Co jsou soubory HAR? -Formát HAR (HTTP ARchive) je archivní soubor ve formátu JSON pro zaznamenávání interakce webového prohlížeče s webem. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. Podrobnější popis formátu HAR a jeho specifikace naleznete na webové stránce [ softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). +Formát HAR (HTTP ARchive) je archivní soubor ve formátu JSON pro zaznamenávání interakce webového prohlížeče s webem. Specifikace formátu HAR definují archivační data pro transakce HTTP, která prohlížeč používá k exportu podrobných informací o načítaných webových stránkách. Podrobnější popis formátu HAR a jeho specifikace naleznete na webové stránce [ softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). -## How to generate HAR files +## Jak generovat soubory HAR -Někdy musíme analyzovat, abychom zablokovali konkrétní reklamy, které je z nějakého důvodu obtížné reprodukovat. To get HAR files, follow these steps: +Někdy musíme analyzovat, abychom zablokovali konkrétní reklamy, které je z nějakého důvodu obtížné reprodukovat. Chcete-li získat soubory HAR, postupujte takto: 1. Otevřete AdGuard a přejděte do **Nastavení** (ikona ⚙ v pravém dolním rohu). 2. Klepněte na **Obecné** →**Pokročilé** → **Nízkoúrovňová nastavení**. @@ -31,7 +31,7 @@ Někdy musíme analyzovat, abychom zablokovali konkrétní reklamy, které je z 6. Přejděte zpět na **Pokročilé**. 7. Klepněte na **Exportovat protokoly a systémové informace** → **Povolit** (je-li to nutné) → **Uložit**. -**Send the generated file with the logs to the AdGuard support service.** +**Vygenerovaný soubor s protokoly odešlete službě podpory AdGuard.** :::note diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index 776701270e5..3c7470705cb 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Zde je návod, jak to udělat: 1. Nainstalujte [nejnovější verzi modulu **adguardcert** Magisk](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Otevřete *Magisk → Moduly → Instalovat z úložiště* a vyberte stažený soubor **adguardcert**. The AdGuard Personal CA certificate will be copied to the system store. +1. Otevřete *Magisk → Moduly → Instalovat z úložiště* a vyberte stažený soubor **adguardcert**. Certifikát AdGuard Personal CA bude zkopírován do systémového úložiště. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 4358a3a37ac..9840cddcf6a 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -1,5 +1,5 @@ --- -title: How to collect debug logs +title: Jak shromažďovat záznamy ladění sidebar_position: 2 --- @@ -15,7 +15,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Záznamy ladění poskytují podrobný náhled do vnitřního fungování AdGuardu pro Android. Pokud vás tým podpory AdGuardu požádá o poskytnutí záznamů ladění, postupujte podle těchto pokynů. +V tomto článku vás provedeme procesem shromažďování záznamů ladění, což je zásadní krok při řešení složitých problémů, které mohou nastat. Záznamy ladění poskytují podrobný náhled do vnitřního fungování AdGuardu pro Android. Pokud vás tým podpory AdGuardu požádá o poskytnutí záznamů ladění, postupujte podle těchto pokynů. :::note @@ -23,9 +23,9 @@ AdGuard se zavazuje chránit vaše soukromí. Přísně dodržujeme naše [Zása ::: -### Recording debug log +### Záznam protokolu ladění -To collect **debug** log and send it to us, you need to perform following steps: +Chcete-li shromáždit záznam **ladění** a odeslat nám jej, musíte provést následující kroky: 1. Jděte do *Nastavení* → *Obecné* → *Pokročilé*. 1. Klepněte na *Úroveň záznamů* a nastavte ji na *Ladění*. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index 0bde452c0e6..262b698488d 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -15,7 +15,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -Někdy nemusí běžný záznam stačit k identifikaci původu problému. V takových případech je nutný systémový záznam. Below are instructions on how to collect and get it: via Developer options and Logcat. +Někdy nemusí běžný záznam stačit k identifikaci původu problému. V takových případech je nutný systémový záznam. Níže jsou uvedeny pokyny, jak je shromáždit a získat: prostřednictvím možností pro vývojáře a Logcat. :::note diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 5b4598da0fc..c8fcd9a6328 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Používejte to pouze pro účely ladění! #### Encrypted Client Hello -Každé šifrované internetové připojení má i nešifrovanou část. Jedná se o první paket, který obsahuje název serveru, ke kterému se připojujete. Technologie Encrypted Client Hello má tento problém vyřešit a zašifrovat poslední kousek nešifrovaných informací. Chcete-li to využít, povolte možnost *Encrypted ClientHello*. K vyhledání konfigurace ECH pro danou doménu používá místní proxy server DNS. If it is found, Client Hello packet will be encrypted. +Každé šifrované internetové připojení má i nešifrovanou část. Jedná se o první paket, který obsahuje název serveru, ke kterému se připojujete. Technologie Encrypted Client Hello má tento problém vyřešit a zašifrovat poslední kousek nešifrovaných informací. Chcete-li to využít, povolte možnost *Encrypted ClientHello*. K vyhledání konfigurace ECH pro danou doménu používá místní proxy server DNS. Pokud je nalezen, paket ClientHello bude zašifrován. #### Kontrola OCSP @@ -147,7 +147,7 @@ Zde můžete zadat rozsahy portů, které mají být filtrovány. Pokud je toto nastavení povoleno, AdGuard zaznamená blokované prvky HTML v sekci *Nedávná aktivita*. -#### Scriptlet debugging +#### Ladění skripletů Pokud je toto nastavení povoleno, bude aktivováno ladění skriptletů a protokol prohlížeče bude zaznamenávat použití pravidel skriptletů. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index e5bafacab72..14beea9efb9 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. Ve starších verzích operačního systému Android se to provádělo automaticky, ale v Androidu 11 a novějších verzích jej uživatelé musí nainstalovat ručně. +Aby bylo možné [filtrovat provoz HTTPS](/general/https-filtering/what-is-https-filtering.md) (což je velmi důležité, protože většina reklam používá HTTPS), musí AdGuard nainstalovat certifikát do uživatelského úložiště vašeho zařízení. Ve starších verzích operačního systému Android se to provádělo automaticky, ale v Androidu 11 a novějších verzích jej uživatelé musí nainstalovat ručně. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Certifikát AdGuardu nainstalujete podle následujících kroků: 1. Když uvidíte oznámení *HTTPS filtrování je vypnuto*, klepněte na *Zapnout*. 1. Poté se zobrazí tři obrazovky s vysvětlením: - Proč filtrovat HTTPS provoz - Bezpečnost tohoto procesu filtrování - - The necessity of the AdGuard certificate + - Nezbytnost AdGuard certifikátu Postupně klepněte na *Další* → *Další* → *Uložit certifikát*. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 5b802d3e3f7..7ed520bb365 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Níže je uveden seznam nejznámějších aplikací, které lze v AdGuardu nakonfigurovat jako proxy servery. :::note @@ -41,11 +41,11 @@ V tomto článku uvádíme příklady nastavení některých nejoblíbenějšíc | Hostitel proxy | *127.0.0.1* | | Port proxy | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Nebo můžete klepnout na **Proxy server** → **Přidat proxy server**, zadat tyto hodnoty ručně a nastavit Orbot jako výchozí proxy. 1. Zapněte hlavní přepínač Proxy a AdGuard ochranu, aby byl provoz zařízení směrován přes proxy server. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Nyní bude AdGuard směrovat veškerý provoz přes Orbot. Pokud zakážete Orbot, připojení k Internetu bude nedostupné, dokud nezakážete nastavení odchozího proxy v AdGuardu. ### Jak používat AdGuard s PIA (Private Internet Access) @@ -157,4 +157,4 @@ Před nastavením procesu byste měli odstranit aplikaci Shadowsocks z filtrová ## Omezení -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. Chcete-li to provést, musíte přejít na **Správa aplikací**, vybrat aplikaci a zapnout **Směrovat provoz skrze AdGuard**. +Přinejmenším jeden faktor však může zabránit tomu, aby byl určitý provoz směrován přes odchozí proxy server, a to i po konfiguraci nastavení proxy serveru AdGuard. To v případě, že samotná aplikace není nakonfigurována tak, aby odesílala svůj provoz přes AdGuard. Chcete-li to provést, musíte přejít na **Správa aplikací**, vybrat aplikaci a zapnout **Směrovat provoz skrze AdGuard**. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index cf1c14f5104..5fa5657d2e4 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Nebo můžete parametry odebrání nakonfigurovat ručně: ::: -**Don't forget to include the password, package name, and class. Musíte tak učinit pro každý záměr.** +**Nezapomeňte uvést heslo, název balíčku a třídu. Musíte tak učinit pro každý záměr.** Dodatek: `password:*******` @@ -136,7 +136,7 @@ Třída: `com.adguard.android.receiver.AutomationReceiver` :::note -Před verzí 4.0 se třída jmenovala `com.adguard.android.receivers.AutomationReceiver`, ale pak jsme její název změnili na `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Před verzí 4.0 se třída jmenovala `com.adguard.android.receivers.AutomationReceiver`, ale pak jsme její název změnili na `com.adguard.android.receiver.AutomationReceiver`. Pokud tuto funkci použijete, nezapomeňte provést aktualizaci na nový název. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md index 76fce39cd39..889ecbb01a2 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md @@ -11,22 +11,22 @@ Tento článek popisuje AdGuard pro iOS, multifunkční blokátor reklam, který :::note -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. +AdGuard pro iOS s povolenou funkcí Premium i AdGuard Pro blokují reklamy ve smartphonech a tabletech Apple. Dříve se jejich funkce lišily kvůli určitým změnám, které byly v minulosti provedeny v zásadách recenzování v obchodě App Store, ale nyní jsou funkce AdGuard se zakoupeným předplatným a AdGuard Pro totožné. ::: -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. +Prémiový AdGuard pro iOS se od bezplatné verze liší několika funkcemi, včetně vlastního nastavení DNS. Pomocí těchto nastavení můžete blokovat reklamy nejen v Safari, ale i v jiných aplikacích, chránit děti před obsahem pro dospělé na internetu a chránit své osobní údaje před krádeží. Existují i další rozdíly. Pojďme si je všechny podrobněji prozkoumat. -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. +1. Modul **Ochrana DNS** šifruje přenosy DNS, čímž zvyšuje soukromí. Funguje ve všech aplikacích a prohlížečích, nejen v Safari, a nabízí širokou ochranu před reklamami a slídiči. - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. + - **Vlastní DNS servery:** Vyberte si některý z oblíbených DNS serverů z našeho seznamu nebo si přidejte vlastní server. - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. + - **Ochrana rodiny:** Internet není vždy vhodný pro děti. Pomocí AdGuard Premium můžete přejít na poskytovatele DNS, kteří blokují obsah pro dospělé a další nevhodný materiál, aby byly vaše děti na internetu v bezpečí. - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. + - **Monitorování a flexibilní konfigurace:** Protokol o nedávné aktivitě umožňuje zobrazit všechny požadavky DNS odeslané vaším zařízením a snadno spravovat provoz přidáním webových stránek do seznamu blokovanýchí nebo seznamu povolených pouhým klepnutím. -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. +2. **Pokročilá ochrana** vám umožňuje používat pokročilá pravidla filtrování k blokování složitějších reklam, které by jinak zůstaly nezablokované. -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. +3. **Další možnosti filtrování:** Při zakoupení AdGuard Premium získáte přístup k vlastním filtrům a kategorii bezpečnostních filtrů, kde si můžete vybrat z více než 50 filtrů, včetně filtrů AdGuard a dalších populárních seznamů. -Access these features by [purchasing a license](https://adguard.com/license.html). +Přístup k těmto funkcím získáte [zakoupením licence](https://adguard.com/license.html). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 45f392f8ceb..128043c80f3 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ Tento článek popisuje AdGuard pro iOS, multifunkční blokátor reklam, který ### iPhone -Requires iOS 13 or later. +iOS 13 nebo novější. ### iPad -Requires iPadOS 13 or later. +iPadOS 13 nebo novější. ### iPod touch -Requires iOS 13 or later. +iOS 13 nebo novější. ## Instalace AdGuardu pro iOS @@ -29,7 +29,7 @@ AdGuard pro iOS je aplikace uvedená v App Store. Chcete-li AdGuard nainstalovat ![Na hlavní obrazovce App Store klepněte na možnost Hledat *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Do vyhledávacího pole zadejte *AdGuard* a klepněte na řetězec *AdGuard*, který bude mezi výsledky vyhledávání. ![Do vyhledávacího pole zadejte "AdGuard" *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro je placená verze AdGuardu pro iOS, která nabízí rozšířenou sa ![Na hlavní obrazovce App Store klepněte na možnost Hledat *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Do vyhledávacího pole zadejte *AdGuard* a klepněte na řetězec *AdGuard Pro*, který bude mezi výsledky vyhledávání. ![Do vyhledávacího pole zadejte "AdGuard" *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. Můžete být požádáni o zadání přihlašovacího jména a hesla k Apple ID. Zadejte ho a počkejte na dokončení instalace. +Na otevřené stránce App Store klepněte na tlačítko s cenou licence pod řetězcem *AdGuard Pro — adblock*a poté klepněte na *ZAKOUPIT*. Můžete být požádáni o zadání přihlašovacího jména a hesla k Apple ID. Zadejte ho a počkejte na dokončení instalace. ![Klepněte na ZÍSKAT pod AdGuardem *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 118c85bf79a..3bc6cf2d2d8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Tento článek popisuje AdGuard pro iOS, multifunkční blokátor reklam, který 1. Vyberte video a klepněte na *Sdílet*. 1. Klepněte na *Více* a poté vyberte *Blokovat reklamy YouTube (pomocí AdGuardu)*. -The video now opens in AdGuard's ad-free player. +Video se nyní otevře v přehrávači AdGuard bez reklam. ## Jak blokovat reklamy YouTube v Safari @@ -31,4 +31,4 @@ Ujistěte se, že jste povolili AdGuardu přístup ke všem webovým stránkám. 1. Vyberte video a klepněte na *Sdílet*. 1. Klepněte na *Blokovat reklamy YouTube (pomocí AdGuardu)*. -The video now opens in AdGuard's ad-free player. +Video se nyní otevře v přehrávači AdGuard bez reklam. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 91afa8e9edc..5793073b9a6 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: Jak se vyhnout problémům s kompatibilitou s FaceTime sidebar_position: 3 --- diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index d5940bd474c..5f0cb575e1b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Chcete-li přejít na *Nízkoúrovňová nastavení*, klepněte na ikonu ozuben Existují dva hlavní režimy tunelu: *Dělený* a *Úplný*. Režim *Dělený tunel* poskytuje kompatibilitu aplikací AdGuard a takzvaných "Osobních VPN". V režimu *Úplný tunel* nemůže žádná jiná VPN pracovat současně s AdGuardem. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. V tuto chvíli nejsou blokovány žádné reklamy a provoz DNS není šifrován. +Existuje specifická funkce režimu *Dělený tunel*: pokud proxy server DNS nefunguje dobře, například pokud se odpověď ze serveru AdGuard DNS nevrátila včas, systém iOS jej "zneplatní" a přesměruje provoz přes server DNS zadaný v nastavení systému iOS. V tuto chvíli nejsou blokovány žádné reklamy a provoz DNS není šifrován. -V režimu *Úplný tunel* se používá pouze server DNS zadaný v nastavení AdGuardu. Pokud neodpovídá, internet jednoduše nefunguje. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +V režimu *Úplný tunel* se používá pouze server DNS zadaný v nastavení AdGuardu. Pokud neodpovídá, internet jednoduše nefunguje. Zapnutý režim *Úplný tunel* může negativně ovlivnit výkon některých programů (např. FaceTime) a způsobit problémy s aktualizací aplikací. Ve výchozím nastavení používá AdGuard režim *Dělený tunel* jako nejstabilnější možnost. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index c241882595c..57f824788f4 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -21,7 +21,7 @@ Chcete-li najít *Pokročilá nastavení*, otevřete AdGuard, klikněte na ikonu ## Pokročilá nastavení -### Network settings +### Nastavení sítě #### `network.extension.exclude.domains` @@ -71,7 +71,7 @@ Doba v sekundách před odesláním další udržovací sondy neodpovídajícím #### `network.https.ech.enabled` -Používá místní DNS proxy k vyhledání konfigurací v seznamech konfigurací ECH. If found, encrypts Client Hellos. +Používá místní DNS proxy k vyhledání konfigurací v seznamech konfigurací ECH. Pokud je nalezeno, zašifruje ClientHellos. #### `network.https.enforce.certificate.transparency` @@ -89,7 +89,7 @@ Nastavením `true` povolíte filtrování lokální sítě. Nastavením `true` povolíte filtrování LoopBack. -### DNS settings +### Nastavení DNS #### `dns.proxy.bootstrap.ips` @@ -159,7 +159,7 @@ Povolí HTTP/3 pro odchozí připojení DNS-over-HTTPS pro zrychlení připojen Odstraní z dotazů parametry Encrypted Client Hello. -### Stealth Mode settings +### Nastavení Režimu utajení #### `stealth.antidpi.http.split.fragment.size` @@ -177,7 +177,7 @@ Přidá dodatečnou mezeru mezi metodu HTTP a URL adresu a odstraní mezeru za p Zde můžete zadat prodlevu v milisekundách po odeslání prvního fragmentu, pokud je provedena fragmentace. -### Subscription link interception settings (userscripts and filters) +### Nastavení zachycení odkazů předplatného (uživatelské skripty a filtry) #### `subscription.link.interception.userscript` diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 65f486eb8a0..6c700a3c316 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Používáte-li Flutter spolu s AdGuardem v režimu "Rozšíření sítě" (nebo #### Aplikace VPN se starším rozhraním API -Přestože je AdGuard v nastavení systému zobrazen jako VPN, neměl by při práci s jinými aplikacemi založenými na VPN způsobovat žádné konflikty. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Přestože je AdGuard v nastavení systému zobrazen jako VPN, neměl by při práci s jinými aplikacemi založenými na VPN způsobovat žádné konflikty. Pokud je však použita aplikace založená na VPN stažená mimo App Store, existuje riziko, že používá staré rozhraní API VPN a musí být vyloučena z filtrování: 1. Otevřete menu AdGuardu. 1. Vyberte *Předvolby...*. @@ -79,9 +79,9 @@ Tyto problémy již společnost Apple odstranila, ale ve starších verzích sys ### Kompatibilita s Little Snitch 5 -V tuto chvíli není režim Rozšíření sítě v AdGuardu kompatibilní s [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Tento problém je přímo způsoben chybou v Big Sur a společnost Apple jsme o něm již informovali. To nás vede k domněnce, že tento problém bude vyřešen v některé z příštích aktualizací. +V tuto chvíli není režim Rozšíření sítě v AdGuardu kompatibilní s [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Pokud jsou spuštěny obě aplikace, můžete se setkat s problémy s chováním různých aplikací, i když nejsou AdGuardem filtrovány. Tento problém je přímo způsoben chybou v Big Sur a společnost Apple jsme o něm již informovali. To nás vede k domněnce, že tento problém bude vyřešen v některé z příštích aktualizací. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Doporučujeme přepnout na režim filtrování [**Automatický proxy**](#automatic-proxy) při spuštění AdGuardu spolu s Little Snitch na Big Sur, alespoň dokud Apple chybu neopraví. +Zakázání sledování připojení v aplikaci Little Snitch však problém nevyřeší, protože se tím rozšíření Little Snitch ze systémové paměti neodstraní. Doporučujeme přepnout na režim filtrování [**Automatický proxy**](#automatic-proxy) při spuštění AdGuardu spolu s Little Snitch na Big Sur, alespoň dokud Apple chybu neopraví. ### Kompatibilita s lokálními proxy @@ -121,7 +121,7 @@ Především potřebujete funkční server na straně proxy. S největší pravd :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Další informace o tom, jak začít, najdete na [webových stránkách Shadowsocks](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 5c1b8bfcf02..76cd47affc0 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro macOS, multifunkční blokátor reklam, kter ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". Jedná se o nový bezpečnostní mechanismus, který se objevil v softwaru High Sierra a vyžaduje výslovné povolení instalace systémového rozšíření třetí strany. Chcete-li dokončit instalaci AdGuardu, musíte ručně povolit načtení rozšíření v *Předvolbách systému* → *Soukromí a zabezpečení* → *Obecné*. +Během instalace AdGuardu v systému macOS High Sierra (nebo novějších) se může zobrazit zpráva: "Systémové rozšíření zablokováno". Jedná se o nový bezpečnostní mechanismus, který se objevil v softwaru High Sierra a vyžaduje výslovné povolení instalace systémového rozšíření třetí strany. Chcete-li dokončit instalaci AdGuardu, musíte ručně povolit načtení rozšíření v *Předvolbách systému* → *Soukromí a zabezpečení* → *Obecné*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index d7e202fad36..fca8796d4c1 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ V důsledku toho, nemůže AdGuard spolupracovat s funkcemi soukromí iCloud Pri 1. iCloud Private Relay se použije pro připojení na úrovni knihovny — předtím, než se dostanou na úroveň, kde funguje AdGuard. 2. iCloud Private Relay používá QUIC, který AdGuard nemůže filtrovat, protože filtrování HTTP/3 ještě není k dispozici. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. V důsledku toho, AdGuard blokuje QUIC, včetně provozu iCloud Private Relay — jinak je blokování reklam nemožné. 4. Když používáte iCloud Private Relay a přepnete AdGuard do režimu "dělený tunel", nemůžete v Safari otevírat webové stránky. 5. Abychom tento problém pro Monterey obešli, použijeme pravidlo "výchozí směrování". Když iCloud Private Relay uvidí toto pravidlo, automaticky se deaktivuje. AdGuard tedy v Monterey funguje bez problémů, ale iCloud Private Relay je vypnuto. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 7ec25432d25..4c2ae99115b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ Na kartě O produktu se zobrazují informace o aktuální verzi produktu a odkaz :::note Připomínka -AdGuard pro Safari si můžete stáhnout zdarma [z App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard pro Safari si můžete stáhnout zdarma [z App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Podrobný návod k nastavení je k dispozici v [databázi znalostí](/adguard-for-safari/installation/). ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index dbf99590d53..94a29ec602b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: Uživatelská pravidla sidebar_position: 4 --- -K přizpůsobení blokování reklam lze použít uživatelská pravidla. Lze je přidat ručně, importovat nebo vytvořit automaticky při zablokování prvku na stránce. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +K přizpůsobení blokování reklam lze použít uživatelská pravidla. Lze je přidat ručně, importovat nebo vytvořit automaticky při zablokování prvku na stránce. Chcete-li přidávat vlastní pravidla filtrování, použijte [speciální syntaxi](/general/ad-filtering/create-own-filters). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/ads-not-blocked.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/ads-not-blocked.md index fa81950ace9..a3461eb9041 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/ads-not-blocked.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/ads-not-blocked.md @@ -16,7 +16,7 @@ V některých případech nemusí filtrování fungovat a reklamy se mohou zobra 1. Otevřete Safari. 2. Klikněte na _Safari_ v nabídce v levém horním rohu. 3. Klikněte na _Nastavení…_ → _Rozšíření_. -4. Clear the checkboxes for AdGuard’s extensions: _Custom_, _General_, _Other_, _Privacy_, _Security_, _Social_, _AdGuard for Safari_, and _AdGuard Assistant_. +4. Zrušte zaškrtnutí políček u rozšíření AdGuard: _Vlastní_, _Obecné_, _Jiné_, _Soukromí_, _Zabezpečení_, _Sociální sítě_, _AdGuard pro Safari_ a _AdGuard Asistent_. ![Unchecked content blockers](https://cdn.adtidy.org/content/Kb/ad_blocker/safari/adg-safari-unchecked-cbs.png) 5. Restartujte Safari. 6. Vraťte se do _Nastavení..._ → _Rozšíření_ a znovu povolte rozšíření pro blokování obsahu. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/filters-after-disable.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/filters-after-disable.md index 2a293acd07d..6d327c5cae0 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/filters-after-disable.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/filters-after-disable.md @@ -16,7 +16,7 @@ Pokud se filtrování po vypnutí AdGuardu pro Safari nezastaví, může to být 1. Otevřete Safari. 2. Klikněte na _Safari_ v nabídce v levém horním rohu. 3. Klikněte na _Nastavení…_ → _Rozšíření_. -4. Clear the checkboxes for AdGuard’s extensions: _Custom_, _General_, _Other_, _Privacy_, _Security_, _Social_, _AdGuard for Safari_, and _AdGuard Assistant_. +4. Zrušte zaškrtnutí políček u rozšíření AdGuard: _Vlastní_, _Obecné_, _Jiné_, _Soukromí_, _Zabezpečení_, _Sociální sítě_, _AdGuard pro Safari_ a _AdGuard Asistent_. ![Unchecked content blockers](https://cdn.adtidy.org/content/Kb/ad_blocker/safari/adg-safari-unchecked-cbs.png) 5. Restartujte Safari. 6. Vraťte se do _Nastavení..._ → _Rozšíření_ a znovu povolte rozšíření pro blokování obsahu. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index c8f409e3d1d..024e312b8d5 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -1,5 +1,5 @@ --- -title: How to collect logs in AdGuard for Safari +title: Jak shromažďovat protokoly v AdGuardu pro Safari sidebar_position: 4 --- @@ -9,22 +9,22 @@ Tento článek je o AdGuardu pro Safari, který chrání pouze váš prohlíže ::: -K analýze a diagnostice různých problémů, které mohou nastat s AdGuardem pro Safari, může služba podpory AdGuardu potřebovat soubory záznamu. Tyto soubory obsahují záznamy o chybách a dalších softwarových událostech. Below are brief instructions on how to collect logs and send them to support if necessary. +K analýze a diagnostice různých problémů, které mohou nastat s AdGuardem pro Safari, může služba podpory AdGuardu potřebovat soubory záznamu. Tyto soubory obsahují záznamy o chybách a dalších softwarových událostech. Níže jsou uvedeny stručné pokyny, jak shromažďovat protokoly a v případě potřeby je odesílat na podporu. -### How to collect logs +### Jak shromažďovat a záznamy 1. Otevřete aplikaci AdGuard pro Safari. 2. Přejděte dolů a klikněte na _Exportovat protokoly_. 3. Zvolte umístění pro uložení souboru .zip a klikněte na _Uložit_. -Now you can send this file to support@adguard.com or attach it to your bug report on GitHub. +Nyní můžete tento soubor odeslat na support@adguard.com nebo jej připojit k hlášení o chybě na GitHubu. :::note -AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/safari.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. +AdGuard se zavazuje chránit vaše soukromí. Přísně dodržujeme naše [Zásady ochrany osobních údajů](https://adguard.com/privacy/safari.html) a neshromažďujeme žádné soukromé informace o uživatelích. Před odesláním protokolů týmu podpory si soubor prohlédněte, protože může obsahovat další informace, které nechcete sdílet. Pokud takové osobní údaje obsahuje, doporučujeme je nejprve smazat. ::: -1. Open the [AdGuard for Safari GitHub repo](https://github.com/AdguardTeam/AdGuardForSafari/issues) and click _New issue_. -2. Send the log file to devteam@adguard.com. Uveďte čas chyby a připojte odkaz na problém nebo jeho číslo (zobrazuje se jako #číslo vedle názvu). - Soubor se záznamem můžete také nahrát na Disk Google a odeslat jej na adresu devteam@adguard.com. Add the file link to your GitHub issue. +1. Otevřete [GitHub repozitář AdGuard pro Safari](https://github.com/AdguardTeam/AdGuardForSafari/issues) a klikněte na _New issue_. +2. Odešlete soubor se záznamem na devteam@adguard.com. Uveďte čas chyby a připojte odkaz na problém nebo jeho číslo (zobrazuje se jako #číslo vedle názvu). + Soubor se záznamem můžete také nahrát na Disk Google a odeslat jej na adresu devteam@adguard.com. Přidejte odkaz na soubor do svého problému na GitHubu. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 4ddb33f3ef1..7d9c5dcee4f 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant je starší asistent, kterého můžete použít, pokud pro v Jedná se o vlastní rozšíření určené k boji proti technice opětovného vkládání blokovaných reklam — tzv. obcházení blokátorů reklam/opětovnému vkládání reklam. V obou případech se jedná o pokročilé metody proti blokování reklam, jejichž obliba mezi inzerenty stále roste. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra je v podstatě miniprogram, který změní fungování stránek tak, aby bylo pro weby mnohem obtížnější používat výše uvedené metody k obcházení blokátorů. **AdGuard blokátor vyskakovacích oken** -Toto rozšíření zabraňuje otevírání vyskakovacích oken při prohlížení webových stránek. Některá vyskakovací okna jsou považována za užitečná — mohou obsahovat nastavení pro správu webu nebo další referenční informace zobrazené po kliknutí na odkaz. Proto můžete blokátor v případě potřeby vypnout. Toto rozšíření nefunguje ani na webových stránkách přidaných do seznamu výjimek AdGuardu. Ve výchozím nastavení je vypnuto, ale můžete jej zapnout v nastavení aplikace. You will find more detailed information about this extension in our Knowledge Base. +Toto rozšíření zabraňuje otevírání vyskakovacích oken při prohlížení webových stránek. Některá vyskakovací okna jsou považována za užitečná — mohou obsahovat nastavení pro správu webu nebo další referenční informace zobrazené po kliknutí na odkaz. Proto můžete blokátor v případě potřeby vypnout. Toto rozšíření nefunguje ani na webových stránkách přidaných do seznamu výjimek AdGuardu. Ve výchozím nastavení je vypnuto, ale můžete jej zapnout v nastavení aplikace. Podrobnější informace o tomto rozšíření najdete v naší databázi znalostí. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust vám umožňuje zjistit pověst každého webu na základě názor ### Síť -Předposlední modul je věnován filtrování sítě a najdete v něm další možnosti související se sítí. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Jedná se o důležitá dodatečná opatření pro lepší filtrování webového prostoru. Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Předposlední modul je věnován filtrování sítě a najdete v něm další možnosti související se sítí. Dvě z nich jsou standardně povoleny: _Povolit filtrování provozu_ a _Filtrovat HTTPS_. Jedná se o důležitá dodatečná opatření pro lepší filtrování webového prostoru. Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. Z mnoha webů, jako je youtube.com, facebook.com a x.com, není možné odstranit reklamy bez HTTPS filtrování. Pokud tedy nemáte pádný důvod, ponechte funkci _Filtrovat HTTPS_ povolenou. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index c03a212a61d..f85f5700111 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Nastavení_ je část, která vyžaduje největší pozornost. Zde můžete pro ### Obecná nastavení -Zde můžete nastavit jazyk a motiv (tmavý nebo světlý), povolit spouštění AdGuardu při startu systému a tiché automatické aktualizace, vybrat aktualizační kanál a interval kontroly aktualizací filtrů. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Zde můžete nastavit jazyk a motiv (tmavý nebo světlý), povolit spouštění AdGuardu při startu systému a tiché automatické aktualizace, vybrat aktualizační kanál a interval kontroly aktualizací filtrů. Pokud AdGuard pro Windows nefunguje správně a tým podpory vás požádal, abyste [shromáždili _Protokoly ladění_](/adguard-for-windows/solving-problems/adguard-logs.md), přejděte do Nastavení. ![Advanced Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -31,7 +31,7 @@ V modulu Blokátor reklam můžete: - povolit automatickou aktivaci jazykově specifických filtrů, - deaktivovat blokování [reklam ve vyhledávání a vlastní propagaci](/general/ad-filtering/search-ads), -- disable ads in the Start menu on Windows 11, +- zakázat reklamy v nabídce Start ve Windows 11, - aktivovat předinstalované filtry, jako je _AdGuard Base filtr_, - instalovat filtry ze seznamu nebo přidat vlastní filtr kliknutím na tlačítko _Přidat filtr_, - provádět změny ve stávajících skupinách pravidel pomocí tlačítka _Editor filtrů_, @@ -80,7 +80,7 @@ Existuje několik webových stránek, ke kterým by měl být omezen přístup z Modul kontroluje obsah webových stránek otevřených v prohlížeči a filtruje ty, jejichž obsah je pro děti nežádoucí: obrázky a texty pro dospělé, hrubý jazyk, násilí, propagace drog atd. Nastavení Rodičovské ochrany jsou zabezpečena heslem, takže dítě nemůže obejít omezení. Tento modul nejenže blokuje vstup na nežádoucí stránky, ale také dokáže z výsledků vyhledávání odstranit odkazy, které jsou nevhodné pro děti. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Můžete také zaškrtnout políčko _Blokovat stahování spustitelných souborů_ a zabránit tak vašemu dítěti ve stahování a instalaci softwaru do PC. V modulu _Rodičovská ochrana_ jsou další dvě možnosti: můžete vybrat konkrétního uživatele Windows, který má být chráněn _Rodičovskou ochranou_ a nastavit heslo pro zabezpečení nastavení AdGuardu před změnami. +V modulu _Rodičovská ochrana_ můžete povolit _Bezpečné vyhledávání_, spravovat _seznam zakázaných_, _seznam povolených_ a přizpůsobit si funkce těchto možností. Můžete také zaškrtnout políčko _Blokovat stahování spustitelných souborů_ a zabránit tak vašemu dítěti ve stahování a instalaci softwaru do PC. V modulu _Rodičovská ochrana_ jsou další dvě možnosti: můžete vybrat konkrétního uživatele Windows, který má být chráněn _Rodičovskou ochranou_ a nastavit heslo pro zabezpečení nastavení AdGuardu před změnami. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index c14950e59e5..ab4b8d1817b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -91,7 +91,7 @@ Další kroky proveďte pouze v případě, že provedení prvních dvou kroků ::: -- Vyberte *Blokátor reklam AdGuard* a *Rozšířený* typ odinstalace a poté klikněte na *Odinstalovat*. Click *Yes, continue* in the window prompt. +- Vyberte *Blokátor reklam AdGuard* a *Rozšířený* typ odinstalace a poté klikněte na *Odinstalovat*. Ve okně výzvy klikněte na *Ano, pokračovat*. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 59826c0f4cb..4e1f089ebc3 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -19,7 +19,7 @@ K analýze a diagnostice různých problémů, které mohou potenciálně nastat :::note -AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. +AdGuard se zavazuje chránit vaše soukromí. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Před odesláním protokolů týmu podpory si soubor prohlédněte, protože může obsahovat další informace, které nechcete sdílet. Pokud takové osobní údaje obsahuje, doporučujeme je nejprve smazat. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index e4fd3d6e4b7..fe4749e935c 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -45,6 +45,6 @@ Odešlete prosím dva soubory, které jste nedávno uložili na adresu **support :::note -AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. +AdGuard se zavazuje chránit vaše soukromí. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Před odesláním protokolů týmu podpory si soubor prohlédněte, protože může obsahovat další informace, které nechcete sdílet. Pokud takové osobní údaje obsahuje, doporučujeme je nejprve smazat. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md index fd6c385ea93..a283ef8b455 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ V části Historie nákupů se zobrazují všechny licence, které jste kdy zako ## Kontaktování podpory -Karta Podpora obsahuje užitečné odkazy, které vám pomohou vyřešit problémy nebo najít odpovědi na vaše otázky týkající se AdGuard produktů. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +Karta Podpora obsahuje užitečné odkazy, které vám pomohou vyřešit problémy nebo najít odpovědi na vaše otázky týkající se AdGuard produktů. Jsou rozděleny do šesti oddílů: FAQ, Odeslat požadavek na chybu/funkci, Nahlásit nesprávné blokování, Kontaktovat podporu, Databáze znalostí a Diskutovat. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 6278a12d56f..e23a2d29f3c 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -235,7 +235,7 @@ Pravidla se zástupným znakem pro TLD nejsou podporována Blokátorem obsahu Ad - `||example.com/ads/*` — jednoduché pravidlo, které odpovídá adresám typu `http://example.com/ads/banner.jpg` a dokonce i `http://subdomain.example.com/ads/otherbanner.jpg`. -- `||example.org^$third-party` — this rule blocks third-party requests to `example.org` and its subdomains. +- `||example.org^$third-party` — toto pravidlo blokuje požadavky třetích stran na `example.org` a jejím subdoménám. - `@@||example.com$document` — obecné pravidlo výjimky. Zcela vypne filtrování pro `example.com` a všechny subdomény. V pravidlech pro výjimky lze použít řadu modifikátorů. Pro více podrobností klikněte na [odkaz ](#exception-modifiers) níže. @@ -265,7 +265,7 @@ Následující modifikátory jsou nejjednodušší a nejčastěji používané. -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| | [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | | [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -284,7 +284,7 @@ Následující modifikátory jsou nejjednodušší a nejčastěji používané. - ✅ — plně podporováno - ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ - funkce, jejíž implementace se plánuje, ale zatím není k dispozici v žádném produktu - ❌ — nepodporováno ::: @@ -326,7 +326,7 @@ Aplikace v hodnotě modifikátoru nemohou mít zástupný znak, např. `$app=com Modifikátor `$denyallow` umožňuje vyhnout se vytváření dalších pravidel, pokud je potřeba zakázat určité pravidlo pro konkrétní domény. `$denyallow` odpovídá pouze cílovým doménám, nikoli doménám odkazujícím. -Přidání tohoto modifikátoru k pravidlu je ekvivalentní vyloučení domén podle shodného vzoru pravidla nebo přidání odpovídajících pravidel výjimek. To add multiple domains to one rule, use the `|` character as a separator. +Přidání tohoto modifikátoru k pravidlu je ekvivalentní vyloučení domén podle shodného vzoru pravidla nebo přidání odpovídajících pravidel výjimek. Chcete-li do jednoho pravidla přidat více domén, použijte jako oddělovací znak `|`. **Příklady** @@ -444,7 +444,7 @@ V následujících příkladech se předpokládá, že požadavky jsou odesílá ##### omezení modifikátoru `$domain` {#domain-modifier-limitations} -:::caution Limitations +:::caution Omezení In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. @@ -575,7 +575,7 @@ AdGuard se pokusí zavřít kartu prohlížeče s jakoukoli adresou, která odpo ##### `$popup` modifier limitations {#popup-modifier-limitations} -:::caution Limitations +:::caution Omezení 1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. 1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. @@ -663,7 +663,7 @@ Místo plného názvu modifikátoru můžete použít kratší název (alias): ` #### **`$to`** {#to-modifier} -`$to` omezuje rozsah pravidla na požadavky **na** zadané domény a jejich subdomény. To add multiple domains to one rule, use the `|` character as a separator. +`$to` omezuje rozsah pravidla na požadavky **na** zadané domény a jejich subdomény. Chcete-li do jednoho pravidla přidat více domén, použijte jako oddělovací znak `|`. **Příklady** @@ -701,7 +701,7 @@ V tom, jak AdGuard určuje typ obsahu na různých platformách, je velký rozd -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| | [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | | [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | @@ -776,7 +776,7 @@ Pravidlo odpovídá požadavkům vyvolaným buď `navigator.sendBeacon()`, nebo ##### `$ping` modifier limitations {#ping-modifier-limitations} -:::caution Limitations +:::caution Omezení AdGuard pro Windows, Mac a Android často nedokáží přesně detekovat `navigator.sendBeacon()`. V seznamech filtrů, které mají používat AdGuard produkty založené na knihovně CoreLibs, se nedoporučuje používat `$ping`. @@ -819,7 +819,7 @@ Místo plného názvu modifikátoru můžete použít kratší název (alias): ` ##### `$subdocument` modified limitations {#subdocument-modifier-limitations} -:::caution Limitations +:::caution Omezení In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. V opačném případě mohou být některé hlavní stránky považovány za dílčí dokumenty. @@ -837,7 +837,7 @@ Pravidlo se vztahuje pouze na připojení WebSocket. ##### `$websocket` modifier limitations {#websocket-modifier-limitations} -:::caution Limitations +:::caution Omezení For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. @@ -900,7 +900,7 @@ Doporučujeme také seznámit se s [přehledem filtrů Adblock Plus](https://adb -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | --------------------------------------- |:----------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| | [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | | [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | @@ -1081,7 +1081,7 @@ Zakáže blokování všech požadavků odeslaných ze stránek, které odpovíd ##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} -:::caution Limitations +:::caution Omezení V AdGuardu pro iOS a AdGuardu pro Safari fungují pravidla `$urlblock` jako [$document exclusion](#document-modifier) — odblokování všeho. @@ -1126,7 +1126,7 @@ Zakáže generická základní pravidla na stránkách, které odpovídají prav ##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} -:::caution Limitations +:::caution Omezení V AdGuardu pro iOS a AdGuardu pro Safari fungují pravidla `$genericblock` jako [$document exclusion](#document-modifier) — odblokování všeho. @@ -1184,7 +1184,7 @@ Tyto modifikátory mohou zcela změnit chování základních pravidel. -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| | [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | | [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | @@ -1212,7 +1212,7 @@ Tyto modifikátory mohou zcela změnit chování základních pravidel. - ✅ — plně podporováno - ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ - funkce, jejíž implementace se plánuje, ale zatím není k dispozici v žádném produktu - ❌ — nepodporováno - 👎 — deprecated; still supported but will be removed in the future @@ -1234,7 +1234,7 @@ This modifier cannot be used as an exception with the `@@` mark. ##### `$all` modifier limitations {#all-modifier-limitations} -:::caution Limitations +:::caution Omezení Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). @@ -1275,7 +1275,7 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma ##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} -:::caution Limitations +:::caution Omezení In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) @@ -1338,7 +1338,7 @@ There are two methods to deactivate `$cookie` rules: the primary method involves ##### `$cookie` modifier limitations {#cookie-modifier-limitations} -:::caution Limitations +:::caution Omezení In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). @@ -1519,7 +1519,7 @@ preroll.ts :::caution Omezení -- Pravidla `$hls` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` pravidla platí pouze pro seznamy stop HLS, což je text kódovaný v UTF-8 začínající řádkem `#EXTM3U`. Jakákoli jiná odpověď nebude těmito pravidly upravena. - Pravidla `$hls` neplatí, pokud je velikost původní odpovědi větší než 10 MB. @@ -2093,7 +2093,7 @@ If there are multiple `$permissions` rules that match the same request, multiple ##### `$permissions` modifier limitations {#permissions-modifier-limitations} -:::caution Limitations +:::caution Omezení Firefox ignores the `Permissions-Policy` header. For more information, see [this issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1694922). @@ -2147,7 +2147,7 @@ Další podrobnosti najdete v [prioritách pravidel](#rule-priorities). ##### `$redirect` modifier limitations {#redirect-modifier-limitations} -:::caution Limitations +:::caution Omezení In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Omezení -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. Aby nedošlo k narušení bezpečnosti, nelze z níže uvedeného seznamu odstranit záhlaví `$removeheader`: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2418,7 +2416,7 @@ With these rules, specified UTM parameters will be removed from any request save ##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} -:::caution Limitations +:::caution Omezení [AdGuard for Chrome MV3][ext-mv3] has some limitations: @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + je převedeno na ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Omezení -- Pravidla s modifikátorem `$removeparam` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters). -- Pravidla `$removeparam` jsou kompatibilní se [základními modifikátory](#basic-rules-basic-modifiers), [modifikátory typu obsahu](#content-type-modifiers) a s modifikátory `$important` a `$app`. Pravidla s jinými modifikátory jsou považována za neplatná a budou vyřazena. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Pravidla s jinými modifikátory jsou považována za neplatná a budou vyřazena. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2509,11 +2508,11 @@ You will need some knowledge of regular expressions to use `$replace` modifier. **Features** -- Pravidla `$replace` platí pro jakoukoli textovou odpověď, ale neplatí pro binární (`media`, `image`, `object` atd.). -- Pravidla `$replace` neplatí, pokud je velikost původní odpovědi větší než 10 MB. -- Pravidla `$replace` mají vyšší prioritu než ostatní základní pravidla (**včetně** pravidel výjimek). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. -- Pravidla výjimek na úrovni dokumentu s modifikátory `$content` nebo `$document` zakáží pravidla `$replace` pro požadavky, které jim odpovídají. -- Ostatní pravidla výjimek na úrovni dokumentu (`$generichide`, `$elemhide` nebo modifikátory `$jsinject`) se uplatňují vedle pravidel `$replace`. To znamená, že můžete upravit obsah stránky pomocí pravidla `$replace` a zároveň zde zakázat kosmetická pravidla. +- `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). +- `$replace` rules do not apply if the size of the original response is more than 10 MB. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. +- Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. `$replace` value can be empty in the case of exception rules. See examples section for further information. @@ -2529,9 +2528,9 @@ In general, `$replace` syntax is similar to replacement with regular expressions replace = "/" regexp "/" replacement "/" modifiers ``` -- **`regexp`** — regulární výraz. -- **`replacement`** — řetězec, který bude použit k nahrazení řetězce odpovídajícího `regexp`. -- **`modifiers`** — příznaky regulárního výrazu. Například `i` — necitlivé vyhledávání nebo `s` — jednořádkový režim. +- **`regexp`** — a regular expression. +- **`replacement`** — a string that will be used to replace the string corresponding to `regexp`. +- **`modifiers`** — a regular expression flags. For example, `i` — insensitive search, or `s` — single-line mode. In the `$replace` value, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` for it. For example, an escaped comma looks like this: `\,`. @@ -2544,8 +2543,8 @@ In the `$replace` value, two characters must be escaped: comma `,` and dollar si There are three parts in this rule: - `regexp` — `()(.|\s)*<\/VAST>`; -- `replacement` — `\$1<\/VAST>` kde `$` je uvozeno; -- `modifikátory` — `i` pro necitlivé vyhledávání. +- `replacement` — `\$1<\/VAST>` where `$` is escaped; +- `modifiers` — `i` for insensitive search. You can see how this rule works here: http://regexr.com/3cesk @@ -2555,17 +2554,17 @@ You can see how this rule works here: http://regexr.com/3cesk 2. `||example.org^$replace=/Z/Y/` 3. `@@||example.org/page/*$replace=/Z/Y/` -- Jak pravidlo 1, tak pravidlo 2 se použijí na všechny požadavky odeslané na `example.org`. -- Pravidlo 2 je zakázáno pro požadavky odpovídající na `||example.org/page/`, **ale pravidlo 1 stále funguje!** +- Both rule 1 and 2 will be applied to all requests sent to `example.org`. +- Rule 2 is disabled for requests matching `||example.org/page/`, **but rule 1 still works!** **Disabling `$replace` rules** -- `@@||example.org^$replace` zakáže všechna pravidla `$replace` odpovídající na `||example.org^`. -- `@@||example.org^$document` nebo `@@||example.org^$content` zakáže všechna pravidla `$replace` **pocházející ze** stránek `example.org` **včetně stránky samotné**. +- `@@||example.org^$replace` will disable all `$replace` rules matching `||example.org^`. +- `@@||example.org^$document` or `@@||example.org^$content` will disable all `$replace` rules **originated from** pages of `example.org` **including the page itself**. :::caution Omezení -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2582,8 +2581,8 @@ The `$urltransform` rules allow you to modify the request URL by replacing text **Features** - `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. -- `$urltransform` nebude použito, pokud je původní URL blokována jinými pravidly. -- `$urltransform` se použije před pravidly `$removeparam`. +- `$urltransform` will not be applied if the original URL is blocked by other rules. +- `$urltransform` will be applied before `$removeparam` rules. The `$urltransform` value can be empty for exception rules. @@ -2599,9 +2598,9 @@ If multiple `$urltransform` rules match a single request, we will apply each of urltransform = "/" regexp "/" replacement "/" modifiers ``` -- **`regexp`** — regulární výraz. -- **`replacement`** — řetězec, který bude použit k nahrazení řetězce odpovídajícího `regexp`. -- **`modifiers`** — příznaky regulárního výrazu. Například `i` — necitlivé vyhledávání nebo `s` — jednořádkový režim. +- **`regexp`** — a regular expression. +- **`replacement`** — a string that will be used to replace the string corresponding to `regexp`. +- **`modifiers`** — a regular expression flags. For example, `i` — insensitive search, or `s` — single-line mode. In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. @@ -2624,8 +2623,8 @@ As stated above, normally `$urltransform` rules are only allowed to change the p There are three parts in this rule: - `regexp` — `(pref\/).*\/(suf)`; -- `replacement` — `\$1\$2` kde `$` je uvozeno; -- `modifikátory` — `i` pro necitlivé vyhledávání. +- `replacement` — `\$1\$2` where `$` is escaped; +- `modifiers` — `i` for insensitive search. **Multiple `$urltransform` rules** @@ -2633,8 +2632,8 @@ There are three parts in this rule: 2. `||example.org^$urltransform=/Z/Y/` 3. `@@||example.org/page/*$urltransform=/Z/Y/` -- Jak pravidlo 1, tak pravidlo 2 se použijí na všechny požadavky odeslané na `example.org`. -- Pravidlo 2 je zakázáno pro požadavky odpovídající na `||example.org/page/`, **ale pravidlo 1 stále funguje!** +- Both rule 1 and 2 will be applied to all requests sent to `example.org`. +- Rule 2 is disabled for requests matching `||example.org/page/`, **but rule 1 still works!** **Re-matching rules after transforming the URL** @@ -2651,14 +2650,14 @@ the request to `https://example.com/firstpath` will be blocked. **Disabling `$urltransform` rules** -- `@@||example.org^$urltransform` zakáže všechna pravidla `$urltransform` odpovídající na `||example.org^`. -- `@@||example.org^$urltransform=/Z/Y/` zakáže pravidlo s `$urltransform=/Z/Y/` pro jakýkoliv požadavek, který odpovídá `||example.org^`. +- `@@||example.org^$urltransform` will disable all `$urltransform` rules matching `||example.org^`. +- `@@||example.org^$urltransform=/Z/Y/` will disable the rule with `$urltransform=/Z/Y/` for any request matching `||example.org^`. `$urltransform` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$urltransform=/X/Y/` for requests to **example.com**, but `@@||example.com^$urlblock` will. :::caution Omezení -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2697,7 +2696,7 @@ Usually, blocked requests look like a server error to browser. If you use `$empt **Příklady** -- `||example.org^$empty` vrátí prázdnou odpověď na všechny požadavky na `example.org` a všechny subdomény. +- `||example.org^$empty` returns an empty response to all requests to `example.org` and all subdomains. :::info Kompatibilita @@ -2717,7 +2716,7 @@ As a response to blocked request AdGuard returns a short video placeholder. **Příklady** -- `||example.com/videa/$mp4` zablokuje všechna stahování videa z `||example.com/videa/*` a změní odpověď na zástupný videoklip. +- `||example.com/videos/$mp4` blocks all video downloads from `||example.com/videos/*` and changes the response to a video placeholder. :::info Kompatibilita @@ -2751,8 +2750,8 @@ The base priority of any rule is 1. If the calculated priority is a floating-poi :::info Kompatibilita -- The concept of priority has been introduced in [TSUrlFilter][] v2.1.0 and [CoreLibs][] v1.13. Dříve neměl AdGuard žádný speciální algoritmus pro výpočet priorit a zpracování kolizí se mohlo lišit v závislosti na produktu a verzi AdGuardu. -- Aplikace AdGuard pro iOS, Safari a Blokátor obsahu AdGuard se spoléhají na implementaci prohlížečů a nemohou dodržovat zde uvedená pravidla. +- The concept of priority has been introduced in [TSUrlFilter][] v2.1.0 and [CoreLibs][] v1.13. Before that AdGuard didn't have any special priority computation algorithm and collisions handling could be different depending on AdGuard product and version. +- AdGuard for iOS, Safari, and AdGuard Content Blocker rely on the browsers implementation and they cannot follow the rules specified here. ::: @@ -2766,16 +2765,16 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve -- [`$app`](#app-modifier) s negovanými aplikacemi pomocí `~`, +- [`$app`](#app-modifier) with negated applications using `~`, - [`$denyallow`](#denyallow-modifier), -- [`$domain`](#domain-modifier) s negovanými doménami pomocí `~`, +- [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), -- [`$method`](#method-modifier) s negovanými metodami pomocí `~`, +- [`$method`](#method-modifier) with negated methods using `~`, - [`$strict-first-party`](#strict-first-party-modifier), - [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), -- omezené [typy obsahu](#content-type-modifiers) s `~`. +- restricted [content-types](#content-type-modifiers) with `~`. When dealing with a negated domain, app, method, or content-type, we add **1 point** for the existence of the modifier itself, regardless of the quantity of negated domains or content-types. This is because the rule's scope is already infinitely broad. Put simply, by prohibiting multiple domains, content-types, methods or apps, the scope of the rule becomes only minimally smaller. @@ -2889,45 +2888,45 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking 1. `||example.com^` - Váha pravidla bez modifikátorů: `1`. + Weight of the rule without modifiers: `1`. 1. `||example.com^$match-case` - Váha pravidla: základní + váha modifikátoru z [kategorie 1](#priority-category-1): `1 + 1 = 2`. + Rule weight: base weight + weight of the modifier from [category 1](#priority-category-1): `1 + 1 = 2`. 1. `||example.org^$removeparam=p` - Váha pravidla: základní váha + 0, protože $removeparam [není zahrnuto](#priority-category-extra) do výpočtu priority: `1 + 0 = 1`. + Rule weight: base weight + 0, since $removeparam [is not involved](#priority-category-extra) in the priority calculation: `1 + 0 = 1`. 1. `||example.org^$document,redirect=nooptext` - Váha pravidla: základní + povolený typ obsahu, [kategorie 3](#priority-category-3) + $redirect z [kategorie 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`. + Rule weight: base weight + allowed content type, [category 3](#priority-category-3) + $redirect from [category 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`. 1. `@@||example.org^$removeparam=p,document` - Váha pravidla: základní váha + pravidlo seznamu povolených [kategorie 5](#priority-category-5) + 0, protože $removeparam [není zapojeno](#priority-category-extra) do výpočtu priority + povolený typ obsahu [kategorie 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`. + Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + 0 because $removeparam [is not involved](#priority-category-extra) in the priority calculation + allowed content type, [category 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`. 1. `@@||example.com/ad/*$domain=example.org|example.net,important` - Váha pravidla: základní váha + pravidlo seznamu povolených [kategorie 5](#priority-category-5) + důležité pravidlo [kategorie 7](#priority-category-7) + povolené domény [kategorie 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`. + Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + important rule, [category 7](#priority-category-7) + allowed domains, [category 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`. -1. `@@||example.org^$document` bez dalších modifikátorů je aliasem pro `@@||example.com^$elemhide,content,jsinject,urlblock,extension` +1. `@@||example.org^$document` without additional modifiers is an alias for `@@||example.com^$elemhide,content,jsinject,urlblock,extension` - Váha pravidla: základní váha + specifické výjimky, [kategorie 4](#priority-category-4) + dva povolené typy obsahu (dokument a subdokument) [kategorie 2](#priority-category-2): `1 + 10000 * 4 + (50 + 50 / 2) = 40076`. + Rule weight: base weight + specific exceptions, [category 4](#priority-category-4) + two allowed content types (document and subdocument), [category 2](#priority-category-2): `1 + 10000 * 4 + (50 + 50 / 2) = 40076`. 1. `*$script,domain=a.com,denyallow=x.com|y.com` - Váha pravidla: základní váha + povolený typ obsahu [kategorie 2](#priority-category-2) + povolená doména, [kategorie 3](#priority-category-3) + denyallow [kategorie 1](#priority-category-1): `1 + (50 + 50/1) + (100 + 100 / 1) + 1 = 303`. + Rule weight: base weight + allowed content type, [category 2](#priority-category-2) + allowed domain, [category 3](#priority-category-3) + denyallow, [category 1](#priority-category-1): `1 + (50 + 50/1) + (100 + 100 / 1) + 1 = 303`. -1. `||example.com^$all` — alias na `||example.com^$document,subdocument,image,script,media,etc. + $popup` +1. `||example.com^$all` — alias to `||example.com^$document,subdocument,image,script,media,etc. + $popup` - Váha pravidla: základní váha + vyskakovací okno ([kategorie 1](#priority-category-1)) + povolené typy obsahu ([kategorie 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`. + Rule weight: base weight + popup ([category 1](#priority-category-1)) + allowed content types ([category 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`. ## Ostatní pravidla {#non-basic-rules} However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Kategorie \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| Kategorie \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | ---------------------------------------- |:----------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| | [Skrytí prvků](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | | [Pravidla CSS](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | @@ -2964,8 +2963,8 @@ Element hiding rules may operate differently [depending on the platform](#cosmet domains = [domain0, domain1[, ...[, domainN]]] ``` -- **`selector`** — [CSS selektor](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors) definuje prvky, které mají být skryty. -- **`domains`** — omezení domény pro dané pravidlo. +- **`selector`** — [CSS selector](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), defines the elements to be hidden. +- **`domains`** — domain restriction for the rule. If you want to limit the rule application area to certain domains, just enter them separated with commas. For example: `example.org,example.com##selector`. @@ -2983,9 +2982,9 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Příklady** -- `example.com##div.textad` — skryje `div` s třídou `textad` na doméně `example.com` a všech subdoménách. -- `example.com,example.org###adblock` — skryje prvek s atributem `id`, který se rovná `adblock` na `example.com`, `example.org` a všech subdoménách. -- `~example.com##.textad` — skryje prvek s třídou `textad` na všech doménách kromě `example.com` a jejích subdomén. +- `example.com##div.textad` — hides a `div` with the class `textad` at `example.com` and all subdomains. +- `example.com,example.org###adblock` — hides an element with attribute `id` equals `adblock` at `example.com`, `example.org` and all subdomains. +- `~example.com##.textad` — hides an element with the class `textad` at all domains, except `example.com` and its subdomains. **Omezení** @@ -3032,9 +3031,9 @@ Sometimes, simple hiding of an element is not enough to deal with advertising. F domains = [domain0, domain1[, ...[, domainN]]] ``` -- **`selector`** — [selektor CSS](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), který definuje prvky, na které chceme styl použít. -- **`domains`** — omezení domény pro dané pravidlo. Stejné zásady jako v [pravidlech pro skrývání prvků](#cosmetic-elemhide-rules). -- **`style`** — styl CSS, který chceme použít na vybrané prvky. +- **`selector`** — [CSS selector](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), that defines the elements we want to apply the style to. +- **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). +- **`style`** — CSS style, that we want to apply to selected elements. **Příklady** @@ -3079,18 +3078,18 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr ### Rozšířené CSS selektory {#extended-css-selectors} - [Omezení](#extended-css-limitations) -- [Pseudo-třída `:has()`](#extended-css-has) -- [Pseudo-třída `:contains()`](#extended-css-contains) +- [Pseudo-class `:has()`](#extended-css-has) +- [Pseudo-class `:contains()`](#extended-css-contains) - [Pseudo-třída `:matches-css()`](#extended-css-matches-css) -- [Pseudo-třída `:matches-attr()`](#extended-css-matches-attr) -- [Pseudo-třída `:matches-property()`](#extended-css-property) -- [Pseudo-třída `:xpath()`](#extended-css-xpath) -- [Pseudo-třída `:nth-ancestor()`](#extended-css-nth-ancestor) -- [Pseudo-třída `:upward()`](#extended-css-upward) -- [Pseudo-třída `:remove()` a pseudo-vlastnost `remove`](#remove-pseudos) -- [Pseudo-třída `:is()`](#extended-css-is) -- [Pseudo-třída `:not()`](#extended-css-not) -- [Pseudo-třída `:if-not()` (odstraněno)](#extended-css-if-not) +- [Pseudo-class `:matches-attr()`](#extended-css-matches-attr) +- [Pseudo-class `:matches-property()`](#extended-css-property) +- [Pseudo-class `:xpath()`](#extended-css-xpath) +- [Pseudo-class `:nth-ancestor()`](#extended-css-nth-ancestor) +- [Pseudo-class `:upward()`](#extended-css-upward) +- [Pseudo-class `:remove()` and pseudo-property `remove`](#remove-pseudos) +- [Pseudo-class `:is()`](#extended-css-is) +- [Pseudo-class `:not()`](#extended-css-not) +- [Pseudo-class `:if-not()` (removed)](#extended-css-if-not) CSS 3.0 is not always enough to block ads. To solve this problem AdGuard extends CSS capabilities by adding support for the new pseudo-elements. We have developed a separate [open-source library](https://github.com/AdguardTeam/ExtendedCss) for non-standard element selecting and applying CSS styles with extended properties. @@ -3112,17 +3111,17 @@ Regardless of the CSS pseudo-classes you are using in the rule, you can use spec The syntax for extended CSS rules: -- `#?#` — pro skrytí prvku, `#@?#` — pro výjimky -- `#$?#` — pro pravidlo CSS, `#@$?#` — pro výjimky +- `#?#` — for element hiding, `#@?#` — for exceptions +- `#$?#` — for CSS rules, `#@$?#` — for exceptions We **strongly recommend** using these markers any time when you use an extended CSS selector. **Příklady** -- `example.org#?#div:has(> a[target="_blank"][rel="nofollow"])` — toto pravidlo blokuje všechny prvky `div` obsahující podřízený uzel, který má odkaz s atributy `[target="_blank"][rel="nofollow"]`. Pravidlo platí pouze pro `example.org` a její subdomény. -- `example.com#$?#h3:contains(cookies) { display: none!important; }` — toto pravidlo nastaví styl `display: none!important` všem prvkům `h3`, které obsahují slovo `cookies`. Pravidlo platí pouze pro `example.com` a všechny její subdomény. -- `example.net#?#.banner:matches-css(width: 360px)` — toto pravidlo blokuje všechny prvky `.banner` s vlastností stylu `width: 360px`. Pravidlo platí pouze pro `example.net` a její subdomény. -- `example.net#@?#.banner:matches-css(width: 360px)` — toto pravidlo zakáže předchozí pravidlo. +- `example.org#?#div:has(> a[target="_blank"][rel="nofollow"])` — this rule blocks all `div` elements containing a child node that has a link with the attributes `[target="_blank"][rel="nofollow"]`. The rule applies only to `example.org` and its subdomains. +- `example.com#$?#h3:contains(cookies) { display: none!important; }` — this rule sets the style `display: none!important` to all `h3` elements that contain the word `cookies`. The rule applies only to `example.com` and all its subdomains. +- `example.net#?#.banner:matches-css(width: 360px)` — this rule blocks all `.banner` elements with the style property `width: 360px`. The rule applies only to `example.net` and its subdomains. +- `example.net#@?#.banner:matches-css(width: 360px)` — this rule will disable the previous rule. You can apply standard CSS selectors using the ExtendedCss library by using the rule marker `#?#`, e.g. `#?#div.banner`. @@ -3138,9 +3137,9 @@ Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still #### Limitace ExtendedCss {#extended-css-limitations} -1. CSS [komentáře](https://developer.mozilla.org/en-US/docs/Web/CSS/Comments) a [at-rules](https://developer.mozilla.org/en-US/docs/Web/CSS/At-rule) nejsou podporovány. +1. CSS [comments](https://developer.mozilla.org/en-US/docs/Web/CSS/Comments) and [at-rules](https://developer.mozilla.org/en-US/docs/Web/CSS/At-rule) are not supported. -2. Konkrétní pseudo-třída může mít svá vlastní omezení: [`:has()`](#extended-css-has-limitations), [`:xpath()`](#extended-css-xpath-limitations), [`:nth-ancestor()`](#extended-css-nth-ancestor-limitations), [`:upward()`](#extended-css-upward-limitations), [`:is()`](#extended-css-is-limitations), [`:not()`](#extended-css-not-limitations), and [`:remove()`](#extended-css-remove-limitations). +2. Specific pseudo-class may have its own limitations: [`:has()`](#extended-css-has-limitations), [`:xpath()`](#extended-css-xpath-limitations), [`:nth-ancestor()`](#extended-css-nth-ancestor-limitations), [`:upward()`](#extended-css-upward-limitations), [`:is()`](#extended-css-is-limitations), [`:not()`](#extended-css-not-limitations), and [`:remove()`](#extended-css-remove-limitations). #### Pseudo-třída `:has()` {#extended-css-has} @@ -3168,8 +3167,8 @@ Synonyms `:-abp-has()` is supported by ExtendedCss for better compatibility. [target]:has(selector) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `selector` — povinný, standardní nebo rozšířený selektor CSS +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selector` — required, standard or extended CSS selector The pseudo-class `:has()` selects the `target` elements that fit to the `selector`. Also the `selector` can start with a combinator. @@ -3179,8 +3178,8 @@ A selector list can be set in `selector` as well. In this case **all** selectors Usage of the `:has()` pseudo-class is [restricted for some cases (2, 3)](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54): -- zakazuje `:has()` uvnitř pseudo akceptující pouze složené selektory; -- zakazuje `:has()` po běžných pseudoprvcích. +- disallow `:has()` inside the pseudos accepting only compound selectors; +- disallow `:has()` after regular pseudo-elements. Native `:has()` pseudo-class does not allow `:has()`, `:is()`, `:where()` inside `:has()` argument to avoid increasing the `:has()` invalidation complexity ([case 1](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54)). But ExtendedCss did not have such limitation earlier and filter lists already contain such rules, so we have not added this limitation to ExtendedCss and allow to use `:has()` inside `:has()` as it was possible before. To use it, just force ExtendedCss usage by setting `#?#`/`#$?#` rule marker. @@ -3245,7 +3244,7 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a ::: -#### Pseudo-třída `:contains()` {#extended-css-contains} +#### Pseudo-class `:contains()` {#extended-css-contains} The `:contains()` pseudo-class principle is very simple: it allows to select the elements that contain specified text or which content matches a specified regular expression. Regexp flags are supported. @@ -3265,8 +3264,8 @@ Synonyms `:-abp-contains()` and `:has-text()` are supported for better compatibi [target]:contains(match) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `shoda` — povinný, řetězec nebo regulární výraz pro shodu prvku `textContent`. Příznaky regulárních výrazů jsou podporovány. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `match` — required, string or regular expression for matching element `textContent`. Regular expression flags are supported. **Příklady** @@ -3314,10 +3313,10 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty [target]:matches-css([pseudo-element, ] property: pattern) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `pseudo-element` — volitelný, platný standardní pseudoprvek, např. `before`, `after`, `first-line` atd. -- `property` — povinný, název vlastnosti CSS, pro kterou se má prvek zkontrolovat -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. Při tomto typu porovnávání, AdGuard vždy porovnává bez ohledu na velikost písmen. V případě regulárního výrazu vypadá vzor takto: `/regexp/`. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. +- `property` — required, a name of CSS property to check the element for +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3371,7 +3370,7 @@ Obsolete pseudo-classes `:matches-css-before()` and `:matches-css-after()` are n ::: -#### Pseudo-třída `:matches-attr()` {#extended-css-matches-attr} +#### Pseudo-class `:matches-attr()` {#extended-css-matches-attr} The `:matches-attr()` pseudo-class allows selecting an element by its attributes, especially if they are randomized. @@ -3381,9 +3380,9 @@ The `:matches-attr()` pseudo-class allows selecting an element by its attributes [target]:matches-attr("name"[="value"]) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `name` — povinný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro shodu názvu atributu -- `value` — volitelný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro shodu hodnoty atributu +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `name` — required, simple string *or* string with wildcard *or* regular expression for attribute name matching +- `value` — optional, simple string *or* string with wildcard *or* regular expression for attribute value matching **Escaping special characters** @@ -3427,7 +3426,7 @@ Regexp patterns **do not support** flags. ::: -#### Pseudo-třída `:matches-property()` {#extended-css-property} +#### Pseudo-class `:matches-property()` {#extended-css-property} The `:matches-property()` pseudo-class allows selecting an element by matching its properties. @@ -3437,9 +3436,9 @@ The `:matches-property()` pseudo-class allows selecting an element by matching i [target]:matches-property("name"[="value"]) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `name` — povinný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro porovnávání názvů vlastností prvků -- `value` — volitelný, jednoduchý řetězec *nebo* řetězec se zástupným znakem *nebo* regulární výraz pro porovnávání názvů vlastností prvků +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `name` — required, simple string *or* string with wildcard *or* regular expression for element property name matching +- `value` — optional, simple string *or* string with wildcard *or* regular expression for element property value matching **Escaping special characters** @@ -3491,8 +3490,8 @@ div:matches-property(memoizedProps._owner.src=/ad/) To check properties of a specific element, do the following: -1. Zkontrolujte prvek stránky nebo jej vyberte na kartě `Elements` v nástroji DevTools prohlížeče -1. Spusťte `console.dir($0)` na kartě `Console` +1. Inspect the page element or select it in `Elements` tab of browser DevTools +1. Run `console.dir($0)` in `Console` tab ::: @@ -3512,8 +3511,8 @@ The `:xpath()` pseudo-class allows selecting an element by evaluating an XPath e [target]:xpath(expression) ``` -- `target` — volitelný, standardní nebo rozšířený selektor CSS -- `expression` — povinný, platný výraz XPath +- `target`- optional, standard or extended CSS selector +- `expression` — required, valid XPath expression ##### `:xpath()` limitations {#extended-css-xpath-limitations} @@ -3541,7 +3540,7 @@ Works properly only at the end of selector, except for [pseudo-class :remove()]( ``` -#### Pseudo-třída `:nth-ancestor()` {#extended-css-nth-ancestor} +#### Pseudo-class `:nth-ancestor()` {#extended-css-nth-ancestor} The `:nth-ancestor()` pseudo-class allows to lookup the *nth* ancestor relative to the previously selected element. @@ -3586,7 +3585,7 @@ For such DOM: `.child:nth-ancestor(1)` selects the element `div#target1`, `div[class="inner"]:nth-ancestor(3)` selects the element `div#target2`. -#### Pseudo-třída `:upward()` {#extended-css-upward} +#### Pseudo-class `:upward()` {#extended-css-upward} The `:upward()` pseudo-class allows to lookup the ancestor relative to the previously selected element. @@ -3597,9 +3596,9 @@ subject:upward(ancestor) ``` - `subjectr` — povinný, standardní nebo rozšířený selektor CSS -- `ancestor` — povinný, specifikace pro předka prvku vybraného pomocí `subject`, lze nastavit jako: - - *číslo* >= 1 a < 256 pro vzdálenost k požadovanému předkovi, stejně jako u položky [`:nth-ancestor()`](#extended-css-nth-ancestor) - - *standardní selektor CSS* pro shodu nejbližšího předka +- `ancestor` — required, specification for the ancestor of the element selected by `subject`, can be set as: + - *number* >= 1 and < 256 for distance to the needed ancestor, same as [`:nth-ancestor()`](#extended-css-nth-ancestor) + - *standard CSS selector* for matching closest ancestor ##### `:upward()` limitations {#extended-css-upward-limitations} @@ -3626,7 +3625,7 @@ For such DOM: `.inner:upward(div[data])` selects the element `div#target1`, `.inner:upward(div[id])` selects the element `div#target2`, `.child:upward(1)` selects the element `div#target1`, `.inner:upward(3)` selects the element `div#target2`. -#### Pseudo-třída `:remove()` a pseudo-vlastnost `remove` {#remove-pseudos} +#### Pseudo-class `:remove()` and pseudo-property `remove` {#remove-pseudos} Sometimes, it is necessary to remove a matching element instead of hiding it or applying custom styles. In order to do it, you can use the `:remove()` pseudo-class as well as the `remove` pseudo-property. @@ -3642,7 +3641,7 @@ selector:remove() selector { remove: true; } ``` -- `selector` — povinný, standardní nebo rozšířený selektor CSS +- `selector` — required, standard or extended CSS selector ##### `:remove()` a `remove` limitations {#extended-css-remove-limitations} @@ -3668,7 +3667,7 @@ Rules with the `remove` pseudo-property must use `#$?#` marker: `$` for CSS-styl ::: -#### Pseudo-třída `:is()` {#extended-css-is} +#### Pseudo-class `:is()` {#extended-css-is} The `:is()` pseudo-class allows to match any element that can be selected by any of selectors passed to it. Invalid selectors are skipped and the pseudo-class deals with valid ones with no error thrown. Our implementation of the [native `:is()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:is). @@ -3678,8 +3677,8 @@ The `:is()` pseudo-class allows to match any element that can be selected by any [target]:is(selectors) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `selectors` — [*odpouštějící seznam selektorů*](https://drafts.csswg.org/selectors-4/#typedef-forgiving-selector-list) standardních nebo rozšířených selektorů. U rozšířených selektorů jsou podporovány pouze složené selektory, nikoli komplexní. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selectors` — [*forgiving selector list*](https://drafts.csswg.org/selectors-4/#typedef-forgiving-selector-list) of standard or extended selectors. For extended selectors, only compound selectors are supported, not complex. ##### `:is()` limitations {#extended-css-is-limitations} @@ -3714,7 +3713,7 @@ Due to limitations `:is(*:not([class]) > .banner)'` does not work but `:is(*:not ``` -#### Pseudo-třída `:not()` {#extended-css-not} +#### Pseudo-class `:not()` {#extended-css-not} The `:not()` pseudo-class allows to select elements which are *not matched* by selectors passed as argument. Invalid argument selectors are not allowed and error is to be thrown. Our implementation of the [`:not()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:not). @@ -3724,8 +3723,8 @@ The `:not()` pseudo-class allows to select elements which are *not matched* by s [target]:not(selectors) ``` -- `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku -- `selectors` — seznam standardních nebo rozšířených selektorů +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selectors` — list of standard or extended selectors ##### `:not()` limitations {#extended-css-not-limitations} @@ -3750,7 +3749,7 @@ The `:not()` is considered as a standard CSS pseudo-class inside the argument of ``` -#### Pseudo-třída `:if-not()` (odstraněno) {#extended-css-if-not} +#### Pseudo-class `:if-not()` (removed) {#extended-css-if-not} :::danger Upozornění na odstranění @@ -3792,12 +3791,12 @@ pseudoClasses = pseudoClass *pseudoClass pseudoClass = ":" pseudoName [ "(" pseudoArgs ")" ] ``` -- **`tagName`** — název prvku s malými písmeny, např. `div` nebo `script`. -- **`domains`** — omezení domény pro dané pravidlo. Stejné zásady jako v [syntaxi pravidel pro skrývání prvků](#cosmetic-elemhide-rules). -- **`attributes`** — seznam atributů, které limitují výběr prvků. `name` — název atributu, `value` — podřetězec, který je obsažen v hodnotě atributu. -- **`pseudoName`** — název pseudotřídy. -- **`pseudoArgs`** — argumenty pseudotřídy typu funkce. -- **`combinator`** — operátor, který funguje podobně jako podřízený kombinátor [CSS](https://developer.mozilla.org/en-US/docs/Web/CSS/Child_combinator): to znamená, že `selector` napravo od `combinator` bude odpovídat pouze prvku, jehož přímý původce odpovídá `selector` vlevo z `combinator`. +- **`tagName`** — name of the element in lower case, for example, `div` or `script`. +- **`domains`** — domain restriction for the rule. Same principles as in [element hiding rule syntax](#cosmetic-elemhide-rules). +- **`attributes`** — a list of attributes that limit the selection of elements. `name` — attribute name, `value` — substring, that is contained in attribute value. +- **`pseudoName`** — the name of a pseudo-class. +- **`pseudoArgs`** — the arguments of a function-style pseudo-class. +- **`combinator`** — an operator that works similarly to the [CSS child combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Child_combinator): that is, the `selector` on the right of the `combinator` will only match an element whose direct parent matches the `selector` on the left of the `combinator`. ### Příklady @@ -3845,7 +3844,7 @@ Following rule will delete all `script` elements with a `banner` substring in th $$script[tag-content="banner"] ``` -:::caution Limitations +:::caution Omezení The `tag-content` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3867,7 +3866,7 @@ For example: `$$script[wildcard="*banner*text*"]` It checks if the element code contains the two consecutive substrings `banner` and `text`. -:::caution Limitations +:::caution Omezení The `wildcard` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3895,7 +3894,7 @@ $$div[tag-content="banner"][max-length="400"] This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which does not exceed `400` characters. -:::caution Limitations +:::caution Omezení The `max-length` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3919,7 +3918,7 @@ $$div[tag-content="banner"][min-length="400"] This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which exceeds `400` characters. -:::caution Limitations +:::caution Omezení The `min-length` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3955,7 +3954,7 @@ The `:contains()` pseudo-class is supported by AdGuard for Windows, Mac, and And Requires that the inner HTML of the element contains the specified text or matches the specified regular expression. -:::caution Limitations +:::caution Omezení A `:contains()` pseudo-class must not appear in a selector to the left of a `>` combinator. @@ -3997,12 +3996,12 @@ We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rule = [domains] "#%#" script ``` -- **`domains`** — omezení domény pro dané pravidlo. Stejné zásady jako v [pravidlech pro skrývání prvků](#cosmetic-elemhide-rules). +- **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). - **`script`** — arbitrary JavaScript code **in one string**. **Příklady** -- `example.org#%#window.__gaq = undefined;` spustí kód `window.__gaq = undefined;` na všech stránkách na `example.org` a jejích subdoménách. +- `example.org#%#window.__gaq = undefined;` executes the code `window.__gaq = undefined;` on all pages at `example.org` and all subdomains. **Výjimky** @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Omezení -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Omezení -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4174,14 +4173,14 @@ rule = "[$" modifiers "]" [rule text] modifiers = modifier0[, modifier1[, ...[, modifierN]]] ``` -- **`modifier`** — sada modifikátorů popsaných níže. -- **`rule text`** — pravidlo, které je třeba změnit. +- **`modifier`** — set of the modifiers described below. +- **`rule text`** — a rule to be modified. For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | | ------------------------------------- |:----------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| | [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | | [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | @@ -4202,10 +4201,10 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` **Příklady** -- `[$app=org.example.app]example.com##.textad` skryje `div` s třídou `textad` na `example.com` a všech subdoménách v požadavcích odeslaných z `org.example.app` v aplikaci Android. -- `[$app=~org.example.app1|~org.example.app2]example.com##.textad` skryje `div` s třídou `textad` na `example.com` a všech subdoménách v požadavcích odeslaných z jakékoli aplikace kromě `org.example.app1` a `org.example.app2`. -- `[$app=com.apple.Safari]example.org#%#//scriptlet('prevent-setInterval', 'check', '!300')` použije skriplet `prevent-setInterval` pouze v prohlížeči Safari na počítači Mac. -- `[$app=org.example.app]#@#.textad` zakáže všechna pravidla `##.textad` pro všechny domény při použití `org.example.app`. +- `[$app=org.example.app]example.com##.textad` hides a `div` with the class `textad` at `example.com` and all subdomains in requests sent from the `org.example.app` Android app. +- `[$app=~org.example.app1|~org.example.app2]example.com##.textad` hides a `div` with the class `textad` at `example.com` and all subdomains in requests sent from any app except `org.example.app1` and `org.example.app2`. +- `[$app=com.apple.Safari]example.org#%#//scriptlet('prevent-setInterval', 'check', '!300')` applies scriptlet `prevent-setInterval` only in Safari browser on Mac. +- `[$app=org.example.app]#@#.textad` disables all `##.textad` rules for all domains while using `org.example.app`. :::info Kompatibilita @@ -4219,20 +4218,20 @@ Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard fo **Příklady** -- `[$domain=example.com]##.textad` — skryje `div` s třídou `textad` na doméně `example.com` a všech subdoménách. -- `[$domain=example.com|example.org]###adblock` — skryje prvek s atributem `id`, který se rovná `adblock` na `example.com`, `example.org` a všech subdoménách. -- `[$domain=~example.com]##.textad` — toto pravidlo skryje prvek `div` se třídou `textad` na všech doménách kromě `example.com` a jejích subdomén. +- `[$domain=example.com]##.textad` — hides a `div` with the class `textad` at `example.com` and all subdomains. +- `[$domain=example.com|example.org]###adblock` — hides an element with attribute `id` equals `adblock` at `example.com`, `example.org` and all subdomains. +- `[$domain=~example.com]##.textad` — this rule hides `div` elements of the class `textad` for all domains, except `example.com` and its subdomains. There are 2 ways to specify domain restrictions for non-basic rules: -1. "klasický" způsob je zadat domény před masku pravidla a atributy: `example.com##.textad`; -2. přístup modifikátoru spočívá v určení domén pomocí modifikátoru `$domain`: `[$domain=example.com]##.textad`. +1. the "classic" way is to specify domains before rule mask and attributes: `example.com##.textad`; +2. the modifier approach is to specify domains via `$domain` modifier: `[$domain=example.com]##.textad`. But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. ### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} -:::caution Limitations +:::caution Omezení Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). @@ -4264,14 +4263,14 @@ If `pattern` is not set for `$path`, rule will apply only on the main page of we **Příklady** -- `[$path=page.html]##.textad` skryje `div` se třídou `textad` na `/page.html` nebo `/page.html?` nebo `/sub/page.html` nebo `/another_page.html` -- `[$path=/page.html]##.textad` skryje `div` se třídou `textad` na `/page.html` nebo `/page.html?` nebo `/sub/page.html` jakékoliv domény kromě `/another_page.html` -- `[$path=|/page.html]##.textad` skryje `div` se třídou `textad` na `/page.html` nebo `/page.html?` jakékoliv domény kromě `/sub/page.html` -- `[$path=/page.html|]##.textad` skryje `div` se třídou `textad` na `/page.html` nebo `/sub/page.html` jakékoliv domény kromě `/page.html?` -- `[$path=/page*.html]example.com##.textad` skryje `div` se třídou `textad` na `/page1.html` nebo `/page2.html` nebo jiné cestě shodné s `/page<...>.html` domény `example.com` -- `[$path]example.com##.textad` skryje `div` se třídou `textad` na hlavní stránce domény `example.com` -- `[$domain=example.com,path=/page.html]##.textad` skryje `div` se třídou `textad` na `page.html` domény `example.com` a všech subdoménách kromě `another_page.html` -- `[$path=/\\/(sub1|sub2)\\/page\\.html/]##.textad` skryje `div` se třídou `textad` na `/sub1/page.html` a `/sub2/page.html` jakékoliv domény (vezměte prosím na vědomí, že [ uvozuje speciální znak](#non-basic-rules-modifiers-syntax)) +- `[$path=page.html]##.textad` hides a `div` with the class `textad` at `/page.html` or `/page.html?` or `/sub/page.html` or `/another_page.html` +- `[$path=/page.html]##.textad` hides a `div` with the class `textad` at `/page.html` or `/page.html?` or `/sub/page.html` of any domain but not at `/another_page.html` +- `[$path=|/page.html]##.textad` hides a `div` with the class `textad` at `/page.html` or `/page.html?` of any domain but not at `/sub/page.html` +- `[$path=/page.html|]##.textad` hides a `div` with the class `textad` at `/page.html` or `/sub/page.html` of any domain but not at `/page.html?` +- `[$path=/page*.html]example.com##.textad` hides a `div` with the class `textad` at `/page1.html` or `/page2.html` or any other path matching `/page<...>.html` of `example.com` +- `[$path]example.com##.textad` hides a `div` with the class `textad` at the main page of `example.com` +- `[$domain=example.com,path=/page.html]##.textad` hides a `div` with the class `textad` at `page.html` of `example.com` and all subdomains but not at `another_page.html` +- `[$path=/\\/(sub1|sub2)\\/page\\.html/]##.textad` hides a `div` with the class `textad` at both `/sub1/page.html` and `/sub2/page.html` of any domain (please note the [escaped special characters](#non-basic-rules-modifiers-syntax)) :::info Kompatibilita @@ -4293,13 +4292,13 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic **Příklady** -- `[$url=||example.com/content/*]##div.textad` skryje `div` se třídou `textad` na adrese jako `https://example.com/content/article.html` a dokonce i `https://subdomain.example.com/content/article.html`. -- `[$url=||example.org^]###adblock` skryje prvek s atributem `id`, který se rovná `adblock` na `example.org` a jejích subdoménách. -- `[$url=/\[az\]+\\.example\\.com^/]##.textad` skryje prvky třídy `div` `textad` pro všechny domény odpovídající regulárnímu výrazu `[a-z]+\. example\.com^`. +- `[$url=||example.com/content/*]##div.textad` hides a `div` with the class `textad` at addresses like `https://example.com/content/article.html` and even `https://subdomain.example.com/content/article.html`. +- `[$url=||example.org^]###adblock` hides an element with attribute `id` equal to `adblock` at `example.org` and its subdomains. +- `[$url=/\[a-z\]+\\.example\\.com^/]##.textad` hides `div` elements of the class `textad` for all domains matching the regular expression `[a-z]+\.example\.com^`. #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Omezení In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4319,9 +4318,9 @@ If you maintain a third-party filter that is known to AdGuard, you might be inte We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: -- [zahrnutý soubor](#include-directive) -- [použití pravidel podmíněně podle typu blokátoru reklam](#conditions-directive) -- [zadání blokátor obsahu pro pravidla platná v Safari](#safari-affinity-directive) +- [including a file](#include-directive) +- [applying rules conditionally by ad blocker type](#conditions-directive) +- [content blocker specifying for rules applying in Safari](#safari-affinity-directive) :::note @@ -4371,9 +4370,9 @@ Filter maintainers can use conditions to supply different rules depending on the There are two possible scenarios: -1. Pokud blokátor reklamy narazí na direktivu `!#if` a ne `!#else`, zkompiluje kód mezi direktivami `!#if` a `!#endif` pouze v případě, že je zadaná podmínka pravdivá. +1. When an ad blocker encounters an `!#if` directive and no `!#else` directive, it will compile the code between `!#if` and `!#endif` directives only if the specified condition is true. -1. Pokud existuje direktiva `!#else`, bude zkompilován kód mezi `!#if` a `!#else`, pokud je podmínka pravdivá; v opačném případě bude zkompilován kód mezi `!#else` a `!#endif`. +1. If there is an `!#else` directive, the code between `!#if` and `!#else` will be compiled if the condition is true; otherwise, the code between `!#else` and `!#endif` will be compiled. :::note @@ -4401,25 +4400,25 @@ false_conditions_rules_list kde: -- `!#if (conditions)` — začátek bloku při splnění podmínek -- `conditions` — stejně jako v některých populárních programovacích jazycích jsou podmínky preprocesoru založeny na konstantách deklarovaných blokátory reklamy. Autoři blokátorů reklam si sami určují, jaké konstanty přesně deklarují. Přípustné hodnoty: - - `adguard` vždy deklarováno; ukazuje správcům, že se jedná o jeden z produktů AdGuard; mělo by to stačit v 95 % případů - - konstanty specifické pro daný produkt pro případy, kdy potřebujete, aby pravidlo fungovalo (nebo nefungovalo — pak je třeba před konstantou použít `!`) pouze v konkrétním produktu: - - `adguard_app_windows` — AdGuard pro Windows - - `adguard_app_mac` — AdGuard pro Mac - - `adguard_app_android` — AdGuard pro Android - - `adguard_app_ios` — AdGuard pro iOS - - `adguard_ext_safari` — AdGuard pro Safari - - `adguard_ext_chromium` — Rozšíření prohlížeče AdGuard pro Chrome (a prohlížeče založené na chromium, např. nový Microsoft Edge.) - - `adguard_ext_firefox` — Rozšíření prohlížeče AdGuard pro Firefox - - `adguard_ext_edge` — Rozšíření prohlížeče AdGuard pro starší Edge - - `adguard_ext_opera` — Rozšíření prohlížeče AdGuard pro Operu - - `adguard_ext_android_cb` — Blokátor obsahu AdGuard pro mobilní prohlížeče Samsung a Yandex +- `!#if (conditions)` — start of the block when conditions are true +- `conditions` — just like in some popular programming languages, preprocessor conditions are based on constants declared by ad blockers. Authors of ad blockers define on their own what exact constants they declare. Possible values: + - `adguard` always declared; shows maintainers that this is one of AdGuard products; should be enough in 95% of cases + - product-specific constants for cases when you need a rule to work (or not work — then `!` should be used before constant) in a specific product only: + - `adguard_app_windows` — AdGuard for Windows + - `adguard_app_mac` — AdGuard for Mac + - `adguard_app_android` — AdGuard for Android + - `adguard_app_ios` — AdGuard for iOS + - `adguard_ext_safari` — AdGuard for Safari + - `adguard_ext_chromium` — AdGuard Browser Extension for Chrome (and chromium-based browsers, e.g. new Microsoft Edge) + - `adguard_ext_firefox` — AdGuard Browser Extension for Firefox + - `adguard_ext_edge` — AdGuard Browser Extension for Edge Legacy + - `adguard_ext_opera` — AdGuard Browser Extension for Opera + - `adguard_ext_android_cb` — AdGuard Content Blocker for mobile Samsung and Yandex browsers - `ext_ublock` — special case; this one is declared when a uBlock version of a filter is compiled by the [FiltersRegistry][] - - `cap_html_filtering` — produkty, které podporují pravidla filtrování HTML: AdGuard pro Windows, AdGuard pro macOS a AdGuard pro Android -- `!#else` — začátek bloku při nesplnění podmínek -- `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — seznamy pravidel -- `!#endif` — konec blokování + - `cap_html_filtering` — products that support HTML filtering rules: AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +- `!#else` — start of the block when conditions are false +- `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — lists of rules +- `!#endif` — end of the block **Příklady** @@ -4456,8 +4455,8 @@ The `!#else` directive is supported by the [FiltersDownloader][gh-filters-downlo It is already supported for filter lists compiled by the [FiltersRegistry][], but it still may not be supported by AdGuard products when adding a filter list with `!#else` as a custom one. The following products will support it in the mentioned versions or later: - AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13; -- Rozšíření prohlížeče AdGuard v4.2.208; -- AdGuard v1.11.16 pro Safari. +- AdGuard Browser Extension v4.2.208; +- AdGuard v1.11.16 for Safari. ::: @@ -4467,12 +4466,12 @@ Safari's limit for each content blocker is 150,000 active rules. But in AdGuard Here is the composition of each content blocker: -- AdGuard General — Blokování reklam, jazykově specifické filtry -- AdGuard Privacy — Soukromí -- AdGuard Social — sociální widgety, obtěžování -- AdGuard Security — Zabezpečení -- AdGuard Other — Jiné -- AdGuard Custom — Vlastní +- AdGuard General — Ad Blocking, Language-specific +- AdGuard Privacy — Privacy +- AdGuard Social — Social Widgets, Annoyances +- AdGuard Security — Security +- AdGuard Other — Other +- AdGuard Custom — Custom User rules and allowlist are added to every content blocker. @@ -4492,17 +4491,17 @@ rules_list kde: -- `!#safari_cb_affinity(content_blockers)` — počátek blokování -- `content_blockers` — seznam blokátorů obsahu oddělený čárkami. Přípustné hodnoty: - - `general` — blokátor obsahu AdGuard General - - `privacy` — blokátor obsahu AdGuard Privacy - - `social` — blokátor obsahu AdGuard Social - - `security` — blokátor obsahu AdGuard Security - - `other` — blokátor obsahu AdGuard Other - - `custom` — blokátor obsahu AdGuard Custom - - `all` — speciální klíčové slovo, které znamená, že pravidla musí být zahrnuta do **všech** blokátorů obsahu -- `rules_list` — seznam pravidel -- `!#safari_cb_affinity` — konec blokování +- `!#safari_cb_affinity(content_blockers)` — start of the block +- `content_blockers` — comma-separated list of content blockers. Possible values: + - `general` — AdGuard General content blocker + - `privacy` — AdGuard Privacy content blocker + - `social` — AdGuard Social content blocker + - `security` — AdGuard Security content blocker + - `other` — AdGuard Other content blocker + - `custom` — AdGuard Custom content blocker + - `all` — special keyword that means that the rules must be included into **all** content blockers +- `rules_list` — list of rules +- `!#safari_cb_affinity` — end of the block **Příklady** @@ -4548,18 +4547,18 @@ Rules usage frequency comes from the collected [filter rules statistics](../trac kde: -- **filter** — identifikátor filtru -- **percent** — očekávané procento optimalizace `~= (počet pravidel v optimalizovaném filtru) / (počet pravidel v původním filtru) * 100` -- **minPercent** — dolní mez hodnoty `percent` -- **maxPercent** — horní mez hodnoty `percent` value -- **strict** — pokud je `percent < minPercent` NEBO `percent > maxPercent` a je zapnutý přísný režim, pak by kompilace filtru měla selhat, jinak je nutné použít původní pravidla +- **filter** — filter identifier +- **percent** — expected optimization percent `~= (rules count in optimized filter) / (rules count in original filter) * 100` +- **minPercent** — lower bound of `percent` value +- **maxPercent** — upper bound of `percent` value +- **strict** — if `percent < minPercent` OR `percent > maxPercent` and strict mode is on then filter compilation should fail, otherwise original rules must be used In other words, `percent` is the "compression level". For instance, for the Base filter it is configured to 40%. It means that optimization algorithm should strip 60% of rules. Eventually, here are the two versions of the Base filter for AdGuard Browser Extension: -- úplná: https://filters.adtidy.org/extension/chromium/filters/2.txt -- optimalizovaná: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt +- full: https://filters.adtidy.org/extension/chromium/filters/2.txt +- optimized: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt **If you want to add a rule which should not be removed at optimization use the `NOT_OPTIMIZED` hint:** @@ -4579,27 +4578,27 @@ Eventually, here are the two versions of the Base filter for AdGuard Browser Ext Used to specify the platforms to apply the rules. List of existing platforms and links to Base filter, for example, for each of them: -- `windows` — AdGuard pro Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) +- `windows` — AdGuard for Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) -- `mac` — AdGuard pro Mac — [https://filters.adtidy.org/mac_v2/filters/2.txt](https://filters.adtidy.org/mac_v2/filters/2.txt) +- `mac` — AdGuard for Mac — [https://filters.adtidy.org/mac_v2/filters/2.txt](https://filters.adtidy.org/mac_v2/filters/2.txt) -- `android` — AdGuard pro Android — [https://filters.adtidy.org/android/filters/2.txt](https://filters.adtidy.org/android/filters/2.txt) +- `android` — AdGuard for Android — [https://filters.adtidy.org/android/filters/2.txt](https://filters.adtidy.org/android/filters/2.txt) -- `ios` — AdGuard pro iOS — [https://filters.adtidy.org/ios/filters/2.txt](https://filters.adtidy.org/ios/filters/2.txt) +- `ios` — AdGuard for iOS — [https://filters.adtidy.org/ios/filters/2.txt](https://filters.adtidy.org/ios/filters/2.txt) -- `ext_chromium` — Rozšíření prohlížeče AdGuard pro Chrome — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) +- `ext_chromium` — AdGuard Browser Extension for Chrome — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) - `ext_chromium_mv3` — AdGuard Browser Extension for Chrome MV3 — [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) -- `ext_ff` — Rozšíření prohlížeče AdGuard pro Firefox — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) +- `ext_ff` — AdGuard Browser Extension for Firefox — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) -- `ext_edge` — Rozšíření prohlížeče AdGuard pro Edge — [https://filters.adtidy.org/extension/edge/filters/2.txt](https://filters.adtidy.org/extension/edge/filters/2.txt) +- `ext_edge` — AdGuard Browser Extension for Edge — [https://filters.adtidy.org/extension/edge/filters/2.txt](https://filters.adtidy.org/extension/edge/filters/2.txt) -- `ext_opera` — Rozšíření prohlížeče AdGuard pro Operu — [https://filters.adtidy.org/extension/opera/filters/2.txt](https://filters.adtidy.org/extension/opera/filters/2.txt) +- `ext_opera` — AdGuard Browser Extension for Opera — [https://filters.adtidy.org/extension/opera/filters/2.txt](https://filters.adtidy.org/extension/opera/filters/2.txt) -- `ext_safari` — AdGuard pro Safari — [https://filters.adtidy.org/extension/safari/filters/2.txt](https://filters.adtidy.org/extension/safari/filters/2.txt) +- `ext_safari` — AdGuard for Safari — [https://filters.adtidy.org/extension/safari/filters/2.txt](https://filters.adtidy.org/extension/safari/filters/2.txt) -- `ext_android_cb` — Blokátor obsahu AdGuard — [https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt](https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt) +- `ext_android_cb` — AdGuard Content Blocker — [https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt](https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt) - `ext_ublock` — uBlock Origin — [https://filters.adtidy.org/extension/ublock/filters/2.txt](https://filters.adtidy.org/extension/ublock/filters/2.txt) @@ -4629,10 +4628,10 @@ 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. -- V **AdGuardu pro Windows** jej najdete na kartě *Blokátor reklam* nebo prostřednictvím nabídky na hlavním panelu -- V **AdGuardu pro Mac** je pod *Nastavení → Pokročilé → Záznam filtrování* -- V **AdGuardu pro Android** je pod *Statistiky → Nedávná aktivita*. *Nedávná aktivita* je také přístupná z *Asistenta* -- V **Rozšíření prohlížeče AdGuard** je přístupný z karty *Různé* nebo kliknutím pravým tlačítkem myši na ikonu rozšíření. Pouze prohlížeče založené na platformě Chromium a Firefox zobrazují použití **pravidel skrývání prvků** (včetně CSS, ExtCSS) a **pravidel JS a skripletů** v jejich záznamech filtrování +- 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 web browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs :::note @@ -4649,21 +4648,21 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** - `selectorParsed` — text of the parsed selector, may differ from the input one -- `timings` — seznam uzlů DOM odpovídajících selektoru - - `appliesCount` — celkový počet použití selektoru na stránce - - `appliesTimings` — doba, po kterou byl selektor na stránce použit, pro každý případ, kdy byl použit (v milisekundách) - - `meanTiming` — průměrná doba, po kterou byl selektor na stránce použit - - `standardDeviation` — standardní odchylka - - `timingsSum` — celkový čas potřebný k použití selektoru na stránce ve všech instancích +- `timings` — list of DOM nodes matched by the selector + - `appliesCount` — total number of times that the selector has been applied on the page + - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) + - `meanTiming` — mean time that it took to apply the selector on the page + - `standardDeviation` — standard deviation + - `timingsSum` — total time it took to apply the selector on the page across all instances **Printed only for remove pseudos:** -- `removed` — příznak signalizující, zda byly prvky odstraněny +- `removed` — flag to signal if elements were removed **Printed if elements are not removed:** -- `matchedElements` — seznam uzlů DOM odpovídajících selektoru -- `styleApplied` — parsovaná deklarace stylu pravidla související se selektorem +- `matchedElements` — list of DOM nodes matched by the selector +- `styleApplied` — parsed rule style declaration related to the selector **Příklady** @@ -4725,7 +4724,7 @@ The following scriptlets also may be used for debug purposes: - [`prevent-requestAnimationFrame`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-requestanimationframe) - [`prevent-setInterval`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-setinterval) - [`prevent-setTimeout`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-settimeout) -- [`prevent-window-open`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-window-open) se specifikovaným parametrem `replacement` +- [`prevent-window-open`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-window-open) with specified `replacement` parameter - [`prevent-xhr`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-xhr) - [`trusted-replace-fetch-response`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-trusted-scriptlets.md#trusted-replace-fetch-response) - [`trusted-replace-xhr-response`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-trusted-scriptlets.md#trusted-replace-xhr-response) @@ -4748,8 +4747,8 @@ The following scriptlets also may be used for debug purposes: - ✅ — plně podporováno - ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru -- 🧩 — může být již implementováno ve verzích nightly nebo beta, ale není ještě podporováno ve verzích pro vydání -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions +- ⏳ - funkce, jejíž implementace se plánuje, ale zatím není k dispozici v žádném produktu - ❌ — nepodporováno - 👎 — deprecated; still supported but will be removed in the future - 🚫 — odstraněno a již nepodporováno @@ -4766,6 +4765,7 @@ The following scriptlets also may be used for debug purposes: [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" +[ext-mv3]: #what-product "Rozšíření prohlížeče AdGuard pro Chrome MV3" [ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index ce92e73e144..81245f2aa58 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,7 +41,7 @@ Mezi AdGuard filtry blokující reklamy patří: - Základní filtr AdGuardu - Filtr mobilních reklam AdGuard - Regionální filtry rozdělené podle jazyků — čínština, holandština, francouzština, němčina, japonština, ruština, španělština/portugalština, turečtina a ukrajinština -- AdGuard Quick Fixes filter +- Filtr rychlých oprav AdGuard ### Účel těchto filtrů diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index 59624a911a3..e6b4200f88b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: Jak funguje blokování reklam sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. Všechny však spojuje to, že blokují reklamy a slídiče. Tento článek popisuje, jak blokování reklam funguje zevnitř. +AdGuard nabízí mnoho produktů pro blokování reklam pro různé platformy, z nichž každá má své vlastní jedinečné funkce. Všechny však spojuje to, že blokují reklamy a slídiče. Tento článek popisuje, jak blokování reklam funguje zevnitř. :::note diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md index 472b767ea19..86ffa0df77a 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: Co je licence AdGuardu? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Na [stránce nákupu](https://adguard.com/license.html) můžete vidět následu - **Roční předplatné** — tyto licence se obnovují automaticky každý rok nebo je lze prodloužit ručně - Osobní — až pro 3 zařízení - Rodinná — až pro 9 zařízení -- **Lifetime** — these licenses are perpetual +- **Doživotní** — tyto licence nejsou časově omezené - Osobní — až pro 3 zařízení - Rodinná — až pro 9 zařízení diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 8c39cb73085..74cfc523a1f 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: Jak generovat soubor HAR sidebar_position: 1 --- diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md index 476da75712b..56938ac44a6 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md @@ -11,7 +11,7 @@ Chcete-li povolit HTTPS filtrování v zařízení, které používá službu Go - V zařízení dítěte přejděte do Nastavení → Účty → Google - Klepněte na účet svého dítěte a zjistěte, zda máte možnost jej odstranit. Pokud tuto možnost nemáte, přejděte k dalšímu kroku - Klepněte na tři tečky v pravém horním rohu obrazovky a zjistěte, zda máte možnost účet odstranit - - Follow the instructions removing the child’s account from the device + - Postupujte podle pokynů a odstraňte účet dítěte ze zařízení 1. Spusťte AdGuard a nainstalujte soubor CA 1. Obnovte účet dítěte v zařízení: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/minidump.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/minidump.md index 9515a9652d0..647dac3ba93 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/minidump.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/minidump.md @@ -18,13 +18,13 @@ Možnost vytvoření souboru minidump je ve výchozím nastavení zakázána, ta ## Nastavení systému Windows pro vytvoření souboru minidump -Even if you don’t experience any BSoD crash errors, you can still set this option — this is a general recommendation, not necessarily related to AdGuard products. Pro automatické vytvoření souboru minidump postupujte podle níže uvedených pokynů. +I když nedochází k chybám při pádu BSoD, můžete tuto možnost nastavit — jedná se o obecné doporučení, které se nemusí nutně týkat produktů AdGuard. Pro automatické vytvoření souboru minidump postupujte podle níže uvedených pokynů. 1. Do vyhledávacího pole Windows napište *sysdm.cpl* a klikněte na **Otevřít**. Na obrazovce se zobrazí okno **Vlastnosti systému**. :::tip - Alternatively, click **Settings** → **System** → **About** → **Advanced system settings**. + Případně klikněte na **Nastavení** → **Systém** → **Informace** → **Pokročilá nastavení systému**. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 9f2db34119a..594c3ea8c8d 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -26,7 +26,7 @@ Pokuste se uvést co nejvíce podrobností — usnadníte nám tak reprodukci ch - Zda se problém opakuje a s jakou frekvencí - Jestli používáte VPN nebo antivirový software -### How to collect logs +### Jak shromažďovat a záznamy Read about collecting logs in dedicated articles for each platform. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/intro.md b/i18n/cs/docusaurus-plugin-content-docs/current/intro.md index 1fa6c65de29..46af0c5d441 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ Vyvíjíme a spravujeme také bezplatná rozšíření prohlížeče pro všechn ## Nejen blokování reklam -Blokátor reklam AdGuard umí víc než jen blokovat reklamy. Ochrání vás před sledováním online a v mnoha ohledech posílí vaše soukromí. V závislosti na konkrétním produktu může AdGuard nabízet také takové výhody, jako je DNS filtrování pro lepší ochranu, rodičovská ochrana, která chrání vaše děti před nevhodným obsahem, záznam filtrování pro lepší kontrolu internetového provozu a další. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +Blokátor reklam AdGuard umí víc než jen blokovat reklamy. Ochrání vás před sledováním online a v mnoha ohledech posílí vaše soukromí. V závislosti na konkrétním produktu může AdGuard nabízet také takové výhody, jako je DNS filtrování pro lepší ochranu, rodičovská ochrana, která chrání vaše děti před nevhodným obsahem, záznam filtrování pro lepší kontrolu internetového provozu a další. Tato databáze znalostí obsahuje podrobné informace o všech z nich — neváhejte přejít na článek, který vás zajímá. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cc4012ad33d..3ccdecfa1f8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Webové stránky neustále mění způsob vkládání reklam a my do našich fil Práce s filtry blokování však vyžaduje specifické dovednosti. Pokud je máte a umíte vytvářet pravidla, přejděte rovnou do našeho [repozitáře AdGuard Filters](https://github.com/AdguardTeam/AdguardFilters) na GitHubu. Najdete zde spoustu otevřených problémů, z nichž každý odkazuje na problém s nějakou webovou stránkou — nezablokovaná reklama, falešný pozitivní výsledek atd. Vyberte si, co chcete a navrhněte vlastní pravidla v komentářích. Inženýři AdGuard filtrů vaše návrhy posoudí a pokud je shledají vhodnými, budou vaše pravidla přidána do filtrů AdGuardu. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Pokud ještě neznáte syntaxi našich pravidel filtrování nebo si ji potřebujete osvěžit, najdete základní informace o syntaxi v [naší databázi znalostí](/general/ad-filtering/create-own-filters). ### Odměny {#rewards} diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index 6b46e2ed85b..5eaa5906323 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Jak se stát se překladatelem/korektorem sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Pokud chcete pomáhat překládat produkty, webové stránky a znalostní databáze AdGuardu, přejděte na [Crowdin](https://crowdin.com/) a zaregistrujte se/přihlaste se. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ba6ccc9b55d..a1e52b6d8fd 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Když se setkáte s překladem, který vyžaduje použití množného čísla, m Zde je několik zdrojů informací, které můžete použít. -[Průvodce překlady](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) obsahuje široký seznam jazyků. Počet tvarů množného čísla pro různé jazyky se zobrazuje takto: `nplurals=2`, `nplurals=4` atd. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Průvodce překlady](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) obsahuje široký seznam jazyků. Počet tvarů množného čísla pro různé jazyky se zobrazuje takto: `nplurals=2`, `nplurals=4` atd. Číslice za znaménkem rovnosti `=` indikuje počet tvarů množného čísla příslušného jazyka. Informace o tvarech množného čísla můžete také získat v databázi [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). Pravidla CLDR pro množné číslo uvádějí další slovní tvar pro desetinná čísla (1,5; 2,3; 100,1…), ale v překladech AdGuardu je nepoužíváme. @@ -137,7 +137,7 @@ Překlad z angličtiny do srbštiny by tedy měl znít: I když je zřejmé, že poslední dvě šablony se neliší, je velmi důležité toto pravidlo dodržet: **Počet šablon by měl odpovídat počtu tvarů množného čísla příslušného jazyka!** (typicky pro tento typ řetězců s množným číslem). -## Short summary {#summary} +## Krátké shrnutí {#summary} Při překladu projektů AdGuardu věnujte zvýšenou pozornost frázím, které vyžadují použití tvarů množného čísla. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 555d2422961..314465b4181 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Překladatelský program AdGuardu sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +Jakékoli dotazy týkající se překladu AdGuardu nám můžete položit zasláním e-mailu na [translate@adguard.com](mailto:translate@adguard.com) nebo se připojit k našemu [elegram chatu](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +Pokud jde o překlady, my v AdGuardu vždy do značné míry spoléháme na dobrovolníky. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Ke správě překladů našich produktů používáme platformu [Crowdin](https://crowdin.com/). Toto je místo pro každého, kdo chce přispět AdGuardu překladem některého z našich produktů. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Pokud se chcete zařadit mezi dobrovolníky, kteří nám pomáhají překládat AdGuard, přečtěte si [jak se stát naším překladatelem](../become-translator) a [ jak s nimi spolupracujeme](../rewards). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 780bb324537..da95197381e 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Jak upřednostnit překlady souborů na Crowdinu sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Na platformě Crowdin existuje pět hlavních projektů AdGuard — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base) a [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). Nemáme jasné pokyny, se kterými soubory nebo produkty projektu *AdGuard Applications* začít. Stačí si vybrat libovolný produkt. Je tu jen pár věcí, které bychom rádi zmínili: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Aplikace je dostupná pouze uživatelům v těch jazycích, pro které byly na platformě Crowdin dokončeny všechny překlady; - Popisy pro obchody s aplikacemi doporučujeme překládat až na druhém místě, protože bez překladu samotných produktů nebudou popisy potřeba. V projektu *AdGuard Websites* je situace jiná. Jazyky lze na web přidat, i když není k dispozici úplná sada překladů. To však závisí i na tom, které soubory již byly přeloženy. Proto doporučujeme začít nejdůležitějšími soubory, které jsou uvedeny níže: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 3bc1c9ba75d..deb167d0545 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Aktualizace databáze znalostí sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Ale věci se neustále mění a někdy už článek neodráží aktuální stav věcí. +Cílem databáze znalostí blokátoru reklam AdGuard je poskytnout všem nejaktuálnější informace o všech druzích témat souvisejících s AdGuardem. Ale věci se neustále mění a někdy už článek neodráží aktuální stav věcí. Proto jsme veškerý obsah KB (databáze znalostí) umístili na [GitHub](https://github.com/AdguardTeam/KnowledgeBase), kam nyní může přispívat doslova každý, a to jak navrhováním úprav a překladů stávajících, tak i zcela nových článků. ## Jak navrhnout změnu nebo napsat nový článek {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Pokud neznáte principy práce s platformou, začněte přečtením [dokumentace GitHub](https://docs.github.com/en). +Pomocí výše uvedených funkcí GitHubu můžete navrhovat změny stávajících článků a přidávat nové články do databáze znalostí. Pokud neznáte principy práce s platformou, začněte přečtením [dokumentace GitHub](https://docs.github.com/en). -Jakmile budete připraveni začít, zapracujte na [repozitáři KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Mějte to na paměti při úpravách nebo psaní článků. Chcete-li se dozvědět více o syntaxi Markdown, následujte [tento odkaz](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). +Jakmile budete připraveni začít, zapracujte na [repozitáři KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBase). Všechny texty v naší znalostní databázi jsou napsány ve značkovacím jazyce `Markdown`. Mějte to na paměti při úpravách nebo psaní článků. Chcete-li se dozvědět více o syntaxi Markdown, následujte [tento odkaz](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Při navrhování změn nebo doplňků berte v úvahu, že všechny dokumenty musí být v souladu se zásadami platformy. Můžete si o nich přečíst v [průvodci Docosaurus](https://docusaurus.io/docs/category/guides). +Webová stránka databáze znalostí je vytvořena pomocí moderního generátoru statických webových stránek Docusaurus 2. Při navrhování změn nebo doplňků berte v úvahu, že všechny dokumenty musí být v souladu se zásadami platformy. Můžete si o nich přečíst v [průvodci Docosaurus](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Tuto databázi znalostí můžete lokálně uložit do svého počítače a zobrazit náhled navrhovaných změn. Podrobný návod, jak to provést, najdete na adrese [v souboru README.md](https://github.com/AdguardTeam/KnowledgeBase#readme) na stránce GitHub této databáze znalostí. ## Překládání článků {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Překlad stávajících článků databáze znalostí se provádí na [platformě Crowdin](https://crowdin.com/profile/adguard). Všechny podrobnosti o překladech a práci s platformou Crowdin najdete [ve speciálním článku](../translate/guidelines) databáze znalostí blokátoru reklam AdGuard. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [V samostatném článku](../translate/plural-forms) jsme podrobně popsali potíže, které mohou nastat při překladu řetězců s množným číslem a poskytli jsme rozsáhlý návod, jak s nimi na platformě Crowdin pracovat. +Při práci na článcích databáze znalostí AdGuardu se můžete setkat s řetězci obsahujícími množné číslo, které byste měli překládat se zvýšenou pozorností. [V samostatném článku](../translate/plural-forms) jsme podrobně popsali potíže, které mohou nastat při překladu řetězců s množným číslem a poskytli jsme rozsáhlý návod, jak s nimi na platformě Crowdin pracovat. ## Práce na otevřených problémech -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Vyberte si téma, které vás zaujme, a začněte na něm pracovat. Pokud máte nějaké dotazy — můžete je položit přímo v komentářích k tomuto vydání. +Někdy existují [otevřené úlohy](https://github.com/AdguardTeam/KnowledgeBase/issues) související s aktualizací databáze znalostí. Můžete nám pomoci urychlit jejich dokončení [stejným způsobem](#suggest-change), jakým byste navrhli jakékoli jiné změny v této databázi znalostí. Vyberte si téma, které vás zaujme, a začněte na něm pracovat. Pokud máte nějaké dotazy — můžete je položit přímo v komentářích k tomuto vydání. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index d96df3b89c1..e1114bb9c0c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ Die maximale Anzahl der gleichzeitig aktivierten Filter beträgt **50**. **Dynamische Regeln:** Es gilt eine strikte Obergrenze von **5.000** Regeln, darunter maximal 1.000 Regex-Regeln. -Wird diese Grenze überschritten, werden nur **5.000 konvertierte Regeln** in folgender Reihenfolge angewendet: zuerst die Positivliste, dann die Benutzerregeln und schließlich die Eigene Filter. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Konvertierte Regeln** sind Regeln, die mit dem [deklarativen Konverter][github-declarative-converter] in das \[DNR-Format] umgewandelt wurden. > Während dieses Umwandlungsprozesses können einige Regeln andere überschreiben (`$badfilter`), einige können kombiniert werden (`$removeparam`), was zu einer Liste von Regeln mit einer etwas anderen Reihenfolge führt. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md index 8da5f5156c2..d4f8474353c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md @@ -11,64 +11,64 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ## Systemanforderungen -**OS version:** Android 7.0 or higher +**OS-Version:** Android 7.0 oder höher **RAM:** mindestens 2 GB -**Free disk space:** 500 MB +**Freier Speicherplatz:** 500 MB ## Installation -Most Android-based apps are distributed via Google Play; however, AdGuard is not presented there, because Google prohibits distribution of network-level ad blockers via Google Play, i.e. apps that block commercials in other apps. You will find more information about Google restrictive policy [in our blog](https://adguard.com/blog/adguard-google-play-removal.html). +Die meisten Android-basierten Apps werden über Google Play vertrieben. AdGuard wird dort jedoch nicht präsentiert, da Google die Verbreitung von Werbeblockern auf Netzwerkebene über Google Play verbietet, d. h. von Apps, die Werbung in anderen Apps sperren. Weitere Informationen über die restriktive Politik von Google finden Sie [in unserem Blog](https://adguard.com/blog/adguard-google-play-removal.html). -That’s why you can only install AdGuard for Android manually. To use the app on your mobile device, you will need to do the following. +Aus diesem Grund können Sie AdGuard für Android nur manuell installieren. Um die App auf Ihrem mobilen Gerät nutzen zu können, müssen Sie Folgendes tun. -1. **Download the app on your device**. Here are a few ways you can do this: +1. **Laden Sie die App auf Ihr Gerät herunter**. Hier sind einige Möglichkeiten, wie Sie dies tun können: - - head over to [our website](https://adguard.com/adguard-android/overview.html) and tap the *Download* button - - start the browser and type in the following URL: [https://adguard.com/apk](https://adguard.com/apk) - - or scan this QR code: + - Besuchen Sie unsere [Website](https://adguard.com/adguard-android/overview.html) und tippen Sie auf die Schaltfläche *Herunterladen*. + - Starten Sie den Browser und geben Sie die folgende URL ein: [https://adguard.com/apk](https://adguard.com/apk) + - oder scannen Sie diesen QR-Code: ![QR-Code *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst-qr-en-1.png) -1. **Allow installing apps from unknown sources**. Once the file download is complete, tap *Open* in the notification. +1. **Erlauben Sie, Apps aus unbekannten Quellen zu installieren**. Sobald das Herunterladen der Datei abgeschlossen ist, tippen Sie in der Benachrichtigung auf *Öffnen*. - ![Installing apps from unknown sources *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_1.png) + ![Apps aus unbekannten Quellen installieren *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_1.png) - A popup will appear. Tap *Settings*, navigate to *Install unknown apps*, and grant permission for the browser you've used to download the file. + Ein Pop-up-Fenster wird angezeigt. Tippen Sie auf *Einstellungen*, navigieren Sie zu *Unbekannte Apps installieren*, und erteilen Sie die Erlaubnis für den Browser, den Sie zum Herunterladen der Datei verwendet haben. - ![Installing apps from unknown sources *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_3.png) + ![Apps aus unbekannten Quellen installieren *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_3.png) -1. **Install the app**. Once the browser has obtained the necessary permissions, the system will ask you if you want to install the AdGuard app. Tap *Install*. +1. **Installieren Sie die App**. Sobald der Browser die erforderlichen Berechtigungen erhalten hat, werden Sie aufgefordert, die AdGuard-App zu installieren. Tippen Sie auf *Installieren*. - ![Installing apps from unknown sources *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_4.png) + ![Apps aus unbekannten Quellen installieren *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_4.png) - You will then be asked to read AdGuard's *License agreement* and *Privacy policy*. You can also participate in product development. To do this, check the boxes for *Send crash reports automatically* and *Send technical and interaction data*. Then tap *Continue*. + Sie werden anschließend aufgefordert, den *Lizenz-Vertrag* und die *Datenschutzerklärung* von AdGuard zu lesen. Sie können sich außerdem an der Produktentwicklung beteiligen. Aktivieren Sie dazu die Kästchen *Absturzberichte automatisch senden* und *Technische und Interaktionsdaten senden*. Klicken Sie dann auf *Weiter*. ![Datenschutzerklärung *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_3.png) -1. **Create a local VPN**. In order to filter all traffic directly on your device and not route it through a remote server, AdGuard needs to establish a VPN connection. +1. **Erstellen Sie ein lokales VPN**. Um den gesamten Datenverkehr direkt auf Ihrem Gerät zu filtern und nicht über einen Remote-Server zu leiten, muss AdGuard eine VPN-Verbindung herstellen. - ![Create a local VPN *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_2.png) + ![Lokales VPN einrichten *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_2.png) -1. **Enable HTTPS filtering**. It is not a mandatory option, however, we advice to turn it on for the best ad-blocking quality. +1. **Aktivieren Sie die HTTPS-Filterung**. Diese Option ist nicht zwingend erforderlich, wir empfehlen jedoch, sie zu aktivieren, um die beste Werbeblockerqualität zu erzielen. - If your device is running Android 7–9, you'll be prompted to install a root certificate and configure HTTPS filtering after the local VPN setup. + Wenn Ihr Gerät unter Android 7–9 läuft, werden Sie nach der lokalen VPN-Einrichtung aufgefordert, ein Stammzertifikat zu installieren und die HTTPS-Filterung zu konfigurieren. - ![Enable HTTPS filtering on Android 7-9 *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/cert_1.jpg) + ![HTTPS-Filterung unter Android 7–9 aktivieren *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/cert_1.jpg) - After you tap *Install now*, a prompt will appear asking you to authenticate the certificate installation with a password or fingerprint. + Nachdem Sie auf *Jetzt installieren* getippt haben, wird eine Aufforderung angezeigt, die Zertifikatsinstallation mit einem Kennwort oder einem Fingerabdruck zu authentifizieren. - ![Enable HTTPS filtering on Android 7-9. Schritt 2 *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/cert_2.jpg) + ![HTTPS-Filterung unter Android 7-9 aktivieren. Schritt 2 *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/cert_2.jpg) - If you have Android 10+ on your device, then after creating a local VPN, you will see the main app screen with a snack bar at the bottom with a suggestion to enable HTTPS filtering: tap *Enable* and follow the instructions on the next screen or check [the article about certificate installation](solving-problems/manual-certificate.md) for more information. + Wenn Sie Android 10+ auf Ihrem Gerät haben, dann sehen Sie nach dem Erstellen eines lokalen VPN den Hauptbildschirm der App mit einer Snackbar am unteren Rand mit einem Vorschlag zur Aktivierung der HTTPS-Filterung: Tippen Sie auf *Aktivieren* und folgen Sie den Anweisungen auf dem nächsten Bildschirm oder lesen Sie [den Artikel über die Zertifikatsinstallation](solving-problems/manual-certificate.md) für weitere Informationen. - ![Enable HTTPS filtering *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_5.png) + ![HTTPS-Filterung aktivieren *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_5.png) ## AdGuard deinstallieren/neu installieren -If you need to uninstall AdGuard on your mobile device, open *Settings* and choose *Apps* (Android 7) or *Apps & notifications* (Android 8+). Find AdGuard in the list of installed apps and press *Uninstall*. +Wenn Sie AdGuard von Ihrem mobilen Gerät deinstallieren möchten, öffnen Sie *Einstellungen* und wählen Sie *Apps* (Android 7) oder *Apps und Benachrichtigungen* (Android 8+). Suchen Sie AdGuard in der Liste der installierten Apps und tippen Sie *Deinstallieren*. ![AdGuard neu installieren *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_4.png) -To reinstall AdGuard, just download the apk file again and follow the steps outlined in the Installation section. Uninstallation is not required beforehand. +Um AdGuard erneut zu installieren, laden Sie einfach die apk-Datei erneut herunter und befolgen Sie die im Abschnitt Installation beschriebenen Schritte. Eine vorherige Deinstallation ist nicht erforderlich. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index fc85796cc07..dd1d9c3a66c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -1,60 +1,60 @@ --- -title: How to install AdGuard for Android TV +title: So installieren Sie AdGuard für Android TV sidebar_position: 17 --- :::info -This article is about AdGuard for Android TV, an ad blocker that protects your TV at the system level. Um zu sehen, wie es funktioniert, [laden Sie die App „AdGuard TV“ herunter](https://agrd.io/tvapk) +Dieser Artikel behandelt AdGuard für Android TV, einen Werbeblocker, der Ihren Fernseher auf Systemebene schützt. Um zu sehen, wie es funktioniert, [laden Sie die App „AdGuard TV“ herunter](https://agrd.io/tvapk) ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In den meisten Fällen können die vorinstallierten Browser keine Dateien auf Ihrem Fernseher installieren. Sie können jedoch einen Browser aus dem Google Play Store herunterladen, der diese Funktion bietet. In unserem Leitfaden werden wir ein Beispiel für die Installation mit dem Browser TV Bro durchgehen, aber es gibt auch andere Optionen, und Sie können diejenige wählen, die Ihren Bedürfnissen am besten entsprechen. Als Alternative können Sie die App [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) verwenden. -## Installing AdGuard for Android TV via browser +## AdGuard für Android TV über den Browser installieren -1. Install the [TV Bro browser](https://play.google.com/store/apps/details?id=com.phlox.tvwebbrowser) on your Android TV. +1. Installieren Sie den [TV Bro-Browser] (https://play.google.com/store/apps/details?id=com.phlox.tvwebbrowser) auf Ihrem Android TV. -2. Download and install AdGuard for Android TV: +2. Laden Sie AdGuard für Android TV herunter und installieren Sie die App: -- Open the installed TV Bro browser on your Android TV. -- In the address bar of the browser, type `https://agrd.io/tvapk` and press _Enter_ or follow the link. -- The browser will start downloading the AdGuard for Android TV installation file automatically. -- Once the download is complete, select _Downloads_ in the browser control bar, then select the downloaded file. -- In a warning message, allow installing files from the browser. -- Return to your browser, open _Downloads_, and click the downloaded file. -- In the system window that appears, click _Install_, then _Done_ or _Open_. +- Öffnen Sie den installierten TV Bro-Browser auf Ihrem Android TV. +- Geben Sie in die Adressleiste des Browsers `https://agrd.io/tvapk` ein und drücken Sie _Eingabe_ oder folgen Sie dem Link. +- Der Browser beginnt automatisch mit dem Herunterladen der Installationsdatei von AdGuard für Android TV. +- Sobald das Herunterladen abgeschlossen ist, wählen Sie in der Kontrollleiste des Browsers _Downloads_ und dann die heruntergeladene Datei aus. +- In einer Warnmeldung müssen Sie die Installation von Dateien über den Browser erlauben. +- Kehren Sie zu Ihrem Browser zurück, öffnen Sie _Downloads_, und klicken Sie auf die heruntergeladene Datei. +- Klicken Sie in dem daraufhin angezeigten Systemfenster auf _Installieren_ und dann auf _Fertig_ oder _Öffnen_. -Done, AdGuard for Android TV is installed. +Fertig, AdGuard für Android TV ist installiert. -1. Launch AdGuard for Android TV: +1. Starten Sie AdGuard für Android TV: -- After the installation is complete, find the AdGuard app in the list of installed apps on your Android TV. -- Click the AdGuard icon to launch the app. -- Follow the on-screen instructions to complete the setup. +- Nachdem die Installation abgeschlossen ist, suchen Sie die AdGuard-App in der Liste der installierten Apps auf Ihrem Android TV. +- Klicken Sie auf das AdGuard-Symbol, um die App zu starten. +- Folgen Sie den Anweisungen auf dem Bildschirm, um die Einrichtung abzuschließen. -## Installing AdGuard for Android TV via ADB +## Installation von AdGuard für Android TV über ADB -1. Make sure that Android Debug Bridge (ADB) is installed on your computer. If not, you can follow the instructions on XDA Developers: [ADB Installation Guide](https://www.xda-developers.com/install-adb-windows-macos-linux). +1. Stellen Sie sicher, dass die Android Debug Bridge (ADB) auf Ihrem Computer installiert ist. Wenn nicht, können Sie die Anweisungen auf XDA Developers befolgen: [ADB-Installationsanleitung](https://www.xda-developers.com/install-adb-windows-macos-linux). -2. Download [AdGuard for Android TV](https://agrd.io/tvapk). +2. Laden Sie [AdGuard für Android TV](https://agrd.io/tvapk) herunter. -3. In your TV settings, go to _System_ → _About_ and press the build number seven times to unlock developer options. Enable _USB debugging_. +3. Gehen Sie in den TV-Einstellungen auf _System_ → _Über_ und drücken Sie sieben Mal auf die Build-Nummer, um die Entwickleroptionen zu aktivieren. Aktivieren Sie _USB-Debugging_. -4. Write down the IP address of your Android TV: +4. Notieren Sie sich die IP-Adresse Ihres Android TV: - - On your Android TV, navigate to Settings. - - Select _System_ → _About_. - - Find _Network_ and select _Wi-Fi_ or _Ethernet_, depending on your connection type. - - Go to the network section and find _IP address_. Note down this IP address. + - Navigieren Sie auf Ihrem Android TV zu „Einstellungen“. + - Wählen Sie _System_ → _Über_. + - Suchen Sie _Netzwerk_ und wählen Sie _Wi-Fi_ oder _Ethernet_, je nach Verbindungstyp. + - Wechseln Sie zum Abschnitt „Netzwerk“ und suchen Sie die _IP-Adresse_. Notieren Sie sich diese IP-Adresse. -5. Connect to Android TV via ADB: +5. Verbinden Sie sich mit Android TV über ADB: - - Open the terminal or command prompt on your computer. - - Enter the command `adb connect` and paste the IP address of your TV. - - The connection will be established. + - Öffnen Sie das Terminal oder die Eingabeaufforderung auf Ihrem Computer. + - Geben Sie den Befehl `adb connect` ein und fügen Sie die IP-Adresse Ihres TV-Geräts ein. + - Die Verbindung wird aufgebaut. -6. Install AdGuard for Android TV via ADB: +6. Installieren Sie AdGuard für Android TV über ADB: - - In the terminal, enter the command `adb install Downloads/adguard_tv.apk`. If necessary, replace `Downloads/adguard_tv.apk` with your path. - - Wait for a message in the terminal indicating the successful installation of the app. + - Geben Sie im Terminal den Befehl `adb install Downloads/adguard_tv.apk` ein. Ersetzen Sie gegebenenfalls `Downloads/adguard_tv.apk` durch Ihren Pfad. + - Warten Sie auf eine Meldung im Terminal, die die erfolgreiche Installation der App anzeigt. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index 5a6f11cbcb2..778009676bf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -9,13 +9,13 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -In some cases, apps won't stay in the background (“alive” or in a sleep mode) due to the Android OS optimization function, or the so-called “battery save mode” — this function can kill background apps. Es kann lästig sein, sie jedes Mal neu zu starten, wenn sie geschlossen wurden. Um das Beenden von Apps im Hintergrund zu vermeiden, müssen Sie die Schritte befolgen, die wir für jeden Hersteller (Version) von Android OS separat beschrieben haben. Beachten Sie, dass die Anleitungen der verschiedenen Hersteller meist sehr ähnlich sind. +In einigen Fällen bleiben Apps aufgrund der Optimierungsfunktion des Android-Betriebssystems oder des so genannten „Batteriesparmodus“ nicht im Hintergrund („aktiv“ oder im Ruhemodus) — diese Funktion kann Hintergrund-Apps abschalten. Es kann lästig sein, sie jedes Mal neu zu starten, wenn sie geschlossen wurden. Um das Beenden von Apps im Hintergrund zu vermeiden, müssen Sie die Schritte befolgen, die wir für jeden Hersteller (Version) von Android OS separat beschrieben haben. Beachten Sie, dass die Anleitungen der verschiedenen Hersteller meist sehr ähnlich sind. ## Asus Die Informationen über Asus-Geräte sind noch lange nicht vollständig, so dass es noch mehr Probleme geben kann, als hier aufgeführt sind. Wir werden diesen Teil des Artikels aktualisieren, sobald wir mehr wissen. -Die Hauptursache für mögliche Probleme mit der Hintergrundarbeit bei Asus-Geräten ist die Optimierungs-App namens Power Master. It is pre-installed and has pretty aggressive default settings, e.g. to block apps from starting and to kill background tasks when your screen turns off. Um sicherzustellen, dass die Hintergrundverarbeitung von Apps funktioniert, richten Sie Folgendes ein: +Die Hauptursache für mögliche Probleme mit der Hintergrundarbeit bei Asus-Geräten ist die Optimierungs-App namens Power Master. Sie ist vorinstalliert und verfügt über ziemlich aggressive Standardeinstellungen, z. B. zum Sperren des Starts von Apps und zum Beenden von Hintergrundaufgaben, wenn der Bildschirm ausgeschaltet wird. Um sicherzustellen, dass die Hintergrundverarbeitung von Apps funktioniert, richten Sie Folgendes ein: 1. Öffnen Sie den **Mobile Manager** → **PowerMaster** → **Einstellungen** (oder **Batteriesparoptionen**) → Deaktivieren Sie **Aufräumen im Standby-Modus** @@ -29,21 +29,21 @@ Xiaomi-Geräte (und insbesondere MIUI-Geräte) gehören zu den problematischsten ### MIUI 13+ und HyperOS -Depending on the MIUI and HyperOS versions, there are two ways to change the battery optimization settings on your phone and block ads more efficiently. +Je nach MIUI- und HyperOS-Version gibt es zwei Möglichkeiten, die Einstellungen für die Akkuoptimierung auf Ihrem Telefon zu ändern und Werbung effizienter zu sperren. Option 1 -1. Go to **Settings** → **Apps** → **Permissions** → **Background autostart** and allow AdGuard to run in the background +1. Öffnen Sie **Einstellungen** → **Apps** → **Berechtigungen** → **Automatisch im Hintegrund starten** und erlauben Sie AdGuard, im Hintergrund ausgeführt zu werden -1. Return to **Settings** → **Apps** → **Manage apps** → **AdGuard** and uncheck **Pause app activity if unused** +1. Wechseln Sie zurück zu **Einstellungen** → **Apps** → **Apps verwalten** → **AdGuard** und entfernen Sie das Häkchen bei **App-Aktivität anhalten, wenn nicht genutzt** -1. Go to **Battery saver** and tap **No restrictions** +1. Öffnen Sie <0>Batteriesparer und tippen Sie auf <0>Keine Einschränkungen. Option 2 -1. Go to **Settings** → **Apps** → **Manage apps** → **AdGuard** and enable **Autostart** +1. Öffnen Sie **Einstellungen** → **Apps** → **Apps verwalten** → **AdGuard** und aktivieren Sie **Autostart** -1. Go to **Battery saver** and tap **No restrictions** +1. Öffnen Sie <0>Batteriesparer und tippen Sie auf <0>Keine Einschränkungen. Fertig! You have successfully set up AdGuard to work in the background. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index c12f9f386c3..2e7a86c1beb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -1,5 +1,5 @@ --- -title: Battery and traffic consumption issues +title: Probleme mit dem Akku- und Datenverkehrverbrauch sidebar_position: 1 --- @@ -9,52 +9,52 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +Aufgrund der eingebauten Statistikprozesse wurde AdGuard bei Android 6 und früher oft ein hoher Daten- und/oder Akkuverbrauch zugeschrieben. Das lag daran, dass AdGuard der gesamte von ihm gefilterte Datenverkehr von verschiedenen Anwendungen zugerechnet wurde. Infolgedessen wurde der Anteil von AdGuard an der gesamten Daten- und Batterienutzung überbewertet, während andere Anwendungen zu niedrig bewertet wurden. -With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. +Mit Android 7 hat sich dieses Szenario jedoch verbessert. Die Daten, die sich in den in Android integrierten Statistiken zur Datennutzung widerspiegeln, kommen der Realität sehr nahe, auch wenn es bei den Daten zur Akku-Nutzung geringfügige Diskrepanzen gibt. -However, AdGuard users can always get a true picture of the situation on the *Battery usage* screen. +AdGuard-Nutzer:innen können sich jedoch jederzeit auf dem Bildschirm *Batterieverbrauch* ein genaues Bild der Situation machen. -### Own battery usage stats screen +### Eigene Statistiken zum Batterieverbrauch -You can access it by navigating to *Statistics* → *Battery usage*. +Sie können darauf zugreifen, indem Sie zu *Statistiken* → *Batterieverbrauch* navigieren. ![Batteriestatistik *mobile_border](https://cdn.adtidy.org/content/articles/battery/1.png) -Inside you will find a chart that shows the AdGuard battery resource consumption within the last 24 hours, with an option to get more detailed hour-to-hour data by tapping on the chart. Besides that, there’s also a numeric breakdown of the relevant data and a short technical explanation. +Darin finden Sie ein Diagramm, das den Verbrauch der AdGuard-Batterieressourcen in den letzten 24 Stunden anzeigt, mit der Option, durch Antippen des Diagramms detailliertere Daten von Stunde zu Stunde zu erhalten. Darüber hinaus gibt es auch eine numerische Aufschlüsselung der relevanten Daten und eine kurze technische Erklärung. -### How much battery resource does AdGuard really consume? +### Wie viel Batteriekapazität verbraucht AdGuard wirklich? -First, let us lay down a bit of theory and links with necessary data. +Lassen Sie uns zunächst ein paar theoretische Überlegungen anstellen und mit den erforderlichen Daten verknüpfen. -1. Android derives traffic consumption judging on so-called Power Profile, which is given by every manufacturer: +1. Android leitet den Datenverkehr nach dem sogenannten Power Profile (Energieprofil) ab, das von jedem Hersteller vorgegeben wird: -1. Main part of Power Profile is a set of values in mAh which define battery consumption for every component of the device: +1. Hauptbestandteil des Energieprofils ist eine Reihe von Werten in mAh, die den Batterieverbrauch für jede Komponente des Geräts definieren: - For example, from the table above: + Ein Beispiel aus der obigen Tabelle: - *wifi.active=* 31mA additional consumption in mAh caused by WiFi data exchange. + *wifi.active=* 31mA zusätzlicher Verbrauch in mAh durch WLAN-Datenaustausch. - *radio.active=* 100-300mA additional consumption in mAh caused by data exchange over Mobile network. + *radio.active=* 100-300mA zusätzlicher Verbrauch in mAh durch Datenaustausch über das Mobilfunknetz. - *cpu.active=* 100-200mA additional consumption in mAh caused by CPU load. + *cpu.active=* 100-200mA zusätzlicher Verbrauch in mAh, verursacht durch CPU-Last. -1. AdGuard by itself almost doesn't consume any traffic, so for the sake of evaluating power consumption let's get rid of 'Mobile/Wi-Fi packets' and stick to 'CPU'. +1. AdGuard selbst verbraucht so gut wie keinen Datenverkehr, also verzichten wir für die Auswertung des Stromverbrauchs auf „Mobile/WLAN-Pakete“ und bleiben bei „CPU“. - Formula to calculate the consumption: + Formel für die Berechnung des Verbrauchs: > “CPU TIME (ms)” X “cpu.active” / (60 *60* 1000) = “POWER USE mAh” - Let's put real numbers into this formula. + Setzen wir reale Zahlen in diese Formel ein. - Let's take *CPU total* from the second screenshot and convert into milliseconds: 506000 + Nehmen wir *CPU total* aus dem zweiten Bildschirmfoto und rechnen es in Millisekunden um: 506000 - A coefficient *cpu.active* for 2GHz will be roughly equal to 225mAh + Ein Koeffizient *cpu.active* für 2GHz entspricht ungefähr 225mAh - Final result: + Endergebnis: > 506000 *225 / (60* 60 * 1000) = 31,625mAh ### Fazit -Real consumption is **several times less** than it is shown in Android statistics. Statt 220mAh sollten es etwa 31-40mAh sein. On the other hand, browser's consumption should be not 66mAh, but ~200mAh. +Der tatsächliche Verbrauch ist **mehrfach geringer** als er in den Android-Statistiken ausgewiesen wird. Statt 220mAh sollten es etwa 31-40mAh sein. Andererseits sollte der Verbrauch des Browsers nicht 66 mAh, sondern ~200 mAh betragen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 276c8bdcd22..daad514d943 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -18,7 +18,7 @@ If you are using AdGuard in the *Local VPN* filtering mode, you cannot run other - Switch to the *Automatic proxy* mode. Wenn Sie dies tun, wird AdGuard kein lokales VPN mehr verwenden und stattdessen „iptables“ neu konfigurieren - Switch to the *Manual proxy* mode. To do this, go to *Settings* → *Filtering* → *Network* → *Routing mode* -:::note Kompatibilität +:::note Compatibility The *Automatic proxy* mode is only accessible on rooted devices. For *Manual proxy*, rooting is required on devices running on Android 10 or later. @@ -40,7 +40,7 @@ To be able to filter HTTPS traffic, AdGuard requires the user to add a certifica - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) -:::note Kompatibilität +:::note Compatibility Requires root access. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md index 277676855d8..bd9ec9ffb4f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md @@ -1,5 +1,5 @@ --- -title: Manual installation of the security certificate into the Firefox browser +title: Manuelle Installation des Sicherheitszertifikats im Firefox-Browser sidebar_position: 11 --- @@ -9,25 +9,25 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -For AdGuard to successfully filter HTTPS traffic in Firefox, the browser needs to trust AdGuard's certificate. It can be achieved differently for different versions of the Firefox. +Damit AdGuard den HTTPS-Datenverkehr in Firefox erfolgreich filtern kann, muss der Browser dem Zertifikat von AdGuard vertrauen. Dies kann bei verschiedenen Firefox-Versionen auf unterschiedliche Weise erreicht werden. -### Method 1 +### Methode 1 :::note -This method works in Firefox for Android version 90.0 and later. +Diese Methode funktioniert in Firefox für Android Version 90.0 und höher. ::: -To make Firefox trust the AdGuard certificate, do the following: +Um Firefox zu ermöglichen, dem AdGuard-Zertifikat zu vertrauen, gehen Sie wie folgt vor: -1. Run the browser. +1. Starten Sie den Browser. -1. Go to **Settings** → **About Firefox**. +1. Öffnen Sie **Einstellungen** → **Über Firefox**. ![Über Firefox *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/firefox-certificates/ff_nightly_about_en.jpeg) -1. Tap the Firefox logo five times. +1. Tippen Sie fünfmal auf das Firefox-Logo. 1. Navigate to **Settings** → **Secret Settings**. @@ -39,7 +39,7 @@ To make Firefox trust the AdGuard certificate, do the following: :::note -This method will only work on **rooted** devices. +Diese Methode funktioniert nur auf **gerooteten** Geräten. ::: @@ -56,26 +56,26 @@ This method will only work on **rooted** devices. 1. Open the **AdGuard settings** (gear icon in the bottom right corner) → **Filtering** → **Network** → **HTTPS filtering** → **Security certificate** → **Instructions for Firefox** → **Install for old versions**; -1. Open the folder `data/data/org.mozilla.firefox/files/mozilla` using `adb shell su` and `cd data/data/...`, then browse to the folder named `xxxxxxx.default` and memorize its name; +1. Öffnen Sie den Ordner `data/data/org.mozilla.firefox/files/mozilla` mit `adb shell su` und `cd data/data/...` und suchen Sie dann den Ordner mit dem Namen `xxxxxxx.default` und merken Sie sich dessen Namen; -1. In the specified folder we are interested in two files: +1. In dem angegebenen Ordner sind wir an zwei Dateien interessiert: - `cert9.db` - `key4.db` -1. We need to move these files to a folder of the browser where the security certificate issue occurred: +1. Es ist notwendig, diese Dateien in einen Ordner des Browsers zu verschieben, in dem das Problem mit dem Sicherheitszertifikat aufgetreten ist: - `data/data/org.mozilla./files/mozilla/yyyyyy.default`. -1. The full command will look like this: +1. Der vollständige Befehl sieht wie folgt aus: - `adb shell su` - `cp -R data/data/org.mozilla.firefox/files/mozilla/xxxxxxxxxx.default/cert9.db data/data/org.mozilla./files/mozilla/yyyyyyyyyy.default` - `cp -R data/data/org.mozilla.firefox/files/mozilla/xxxxxxxxxx.default/key4.db data/data/org.mozilla./files/mozilla/yyyyyyyyyy.default` - In case you received the system notification **permission denied**, you should first move the specified files to the permission-free directory. And after that you should move them to the necessary folder in your Firefox browser. + In case you received the system notification **permission denied**, you should first move the specified files to the permission-free directory. Danach sollten Sie sie in den entsprechenden Ordner in Ihrem Firefox-Browser verschieben. - The full command should look something like this: + Der vollständige Befehl sollte in etwa so aussehen: - `adb shell su` - `cp -R data/data/org.mozilla.firefox/files/mozilla/xxxxxxxx.default/cert9.db sdcard/Download` @@ -83,4 +83,4 @@ This method will only work on **rooted** devices. - `cp -R sdcard/Download/cert9.db data/data/org.mozilla./files/mozilla/yyyyyyyyyy.default` - `cp -R sdcard/Download/key4.db data/data/org.mozilla./files/mozilla/yyyyyyyyyy.default` - If `adb shell su` does not work, you should try `adb shell` initially, and then `su`. + Wenn `adb shell su` nicht funktioniert, sollten Sie zunächst `adb shell` und dann `su`versuchen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 145889dd56d..991a4f1b4ec 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -15,33 +15,33 @@ HAR-Dateien werden in Übereinstimmung mit der [Datenschutzrichtlinie von AdGuar ::: -## What are HAR files? +## Was sind HAR-Dateien? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +Das HAR-Format (HTTP ARchive) ist eine JSON-formatierte Archivdatei zur Protokollierung der Interaktion eines Webbrowsers mit einer Website. Die Spezifikationen des HAR-Formats definieren Archivierungsdaten für HTTP-Transaktionen, die ein Browser verwendet, um detaillierte Informationen über die von ihm geladenen Webseiten zu exportieren. Eine genauere Beschreibung des HAR-Dateiformats und seiner Spezifikationen finden Sie auf der Website [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). ## So können HAR-Dateien erzeugt werden -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Manchmal müssen wir sie analysieren, um bestimmte Anzeigen zu sperren, die aus irgendeinem Grund schwer zu reproduzieren sind. Gehen Sie wie folgt vor, um HAR-Dateien zu erstellen: -1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). -2. Tap **General** →**Advanced** → **Low-level settings**. +1. Öffnen Sie AdGuard und gehen Sie zu **Einstellungen** (⚙ Symbol in der unteren rechten Ecke). +2. Tippen Sie auf **Allgemein** → **Erweitert** → **Low-Level-Einstellungen**. 3. Scroll down and activate **Capture HAR** in the Filtering section. -4. Open the app and perform the necessary actions to reproduce the problem. +4. Öffnen Sie die App und führen Sie die erforderlichen Aktionen durch, um das Problem zu reproduzieren. 5. Turn **Capture HAR** off. -6. Go back to **Advanced**. +6. Wechseln Sie zurück zu **Erweitert**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Senden Sie die erzeugte Datei mit den Protokollen an den AdGuard-Support.** :::note -Our support team will process your ticket much faster if you specify the HelpDesk ticket number or the GitHub issue number in your message. +Unser Support-Team wird Ihr Ticket viel schneller bearbeiten, wenn Sie die HelpDesk-Ticketnummer oder die GitHub-Issue-Nummer in Ihrer Nachricht angeben. ::: -## How to analyze HAR files +## So können Sie HAR-Dateien analysieren -Here are some sources that we can recommend to analyze HAR files: +Hier sind einige Anwendungen, die wir für die Analyse von HAR-Dateien empfehlen können: -- [HTTP Archive Viewer master](https://gitgrimbo.github.io/harviewer/master/) is a HAR analyzer tool, visualizes HTTP Archive (HAR) log files created by HTTP tracking tools. -- [Fiddler](https://www.telerik.com/fiddler) is a web debugging proxy, lets you capture, inspect, monitor all HTTP(S) traffic between your computer and the Internet, mock requests, and diagnose network issues. +- [HTTP Archive Viewer master](https://gitgrimbo.github.io/harviewer/master/) ist ein HAR-Analysetool, das von HTTP-Tracking-Tools erstellte HTTP Archive (HAR) Log-Dateien visualisiert. +- [Fiddler](https://www.telerik.com/fiddler) ist ein Web-Debugging-Proxy, mit dem Sie den gesamten HTTP(S)-Verkehr zwischen Ihrem Computer und dem Internet erfassen, untersuchen, überwachen, Anfragen simulieren und Netzwerkprobleme diagnostizieren können. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md index cfdc7bcba8f..6a5dd95f894 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md @@ -1,5 +1,5 @@ --- -title: Problems caused by multiple user profiles +title: Probleme, die durch mehrere Benutzerprofile verursacht werden sidebar_position: 10 --- @@ -11,13 +11,13 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc In this article you will find the methods on how to solve problems with AdGuard when you set up *multiple accounts* or *Restricted Profiles* on your Android devices. -## Problems caused by multiple user profiles +## Probleme, die durch mehrere Benutzerprofile verursacht werden -On Android 9 and later, if AdGuard is installed for more than one user profile on your device, you may encounter problems when uninstalling the app. When you uninstall AdGuard from one user profile, the app will still appear on the app list, but you won't be able to uninstall or reinstall it. This happens because AdGuard is installed for a different user profile on the device. +Unter Android 9 und höher, wenn AdGuard für mehr als ein Benutzerprofil auf Ihrem Gerät installiert ist, können Probleme bei der Deinstallation der App auftreten. Wenn Sie AdGuard aus einem Benutzerprofil deinstallieren, wird die App weiterhin in der App-Liste angezeigt, aber Sie können sie weder deinstallieren noch neu installieren. This happens because AdGuard is installed for a different user profile on the device. If you try to reinstall AdGuard after an unsuccessful removal attempt, you will see the error message “You can't install the app on your device”. -To solve this problem, you need to uninstall the application for all users: go to Settings → All apps → AdGuard. Tap the three-dot menu in the top right corner and select *Uninstall for all users*. +Um dieses Problem zu lösen, müssen Sie die App für alle Benutzer deinstallieren: Gehen Sie zu Einstellungen → Alle Apps → AdGuard. Tap the three-dot menu in the top right corner and select *Uninstall for all users*. ![Uninstall *mobile border](https://cdn.adtidy.org/blog/new/tu49hmultiple_users.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md index 87c509fef20..c3a382b949c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md @@ -1,5 +1,5 @@ --- -title: How to block ads in the YouTube app +title: So blockieren Sie Werbung in der YouTube-App sidebar_position: 7 --- @@ -9,24 +9,24 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -One of the most popular questions users ask us is: 'Is it possible to block ads in YouTube on Android?'. Due to the technical restrictions of the Android OS, there is no way to *completely* remove ads from the YouTube app. But we've found an alternative that brings you to it as close as possible, while getting around the Android-imposed restrictions. +Eine der häufigsten Fragen, die wir erhalten, lautet: „Ist es möglich, YouTube-Werbung auf Android zu blockieren?“. Aufgrund der technischen Einschränkungen des Android-Betriebssystems gibt es keine Möglichkeit, *Werbung vollständig* aus der YouTube-App zu entfernen. Wir haben jedoch eine Alternative gefunden, die Sie so nah wie möglich daran heranführt und gleichzeitig die von Android auferlegten Einschränkungen umgeht. -## Watch YouTube in the AdGuard app +## YouTube in der AdGuard-App ansehen -![Instruction *mobile](https://cdn.adtidy.org/public/Adguard/Blog/Android/3-6/share.gif) +![Anweisung *mobile](https://cdn.adtidy.org/public/Adguard/Blog/Android/3-6/share.gif) -1. Open the YouTube app and start the video you want to watch. +1. Öffnen Sie die YouTube-App und starten Sie das Video, das Sie ansehen möchten. -1. Tap the *Share* button. +1. Tippen Sie auf die Schaltfläche *Teilen*. - ![Share to YouTube step 1 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/youtube/android-youtube-share-step1.png) + ![Auf YouTube teilen: Schritt 1 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/youtube/android-youtube-share-step1.png) -1. Select *AdGuard* from the list of apps. +1. Wählen Sie *AdGuard* aus der Liste der Apps. - ![Share to YouTube step 2 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/youtube/android-youtube-share-step2.png) + ![Auf YouTube teilen: Schritt 2 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/youtube/android-youtube-share-step2.png) -That's it! A new window with the video will open where you'll be able to watch it without being interrupted by ads. +Das war's! Es öffnet sich ein neues Fenster mit dem Video, in dem Sie es ohne Unterbrechung durch Werbung ansehen können. -## Watch YouTube in a browser +## YouTube in einem Browser ansehen -Alternatively, you can also watch YouTube in a browser and there will be no ads if you have AdGuard installed and enabled. +Alternativ können Sie YouTube auch in einem Browser ansehen und es wird keine Werbung angezeigt, wenn Sie AdGuard installiert und aktiviert haben. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index a9b13d9f508..c2bd00c022d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -11,15 +11,15 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc AdGuard can significantly broaden website functionality working as a [user script manager](/general/userscripts). Sie können ihre eigenen Skripte hinzufügen und bestehende Skripte verwalten. -![Extensions \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/userscripts.png) +![Erweiterungen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/userscripts.png) -**Automatically detect userscripts** +**Benutzerskripte automatisch erkennen** Wenn diese Option aktiviert ist, definiert AdGuard automatisch Browser-Anfragen an Benutzerskripte und schlägt deren Installation vor. Andernfalls können die Erweiterungen (Benutzerskripte) heruntergeladen und manuell installiert werden. Die folgenden Erweiterungen werden mit AdGuard installiert: -![Preinstalled userscripts \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/preinstalled-userscripts.png) +![Vorinstallierte Benutzerskripte \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/preinstalled-userscripts.png) **AdGuard-Assistent** @@ -41,9 +41,9 @@ Mit Web of Trust können Sie den Ruf jeder Website auf der Grundlage von Nutzerm ### Netzwerk -Das vorletzte Modul ist der Netzwerkfilterung gewidmet, und hier finden Sie weitere netzwerkbezogene Optionen. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Dies sind wichtige zusätzliche Vorsichtsmaßnahmen, um Ihren Webspace besser zu filtern. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Das vorletzte Modul ist der Netzwerkfilterung gewidmet, und hier finden Sie weitere netzwerkbezogene Optionen. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Dies sind wichtige zusätzliche Vorsichtsmaßnahmen, um Ihren Webspace besser zu filtern. Die meisten Websites verwenden jetzt HTTPS, und dies gilt auch für die Werbung. Von vielen Websites, wie youtube.com, facebook.com und x.com, ist es unmöglich, Werbung ohne HTTPS-Filterung zu entfernen. Lassen Sie also die Funktion _HTTPS filtern_ aktiviert, es sei denn, Sie haben einen triftigen Grund, dies nicht zu tun. -![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) +![Netzwerkeinstellungen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) In diesem Modul können Sie das Kontrollkästchen „AdGuard als HTTP-Proxy verwenden“ aktivieren, um AdGuard als regulären HTTP-Proxy zu verwenden, der den gesamten Datenverkehr filtert. You can also enable the _Filter websites with EV certificates_ feature. Extended Validation (EV) SSL-Zertifikate bieten eine stärkere Sicherheitsgarantie; die Inhaber solcher Websites müssen ein gründliches und weltweit standardisiertes Identitätsprüfungsverfahren durchlaufen, das durch EV-Richtlinien definiert ist. Aus diesem Grund vertrauen einige Benutzer Websites mit solchen Zertifikaten und ziehen es vor, sie nicht zu filtern. @@ -55,7 +55,7 @@ Der letzte Abschnitt ist AdGuard VPN gewidmet, einem nützlichen Tool, das Siche Wie funktioniert AdGuard VPN? Ohne auf technische Details einzugehen, können wir sagen, dass VPN einen sicheren verschlüsselten Tunnel zwischen dem Computer oder Mobilgerät und einem entfernten VPN-Server herstellt. Auf diese Weise bleibt die Vertraulichkeit der Daten und Ihre Anonymität gewahrt, da ein Dritter nur die IP-Adresse des VPN-Servers und nicht Ihre tatsächliche IP-Adresse sieht. -**What AdGuard VPN does:** +**Was AdGuard VPN leistet:** - verbirgt Ihren tatsächlichen Aufenthaltsort und hilft Ihnen, anonym zu bleiben - ändert Ihre IP-Adresse, um Ihre Daten vor Verfolgung zu schützen diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md index 6af21ea159a..2ee12c2ac48 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md @@ -13,4 +13,4 @@ AdGuard für Windows ist ein einfach zu bedienendes Tool, das lästige Banner, P ![Hauptbildschirm \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/home-screen.png) -Sobald Sie AdGuard für Windows starten, wird der Hauptbildschirm der App angezeigt. Its most noticeable detail is the _enable/disable protection_ button. Auf dieser Seite können Sie auch Statistiken über blockierte Werbung, Tracker und Bedrohungen einsehen, die aktuelle Version der App abrufen oder die App aktualisieren. Furthermore, there are four tabs in the upper right corner: _Settings_, _Support_, _License_, and _About_. Jeder dieser Punkte ist es wert, gesondert behandelt zu werden. +Sobald Sie AdGuard für Windows starten, wird der Hauptbildschirm der App angezeigt. Das auffälligste Detail ist die Schaltfläche _Schutz aktivieren/deaktivieren_. Auf dieser Seite können Sie auch Statistiken über blockierte Werbung, Tracker und Bedrohungen einsehen, die aktuelle Version der App abrufen oder die App aktualisieren. Außerdem gibt es in der oberen rechten Ecke vier Registerkarten: _Einstellungen_, _Support_, _Lizenz_ und _Über_. Jeder dieser Punkte ist es wert, gesondert behandelt zu werden. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md index 7643ca57ff3..41f959d1cd8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md @@ -34,7 +34,7 @@ Zusätzlich zu den Informationen über die aktuelle Version des Programms bietet ### Auf Aktualisierungen prüfen -![Check for updates \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/check-updates.png) +![Nach Aktualisierungen suchen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/check-updates.png) Um zu prüfen, ob Filter und Benutzerskripte aktualisiert wurden, klicken Sie auf das Symbol mit den rotierenden Pfeilen in der oberen rechten Ecke des Hauptbildschirms der App. @@ -44,11 +44,11 @@ Um Ihnen die Navigation durch die Menüs des AdGuard zu ersparen, sind viele der - Schutz aktivieren - Schutz deaktivieren: vollständig oder für 30 Sekunden -- go to _Settings_ -- open the _Tools_ and _Advanced_ menus -- Prüfen auf Filteraktualisierungen -- Suchen nach App-Aktualisierungen +- _Einstellungen_ öffnen +- Menüs _Extras_ und _Erweitert_ öffnen +- auf Filteraktualisierungen prüfen +- nach App-Aktualisierungen suchen - die letzte Pop-up-Meldung aufrufen -- reach the _Support_ and _About_ sections +- die Abschnitte _Support_ und _Über_ erreichen - AdGuard schließen, aber weiterhin filtern - AdGuard beenden diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3522eb92417..7ee4a800ddb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc ::: -_Settings_ is the section that requires the most attention. Hier können Sie die App so konfigurieren, dass sie genau Ihren Bedürfnissen entspricht: Sie blockiert nur das, was Sie stört, verwendet den DNS-Server des vertrauenswürdigen Anbieters, entfernt Cookies von Drittanbietern und so weiter. +_Einstellungen_ ist der Bereich, der die meiste Aufmerksamkeit erfordert. Hier können Sie die App so konfigurieren, dass sie genau Ihren Bedürfnissen entspricht: Sie blockiert nur das, was Sie stört, verwendet den DNS-Server des vertrauenswürdigen Anbieters, entfernt Cookies von Drittanbietern und so weiter. ![Einstellungen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/settings.png) @@ -19,11 +19,11 @@ Hier können Sie die Sprache und das Design (dunkel oder hell) festlegen, den St ![Erweiterte Einstellungen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) -At the very bottom of the screen you will find _Advanced Settings_. Wenn Sie einige von ihnen unbedacht ändern, kann dies zu Problemen mit der Leistung führen, die Internetverbindung unterbrechen oder Ihre Sicherheit und Privatsphäre gefährden. Deshalb empfehlen wir Ihnen, diesen Bereich nur zu öffnen, wenn Sie sicher sind, was Sie tun, oder wenn unser Support-Team Sie danach gefragt hat. If you want to know what can be set up in _Advanced Setting_ read the [dedicated article](/adguard-for-windows/solving-problems/low-level-settings.md). +Ganz unten auf dem Bildschirm finden Sie _Erweiterte Einstellungen_. Wenn Sie einige von ihnen unbedacht ändern, kann dies zu Problemen mit der Leistung führen, die Internetverbindung unterbrechen oder Ihre Sicherheit und Privatsphäre gefährden. Deshalb empfehlen wir Ihnen, diesen Bereich nur zu öffnen, wenn Sie sicher sind, was Sie tun, oder wenn unser Support-Team Sie danach gefragt hat. Wenn Sie wissen möchten, was unter _Erweiterte Einstellungen_ eingestellt werden kann, lesen Sie den [entsprechenden Artikel](/adguard-for-windows/solving-problems/low-level-settings.md). ### Werbeblocker -Dies ist das Hauptmodul von AdGuard für Windows, das Werbung von den von Ihnen besuchten Websites und von den auf Ihrem Gerät installierten Apps entfernt. To filter out advertising and privacy-threatening content such as banners, pop-ups, or trackers AdGuard uses different filters: groups of rules with a similar purpose written with a [special syntax](/general/ad-filtering/create-own-filters). To understand what filters are and how they work read [this article](/general/ad-filtering/how-ad-blocking-works). +Dies ist das Hauptmodul von AdGuard für Windows, das Werbung von den von Ihnen besuchten Websites und von den auf Ihrem Gerät installierten Apps entfernt. To filter out advertising and privacy-threatening content such as banners, pop-ups, or trackers AdGuard uses different filters: groups of rules with a similar purpose written with a [special syntax](/general/ad-filtering/create-own-filters). Um zu verstehen, was Filter sind und wie sie funktionieren, lesen Sie [diesen Artikel](/general/ad-filtering/how-ad-blocking-works). ![Werbeblocker \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/settings_ad_blocker.png) @@ -38,7 +38,7 @@ Im Werbeblocker-Modul können Sie: - see all the requests sent by browsers and apps installed on your computer by clicking the _Filtering log_ button. Von dort aus können Sie auch jede Anfrage sperren oder freigeben, indem Sie eine benutzerdefinierte Regel erstellen, - einen Filter aus Ihren eigenen, manuell erstellten, importierten oder mit der Erweiterung Browser-Assistent erstellten Regeln zusammenstellen. -Before you start manually writing your own rules read our detailed [syntax guide](/general/ad-filtering/create-own-filters). +Bevor Sie mit dem manuellen Schreiben eigener Regeln beginnen, lesen Sie unsere detaillierte [Syntax-Anleitung](/general/ad-filtering/create-own-filters). ### Privatsphäre @@ -52,7 +52,7 @@ To learn everything about Stealth Mode and its many options, [read this article] ### Internetsicherheit -Browsing security gives strong protection against malicious and phishing websites. AdGuard für Windows ist natürlich kein Antivirenprogramm. Die App kann weder das Herunterladen eines Virus stoppen, wenn es bereits begonnen hat, noch bereits vorhandene Viren löschen. Sie werden jedoch gewarnt, wenn Sie eine Website aufrufen oder eine Datei von einer Website herunterladen, deren Domain in unserer Datenbank „Nicht vertrauenswürdige Websites“ aufgeführt ist. You can find more information about how this module works in the [dedicated article](/general/browsing-security). +Internetsicherheit bietet starken Schutz vor bösartigen und Phishing-Websites. AdGuard für Windows ist natürlich kein Antivirenprogramm. Die App kann weder das Herunterladen eines Virus stoppen, wenn es bereits begonnen hat, noch bereits vorhandene Viren löschen. Sie werden jedoch gewarnt, wenn Sie eine Website aufrufen oder eine Datei von einer Website herunterladen, deren Domain in unserer Datenbank „Nicht vertrauenswürdige Websites“ aufgeführt ist. You can find more information about how this module works in the [dedicated article](/general/browsing-security). In diesem Modul können Sie: @@ -80,7 +80,7 @@ Es gibt eine Reihe von Websites, auf die der Zugriff von einem von Kindern benut Das Modul prüft den Inhalt der im Browser geöffneten Webseiten und filtert diejenigen mit für Kinder unerwünschten Inhalten: Bilder und Texte für Erwachsene, Schimpfwörter, Gewalt, Drogenpropaganda usw. Die Einstellungen der Kindersicherung sind passwortgeschützt, so dass das Kind die Einschränkungen nicht umgehen kann. Dieses Modul blockiert nicht nur die Weiterleitung auf unerwünschte Seiten, sondern kann auch die für Kinder ungeeigneten Links aus den Suchergebnissen entfernen. -Im Modul _Kindersicherung_ können Sie die _Sichere Suche_ aktivieren und die _Sperrliste_ und die _Positivliste_ verwalten, um die Funktionsweise dieser Option anzupassen. Sie können auch das Kontrollkästchen _Herunterladen von ausführbaren Dateien sperren_ aktivieren, um zu verhindern, dass Ihr Kind Software auf den Computer herunterlädt und installiert. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +Im Modul _Kindersicherung_ können Sie die _Sichere Suche_ aktivieren und die _Sperrliste_ und die _Positivliste_ verwalten, um die Funktionsweise dieser Option anzupassen. Sie können auch das Kontrollkästchen _Herunterladen von ausführbaren Dateien sperren_ aktivieren, um zu verhindern, dass Ihr Kind Software auf den Computer herunterlädt und installiert. Im Modul _Kindersicherung_ gibt es zwei weitere Optionen: Sie können einen bestimmten Windows-Benutzer auswählen, der durch die _Kindersicherung_ geschützt werden soll, und ein Passwort festlegen, um die Einstellungen vor Änderungen zu schützen. ![Kindersicherung \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 13d920afeac..78d8b8ee7d7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -31,7 +31,7 @@ Um AdGuard auf einem PC oder Tablet unter Microsoft Windows zu verwenden, müsse ![Drücken Sie "Ausführen"](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/click-download.png) -3. You’ll see the User Account Control dialogue box requesting to allow the app to make changes to your PC. Klicken Sie auf *Ja*. +3. Es wird das Dialogfeld der Benutzerkontensteuerung angezeigt, in dem Sie aufgefordert werden, der Anwendung zu erlauben, Änderungen an Ihrem PC vorzunehmen. Klicken Sie auf *Ja*. ![Lassen Sie Änderungen zu *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) @@ -77,9 +77,9 @@ Falls die reguläre Deinstallation aus irgendeinem Grund nicht funktioniert, kö ![Standard-Deinstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) -- Click *OK* once the warning window pops up: +- Klicken Sie auf *OK*, sobald das Warnfenster angezeigt wird: -![Standard uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![Standard-Deinstallationshinweis *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) - Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: @@ -87,7 +87,7 @@ Falls die reguläre Deinstallation aus irgendeinem Grund nicht funktioniert, kö :::caution -Follow the next steps only if performing the first two steps wasn’t enough for some reason. We strongly suggest contacting our support before using steps 3-4 of advanced uninstall instruction. +Führen Sie die nächsten Schritte nur aus, wenn die ersten beiden Schritte aus irgendeinem Grund nicht ausreichend waren. Wir empfehlen dringend, unseren Support zu kontaktieren, bevor Sie die Schritte 3-4 der erweiterten Deinstallationsanweisung ausführen. ::: @@ -95,12 +95,12 @@ Follow the next steps only if performing the first two steps wasn’t enough for ![Erweiterte Deinstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) -- Click *OK* once the warning window pops up: +- Klicken Sie auf *OK*, sobald das Warnfenster angezeigt wird: ![Extended uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) - Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: -![Extended uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) +![Erweiterte Deinstallation abgeschlossen *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) AdGuard wurde erfolgreich deinstalliert! diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md index 42f02784227..86b4954a8ce 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md @@ -31,8 +31,8 @@ Geräte, die an Ihre AdGuard Werbeblocker-Lizenzen gebunden sind, können gelös ## Käufe ansehen -Im Abschnitt Kaufhistorie werden alle Lizenzen angezeigt, die Sie jemals über das E-Mail-Konto erworben haben, mit dem Sie Ihr AdGuard-Konto registriert haben. You will also find there information about the date of purchase, order ID, payment method, and cost of the purchase. +Im Abschnitt Kaufhistorie werden alle Lizenzen angezeigt, die Sie jemals über das E-Mail-Konto erworben haben, mit dem Sie Ihr AdGuard-Konto registriert haben. Dort finden Sie auch Informationen über das Kaufdatum, die Bestellnummer, die Zahlungsmethode und die Kosten des Kaufs. ## Support kontaktieren -Der Tab „Support” enthält nützliche Links, die Ihnen helfen, Probleme zu lösen oder Antworten auf Ihre Fragen zu AdGuard-Produkten zu finden. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +Der Tab „Support” enthält nützliche Links, die Ihnen helfen, Probleme zu lösen oder Antworten auf Ihre Fragen zu AdGuard-Produkten zu finden. Diese sind in sechs Abschnitte unterteilt: Häufig gestellte Fragen (FAQ), Fehlerbericht/Funktionsanforderung senden, Fehlerhafte Sperrung melden, Support kontaktieren, Wissensdatenbank und Diskutieren. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/account/register.md b/i18n/de/docusaurus-plugin-content-docs/current/general/account/register.md index be8e155c132..ed7c435c137 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/account/register.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/account/register.md @@ -13,7 +13,7 @@ Um ein Konto zu erstellen, öffnen Sie die offizielle Website von [AdGuard](http :::tip -If you enter your email address when purchasing a license, or receive a license linked to your email address as a gift, an account will be created automatically. Um ein Passwort festzulegen, können Sie einem Link in einer Transaktions- oder Geschenk-E-Mail folgen. Sie können sich auch mit der oben genannten Methode registrieren. +Wenn Sie beim Kauf einer Lizenz Ihre E-Mail-Adresse angeben oder eine mit Ihrer E-Mail-Adresse verknüpfte Lizenz als Geschenk erhalten, wird automatisch ein Konto erstellt. Um ein Passwort festzulegen, können Sie einem Link in einer Transaktions- oder Geschenk-E-Mail folgen. Sie können sich auch mit der oben genannten Methode registrieren. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 21cbb6ac944..433af01c1f6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2729,7 +2728,7 @@ Rules with `$mp4` modifier are not supported by AdGuard Content Blocker, AdGuard Each rule has its own priority, which is necessary when several rules match the request and the filtering engine needs to select one of them. Priority is measured by a positive integer. -:::note Kollisionen +:::note Collisions When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. @@ -3941,7 +3940,7 @@ or :contains(/reg(ular )?ex(pression)?/) ``` -:::note Kompatibilität +:::note Compatibility `:-abp-contains()` and `:has-text()` are synonyms for `:contains()`. @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index d27d3d0c6f8..bc0244e767f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,14 @@ AdGuard-Filter zum Blockieren von Werbung umfassen: - AdGuard Basisfilter - AdGuard-Filter gegen mobile Werbung - Regionale Filter nach Sprachprinzip — Chinesisch, Niederländisch, Französisch, Deutsch, Japanisch, Russisch, Spanisch/Portugiesisch, Türkisch, und Ukrainisch -- AdGuard Quick Fixes filter +- AdGuard Quick Fixes-Filter ### Der Zweck dieser Filter - **Der Basisfilter** blockiert Werbung auf englischsprachigen Websites und solchen, für die es keinen eigenen Filter gibt. Er enthält auch allgemeine Filterregeln, die für alle Websites unabhängig von der Sprache gelten - **Filter gegen mobile Werbung** blockiert Werbung auf mobilen Versionen von Websites und in mobilen Apps. Es gibt keine Unterteilung nach Sprachen - **Sprachspezifische Filter** folgen der gleichen Politik wie der **Basisfilter**, sind aber auf Websites in bestimmten Sprachen beschränkt -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. +- Quick-Fixes-Filter zur schnellen Behebung kritischer Probleme bei der Filterung von Inhalten auf beliebten Websites ohne Aktualisierung der MV3-Erweiterung. Das Ziel von Werbeblockern ist es, alle Arten von Werbung auf Websites, in Apps und auf bestimmten Geräten, die Werbung aus dem Internet laden können, zu blockieren: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..f87dcd9549e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -19,7 +19,7 @@ Simply put, HTTPS means data encryption. But there’s still a problem: how can ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Die meisten Websites verwenden jetzt HTTPS, und dies gilt auch für die Werbung. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. ### How does HTTPS filtering work? diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md index 6fb1cad57e8..6f7489e7859 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: Was ist eine AdGuard-Lizenz? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Auf der [Kaufseite](https://adguard.com/license.html) sind folgende Arten von Li - **1-Jahres-Abonnements** — diese Lizenzen werden automatisch jedes Jahr erneuert oder können manuell verlängert werden - Einzellizenz — schützt bis zu 3 Geräte - Familienlizenz — schützt bis zu 9 Geräte -- **Lifetime** — these licenses are perpetual +- **Lebenslang** — diese Lizenzen sind zeitlich unbefristet - Einzellizenz — schützt bis zu 3 Geräte - Familienlizenz — schützt bis zu 9 Geräte diff --git a/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 9f9a4a15e41..1207b985d74 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: So können HAR-Dateien erzeugt werden sidebar_position: 1 --- diff --git a/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 9596767a128..b10ca7f6690 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Prüfen Sie, ob Sie die aktuellste Version haben, und wenn nicht, aktualisieren ### Wie man ein Problem beschreibt -Versuchen Sie, so viele Details wie möglich anzugeben — das macht es für uns einfacher, den Fehler zu reproduzieren und herauszufinden, wie er behoben werden kann. Here’s what we expect a bug report to include: +Versuchen Sie, so viele Details wie möglich anzugeben — das macht es für uns einfacher, den Fehler zu reproduzieren und herauszufinden, wie er behoben werden kann. Wir erwarten, dass ein Fehlerbericht folgende Angaben enthält: - Ihre App-Version - Ihre OS-Version @@ -28,7 +28,7 @@ Versuchen Sie, so viele Details wie möglich anzugeben — das macht es für uns ### So erfassen Sie Protokolle -Read about collecting logs in dedicated articles for each platform. +Lesen Sie über das Erfassen von Protokollen in speziellen Artikeln für jede Plattform. ## Wie man für Fehlerberichte oder Funktionswünsche abstimmt diff --git a/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 9c985b92a2c..1a1cce1e52b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ Auf manchen Laptops müssen Sie *Fn* gedrückt halten und dann *Druck* drücken. Windows erfasst den gesamten Bildschirm und kopiert ihn in die Zwischenablage. -To take a screenshot of an active window, use the following shortcut keys: +Um ein Bildschirmfoto eines aktiven Fensters zu erstellen, verwenden Sie das folgende Tastaturkürzel: - **Halten Sie *Alt* gedrückt und drücken Sie *Druck* (oder *Fn + Alt + Druck* auf einigen Laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +Um ein Bildschirmfoto von einem bestimmten Bereich zu machen, verwenden Sie das folgende Tastaturkürzel: - ***Drücken Sie ***Win + Umschalt + S****** -Nachdem Sie ein Bildschirmfoto erstellt haben, wird es in der Zwischenablage gespeichert. In den meisten Fällen können Sie es mit dem Tastaturkürzel *Strg + V* in ein Dokument einfügen, das Sie gerade bearbeiten. Wenn Sie das Bildschirmfoto in einer Datei speichern möchten, sollten Sie alternativ das Standardprogramm **Paint** (oder eine andere Anwendung, die mit Bildern arbeiten kann) öffnen. Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Nachdem Sie ein Bildschirmfoto erstellt haben, wird es in der Zwischenablage gespeichert. In den meisten Fällen können Sie es mit dem Tastaturkürzel *Strg + V* in ein Dokument einfügen, das Sie gerade bearbeiten. Wenn Sie das Bildschirmfoto in einer Datei speichern möchten, sollten Sie alternativ das Standardprogramm **Paint** (oder eine andere Anwendung, die mit Bildern arbeiten kann) öffnen. Fügen Sie Ihr Bildschirmfoto mit denselben Tastenkombinationen oder durch Klicken auf die Schaltfläche „Einfügen” (in der Regel in der oberen linken Ecke des Bildschirms) ein und speichern Sie es dann. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Sobald Sie diese Tasten drücken, wird das Bildschirmfoto automatisch als Datei in Ihrem Ordner *Bilder* → *Bildschirmfotos* gespeichert. +In Windows 8 und 10 können Sie mit den Tastaturkürzeln *Win + PrtScn* sehr schnell ein Bildschirmfoto erstellen. Sobald Sie diese Tasten drücken, wird das Bildschirmfoto automatisch als Datei in Ihrem Ordner *Bilder* → *Bildschirmfotos* gespeichert. Es gibt auch ein spezielles Programm zum Erstellen von Bildschirmfotos namens *Snipping Tool*. Sie finden es im Startmenü unter den Standardprogrammen Ihres Computers. Mit dem Snipping Tool können Sie einen beliebigen Bereich Ihres Desktops oder den gesamten Bildschirm erfassen. Nach der Aufnahme eines Bildschirmfotos mit diesem Programm können Sie das Bild bearbeiten und in einem beliebigen Ordner auf Ihrem Computer speichern. @@ -70,26 +70,26 @@ Außerdem können Sie auch versuchen, verschiedene Apps zum Aufnehmen von Bildsc ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Um ein Bildschirmfoto auf dem Mac zu erstellen, verwenden Sie die folgenden Tastaturkürzel: - ***Drücken und halten Sie ***⌘ Cmd + Umschalt + 3****** Ihr Mac erfasst den gesamten Bildschirm und speichert ihn als Datei auf dem Desktop. -To take a screenshot of an active window, use the following shortcut keys: +Um ein Bildschirmfoto eines aktiven Fensters zu erstellen, verwenden Sie das folgende Tastaturkürzel: - **Drücken und halten Sie *⌘ Cmd + Umschalt + 4 + Leertaste*. Der Zeiger verwandelt sich in ein Kamerasymbol. Klicken Sie auf das Fenster, um es zu erfassen. Drücken Sie die Esc-Taste, um die Aufnahme eines Bildschirmfotos abzubrechen** -To take a screenshot of a specific area, use the following shortcut keys: +Um ein Bildschirmfoto von einem bestimmten Bereich zu machen, verwenden Sie das folgende Tastaturkürzel: - ***Drücken Sie ***⌘ Cmd + Umschalt + 5******. Ziehen Sie das Fadenkreuz, um den gewünschten Bereich auszuwählen. Lassen Sie die Maus oder das Trackpad los, um ein Bildschirmfoto zu erstellen, und drücken Sie Esc, um den Vorgang abzubrechen. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Um ein Bildschirmfoto der *Touch Bar* (MacBook Pro) zu erstellen, verwenden Sie die folgenden Tastaturkürzel: - ***Drücken Sie ***⌘ Cmd + Umschalt + 6****** Ihr Mac nimmt die gesamte *Touch Bar* auf und speichert sie als Datei auf dem Desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Um ein Bildschirmfoto in die Zwischenablage zu kopieren, anstatt es zu speichern, halten Sie die Steuerungstaste *Ctrl* zusammen mit einer der oben genannten Tastaturkürzel gedrückt. Dann können Sie das Bildschirmfoto (aus der Zwischenablage) mit der Tastenkombination *Cmd + V* in ein Dokument oder ein Bild einfügen, das Sie gerade bearbeiten. Sie können auch Bildschirmfotos erstellen, indem Sie die **Vorschau** verwenden und **Bildschirmfoto aufnehmen** (von dem ausgewählten Bereich, Fenster oder dem gesamten Bildschirm) wählen. Mit der **Vorschau** können Sie Ihre Bildschirmfotos in JPG, TIFF, PDF und anderen Dateiformaten speichern. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..76e67a5634a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -1,76 +1,76 @@ --- -title: AdGuard Browser Extension for Chrome MV3 +title: Extensión de navegador AdGuard para Chrome MV3 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +Como las extensiones MV2 se están eliminando gradualmente de Chrome Web Store, es posible que los usuarios de Chrome necesiten cambiar a extensiones MV3 que sean compatibles con la nueva API Manifest V3 de Chrome. Nuestras opiniones sobre este tema se debaten ampliamente en [nuestro blog](https://adguard.com/es/blog/tag/manifest-v3.html). -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +Nuestra extensión MV3 bloquea eficazmente anuncios y rastreadores mientras administra sin problemas widgets sociales, banners y anuncios de video. La mayoría de los usuarios no notarán ninguna diferencia operativa, pero hay algunas limitaciones y cambios que conviene tener en cuenta. -## Where to find our extensions +## Dónde encontrar nuestras extensiones -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +La **versión MV3** ha reemplazado nuestra antigua extensión en [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +La **versión beta de MV3** seguirá estando disponible en [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +La antigua extensión beta cambiará de nombre a [**Bloqueador AdGuard MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) y recibirás soporte hasta que Google la elimine. -## Main changes in features and settings +## Principales cambios en funciones y configuraciones -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **No hay actualizaciones de filtros automáticas ni manuales.** Las opciones _Actualizar filtros automáticamente_ y _Verificar actualización de filtros_ ya no están disponibles en la pestaña _Filtros_. Dado que algunas de las reglas ahora se aplican en formato DNR, no podemos actualizar los filtros a pedido, solo a través del proceso completo de actualización de la extensión junto con la revisión en las tiendas. -- **Filtering log** +- **Registro de filtrado** - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) + ![Registro de filtrado \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + Debido a las restricciones del DNR, no podemos mostrar exactamente qué regla funcionó, pero proporcionaremos una “regla asumida que se activó” según nuestro motor. Para obtener información precisa, deberás instalar la forma “descomprimida” de la extensión en tu navegador. Encontrarás instrucciones detalladas sobre cómo hacer esto en un [artículo separado](/adguard-browser-extension/solving-problems/debug-rules/). -- _Tracking protection_ (formerly known as _Stealth mode_) +- _Protección de seguimiento_ (antes conocida como _Modo oculto_) - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) + ![Protección contra el seguimiento \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + No hay una sección de _Cookies_, junto con _Autodestrucción de cookies propias_ y _Autodestrucción de cookies de terceros_, ya que no podemos establecer el TTL de las cookies mediante reglas declarativas. -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- La _Protección contra phishing y malware_ ya no está disponible en la configuración general. Para protegerte de sitios web maliciosos y estafas, habilita los filtros de _Seguridad_ adecuados en la pestaña _Filtros_. - ![Security \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) + ![Seguridad \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) -## Limitations +## Limitaciones -### Maximum number of rules and filters +### Número máximo de reglas y filtros -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +El manifiesto V3 impone límites a las reglas estáticas y regex por extensión. Los usuarios podrán recibir notificaciones cuando se excedan estos límites. -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) +![Límites de reglas \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) +![Demasiadas extensiones \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +Básicamente, Manifest V3 divide las reglas en estáticas (integradas) y dinámicas, con límites estrictos establecidos. -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +**Reglas estáticas:** mínimo **30 000** reglas por extensión, con un límite acumulativo de **330 000** para todas las extensiones instaladas por un solo usuario. -For regex rules, the limit is set at **1,000 per extension**. +Para las reglas de expresiones regulares, el límite se establece en **1 000 por extensión**. -The maximum number of simultaneously enabled filters is **50**. +El número máximo de filtros habilitados simultáneamente es **50**. -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +**Reglas dinámicas:** se impone un límite estricto de **5 000** reglas, que incluye un máximo de 1 000 reglas de expresiones regulares. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> **Las reglas convertidas** son reglas que se han transformado +> a \[formato DNR] usando el [convertidor declarativo][github-declarative-converter]. +> Durante este proceso de conversión, algunas reglas pueden sobrescribir a otras (`$badfilter`), algunas pueden combinarse (`$removeparam`), +> resultando en una lista de reglas con un orden ligeramente diferente. > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> De esta lista de reglas convertidas, solo utilizaremos 5000 reglas. El resto se mostrarán en el editor, pero no se aplicarán. -Here's how a rule with a basic modifier is converted to a declarative rule: +Así es como una regla con un modificador básico se convierte en una regla declarativa: ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +se convierte a ```json [ @@ -94,14 +94,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +Puedes encontrar más ejemplos en [GitHub][github-declarative-converter-examples]. -### Network rule modifiers +### Modificadores de reglas de red -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +Los modificadores de reglas de red tienen limitaciones: algunos de ellos no se pueden implementar en MV3 o solo se pueden implementar con restricciones. -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +Puedes encontrar más detalles sobre las limitaciones en [GitHub][github-declarative-converter]. +Para más información sobre los modificadores, consulta nuestra [Base de conocimientos](/general/ad-filtering/create-own-filters). [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md index af7507b1355..b3db1ca5903 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index a7841c27ad3..e040f5d86cc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -167,91 +167,91 @@ Para configurar el trabajo en segundo plano de AdGuard en dispositivos Xiaomi, d - Selecciona **Inicio automático** -- Make sure that autostart function is enabled for AdGuard: +- Asegúrate de que la función de inicio automático esté habilitada para AdGuard: ![Xiaomi *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomiautostart.png) ## Samsung -On many Samsung devices, any app that is unused for 3 days will not be able to start from background. You should turn off **Adaptive battery** and **Put apps to sleep** options wherever possible to prevent that. Note that after an app or OS update, these settings often revert to their default values and will need to be turned off again. +En muchos dispositivos Samsung, cualquier aplicación que no se utilice durante 3 días no podrá iniciarse en segundo plano. Debes desactivar las opciones **Batería adaptable** y **Poner aplicaciones en suspensión** siempre que sea posible para evitarlo. Ten en cuenta que después de una actualización de la aplicación o del sistema operativo, estas configuraciones suelen volver a sus valores predeterminados y será necesario desactivarlas nuevamente. ### Android 11+ -On Android 11, Samsung will prevent apps (including AdGuard) from working in background by default unless you exclude them from battery optimizations. To make sure AdGuard will not get killed in the background: +En Android 11, Samsung evitará que las aplicaciones (incluido AdGuard) funcionen en segundo plano de forma predeterminada, a menos que las excluya de las optimizaciones de la batería. Para asegurarte de que AdGuard no se elimine en segundo plano: -1. Lock AdGuard in Recent +1. Bloquea AdGuard en Recientes - - Open **Recent apps**. - - Find AdGuard. - - Long-press the icon of the AdGuard app. + - Abre **Aplicaciones recientes**. + - Encuentra AdGuard. + - Mantén presionado el ícono de la aplicación AdGuard. -1. To keep AdGuard working properly: +1. Para mantener AdGuard funcionando correctamente: - Go to **Settings** → **Apps** → **AdGuard** → **Battery** → **Optimize battery usage** + Ve a **Configuración** → **Aplicaciones** → **AdGuard** → **Batería** → **Optimizar el uso de la batería** ![Samsung](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/samsung-a11-optimize.png) - In the drop-down menu, select **All**. Then find AdGuard on the list and set the state for it to **Don’t optimize** (on some models, there may be a switch that you need to toggle off). + En el menú desplegable, selecciona **Todos**. Luego, busca AdGuard en la lista y configura el estado en **No optimizar** (en algunos modelos, puede haber un interruptor que necesites desactivar). ![Samsung](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/samsung-a11-optimize-2.png) - On some devices, the relevant setting may be named differently and be located in other places. Among the possible paths is: + En algunos dispositivos, la configuración relevante puede tener un nombre diferente y estar ubicada en otros lugares. Entre los caminos posibles, está: - **Settings** → **Apps** → (⁝) menu → **Special Access** → **Optimize battery usage** → Find AdGuard on the list and uncheck it + **Configuración** → **Aplicaciones** → Menú (⁝) → **Acceso especial** → **Optimizar el uso de la batería** → Busca AdGuard en la lista y desmárcalo -1. Disable automatic optimization. Para hacerlo: +1. Desactivar la optimización automática. Para hacerlo: - Open **Battery** → (⁝) menu → Choose **Automation** → Toggle off all of the settings there + Abre **Batería** → Menú (⁝) → Elige **Automatización** → Desactiva todas las configuraciones allí - Again, the exact path may differ, for example on some devices you should go to: + Nuevamente, la ruta exacta puede variar. Por ejemplo, en algunos dispositivos debes ir a: - Phone **Settings** → **Device care** → Tap the (⁝) 3-dot menu → **Advanced** → Disable **Auto optimization** and **Optimize settings** + **Configuración del celular** → **Cuidado del dispositivo** → Toca el menú de 3 puntos (⁝) → **Avanzado** → Deshabilita **Optimización automática** y **Optimizar configuración** -1. If your phone has it, disable Adaptive battery: +1. Si tu celular lo tiene, desactiva la Batería adaptable: - Open phone **Settings** → **Battery** → **More battery settings** → Toggle off **Adaptive battery** + Abre **Ajustes** → **Batería** → **Más ajustes de batería** → Desactiva **Batería adaptativa** -1. Disable Sleeping apps (the exact name of this setting and the path to it may vary depending on the device): +1. Deshabilita las aplicaciones inactivas (el nombre exacto de esta configuración y la ruta a la misma pueden variar según el dispositivo): - Open phone **Settings** → **Battery** → **Background usage limits** → Disable **Put unused apps to sleep** + Abre **Ajustes** → **Batería** → **Límites de uso en segundo plano** → Deshabilita **Poner en reposo las aplicaciones no utilizadas** ### Android 9 & 10 -- Go to **Phone settings** → **Device care** → Tap on the **Battery** item → (⁝) **3-dot menu** → **Settings** and uncheck **Put unused apps to sleep** and **Auto-disable unused apps**. +- Ve a **Configuración** → **Cuidado del dispositivo** → Toca el elemento **Batería** → **Menú de 3 puntos (⁝)** → **Configuración** y desmarca **Poner aplicaciones no utilizadas en reposo** y **Deshabilitar automáticamente aplicaciones no utilizadas**. -- Check that **Phone settings** → **Apps** → **Sleep as Android** → **Battery** → **Background restriction** is set to **App can use battery in background** for AdGuard. +- Verifica si **Configuración** → **Aplicaciones** → **Dormir como Android** → **Batería** → **Restricción en segundo plano** está configurada como **La aplicación puede usar la batería en segundo plano** para AdGuard. -- Remove AdGuard from Sleeping apps. To do that: +- Elimina AdGuard de las aplicaciones inactivas. Para ello: - 1. Go to **Phone settings** → **Device care** + 1. Ve a **Configuración** → **Cuidado del dispositivo** ![Samsung *mobile_border](https://cdn.adtidy.org/public/Adguard/screenshots/android/samsung1en.png) - 1. Tap **Battery** + 1. Toca **Batería** ![Samsung *mobile_border](https://cdn.adtidy.org/public/Adguard/screenshots/android/samsung2en.png) - 1. Tap the **3-dot menu** → **Settings** + 1. Toca el **Menú de 3 puntos** → **Configuración** ![Samsung *mobile_border](https://cdn.adtidy.org/public/Adguard/screenshots/android/samsung3en.png) - 1. Tap **Sleeping apps** + 1. Toca **Aplicaciones inactivas** ![Samsung *mobile_border](https://cdn.adtidy.org/public/Adguard/screenshots/android/samsung45en.png) - 1. **Wake up** AdGuard using the trashcan icon + 1. **Despierta** AdGuard usando el icono de la papelera ![Samsung *mobile_border](https://cdn.adtidy.org/public/Adguard/screenshots/android/samsung6en.png) -### Old Samsung devices +### Dispositivos Samsung antiguos -For early Samsung devices, there is no huge need for setting up the background operation, but if in your case the AdGuard app is getting closed or disappears from the recent tasks after a while, do the following: +Para los primeros dispositivos Samsung, no es necesario configurar la operación en segundo plano, pero si en tu caso la aplicación AdGuard se cierra o desaparece de las tareas recientes después de un tiempo, haz lo siguiente: -- Tap the **Recent tasks** button, tap the **Additional settings** icon. Debería verse así: +- Toca el botón **Tareas recientes**, toca el ícono **Configuraciones adicionales**. Debería verse así: ![Configuración de Samsung *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/oldsamsung_1.png) -- Tap **Lock Apps**: +- Toca **Bloquear aplicaciones**: ![Configuración de Samsung *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/oldsamsung_2.png) @@ -331,51 +331,51 @@ Si AdGuard sigue cerrándose, intenta también ejecutar - **Configuración del teléfono** → **Configuración avanzada** → **Administrador de batería** → **Plan de energía** establecido en **Rendimiento**; - **Configuración del teléfono** → **Configuración avanzada** → **Administrador de batería** → **Aplicaciones protegidas** — establece AdGuard como **Protegido**; -- **Phone Settings** → **Apps** → **Your app** → **Battery** → **Power-intensive prompt** `[uncheck]` and **Keep running after screen off** `[check]`; -- **Phone settings** → **Apps** → **Advanced (At the bottom)** → **Ignore optimizations** → Press Allowed → **All apps** → Find AdGuard on the list and set to **Allow**. +- **Configuración** → **Aplicaciones** → **Tu aplicación** → **Batería** → **Aviso de consumo intensivo de energía** `[uncheck]` y **Seguir funcionando después de apagar la pantalla** `[check]`; +- **Configuración del teléfono** → **Aplicaciones** → **Avanzadas (en la parte inferior)** → **Ignorar optimizaciones** → Presiona Permitido → **Todas las aplicaciones** → Busca AdGuard en la lista y configúralo en **Permitir**. #### Huawei P9 Plus -Open device settings → **Apps** → **Settings** → **Special access** → choose **Ignore battery optimization** → select **Allow** for AdGuard. +Abre la configuración del dispositivo → **Aplicaciones** → **Configuración** → **Acceso especial** → elige **Ignorar optimización de batería** → selecciona **Permitir** para AdGuard. -### Huawei P20, Huawei Honor 9 Lite and Huawei Mate 9 Pro +### Huawei P20, Huawei Honor 9 Lite y Huawei Mate 9 Pro -Open device settings → **Battery** → **App launch** → set AdGuard to **Manage manually** and make sure everything is turned on. +Abre la configuración del dispositivo → **Batería** → **Inicio de aplicación** → configura AdGuard en **Administrar manualmente** y asegúrate de que todo esté activado. ### Huawei P20, Huawei P20 Lite, Huawei Mate 10 -**Phone settings** → **Battery** → **App launch** → set AdGuard to **Manage manually** and make sure everything is turned on. Also for reliable background processes you may need to uninstall PowerGenie as described above. +**Configuración** → **Batería** → **Inicio de la aplicación** → configura AdGuard en **Administrar manualmente** y asegúrate de que todo esté encendido. También para procesos en segundo plano confiables es posible que necesites desinstalar PowerGenie como se describe anteriormente. -### Early Huawei +### Los primeros Huawei -Old Huawei devices are the easiest to set up, it is enough to perform two simple steps to lock AdGuard in the background so it won't be terminated by battery saving or background killer process. +Los dispositivos Huawei más antiguos son los más fáciles de configurar, basta con realizar dos simples pasos para bloquear AdGuard en segundo plano para que no sea terminado por el proceso de ahorro de batería o de apagado en segundo plano. -- Tap the **Recent tasks** button: +- Toca el botón **Tareas recientes**: - ![Huawei recent apps *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/huaweirecentapps.jpeg) + ![Aplicaciones recientes de Huawei *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/huaweirecentapps.jpeg) -- Tap on the lock icon: +- Toca el icono del candado: - ![Huawei lock *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/huaweilock.jpeg) + ![Bloqueo de Huawei *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/huaweilock.jpeg) -Besides, to set up the background work of AdGuard more effectively, you should open device settings and do the following: +Además, para configurar el trabajo en segundo plano de AdGuard de manera más efectiva, debes abrir la configuración del dispositivo y hacer lo siguiente: -- Go to **Settings** → open **Battery Manager** → set **Power plan** to **Performance**; -- Then choose **Protected apps** in the **Battery Manager** and check if AdGuard is Protected; -- Go to **Apps** in the main settings and tap AdGuard there → choose **Battery** → enable **Power-intensive prompt** and **Keep running after screen is off**; -- Then in the **Apps** section open **Settings** (at the bottom) → **Special access** → choose **Ignore battery optimization** → press **Allowed** → **All apps** → find AdGuard on the list and set it to **Deny**. +- Ve a **Configuración** → abre **Administrador de batería** → establece **Plan de energía** en **Rendimiento**; +- Luego selecciona **Aplicaciones protegidas** en el **Administrador de batería** y verifica si AdGuard está protegido; +- Ve a **Aplicaciones** en los ajustes principales y toca allí AdGuard → elige **Batería** → activa **Preguntar si consume mucha energía** y **Seguir funcionando después de apagar la pantalla**; +- A continuación, en la sección **Apps** abre **Ajustes** (en la parte inferior) → **Acceso especial** → elige **Ignorar optimización de batería** → pulsa **Permitido** → **Todas las apps** → busca AdGuard en la lista y establécelo en **Denegar**. ## Meizu -Meizu has almost the same approach to the background process limitations as Huawei and Xiaomi. So you can avoid disabling the background work of AdGuard and any other app by adjusting the following settings: +Meizu tiene casi el mismo enfoque en las limitaciones del proceso en segundo plano que Huawei y Xiaomi. Para evitar deshabilitar el trabajo en segundo plano de AdGuard y cualquier otra aplicación, ajusta la siguiente configuración: -- Go to **Advanced Settings** → open **Battery Manager** → set **Power plan** to **Performance**; -- Then choose **Protected apps** in the **Battery Manager** and check if AdGuard is Protected; -- Go to **Apps** section and tap AdGuard there → choose **Battery** → enable **Power-intensive prompt** and **Keep running after screen is off**. +- Ve a **Configuración avanzada** → abre **Administrador de batería** → establece **Plan de energía** en **Rendimiento**; +- Luego seleccionA **Aplicaciones protegidas** en el **Administrador de batería** y verifica si AdGuard está protegido; +- Ve a la sección **Aplicaciones** y toca AdGuard allí → elige **Batería** → habilita **Aviso de uso intensivo de energía** y **Seguir funcionando después de que la pantalla se apague**. ## Nokia -Nokia devices running Android 9+ have **The Evenwell Power saver** disabled, which was the main culprit for killing background processes. If AdGuard still gets killed on your Nokia phone, check out the [legacy instruction](https://dontkillmyapp.com/hmd-global). +Los dispositivos Nokia con Android 9+ tienen el **Ahorrador de energía Evenwell** deshabilitado, que era el principal culpable de matar los procesos en segundo plano. Si AdGuard aún falla en tu teléfono Nokia, consulta la [instrucción antigua](https://dontkillmyapp.com/hmd-global). ### Nokia 1 (Android Go) @@ -387,13 +387,13 @@ Nokia devices running Android 9+ have **The Evenwell Power saver** disabled, whi 1. Habilita la ** depuración USB** dentro de las opciones de desarrollador en tu teléfono; -1. Uninstall the **com.evenwell.emm** package via the following ADB commands: +1. Desinstala el paquete **com.evenwell.emm** mediante los siguientes comandos ADB: `adb shell` `pm uninstall --user 0 com.evenwell.emm` -### Nokia 3.1 and 5.1 +### Nokia 3.1 y 5.1 -On these devices there is a task killer called **DuraSpeed** that terminates all background apps. It can't be uninstalled or disabled by regular means. These actions require ADB, and even then, when disabled, DuraSpeed will re-enable itself on reboot. You need a tasker app like [MacroDroid](https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid) for automatic DuraSpeed's disabling. +En estos dispositivos hay un eliminador de tareas llamado **DuraSpeed** que finaliza todas las aplicaciones en segundo plano. No se puede desinstalar ni deshabilitar por los medios habituales. Estas acciones requieren ADB, e incluso entonces, cuando está deshabilitado, DuraSpeed se volverá a habilitar al reiniciar. Necesita una aplicación de tareas como [MacroDroid](https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid) para desactivar automáticamente DuraSpeed. 1. [Instala ADB](https://www.xda-developers.com/install-adb-windows-macos-linux/) en tu computadora; @@ -403,37 +403,37 @@ On these devices there is a task killer called **DuraSpeed** that terminates all 1. Habilita la ** depuración USB** dentro de las opciones de desarrollador en tu teléfono; -1. Grant MacroDroid (or your choice of automation app) the ability to write to the global settings store by entering this command: +1. Concede a MacroDroid (o a la aplicación de automatización que elijas) la capacidad de escribir en el almacenamiento de ajustes globales introduciendo este comando: - `adb shell pm grant com.arlosoft.macrodroid android.permission.WRITE_SECURE_SETTINGS` + `adb shell pm grant com.arlosoft.macrodroid android.permiso.WRITE_SECURE_SETTINGS` -1. Create a task triggered at **Device Boot** that performs the following: +1. Crea una tarea activada en **Arranque del dispositivo** que realiza lo siguiente: - - System Setting: type **Global**, name `setting.duraspeed.enabled`, value **-1** - - System Setting: type **System**, name `setting.duraspeed.enabled`, value **-1** - - System Setting: type **Global**, name `setting.duraspeed.enabled`, value **0** - - System Setting: type **System**, name `setting.duraspeed.enabled`, value **0** + - Configuración del sistema: tipo **Global**, nombre `setting.duraspeed.enabled`, valor **-1** + - Configuración del sistema: tipo ** System**, nombre `setting.duraspeed.enabled`, valor **-1** + - Configuración del sistema: tipo **Global**, nombre `setting.duraspeed.enabled`, valor **0** + - Configuración del sistema: tipo ** System**, nombre `setting.duraspeed.enabled`, valor **0** ![Nokia tasker *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/nokia_tasker.png) :::note - You need both **Global** and **System** type settings. The screenshot shows only Global as an example. + Necesita configuraciones de tipo **Global** y **Sistema**. La captura de pantalla muestra solo Global como ejemplo. ::: -### Other Nokia models +### Otros modelos de Nokia -- Go to phone **Settings** → **Apps** → **See all apps**. +- Ve a **Configuración** → **Aplicaciones** → **Ver todas las aplicaciones**. -- Tap on the right top corner menu → **Show system**. +- Toca en el menú de la esquina superior derecha → **Mostrar sistema**. -Find **Power saver app** on the list, select it and tap **Force close**. It will remain stopped for a while but will restart at some point. +Busca la aplicación de **ahorro de energía** en la lista, selecciónela y toca **Forzar cierre**. Permanecerá detenido por un tiempo pero se reiniciará en algún momento. -From now on, AdGuard should work normally and use the standard Android battery optimizations until Power Saver restarts. +A partir de ahora, AdGuard debe funcionar normalmente y utilizar las optimizaciones de batería estándar de Android hasta que se reinicie Power Saver. -An alternative, more permanent solution for more tech-savvy users: +Una solución alternativa más permanente para los usuarios más expertos en tecnología: 1. [Instala ADB](https://www.xda-developers.com/install-adb-windows-macos-linux/) en tu computadora; @@ -443,83 +443,83 @@ An alternative, more permanent solution for more tech-savvy users: 1. Habilita la ** depuración USB** dentro de las opciones de desarrollador en tu teléfono; -1. Uninstall the **com.evenwell.powersaving.g3** package via the following ADB commands: +1. Desinstala el paquete **com.evenwell.powersaving.g3** mediante los siguientes comandos ADB: `adb shell` `pm uninstall --user 0 com.evenwell.powersaving.g3` ## Oppo -Sometimes background services are being killed (including accessibility services, which then need re-enabling) when you turn the screen off. So far, a workaround for this is: +A veces, los servicios en segundo plano se eliminan (incluidos los servicios de accesibilidad, que luego deben volver a habilitarse) cuando apagas la pantalla. Hasta ahora, una solución alternativa para esto es: -Go to **Security Centre** → tap **Privacy Permissions** → **Startup manager** and allow AdGuard app to run in background. +Ve a **Centro de seguridad** → toca **Permisos de privacidad** → **Administrador de inicio** y permite que la aplicación AdGuard se ejecute en segundo plano. -Other solutions: +Otras soluciones: -- Pin AdGuard to the recent apps screen -- Enable AdGuard in the app list inside the security app’s “startup manager” and “floating app list” (com.coloros.safecenter / com.coloros.safecenter.permission.Permission) -- Turn off battery optimizations +- Fijar AdGuard a la pantalla de aplicaciones recientes +- Habilitar AdGuard en la lista de aplicaciones dentro del “administrador de inicio” y la “lista de aplicaciones flotante” de la aplicación de seguridad (com.coloros.safecenter / com.coloros.safecenter.permission.Permission) +- Desactivar las optimizaciones de batería ## OnePlus -Devices with OxygenOS on board are the most problematic, with its OS-specific cache cleaning and free RAM, including OS optimization. In addition, OxygenOS can interrupt the AdGuard's work if you do not use it for a while. To avoid these unwanted consequences, follow these steps. +Los dispositivos con OxygenOS integrado son los más problemáticos, con su limpieza de caché específica del sistema operativo y RAM libre, incluida la optimización del sistema operativo. Además, OxygenOS puede interrumpir el trabajo de AdGuard si no lo utilizas durante un tiempo. Para evitar estas consecuencias no deseadas, sigue estos pasos. -### Locking the app +### Bloqueo de la aplicación -- Go to **Settings** +- Ve a **Configuración** -- **Battery** → **Battery optimization** +- **Batería** → **Optimización de la batería** -- Find AdGuard +- Encuentra AdGuard -- Tap on it and select **Don't optimize** option +- Pulsa sobre él y selecciona la opción **No optimizar** -- Tap **Done** to save +- Pulsa **Listo** para guardar -- Open recent apps menu (as showed on this screenshot): +- Abre el menú de aplicaciones recientes (como se muestra en esta captura de pantalla): ![Onepluslock *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/android/onepluslock.png) -- Lock AdGuard app: +- Bloquea la aplicación AdGuard: ![Oneplusdots *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/android/oneplusdots.png) :::caution -On some OnePlus phones there is also a thing called App Auto-Launch and Deep Optimization which essentially prevents apps from working in the background. Por favor, desactívalo para AdGuard. +En algunos teléfonos OnePlus también hay una cosa llamada App Auto-Launch y Deep Optimization que esencialmente impide que las aplicaciones funcionen en segundo plano. Por favor, desactívalo para AdGuard. ::: -### Battery optimization +### Optimización de la batería -- Open device settings → **Battery** → **Battery optimization** → switch to the **All apps** list (top menu) → choose AdGuard → activate **Don’t optimize** +- Abre la configuración del dispositivo → **Batería** → **Optimización de la batería** → cambia a la lista **Todas las aplicaciones** (menú superior) → elige AdGuard → activa **No optimizar** -- Open device settings → **Battery** → **Battery Optimization** → (⁝) three-dot menu → **Advanced Optimization** → Disable Deep Optimization +- Abre la configuración del dispositivo → **Batería** → **Optimización de la batería** → Menú de tres puntos (⁝) → **Optimización avanzada** → Deshabilitar optimización profunda -### App Auto-Launch +### Inicio automático de la aplicación -App Auto-Launch (on some OnePlus phones) essentially prevents apps from working in the background. Por favor, desactívalo para AdGuard. +El inicio automático de aplicaciones (en algunos teléfonos OnePlus) esencialmente evita que las aplicaciones funcionen en segundo plano. Por favor, desactívalo para AdGuard. -### Enhanced / Advanced optimization +### Optimización mejorada/avanzada -For OnePlus 6 and above: +Para OnePlus 6 y superior: -- Open **System settings** → **Battery** → **Battery optimization** → (⁝) three-dot menu → **Advanced optimization** -- Disable **Deep optimization** / **Adaptive Battery** -- Disble **Sleep standby optimization**. OnePlus tries to learn when you are usually asleep, and in those times it will then disable the phone’s network connections. This setting will prevent push notifications from being delivered. +- Abre **Ajustes del sistema** → **Batería** → **Optimización de la batería** → Menú de tres puntos (⁝) → **Optimización avanzada** +- Desactiva **Optimización profunda** / **Batería adaptable** +- Deshabilitar **Optimización del modo de suspensión**. OnePlus intenta aprender cuándo estás en modo de suspensión y, en esos momentos, desactivará las conexiones de red del teléfono. Esta configuración evitará que se envíen notificaciones push. -For OnePlus below 6: +Para OnePlus inferiores a 6: -- Turn off **System settings** → **Battery** → **Battery optimization** → (⁝) three-dot menu → **Enhanced optimization**. +- Desactiva **Configuración del sistema** → **Batería** → **Optimización de la batería** → Menú de tres puntos (⁝) → **Optimización mejorada**. -### Recent apps clearing behaviour +### Comportamiento de limpieza de aplicaciones recientes -Normally when you swipe an app away, it won’t close. On OnePlus this may however work in a different way. Recent app clear behaviour manager might be set up in a way that swiping the app to close will kill it. To return it to the “normal” mode: +Normalmente, cuando deslizas una aplicación hacia afuera, esta no se cierra. Sin embargo, en OnePlus esto puede funcionar de forma diferente. Es posible que el administrador de comportamiento de limpieza de aplicaciones recientes esté configurado de manera tal que al deslizar la aplicación para cerrarla, la cierre. Para volver al modo “normal”: -Go to **Settings** → **Advanced** → **Recent app management** → Switch to **Normal clear** +Ve a **Configuración** → **Avanzado** → **Administración de aplicaciones recientes** → Cambia a **Normal clear** ## Sony -Sony was the first mobile OS developer to introduce non-standard background process optimization. It is called **Stamina mode** and it instantly breaks all background processes if enabled. Para solucionarlo: +Sony fue el primer desarrollador de sistemas operativos móviles en introducir una optimización de procesos en segundo plano no estándar. Se llama modo **Stamina** y rompe instantáneamente todos los procesos en segundo plano si está habilitado. Para solucionarlo: Ve a **Configuración** → **Batería** → Deshabilita **Modo STAMINA** diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 88a9188efee..1c4803f70e8 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -55,6 +55,6 @@ Primero, expongamos un poco de teoría y vínculos con los datos necesarios. > 506000 *225 / (60* 60 * 1000) = 31,625 mAh -### Conclusion +### Conclusión -Real consumption is **several times less** than it is shown in Android statistics. Instead of 220mAh it should be somewhere around 31-40mAh. On the other hand, browser's consumption should be not 66mAh, but ~200mAh. +El consumo real es **varias veces menor** de lo que se muestra en las estadísticas de Android. En lugar de 220 mAh, debería rondar los 31-40 mAh. Por otro lado, el consumo del navegador no debería ser de 66 mAh, sino de ~200 mAh. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 5efcf33a393..757ba19a5e4 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -1,21 +1,21 @@ --- -title: Known compatibility issues with Android apps +title: Problemas de compatibilidad conocidos con aplicaciones de Android sidebar_position: 16 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: -## VPN apps +## Aplicaciones VPN -If you are using AdGuard in the *Local VPN* filtering mode, you cannot run other VPN apps at the same time. To solve this problem, we suggest that you: +Si estás utilizando AdGuard en el modo de filtrado *VPN local*, no podrás ejecutar otras aplicaciones VPN al mismo tiempo. Para solucionar este problema, te sugerimos: -- Use [AdGuard VPN](https://adguard-vpn.com/welcome.html) — its *Integrated mode* allows two apps to operate simultaneously -- Configure your VPN app to act as an [outbound proxy](../solving-problems/outbound-proxy.md) and set up a local outbound proxy using the parameters from the third-party app -- Switch to the *Automatic proxy* mode. When you do that, AdGuard will no longer use local VPN and will reconfigure iptables instead +- Usar [AdGuard VPN](https://adguard-vpn.com/welcome.html) — el *modo integrado* permite que dos aplicaciones funcionen simultáneamente +- Configura tu aplicación VPN para que actúe como un proxy de salida [](../solving-problems/outbound-proxy.md) y configura un proxy de salida local usando los parámetros de la aplicación de terceros +- Cambia al modo de *Proxy automático*. Cuando lo haces, AdGuard deja de utilizar la VPN local y reconfigura iptables en su lugar - Cambia al modo de *proxy manual*. Para ello, ve a *Configuración* → *Filtrado* → *Red* → *Modo de enrutamiento* :::note Compatibilidad diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 6bd1b2b5376..30bcd2f0c03 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,47 +1,47 @@ --- -title: How to generate HAR files +title: Cómo generar archivos HAR sidebar_position: 5 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: :::note -HAR files are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). +Los archivos HAR se procesan de acuerdo con la [Política de privacidad de AdGuard](https://adguard.com/en/privacy.html). ::: -## What are HAR files? +## ¿Qué son los archivos HAR? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +El formato HAR (HTTP ARchive) es un archivo de almacenamiento con formato JSON para registrar la interacción de un navegador web con un sitio. Las especificaciones del formato HAR definen datos de archivo para las transacciones HTTP que un navegador utiliza para exportar información detallada sobre las páginas web que carga. Puedes encontrar una descripción más detallada del formato de archivo HAR y su especificación en el sitio web [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). -## How to generate HAR files +## Cómo generar archivos HAR -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +A veces necesitamos analizarlo para bloquear anuncios específicos que son difíciles de reproducir por algún motivo. Para obtener archivos HAR, sigue estos pasos: -1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). -2. Tap **General** →**Advanced** → **Low-level settings**. -3. Scroll down and activate **Capture HAR** in the Filtering section. -4. Open the app and perform the necessary actions to reproduce the problem. -5. Turn **Capture HAR** off. -6. Go back to **Advanced**. -7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. +1. Abre AdGuard y ve a **Configuración** (ícono ⚙ en la esquina inferior derecha). +2. Toca **General** →**Avanzado** → **Configuración de bajo nivel**. +3. Desplázate hacia abajo y activa **Capturar HAR** en la sección Filtrado. +4. Abre la aplicación y realiza las acciones necesarias para reproducir el problema. +5. Desactive **Capturar HAR**. +6. Regresa a **Avanzado**. +7. Toca **Exportar registros e información del sistema** → **Permitir** (si es necesario) → **Guardar**. -**Send the generated file with the logs to the AdGuard support service.** +**Envía el archivo generado con los registros al servicio de soporte de AdGuard.** :::note -Our support team will process your ticket much faster if you specify the HelpDesk ticket number or the GitHub issue number in your message. +Nuestro equipo de soporte procesará tu ticket mucho más rápido si especificas el número de ticket de HelpDesk o el número de problema de GitHub en tu mensaje. ::: -## How to analyze HAR files +## Cómo analizar archivos HAR -Here are some sources that we can recommend to analyze HAR files: +Aquí hay algunas fuentes que podemos recomendar para analizar archivos HAR: -- [HTTP Archive Viewer master](https://gitgrimbo.github.io/harviewer/master/) is a HAR analyzer tool, visualizes HTTP Archive (HAR) log files created by HTTP tracking tools. -- [Fiddler](https://www.telerik.com/fiddler) is a web debugging proxy, lets you capture, inspect, monitor all HTTP(S) traffic between your computer and the Internet, mock requests, and diagnose network issues. +- [HTTP Archive Viewer master](https://gitgrimbo.github.io/harviewer/master/) es una herramienta analizadora HAR que visualiza archivos de registro HTTP Archive (HAR) creados por herramientas de seguimiento HTTP. +- [Fiddler](https://www.telerik.com/fiddler) es un proxy de depuración web que le permite capturar, inspeccionar y monitorear todo el tráfico HTTP(S) entre tu computadora e Internet, simular solicitudes y diagnosticar problemas de red. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index 5c2b5466dcf..2373825cbaf 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -1,52 +1,52 @@ --- -title: Moving the CA certificate to the system store on rooted devices +title: Trasladar el certificado de CA al almacenamiento del sistema en dispositivos rooteados sidebar_position: 14 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: -AdGuard for Android can [filter encrypted HTTPS traffic](/general/https-filtering/what-is-https-filtering), thus blocking most ads and trackers on websites. On rooted devices, AdGuard also allows you to filter HTTPS traffic in apps. HTTPS filtering requires adding AdGuard's CA certificate to the list of trusted certificates. +AdGuard para Android puede [filtrar el tráfico HTTPS cifrado](/general/https-filtering/what-is-https-filtering), bloqueando así la mayoría de los anuncios y rastreadores en los sitios web. En dispositivos rooteados, AdGuard también te permite filtrar el tráfico HTTPS en las aplicaciones. El filtrado HTTPS requiere agregar el certificado CA de AdGuard a la lista de certificados confiables. -On non-rooted devices, CA certificates can be installed to the **user store**. Only a limited subset of apps (mostly browsers) trust CA certificates installed to the user store, meaning HTTPS filtering will work only for such apps. +En dispositivos no rooteados, los certificados CA se pueden instalar en el **almacenamineto de usuario**. Solo un subconjunto limitado de aplicaciones (principalmente navegadores) confían en los certificados CA instalados en la tienda del usuario, lo que significa que el filtrado HTTPS funcionará solo para dichas aplicaciones. -On rooted devices, you can install a certificate to the **system store**. That will allow AdGuard to filer HTTPS traffic in other apps as well. +En dispositivos rooteados, puedes instalar un certificado en el **almacenamiento del sistema**. Esto permitirá que AdGuard filtre el tráfico HTTPS en otras aplicaciones también. -Here's how to do that. +Aquí te explicamos cómo hacerlo. -## How to install AdGuard's certificate to the system store +## Cómo instalar el certificado de AdGuard en el sistema -1. Open *AdGuard → Settings → Filtering → Network → HTTPS filtering → Security certificates*. +1. Abra *AdGuard → Configuración → Filtrado → Red → Filtrado HTTPS → Certificados de seguridad*. -1. If you don't have any certificate yet, **install the AdGuard Personal CA into the user store**. This will allow AdGuard to filter HTTPS traffic in browsers. +1. Si aún no tienes ningún certificado, **instala AdGuard Personal CA en el almacenamiento de usuarios**. Esto permitirá que AdGuard filtre el tráfico HTTPS en los navegadores. -1. **Install the AdGuard Intermediate CA into the user store**. You'll need it to run the adguardcert Magisk module that allows you to move certificates to the system store. +1. **Instala el CA intermedio de AdGuard en el almacenamiento de usuarios**. Lo necesitarás para ejecutar el módulo Magisk adguardcert que te permite mover certificados al almacenamiento del sistema. - ![Install the certificate *mobile_border](https://cdn.adtidy.org/blog/new/asx1xksecurity_certificates.png) + ![Instala el certificado *mobile_border](https://cdn.adtidy.org/blog/new/asx1xksecurity_certificates.png) -1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). +1. Instale la última versión del [ módulo Magisk **adguardcert**](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Abre *Magisk → Módulos → Instalar desde el almacenamiento* y selecciona el archivo **adguardcert** descargado. El certificado CA personal de AdGuard se copiará al almacén del sistema. - ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) + ![Abre los módulos Magisk *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) - ![Install from storage *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-5.png) + ![Instala desde el almacenamiento *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-5.png) - ![Select adguardcert *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-6.png) + ![Selecciona adguardcert *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-6.png) -1. Tap **Reboot**. +1. Toca **Reiniciar**. - ![Reboot the device *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-7.png) + ![Reinicia el dispositivo *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-7.png) -After the transfer, the **AdGuard Personal CA** in the system store will allow you to filter HTTPS traffic in apps, while the **AdGuard Intermediate CA** in the user store will allow you to filter HTTPS traffic in Chromium-based browsers (see below why). +Después de la transferencia, el **CA personal de AdGuard ** en el almacenamiento del sistema te permitirá filtrar el tráfico HTTPS en las aplicaciones, mientras que el **CA Intermedio de AdGuard** en la tienda del usuario te permitirá filtrar el tráfico HTTPS en los navegadores basados en Chromium (entiende por qué a continuación). -## Known issues with Chrome and Chromium-based browsers +## Problemas conocidos con Chrome y los navegadores basados en Chromium -Chrome and other Chromium-based browsers require Certificate Transparency (CT) logs for certificates located in the system store. CT logs don't contain information about certificates issued by HTTPS-filtering apps. Therefore, AdGuard requires an additional certificate in the user store to filter HTTPS traffic in these browsers. +Chrome y otros navegadores basados en Chromium requieren registros de Transparencia de certificados (CT) para los certificados ubicados en la tienda del sistema. Los registros CT no contienen información sobre los certificados emitidos por aplicaciones de filtrado HTTPS. Por lo tanto, AdGuard requiere un certificado adicional en el almacenamiento de usuarios para filtrar el tráfico HTTPS en estos navegadores. -### Bromite browser +### Navegador Bromite -In addition to the above issue, Bromite doesn't trust certificates in the user store by default. To filter HTTPS traffic there, open Bromite, go to `chrome://flags`, and set *Allow user certificates* to *Enabled*. **This applies to both rooted and non-rooted devices**. +Además del problema mencionado anteriormente, Bromite no confía en los certificados del almacenamiento de usuarios de forma predeterminada. Para filtrar el tráfico HTTPS allí, abre Bromite, ve a `chrome://flags`y configura *Permitir certificados de usuario* en *Habilitado*. **Esto se aplica tanto a dispositivos rooteados como a no rooteados**. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 0731903c504..28d5f11e4a5 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -1,38 +1,38 @@ --- -title: How to collect debug logs +title: Cómo recopilar registros de depuración sidebar_position: 2 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: :::note -Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). +Los datos y/o archivos proporcionados en los registros se procesan de acuerdo con [la Política de privacidad de AdGuard](https://adguard.com/en/privacy.html). ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +En este artículo, te guiaremos a través del proceso de recopilación de registros de depuración, un paso de solución de problemas esencial para resolver problemas complejos que puedan surgir. Los registros de depuración brindan información detallada sobre el funcionamiento interno de AdGuard para Android. Si el equipo de soporte de AdGuard te solicita que proporcione registros de depuración, simplemente sigue estas instrucciones. :::note -AdGuard se compromete a proteger tu privacidad. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. +AdGuard se compromete a proteger tu privacidad. Seguimos estrictamente nuestra [Política de Privacidad](https://adguard.com/privacy/android.html) y no recopilamos ninguna información privada sobre los usuarios. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. ::: -### Recording debug log +### Grabación del registro de depuración -To collect **debug** log and send it to us, you need to perform following steps: +Para recopilar el registro de ** depuración** y enviárnoslo, debes realizar los siguientes pasos: -1. Go to *Settings* → *General* → *Advanced*. -1. Tap *Logging level* and set it to *Debug*. -1. Reproduce the problem and try to remember the exact time it occurred. -1. Wait a while, then return to *Settings* and choose the *Support* tab. Tap *Report a bug* and complete the required fields. Don't forget to check the *Send app logs and system info* checkbox. Finally tap *Send*. +1. Ve a *Configuración* → *General* → *Avanzado*. +1. Toca *Nivel de registro* y configúralo en *Depuración*. +1. Reproduzca el problema e intenta recordar la hora exacta en que ocurrió. +1. Espera un momento, luego regresa a *Configuración* y elige la pestaña *Soporte*. Toca *Informar un error* y completa los campos obligatorios. No olvides marcar la casilla de verificación *Enviar registros de aplicaciones e información del sistema*. Finalmente, toca *Enviar*. -If you're interested in following the resolution of your issue and engaging in a dialogue with the developers, we recommend that you take the following steps after completing the first three: +Si estás interesado en seguir la resolución de tu problema y iniciar un diálogo con los desarrolladores, te recomendamos que sigas los siguientes pasos después de completar los primeros tres: -1. Wait a while, then return to the *Advanced* screen and export logs via *Export logs and system info*. Then report a bug on GitHub by following these [instructions](/guides/report-bugs.md). -1. After creating an issue on GitHub, send the log file to devteam@adguard.com. Include the time of the bug and attach a link to your issue or its number (it appears as #number next to the title). Alternatively, you can upload the log file to Google Drive and send it to devteam@adguard.com. Add the file link to your GitHub issue +1. Espera un momento, luego regresa a la pantalla *Avanzado* y exporte registros a través de *Exportar registros e información del sistema*. Luego, informa un error en GitHub siguiendo estas [instrucciones](/guides/report-bugs.md). +1. Después de crear un problema en GitHub, envía el archivo de registro a devteam@adguard.com. Incluye la hora del error y adjunta un enlace a tu issue o su número (aparece como #número junto al título). Alternativamente, puedes transferir el archivo de registro en Google Drive y enviarlo a devteam@adguard.com. Agrega el enlace del archivo a tu problema de GitHub diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index 577b6df5f05..7991da7f1c3 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -1,111 +1,111 @@ --- -title: How to get system logs +title: Cómo obtener registros del sistema sidebar_position: 4 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: :::note -Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). +Los datos y/o archivos proporcionados en los registros se procesan de acuerdo con [la Política de privacidad de AdGuard](https://adguard.com/en/privacy.html). ::: -Sometimes a regular log may not be sufficient to identify the origin of the problem. In such cases a system log is needed. Below are instructions on how to collect and get it: via Developer options and Logcat. +A veces, un registro regular puede no ser suficiente para identificar el origen del problema. En tales casos es necesario un registro del sistema. A continuación, encontrarás instrucciones sobre cómo recopilarlo y obtenerlo: a través de las opciones de desarrollador y Logcat. :::note -AdGuard se compromete a proteger tu privacidad. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. +AdGuard se compromete a proteger tu privacidad. Seguimos estrictamente nuestra [Política de Privacidad](https://adguard.com/privacy/android.html) y no recopilamos ninguna información privada sobre los usuarios. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. ::: -## Capture a bug report from a device +## Capturar un informe de bug de un dispositivo -To get a bug report directly from your device, do the following: +Para obtener un informe de bug directamente desde tu dispositivo, haz lo siguiente: -1. Be sure you have [Developer options](https://developer.android.com/studio/run/device.html#developer-device-options) enabled. +1. Asegúrate de tener las [Opciones de desarrollador](https://developer.android.com/studio/run/device.html#developer-device-options) habilitadas. -1. In **Developer options**, tap **Take bug report**. +1. En **Opciones de desarrollador**, toca **Hacer un informe de bug**. - ![Bug report *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreporten.png) + ![Informe de bug *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreporten.png) -1. Select the type of bug report you want and tap **Report**. +1. Selecciona el tipo de informe de bug que deseas y toca **Informar**. :::note - After a moment, you will see a notification that the bug report is ready (see Figure 2). + Después de un momento, verás una notificación de que el informe de bug está listo (ver Figura 2). ::: - ![Bug report *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreporteen.png) + ![Informe de bug *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreporteen.png) -1. To share the bug report, tap the notification. +1. Para compartir el informe de error, toca la notificación. - ![Bug report *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreport3en.png) + ![Informe de bug *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/Android3.1/bugreport3en.png) -1. Send this log to our support team. +1. Envía este registro a nuestro equipo de soporte. :::note - Our support team will process your ticket much faster if you specify the HelpDesk ticket number or the GitHub issue number in your message to support. + Nuestro equipo de soporte procesará tu ticket mucho más rápido si especificas el número de ticket de HelpDesk o el número de problema de GitHub en tu mensaje de soporte. ::: -## Capture a bug report via Logcat +## Captura un informe de bug a través de Logcat -On devices with Android 7 and below, it is not possible to send a bug report automatically. Then you can capture it manually via Logcat — a standard Android command-line tool that dumps a log of system messages. +En dispositivos con Android 7 y anteriores, no es posible enviar un informe de bug automáticamente. Luego puedes capturarlo manualmente a través de Logcat, una herramienta de línea de comandos estándar de Android que genera un registro de mensajes del sistema. -Follow this instruction: +Sigue estas instrucciones: -**Part #1: prepare the device** +**Parte #1: prepara el dispositivo** -1. Switch device to the developer mode. To do this: go to **Settings** → **About** → tap **Build Number** 7 times. +1. Pon el dispositivo al modo de desarrollador. Para ello: ve a **Ajustes** → **Acerca de** → toca el **Número de compilación** 7 veces. -1. Go to **Developer Options**. +1. Ve a **Opciones de desarrollador**. -1. Enable **USB debugging**. +1. Activa **la depuración USB**. -1. Increase **Logger buffer** sizes to 4 MB per log buffer. +1. Aumenta el tamaño del **Logger buffer** a 4 MB por log buffer. -4 MB should be enough for storing the logs we need until you're able to do the second part (getting the log from the device); +4 MB deberían ser suficientes para almacenar los registros que necesitamos hasta que puedas hacer la segunda parte (obtener el registro del dispositivo); -**Part #2: reproduce the problem** +**Parte #2: reproduce el problema** -It is important to reproduce the problem after you're done with the first part. +Es importante reproducir el problema después de terminar con la primera parte. 1. Reproduce el problema. -1. Remember/write down the date and time of reproduction and include it in the email to our support later. +1. Recuerda/anota la fecha y hora de reproducción e inclúyela en el correo electrónico que enviarás posteriormente a nuestro soporte. -**Part #3: get the log** +**Parte nº 3: obtén el log** -1. Connect your device to a PC with a USB cable. +1. Conecta tu dispositivo a una PC con un cable USB. -1. Download [Android SDK Platform Tools](https://developer.android.com/studio/releases/platform-tools#downloads). Choose the appropriate download link for your OS from the Downloads section. Once you tap the link, a ZIP file will be downloaded. You can extract the ADB (Android Debug Bridge) files from the ZIP file and store them wherever you want. +1. Descarga [Herramientas de la plataforma Android SDK](https://developer.android.com/studio/releases/platform-tools#downloads). Elige el enlace de descarga apropiado para tu sistema operativo en la sección Descargas. Una vez que toques el enlace, se descargará un archivo ZIP. Puedes extraer los archivos ADB (Android Debug Bridge) del archivo ZIP y almacenarlos donde quieras. -1. Test whether ADB is working properly: connect your Android device to your computer using a USB cable, open the Command Prompt, PowerShell or Terminal and run the following command: +1. Verifica si ADB funciona correctamente: conecta tu dispositivo Android a tu computadora usando un cable USB, abre el Símbolo del sistema, PowerShell o Terminal y ejecuta el siguiente comando: `adb devices` - An example of a successful result: + Un ejemplo de un resultado exitoso: - ![Step 3](https://cdn.adtidy.org/content/kb/ad_blocker/android/logcat/logcat_step-3.png) + ![Paso 3](https://cdn.adtidy.org/content/kb/ad_blocker/android/logcat/logcat_step-3.png) -1. Then run the following command (insert the relevant path): +1. Luego ejecuta el siguiente comando (introduce la ruta correspondiente): `adb logcat -v threadtime -d > C:\Program Files\platform-tools\logs.txt` - Email the created `txt` file as well as the time the problem was reproduced (from part #2) to our support team at support@adguard.com. + Envíe por correo electrónico el archivo `txt` creado, así como la hora en que se reprodujo el problema (de la parte n.° 2) a nuestro equipo de soporte a support@adguard.com. -### Alternative way for ROOT users +### Forma alternativa para usuarios ROOT -1. Download and run [Logcat](https://play.google.com/store/apps/details?id=com.pluscubed.matlog). +1. Descarga y ejecuta [Logcat](https://play.google.com/store/apps/details?id=com.pluscubed.matlog). 1. Selecciona **Grabar** en el menú. Elige un nombre para un archivo de registro o simplemente presiona **OK**. Ahora puedes presionar el botón **Inicio**, CatLog continuará grabando el registro en segundo plano. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 3a99b7e9dea..d2fcc75883b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -35,9 +35,9 @@ Aquí puedes enumerar los dominios que se reenviarán directamente a los servido #### Detectar dominios de búsqueda -If this setting is enabled, AdGuard will detect search domains and automatically forward them to fallback upstreams. +Si esta configuración está habilitada, AdGuard detectará los dominios de búsqueda y los reenviará automáticamente a los dominios fallback de subida. -#### Bootstrap upstreams +#### Bootstrap de subida DNS de arranque para servidores DoH, DoT y DoQ. El *DNS automático* (el DNS del sistema o DNS AdGuard) se utiliza de forma predeterminada. Al seleccionar *DNS personalizado*, puedes enumerar las direcciones de servidor IPv4 e IPv6 para usar como enlaces ascendentes de arranque. @@ -45,19 +45,19 @@ DNS de arranque para servidores DoH, DoT y DoQ. El *DNS automático* (el DNS del Aquí puedes especificar el tipo de respuesta para los dominios bloqueados por las reglas DNS según la sintaxis de la regla de bloqueo de publicidad (por ejemplo, `||example.org^`). -- Respond with REFUSED -- Respond with NXDOMAIN -- Respond with Custom IP address (IPv4 and IPv6 addresses can be specified here) +- Responder con REFUSED +- Responder con NXDOMAIN +- Responder con dirección IP personalizada (aquí se pueden especificar direcciones IPv4 e IPv6) #### Modo de bloqueo para reglas de hosts -Here you can specify the response type for domains blocked by DNS rules based on hosts rule syntax (for instance, ` 0.0.0.0 example.com`). +Aquí puede especificar el tipo de respuesta para los dominios bloqueados por las reglas DNS según la sintaxis de la regla de hosts (por ejemplo, ` 0.0.0.0 example.com`). -- Respond with REFUSED -- Respond with NXDOMAIN -- Respond with Custom IP address (IPv4 and IPv6 addresses can be specified here) +- Responder con REFUSED +- Responder con NXDOMAIN +- Responder con dirección IP personalizada (aquí se pueden especificar direcciones IPv4 e IPv6) -#### DNS request timeout +#### Tiempo de espera de petición de DNS Aquí puedes especificar el tiempo en milisegundos que AdGuard esperará la respuesta del servidor DNS seleccionado antes de recurrir al fallback. Si no completas este campo o ingresas un valor no válido, se utilizará el valor de 5000. @@ -65,67 +65,67 @@ Aquí puedes especificar el tiempo en milisegundos que AdGuard esperará la resp Aquí puedes especificar el valor TTL (tiempo de vida) que se devolverá en respuesta a una solicitud bloqueada. -#### DNS cache size +#### Tamaño de caché de DNS -Here you can specify the maximum number of cached responses. Default value is 1000. +Aquí puedes especificar el número máximo de respuestas almacenadas en caché. El valor predeterminado es 1000. -#### ECH blocking +#### Bloqueo ECH -If enabled, AdGuard strips Encrypted Client Hello parameters from DNS responses. +Si está habilitado, AdGuard elimina los parámetros Encrypted Client Hello de las respuestas DNS. -#### Ignore unavailable outbound proxy +#### Ignorar proxy de salida no disponible -If this setting is enabled, AdGuard will send DNS requests directly when the outbound proxy is unavailable. +Si esta configuración está habilitada, AdGuard enviará solicitudes de DNS directamente cuando el proxy saliente no esté disponible. -#### Try HTTP/3 for DNS-over-HTTPS upstreams +#### Probar HTTP/3 para upstreams de DNS-over-HTTPS -If this setting is enabled, AdGuard will use HTTP/3 to speed up DNS query resolution for DoH upstreams. Otherwise, AdGuard will revert to its default behavior and use HTTP/2 to send all DNS requests for DNS-over-HTTPS. +Si esta configuración está habilitada, AdGuard utilizará HTTP/3 para acelerar la resolución de consultas DNS para los enlaces ascendentes de DoH. De lo contrario, AdGuard volverá a su comportamiento predeterminado y utilizará HTTP/2 para enviar todas las solicitudes de DNS para DNS sobre HTTPS. -#### SERVFAIL failure response +#### Respuesta a fallos de SERVFAIL -If this setting is enabled and all upstreams, including fallback ones, fail to respond, AdGuard will send a SERVFAIL response to the client. +Si esta configuración está habilitada y todos los upstreams, incluidos los de respaldo, no responden, AdGuard enviará una respuesta SERVFAIL al cliente. -#### Use fallback for non-fallback domains +#### Usar fallback para dominios que no son de fallback -If this setting is enabled, AdGuard will use fallback upstreams for all domains. Otherwise, fallback upstreams will only be used for fallback domains and search domains if the corresponding option is enabled. +Si esta configuración está habilitada, AdGuard utilizará rutas ascendentes de respaldo para todos los dominios. De lo contrario, los upstreams de respaldo solo se utilizarán para dominios de respaldo y dominios de búsqueda si la opción correspondiente está habilitada. -#### Validate DNS upstreams +#### Validar upstreams DNS -If this setting is enabled, AdGuard will test DNS upstreams before adding or updating custom DNS servers. +Si esta configuración está habilitada, AdGuard probará los servidores DNS ascendentes antes de agregar o actualizar servidores DNS personalizados. -#### Filter secure DNS +#### Filtrar DNS seguro -If this setting is on, AdGuard will apply all enabled DNS filters and DNS user rules to encrypted DNS-over-HTTPS (DoH) traffic and not only to plain DNS. DoH traffic mostly comes from Chrome and other browsers that have a *Secure DNS* (or similar) setting. You can use *Filter secure DNS* in two different modes: +Si esta configuración está activada, AdGuard aplicará todos los filtros DNS habilitados y las reglas de usuario DNS al tráfico DNS sobre HTTPS (DoH) cifrado y no solo al DNS simple. El tráfico de DoH proviene principalmente de Chrome y otros navegadores que tienen una configuración *DNS seguro* (o similar). Puedes usar *Filtro DNS seguro* en dos modos diferentes: -- **Filter on the fly**. In this mode, AdGuard applies all enabled DNS filters and DNS user rules to DoH traffic but doesn’t redirect it to the local DNS proxy. If a DNS server is specified in the browser’s settings, this server will handle the DoH traffic for this browser +- **Filtrar en tiempo real**. En este modo, AdGuard aplica todos los filtros DNS habilitados y las reglas de usuario DNS al tráfico DoH, pero no lo redirecciona al proxy DNS local. Si se especifica un servidor DNS en la configuración del navegador, este servidor manejará el tráfico DoH para este navegador -- **Redirect to DNS proxy**. In this mode, AdGuard applies all enabled DNS filters and DNS user rules to DoH traffic by redirecting it to the local DNS proxy. The DNS server specified in the AdGuard’s DNS settings will handle all DoH traffic +- **Redirigir al proxy DNS**. En este modo, AdGuard aplica todos los filtros DNS habilitados y las reglas de usuario DNS al tráfico DoH redirigiéndolo al proxy DNS local. El servidor DNS especificado en la configuración de DNS de AdGuard manejará todo el tráfico DoH -### Filtering +### Filtrado -#### Capture HAR +#### Capturar HAR -If this setting is enabled, AdGuard will capture HAR files. It will create a directory named “har” inside the app cache directory and add there information about all filtered HTTP requests in HAR 1.2 format that can be analyzed with the Fiddler program. +Si esta configuración está habilitada, AdGuard capturará archivos HAR. Creará un directorio llamado “har” dentro del directorio de caché de la aplicación y agregará allí información sobre todas las solicitudes HTTP filtradas en formato HAR 1.2 que se pueden analizar con el programa Fiddler. -Use it only for debugging purposes! +¡Úsalo sólo para fines de depuración! ### Filtrado HTTPS #### Encrypted Client Hello -Toda conexión a Internet cifrada tiene una parte no cifrada. Este es el primer paquete que contiene el nombre del servidor al que te estás conectando. La tecnología Encrypted Client Hello resuelve este problema y cifra la última parte de la información no cifrada. To benefit from it, enable the *Encrypted Client Hello* option. Utiliza un proxy DNS local para buscar la configuración de ECH para el dominio. If it is found, Client Hello packet will be encrypted. +Toda conexión a Internet cifrada tiene una parte no cifrada. Este es el primer paquete que contiene el nombre del servidor al que te estás conectando. La tecnología Encrypted Client Hello resuelve este problema y cifra la última parte de la información no cifrada. Para beneficiarte de ello, habilita la opción *Encrypted Client Hello*. Utiliza un proxy DNS local para buscar la configuración de ECH para el dominio. Si se encuentra, se cifrará el paquete Client Hello. -#### OCSP checking +#### Verificación de OCSP -If this setting is enabled, AdGuard will perform asynchronous OCSP checks to get the revocation status of a website's SSL certificate. +Si esta configuración está habilitada, AdGuard realizará comprobaciones OCSP asincrónicas para obtener el estado de revocación del certificado SSL de un sitio web. -If an OCSP check is completed within the required timeout, AdGuard will immediately block the connection if the certificate is revoked or establish the connection if the certificate is valid. +Si se completa una verificación OCSP dentro del tiempo de espera requerido, AdGuard bloqueará inmediatamente la conexión si se revoca el certificado o establecerá la conexión si el certificado es válido. -If the verification takes too long, AdGuard will allow the connection while continuing to check the certificate status in the background. Si se revoca el certificado, se bloquearán las conexiones actuales y futuras al dominio. +Si la verificación tarda demasiado tiempo, AdGuard permitirá la conexión mientras continúa verificando el estado del certificado en segundo plano. Si se revoca el certificado, se bloquearán las conexiones actuales y futuras al dominio. -#### Redirect DNS-over-HTTPS requests +#### Redirigir solicitudes de DNS-over-HTTPS -If this setting is enabled, AdGuard will redirect DNS-over-HTTPS requests to the local DNS proxy in addition to plain DNS requests. We recommend disabling fallback upstreams and using only encrypted DNS servers to maintain privacy. +Si esta configuración está habilitada, AdGuard redirigirá las solicitudes de DNS-over-HTTPS al proxy DNS local, además de las solicitudes de DNS simples. Recomendamos deshabilitar los servidores ascendentes de respaldo y utilizar solo servidores DNS encriptados para mantener la privacidad. #### Filtrar HTTP/3 @@ -153,78 +153,78 @@ Si esta configuración está habilitada, se activará la depuración en scriptle #### Aplicaciones excluidas -Here you can list package names and UIDs that you want to exclude from AdGuard protection. +Aquí puedes enumerar los nombres de los paquetes y los UID que deseas excluir de la protección de AdGuard. -#### QUIC bypass packages +#### Paquetes de derivación QUIC -Here you can specify package names for which AdGuard should bypass QUIC traffic. +Aquí puedes especificar los nombres de los paquetes para los cuales AdGuard debe omitir el tráfico QUIC. -#### Reconfigure Automatic proxy when network changes +#### Reconfiguración automática del proxy cuando cambia la red -If this setting is enabled, the AdGuard protection will restart to reconfigure the automatic proxy settings when your device connects to another network. This setting only applies if *Routing mode* is set to *Automatic proxy*. +Si esta configuración está habilitada, la protección AdGuard se reiniciará para reconfigurar la configuración automática del proxy cuando tu dispositivo se conecte a otra red. Esta configuración solo se aplica si el *Modo de enrutamiento* está configurado en *Proxy automático*. -#### IPv6 filtering +#### Filtrado IPv6 -If this setting is enabled, AdGuard will filter IPv6 networks if an IPv6 network interface is available. +Si esta configuración está habilitada, AdGuard filtrará las redes IPv6 si hay una interfaz de red IPv6 disponible. -#### IPv4 ranges excluded from filtering +#### Intervalos de IPv4 excluidos del filtrado -Filtering for the IPv4 ranges listed in this section is disabled. +El filtrado para los intervalos de IPv4 enumerados en esta sección está deshabilitado. -#### IPv6 ranges excluded from filtering +#### Intervalos de IPv6 excluidos del filtrado -Filtering for the IPv6 ranges listed in this section is disabled. +El filtrado para los intervalos de IPv6 enumerados en esta sección está deshabilitado. -#### TCP keepalive for outgoing sockets +#### TCP keepalive para sockets salientes -If this setting is enabled, AdGuard will send a keepalive probe after the specified time period to ensure that the TCP connection is alive. Here, you can specify the idle time before starting keepalive probes and the time between keepalive probes for an unresponsive peer. +Si esta configuración está habilitada, AdGuard enviará una sonda de mantenimiento después del período de tiempo especificado para garantizar que la conexión TCP esté activa. Aquí puedes especificar el tiempo de inactividad antes de iniciar las sondas keepalive y el tiempo entre sondas keepalive para un peer que no responde. -After a system-defined number of unsuccessful attempts to get a response from the server, the system automatically closes the TCP connection. +Después de un número definido por el sistema de intentos fallidos de obtener una respuesta del servidor, el sistema cierra automáticamente la conexión TCP. -### Local VPN settings +### Configuración de VPN local -#### Recovery delay for revoked VPN +#### Retraso de recuperación para VPN revocada -Here you can set the time of a delay in milliseconds before AdGuard tries to restore VPN protection after it has been revoked by a third-party VPN app or by deleting the VPN profile. The default value is 5000 ms. +Aquí puedes establecer el tiempo de retraso en milisegundos antes de que AdGuard intente restaurar la protección VPN después de que haya sido revocada por una aplicación VPN de terceros o eliminando el perfil VPN. El valor predeterminado es 5000 ms. -#### Reschedule delay for revoked VPN recovery +#### Reprogramar el retraso para la recuperación de VPN revocada -Here you can set the time of a delay in milliseconds before AdGuard reschedules the restoration of VPN protection after it has been revoked by a third-party VPN app or by deleting the VPN profile. The default value is 5000 ms. +Aquí puedes establecer el tiempo de retraso en milisegundos antes de que AdGuard reprograme la restauración de la protección VPN después de que haya sido revocada por una aplicación VPN de terceros o al eliminar el perfil VPN. El valor predeterminado es 5000 ms. #### MTU -Here you can set the maximum transmission unit (MTU) of the VPN interface. The recommended range is 1500-1900 bytes. +Aquí puedes configurar la unidad de transmisión máxima (MTU) de la interfaz VPN. El intervalo recomendado es de 1500 a 1900 bytes. -#### Restore VPN automatically +#### Restaurar VPN automáticamente -If this setting is enabled, AdGuard’s local VPN will be automatically re-enabled after being turned off due to network absence, tethering, or low-power mode. +Si esta configuración está habilitada, la VPN local de AdGuard se volverá a habilitar automáticamente después de apagarse debido a ausencia de red, conexión compartida o modo de bajo consumo. -#### Packet capture (PCAP) +#### Captura de paquetes (PCAP) -If this setting is enabled, AdGuard will create a file `timestamp.pcap` (for instance, 1682599851461.pcap) in the app cache directory. This file lists all network packets transferred through the VPN and can be analyzed with the Wireshark program. +Si esta configuración está habilitada, AdGuard creará un archivo `timestamp.pcap` (por ejemplo, 1682599851461.pcap) en el directorio de caché de la aplicación. Este archivo enumera todos los paquetes de red transferidos a través de la VPN y puede analizarse con el programa Wireshark. -#### Include Wi-Fi gateway in VPN routes +#### Incluir puerta de enlace Wi-Fi en rutas VPN -If this setting is enabled, the gateway IP addresses will be added to VPN routes when on Wi-Fi. +Si esta configuración está habilitada, las direcciones IP de la puerta de enlace se agregarán a las rutas VPN cuando esté en Wi-Fi. -#### IPv4 address +#### Dirección IPv4 -Here you can enter the IP address that will be used to create a TUN interface. By default, it is `172.18.11.218`. +Aquí puedes ingresar la dirección IP que se utilizará para crear una interfaz TUN. De forma predeterminada, es `172.18.11.218`. -#### Forcibly route LAN IPv4 +#### Enrutar a la fuerza LAN IPv4 -If this setting is enabled, AdGuard will filter all LAN connections, including local IPv4 network traffic, even if the *Route all LAN IPv4 connections* option is enabled. +Si esta configuración está habilitada, AdGuard filtrará todas las conexiones LAN, incluido el tráfico de red IPv4 local, incluso si la opción *Enrutar todas las conexiones IPv4 LAN* está habilitada. -#### Route all LAN IPv4 connections +#### Enrutar todas las conexiones LAN IPv4 -If this setting is enabled, AdGuard will exclude LAN connections from filtering for simple networks. This may not work for complex networks. This setting only applies if *Forcibly route LAN IPv4* is disabled. +Si esta configuración está habilitada, AdGuard excluirá las conexiones LAN del filtrado para redes simples. Es posible que esto no funcione para redes complejas. Esta configuración solo se aplica si la opción *Enrutar forzosamente LAN IPv4* está deshabilitada. -#### IPv6 address +#### Dirección IPv6 -Here you can enter the IP address that will be used to create a TUN interface. By default, it is `2001:db8:ad:0:ff::`. +Aquí puedes ingresar la dirección IP que se utilizará para crear una interfaz TUN. De forma predeterminada, es `2001:db8:ad:0:ff::`. ### Misceláneo -#### Detect Samsung Pay +#### Detectar Samsung Pay -If this setting is enabled, AdGuard protection will be paused while Samsung Pay is in use. Korean users require this feature as they experience [issues with Samsung Pay](/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea) when AdGuard is enabled. +Si esta configuración está habilitada, la protección de AdGuard se pausará mientras Samsung Pay esté en uso. Los usuarios coreanos requieren esta función porque experimentan [problemas con Samsung Pay](/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea) cuando AdGuard está habilitado. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index bc552d9ff07..8ad647c83ca 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -1,46 +1,46 @@ --- -title: Certificate installation on devices with Android 11+ +title: Instalación de certificados en dispositivos con Android 11+ sidebar_position: 12 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +Para poder filtrar [el tráfico HTTPS](/general/https-filtering/what-is-https-filtering.md) (lo cual es extremadamente importante ya que la mayoría de los anuncios usan HTTPS), AdGuard necesita instalar su certificado en el almacenamiento de usuario de tu dispositivo. En versiones anteriores del sistema operativo Android, esto se hacía automáticamente, pero en Android 11 y versiones posteriores los usuarios deben instalarlo manualmente. -![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) +![Certificado *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Sigue estos pasos para instalar el certificado AdGuard: -1. When you see the *HTTPS filtering is off* notification, tap *Enable*. +1. Cuando veas la notificación *El filtrado HTTPS está desactivado*, toca *Habilitar*. -1. Then you'll be presented with three screens that explain: - - Why filter HTTPS traffic - - The safety of this filtering process - - The necessity of the AdGuard certificate +1. A continuación, aparecerán tres pantallas explicativas: + - ¿Por qué filtrar el tráfico HTTPS? + - La seguridad de este proceso de filtrado + - La necesidad del certificado AdGuard - Consecutively tap *Next* → *Next* → *Save certificate*. + Pulsa consecutivamente *Siguiente* → *Siguiente* → *Guardar certificado*. -1. Tap *Save* at the bottom of the opened *Download* folder. +1. Toca *Guardar* en la parte inferior de la carpeta *Descargar* abierta. -1. After saving, tap *Open Settings*. +1. Después de guardar, toca *Abrir Configuración*. -1. Tap *More security settings* → *Encryption & credentials* → *Install a certificate* → *CA certificate*. +1. Toca *Más configuraciones de seguridad* → *Cifrado & credenciales* → *Instalar un certificado* → *Certificado CA*. -1. You might see a warning. If so, tap *Install anyway* and enter your PIN if necessary. +1. Es posible que veas una advertencia. Si es así, toca *Instalar de todos modos* e ingresa tu PIN si es necesario. -1. Select the AdGuard certificate file. Its name should look like *adguard_1342_020322.crt*. +1. Selecciona el archivo de certificado AdGuard. Su nombre debería verse así: *adguard_1342_020322.crt*. -You're all set! Once the certificate is installed successfully, you've enabled HTTPS filtering. +¡Ya está todo listo! Una vez que el certificado se haya instalado correctamente, habrás habilitado el filtrado HTTPS. -Please note that the steps provided are based on the Google Pixel 7 smartphone. If you're using a different Android device, the exact menu names or options might vary. For easier navigation consider searching for a certificate by entering “certificate” or “credentials” in the settings search bar. +Ten en cuenta que los pasos proporcionados se basan en el teléfono inteligente Google Pixel 7. Si está utilizando un dispositivo Android diferente, los nombres o las opciones exactas del menú pueden variar. Para facilitar la navegación, busca un certificado introduciendo "certificado" o "credenciales" en la barra de búsqueda de la configuración. -If you experience issues during the manual certificate installation (for example, you installed the certificate, but the application keeps ignoring it), you can follow one of the solutions below. +Si tienes problemas durante la instalación manual del certificado (por ejemplo, ha instalado el certificado, pero la aplicación sigue ignorándolo), puedes seguir una de las soluciones que se indican a continuación. -1. Restart AdGuard. -2. Try to install the correct certificate (AdGuard Personal CA) one more time. +1. Reinicia AdGuard. +2. Intenta instalar el certificado correcto (AdGuard Personal CA) una vez más. -If you still encounter a problem and can't install the certificate, please contact our support team at support@adguard.com. +Si aún tienes algún problema y no puedes instalar el certificado, comunícate con nuestro equipo de soporte en support@adguard.com. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md index bdda4918b97..3a25d9d5039 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md @@ -21,9 +21,9 @@ Para solucionar este problema, debes desinstalar la aplicación para todos los u ![Desinstalar *mobile border](https://cdn.adtidy.org/blog/new/tu49hmultiple_users.png) -## Problems caused by using a Restricted Mode profile +## Problemas causados por el uso de un perfil en modo restringido -The owners of phones, tablets, or TVs running the Android 7+ operating system might face the problem caused by using **a profile with Restricted Mode**. Si tienes un perfil de este tipo, **AdGuard**, al igual que otras aplicaciones que utilizan VPN, obtiene restricciones en el filtrado selectivo del tráfico VPN. Como resultado, AdGuard no puede iniciar la protección en un **modo VPN local**. Además, una de las razones de esta situación puede ser el uso del **Perfil Dual App/Dual Messenger** en tu dispositivo. A continuación, se describen las recomendaciones que puedes aplicar cuando se presenta este problema. +Los propietarios de teléfonos, tabletas o televisores con el sistema operativo Android 7+ pueden enfrentar el problema causado por el uso de **un perfil con modo restringido**. Si tienes un perfil de este tipo, **AdGuard**, al igual que otras aplicaciones que utilizan VPN, obtiene restricciones en el filtrado selectivo del tráfico VPN. Como resultado, AdGuard no puede iniciar la protección en un **modo VPN local**. Además, una de las razones de esta situación puede ser el uso del **Perfil Dual App/Dual Messenger** en tu dispositivo. A continuación, se describen las recomendaciones que puedes aplicar cuando se presenta este problema. ### Soluciones diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 3c3b5ee7e1f..3c45b199740 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -1,160 +1,160 @@ --- -title: How to set up outbound proxy +title: Cómo configurar un proxy saliente sidebar_position: 8 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +A continuación se muestra una lista de las aplicaciones más conocidas que se pueden configurar para funcionar como proxies en AdGuard. :::note -If your app is not listed below, please check on its proxy configurations in the settings or contact its support team. +Si tu aplicación no aparece en la lista a continuación, verifica tus configuraciones de proxy en la configuración o comunícate con tu equipo de soporte. ::: -AdGuard allows you to route your device's traffic through a proxy server. To access proxy settings, open **Settings** and then proceed to **Filtering** → **Network** → **Proxy**. +AdGuard te permite enrutar el tráfico de tu dispositivo a través de un servidor proxy. Para acceder a la configuración del proxy, abre **Configuración** y luego proceda a **Filtrado** → **Red** → **Proxy**. -## Proxy configuration examples +## Ejemplos de configuración de proxy -In this article we give examples of how to set up some of the most popular proxies to work with AdGuard. +En este artículo, damos ejemplos de cómo configurar algunos de los proxies más populares para que funcionen con AdGuard. -### How to use AdGuard with Tor +### Cómo utilizar AdGuard con Tor -1. Open AdGuard and go to **Settings** → **Filtering** → **Network** → **Proxy**. Download “Orbot: Proxy with Tor” directly from [Google Play](https://play.google.com/store/apps/details?id=org.torproject.android&noprocess) or by tapping **Integrate with Tor** and then **Install**. +1. Abre AdGuard y ve a **Configuración** → **Filtrado** → **Red** → **Proxy**. Descarga “Orbot: Proxy con Tor” directamente desde [Google Play](https://play.google.com/store/apps/details?id=org.torproject.android&noprocess) o tocando **Integrar con Tor** y luego **Instalar**. -1. Open Orbot and press the **Start** button on the application's main screen. +1. Abre Orbot y presiona el botón **Iniciar** en la pantalla principal de la aplicación. -1. Go back to the **Proxy** screen of AdGuard. +1. Regrese a la pantalla **Proxy** de AdGuard. -1. Tap the **Integrate with Tor** button. +1. Toca el botón **Integrar con Tor**. -1. All the required fields will be pre-filled: +1. Todos los campos obligatorios se rellenarán previamente: - | Field | Value | - | ---------- | -------------------- | - | Proxy type | *SOCKS4* or *SOCKS5* | - | Proxy host | *127.0.0.1* | - | Proxy port | *9050* | + | Campo | Valor | + | ---------------- | ------------------- | + | Tipo de proxy | *SOCKS4* o *SOCKS5* | + | Host del proxy | *127.0.0.1* | + | Puerto del proxy | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + O puedes tocar **Servidor proxy** → **Agregar servidor proxy**, ingresar estos valores manualmente y configurar Orbot como el proxy predeterminado. -1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. +1. Habilita el conmutador Proxy principal y la protección AdGuard para enrutar el tráfico de tu dispositivo a través del proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Ahora AdGuard enrutará todo el tráfico a través de Orbot. Si desactivas Orbot, la conexión a Internet no estará disponible hasta que desactives la configuración del proxy saliente en AdGuard. -### How to use AdGuard with PIA (Private Internet Access) +### Cómo utilizar AdGuard con PIA (Private Internet Access) -*Here we presume that you are already a PIA VPN client and have it installed on your device.* +*Aquí asumimos que ya eres un cliente de PIA VPN y lo tienes instalado en tu dispositivo.* -1. Open AdGuard and go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server**. +1. Abre AdGuard y ve a **Configuración** → **Filtrado** → **Red** → **Proxy** → **Servidor proxy**. -1. Tap the **Add proxy server** button and enter the following data: +1. Pulsa el botón **Agregar servidor proxy** e ingresa los siguientes datos: - | Field | Value | - | ---------- | ------------------------------------ | - | Proxy type | *SOCKS5* | - | Proxy host | *proxy-nl.privateinternetaccess.com* | - | Proxy port | *1080* | + | Campo | Valor | + | ---------------- | ------------------------------------ | + | Tipo de proxy | *SOCKS5* | + | Host del proxy | *proxy-nl.privateinternetaccess.com* | + | Puerto del proxy | *1080* | -1. You also need to fill out the **Username/Password** fields. To do so, log in to the [Client Control Panel](https://www.privateinternetaccess.com/pages/client-sign-in) on the PIA website. Tap the **Generate Password** button under the **Generate PPTP/L2TP/SOCKS Password** section. A username starting with “x” and a random password will be shown. Use them to fill out the **Proxy username** and **Proxy password** fields in AdGuard. +1. También debes completar los campos **Nombre de usuario/Contraseña**. Para ello, inicia sesión en el [Panel de Control del Cliente](https://www.privateinternetaccess.com/pages/client-sign-in) en el sitio web de PIA. Toca el botón **Generar contraseña** debajo de la sección **Generar contraseña PPTP/L2TP/SOCKS**. Se mostrará un nombre de usuario que comienza con “x” y una contraseña aleatoria. Úsalos para completar los campos **Nombre de usuario de proxy** y **Contraseña de proxy** en AdGuard. -1. Tap **Save and select**. +1. Toca **Guardar y seleccionar**. -1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. +1. Habilita el conmutador Proxy principal y la protección AdGuard para enrutar el tráfico de tu dispositivo a través del proxy. -### How to use AdGuard with TorGuard +### Cómo utilizar AdGuard con TorGuard -*Here we presume that you are already a TorGuard client and have it installed on your device.* +*Aquí asumimos que ya eres un cliente de TorGuard y lo tienes instalado en tu dispositivo.* -1. Open AdGuard and go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server**. +1. Abre AdGuard y ve a **Configuración** → **Filtrado** → **Red** → **Proxy** → **Servidor proxy**. -1. Tap the **Add proxy server** button and enter the following data: +1. Pulsa el botón **Agregar servidor proxy** e ingresa los siguientes datos: - | Field | Value | - | ---------- | ------------------------------------------- | - | Proxy type | *SOCKS5* | - | Proxy host | *proxy.torguard.org* or *proxy.torguard.io* | - | Proxy port | *1080* or *1085* or *1090* | + | Campo | Valor | + | ---------------- | ------------------------------------------ | + | Tipo de proxy | *SOCKS5* | + | Host del proxy | *proxy.torguard.org* o *proxy.torguard.io* | + | Puerto del proxy | *1080* o *1085* o *1090* | -1. For **Username** and **Password** fields, enter your proxy username and proxy password you have chosen at TorGuard signup. +1. Para los campos **Nombre de usuario** y **Contraseña**, ingresa el nombre de usuario y la contraseña de proxy que hayas elegido al registrarte en TorGuard. -1. Tap **Save and select**. +1. Toca **Guardar y seleccionar**. -1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. +1. Habilita el conmutador Proxy principal y la protección AdGuard para enrutar el tráfico de tu dispositivo a través del proxy. -### How to use AdGuard with NordVPN +### Cómo utilizar AdGuard con NordVPN -1. Log in to your NordVPN account. +1. Inicia sesión en tu cuenta de NordVPN. -1. Go to **Services** → **NordVPN** → **Manual setup** and set up your service credentials manually. +1. Ve a **Servicios** → **NordVPN** → **Configuración manual** y configura tus credenciales de servicio manualmente. -1. You will receive a verification code on the email address you use for NordVPN. Use it on your NordVPN account as requested, then tap *Apply* and *OK* to save the changes. +1. Recibirás un código de verificación en la dirección de correo electrónico que utilices para NordVPN. Úsalo en tu cuenta de NordVPN según lo solicitado, luego toca *Aplicar* y *Aceptar* para guardar los cambios. -![Manual setup](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/outbound-proxy/nordvpn-manual-setup.png) +![Configuración manual](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/outbound-proxy/nordvpn-manual-setup.png) -1. Open the AdGuard app, go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server** → **Add proxy server**. +1. Abre la aplicación AdGuard, ve a **Configuración** → **Filtrado** → **Red** → **Proxy** → **Servidor proxy** → **Agregar servidor proxy**. -1. Enter the following data: +1. Introduce los siguientes datos: - | Field | Value | - | ---------- | ----------------------------------------------------------------------------------------------------------------------------- | - | Proxy type | *SOCKS5* | - | Proxy host | Any server from [this list](https://support.nordvpn.com/hc/en-us/articles/20195967385745-NordVPN-proxy-setup-for-qBittorrent) | - | Proxy port | *1080* | + | Campo | Valor | + | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------ | + | Tipo de proxy | *SOCKS5* | + | Host del proxy | Cualquier servidor de [esta lista](https://support.nordvpn.com/hc/en-us/articles/20195967385745-NordVPN-proxy-setup-for-qBittorrent) | + | Puerto del proxy | *1080* | -1. Enter your NordVPN credentials in the **Username** and **Password** fields. +1. Ingresa tus credenciales de NordVPN en los campos **Nombre de usuario** y **Contraseña**. -1. Tap **Save and select**. +1. Toca **Guardar y seleccionar**. -1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. +1. Habilita el conmutador Proxy principal y la protección AdGuard para enrutar el tráfico de tu dispositivo a través del proxy. -### How to use AdGuard with Shadowsocks +### Cómo utilizar AdGuard con Shadowsocks -*Here we presume that you have already configured a Shadowsocks server and a client on your device.* +*Aquí asumimos que ya has configurado un servidor Shadowsocks y un cliente en tu dispositivo.* :::note -You should remove Shadowsocks app from filtering before setting up the process (**App management** → **Shadowsocks** → **Route traffic through AdGuard**) to avoid infinite loops and drops. +Debes eliminar la aplicación Shadowsocks del filtrado antes de configurar el proceso (**Administración de aplicaciones** →**Shadowsocks** → **Enrutar tráfico a través de AdGuard**) para evitar bucles y caídas infinitas. ::: -1. Open AdGuard and go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server**. +1. Abre AdGuard y ve a **Configuración** → **Filtrado** → **Red** → **Proxy** → **Servidor proxy**. -1. Tap the **Add proxy server** and fill in the fields: +1. Toca **Agregar servidor proxy** y completa los campos: - | Field | Value | - | ---------- | ----------- | - | Proxy type | *SOCKS5* | - | Proxy host | *127.0.0.1* | - | Proxy port | *1080* | + | Campo | Valor | + | ---------------- | ----------- | + | Tipo de proxy | *SOCKS5* | + | Host del proxy | *127.0.0.1* | + | Puerto del proxy | *1080* | -1. Tap **Save and select**. +1. Toca **Guardar y seleccionar**. -1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. +1. Habilita el conmutador Proxy principal y la protección AdGuard para enrutar el tráfico de tu dispositivo a través del proxy. -### How to use AdGuard with Clash +### Cómo utilizar AdGuard con Clash -*Here we presume that you are already a Clash client and have it installed on your device.* +*Aquí asumimos que ya eres un cliente de Clash y lo tienes instalado en tu dispositivo.* -1. Open Clash and go to **Settings** → **Network** → **Route System Traffic** and toggle the switch. This will set Clash to proxy mode. +1. Abre Clash y ve a **Configuración** → **Red** → **Tráfico del sistema de ruta** y actívalo. Esto establecerá Clash en modo proxy. -1. Open AdGuard and go to **App management**. Choose **Clash For Android** and disable **Route traffic through AdGuard**. This will eliminate traffic looping. +1. Abre AdGuard y ve a **Administración de aplicaciones**. Elige **Clash para Android** y desactiva **Enrutar tráfico a través de AdGuard**. Esto eliminará los loopings de tráfico. -1. Then go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server**. +1. Luego ve a **Configuración** → **Filtrado** → **Red** → **Proxy** → **Servidor proxy**. -1. Tap **Add proxy server** and fill in the fields: +1. Toca **Agregar servidor proxy** y completa los campos: - | Field | Value | - | ---------- | ----------- | - | Proxy type | *SOCKS5* | - | Proxy host | *127.0.0.1* | - | Proxy port | *7891* | + | Campo | Valor | + | ---------------- | ----------- | + | Tipo de proxy | *SOCKS5* | + | Host del proxy | *127.0.0.1* | + | Puerto del proxy | *7891* | -## Limitations +## Limitaciones -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**. +Sin embargo, al menos un factor puede impedir que cierto tráfico se enrute a través del proxy saliente, incluso después de configurar los ajustes del proxy AdGuard. Esto sería si la aplicación en sí no está configurada para enviar tu tráfico a través de AdGuard. Para ello, debes ir a **Gestión de aplicaciones**, elegir la aplicación y activar **Enrutar tráfico a través de AdGuard**. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md index c0fc571a997..04c46a4536f 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md @@ -35,4 +35,4 @@ Después de habilitar esta función, cuando cambie de Samsung Pay a AdGuard, apa ![samsungpay *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/samsungpay-with-adguard-in-south-korea/samsung_pay.png) -Alternatively, you can disable filtering for Samsung Pay in *App management*. Simply go to the *App management* screen (third tab from the bottom), find Samsung Pay in the list, and turn off the switch at *Route traffic through AdGuard*. +Alternativamente, puedes desactivar el filtrado para Samsung Pay en *Administración de aplicaciones*. Simplemente ve a la pantalla *Administración de aplicaciones* (tercera pestaña desde abajo), busca Samsung Pay en la lista y desactiva *Dirigir el tráfico a través de AdGuard*. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md index cbf78e22929..3ef35fd0f3e 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md @@ -1,19 +1,19 @@ --- -title: Certificate installation in a Secure folder +title: Instalación del certificado en una carpeta segura sidebar_position: 13 --- :::info -Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: -If you install AdGuard to [the *Secure folder* on your Android](https://www.samsung.com/uk/support/mobile-devices/what-is-the-secure-folder-and-how-do-i-use-it/) (this applies mainly to Samsung devices), you may face some difficulties when installing the HTTPS certificate. The thing is, the *Secure folder* has its own space where the certificates are stored. However, if you do everything according to the regular certificate installation instructions ([described here](/adguard-for-android/features/settings#https-filtering)), the certificate will be installed into the main memory and will play no role for your ad blocker in the *Secure folder*. To solve this problem and install the certificate for your AdGuard for Android into the *Secure folder's* storage, please follow these instructions instead: +Si instalas AdGuard en [la *carpeta segura* en tu Android](https://www.samsung.com/uk/support/mobile-devices/what-is-the-secure-folder-and-how-do-i-use-it/) (esto se aplica principalmente a los dispositivos Samsung), puedes enfrentar algunas dificultades al instalar el certificado HTTPS. El problema es que la *carpeta segura* tiene su propio espacio donde se almacenan los certificados. Sin embargo, si hace todo de acuerdo con las instrucciones de instalación del certificado normal ([descritas aquí](/adguard-for-android/features/settings#https-filtering)), el certificado se instalará en la memoria principal y no tendrá ningún papel para tu bloqueador de anuncios en la *Carpeta segura*. Para resolver este problema e instalar el certificado de tu AdGuard para Android en el almacenamiento de la *carpeta segura*, sigue estas instrucciones: -1. After installing the app and connecting the local VPN, tap **ENABLE** next to the *HTTPS filtering is off* message. -1. Tap **Next** → **Next** → **Save it now** → **Save certificate**. -1. Save the certificate (at this stage, you can rename it to make it easier to locate it later, which you will need to do). +1. Después de instalar la aplicación y conectar la VPN local, toca **HABILITAR** junto al mensaje *El filtrado HTTPS está desactivado*. +1. Toca **Siguiente** → **Siguiente** → **Guardar ahora** → **Guardar certificado**. +1. Guarda el certificado (en esta etapa, puedes cambiarle el nombre para que sea más fácil localizarlo más adelante). 1. Después de que aparezca la ventana emergente *Instrucciones de instalación*, **NO** toca **Abrir Configuración**. 1. Minimiza la aplicación y ve a la *carpeta segura*. 1. Toca el menú de tres puntos y ve a **Configuración** →**Otras configuraciones de seguridad**. @@ -21,4 +21,4 @@ If you install AdGuard to [the *Secure folder* on your Android](https://www.sams 1. Confirma la instalación con tu clave gráfica/contraseña/huella digital. 1. Busca y selecciona el certificado previamente guardado, luego toca **Listo**. 1. Regresa a la aplicación AdGuard y vuelve a la pantalla principal. Es posible que tengas que deslizar y reiniciar la aplicación para deshacerte del mensaje *El filtrado HTTPS está desactivado*. -1. ¡Listo! The certificate has been installed. +1. ¡Listo! El certificado ha sido instalado. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index c3ad4dbe9de..1cb8dec51dc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -1,5 +1,5 @@ --- -title: How to automate AdGuard for Android +title: Cómo automatizar AdGuard para Android sidebar_position: 3 --- @@ -65,85 +65,85 @@ La lista completa de nombres de proveedores admitidos se puede encontrar en nues `server:custom` cambia al servidor previamente añadido llamado `custom`; - `servidor:tls://dns.adguard.com` crea un nuevo servidor y cambia a él si los servidores y proveedores agregados anteriormente no contienen un servidor con la misma dirección. De lo contrario, cambia al servidor correspondiente. You can add server addresses as IP ( regular DNS), `sdns://…` (DNSCrypt or DNS-over-HTTPS), `https://…` (DNS-over-HTTPS) or `tls://...` (DNS-over-TLS); + `servidor:tls://dns.adguard.com` crea un nuevo servidor y cambia a él si los servidores y proveedores agregados anteriormente no contienen un servidor con la misma dirección. De lo contrario, cambia al servidor correspondiente. Puedes agregar direcciones de servidor como IP (DNS normal), `sdns://…` (DNSCrypt o DNS-over-HTTPS), `https://…` (DNS-over-HTTPS) o `tls://...` (DNS-over-TLS); - `server:1.1.1.1, tls://1.1.1.1` creates a server with comma separated addresses and switches to it. When adding a server via `server:1.1.1.1, tls://1.1.1.1`, the previously added server is removed. + `server:1.1.1.1, tls://1.1.1.1` crea un servidor con direcciones separadas por comas y conmuta a él. Al agregar un servidor a través de `server:1.1.1.1, tls://1.1.1.1`, se elimina el servidor agregado anteriormente. - `server:system` resets DNS settings to default system DNS servers. + `servidor:sistema` restablece la configuración de DNS a los servidores DNS del sistema predeterminados. ----- -`proxy_state` enables/disables the outbound proxy. Requiere una bandera extra: +`proxy_state` habilita/deshabilita el proxy saliente. Requiere una bandera extra: -`enable:true` or `enable:false` activates or deactivates the outbound proxy, accordingly. +`enable:true` o `enable:false` activa o desactiva el proxy saliente, según corresponda. ----- -`proxy_default` sets the proxy from the list of previously added ones as default or creates a new one if server has not been added before. +`proxy_default` establece el proxy de la lista de los agregados previamente como predeterminado o crea uno nuevo si no se ha agregado ningún servidor antes. -You need to specify additional data: +Es necesario especificar datos adicionales: -`server:[name]` where `[name]` is the name of the outbound proxy from the list. +`server:[name]` donde `[nombre]` es el nombre del proxy saliente de la lista. -Or you can configure server parameters manually: +O puedes configurar los parámetros del servidor manualmente: `server:[type=…&host=…&port=…&username=…&password=…&udp=…&trust=…]`. -`proxy_remove` removes the proxy server from the list of previously added ones. +`proxy_remove` elimina el servidor proxy de la lista de los agregados previamente. -`server:[name]` where `[name]` is the name of the outbound proxy from the list. +`server:[name]` donde `[name]` es el nombre del proxy saliente de la lista. -Or you can configure remove parameters manually: +También puedes configurar manualmente los parámetros de eliminación: `server:[type=…&host=…&port=…&username=…&password=…&udp=…&trust=…]`. -- **Compulsory parameters**: +- **Parámetros obligatorios**: -`[type]` — proxy server type: +`[type]` — tipo de servidor proxy: - HTTP - SOCKS4 - SOCKS5 - HTTPS_CONNECT -`[host]` — outbound proxy domain or IP address; +`[host]` — dominio proxy saliente o dirección IP; -`[port]` — outbound proxy port (integer number from 1 to 65535); +`[port]` — puerto proxy de salida (número entero de 1 a 65535); -- **Optional parameters**: +- **Parámetros opcionales**: - `[login and password]` — only if proxy requires it. This data is ignored when setting up **SOCKS4**; + `[login and password]` — solo si el proxy lo requiere. Estos datos se ignoran al configurar **SOCKS4**; - `[udp]` applied only on **SOCKS5** server type and include option **UDP through SOCKS5**. It is necessary to set **true or false** value; + `[udp]` se aplica solo en el tipo de servidor **SOCKS5** e incluye la opción **UDP a través de SOCKS5**. Es necesario establecer el valor **true o false**; - `[trust]` applies for **HTTPS_CONNECT** server type only and include option **Trust any certificates**. It is necessary to set **true or false** value. + `[trust]` se aplica solo al tipo de servidor **HTTPS_CONNECT** e incluye la opción **Confiar en cualquier certificado**. Es necesario establecer el valor **true o false**. -:::note Example +:::note Ejemplo -`setting by name`: server:MyServer +`configuración por nombre`: servidor:MyServer `manually settings`: server:host=1.2.3.4&port=80&type=SOCKS5&username=foo&password=bar&udp=true ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**No olvides incluir la contraseña, el nombre del paquete y la clase. Debes hacer lo mismo para cada intención.** -Extra: `password:*******` +Extra: `contraseña:*******` -Package name: `com.adguard.android` +Nombre del paquete: `com.adguard.android` -Class: `com.adguard.android.receiver.AutomationReceiver` +Clase: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Antes de la v4.0 la clase se llamaba `com.adguard.android.receivers.AutomationReceiver` pero luego cambiamos su nombre a `com.adguard.android.receiver.AutomationReceiver`. Si se utiliza esta función, recuerda actualizar al nuevo nombre. ::: -### Execution without notification +### Ejecución sin notificación -To perform a task without showing a toast, add an additional EXTRA `quiet: true` +Para realizar una tarea sin mostrar un mensaje, agrega un EXTRA adicional `quiet: true` -### Example +### Ejemplo -![Automation *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/tasker/automation2.png) +![Automatización *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/tasker/automation2.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index fefbc8ca9a0..78090021a4e 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -Este artículo trata sobre AdGuard para Windows, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel de sistema. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Este artículo trata sobre AdGuard para Windows, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel de sistema. Para ver cómo funciona, [descarga la aplicación AdGuard](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index c0f0abb79ea..916a686784a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + se convierte a ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2987,7 +2986,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl - `example.com,example.org###adblock` — hides an element with attribute `id` equals `adblock` at `example.com`, `example.org` and all subdomains. - `~example.com##.textad` — hides an element with the class `textad` at all domains, except `example.com` and its subdomains. -**Limitations** +**Limitaciones** Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. @@ -3078,7 +3077,7 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr ### Extended CSS selectors {#extended-css-selectors} -- [Limitations](#extended-css-limitations) +- [Limitaciones](#extended-css-limitations) - [Pseudo-class `:has()`](#extended-css-has) - [Pseudo-class `:contains()`](#extended-css-contains) - [Pseudo-class `:matches-css()`](#extended-css-matches-css) @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4766,6 +4765,7 @@ The following scriptlets also may be used for debug purposes: [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" +[ext-mv3]: #what-product "Extensión de navegador AdGuard para Chrome MV3" [ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..868f8f8b49e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -1,76 +1,76 @@ --- -title: AdGuard Browser Extension for Chrome MV3 +title: Extension AdGuard pour Chrome MV3 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +À mesure que les extensions MV2 sont supprimées du Chrome Web Store, les utilisateurs de Chrome devront peut-être passer à des extensions MV3 compatibles avec la nouvelle API Manifest V3 de Chrome. Nos réflexions sur ce sujet sont largement discutées sur [notre blog](https://adguard.com/fr/blog/tag/manifest-v3.html). -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +Notre extension MV3 bloque efficacement les publicités et les traqueurs tout en gérant de manière transparente les widgets sociaux, les bannières et les publicités vidéo. La plupart des utilisateurs ne remarqueront aucune différence opérationnelle, mais il existe certaines limitations et modifications dont il faut être conscient. -## Where to find our extensions +## Où trouver nos extensions -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +La **version MV3** a remplacé notre ancienne extension dans le [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +La **version bêta de MV3** sera toujours disponible dans le [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +L'ancienne extension bêta sera renommée [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) et sera prise en charge jusqu'à ce que Google la supprime. -## Main changes in features and settings +## Principales modifications des fonctionnalités et des paramètres -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **Pas de mises à jour automatiques et manuelles des filtres.** Les options _Mise à jour automatique des filtres_ et _Vérifier la mise à jour des filtres_ ne sont plus disponibles dans l'onglet _Filtres_. Étant donné que certaines règles sont désormais appliquées sous forme de DNR, nous ne pouvons pas mettre à jour les filtres sur demande, uniquement via le processus complet de mise à jour de l'extension ainsi que l'examen dans les magasins. -- **Filtering log** +- **Journal de filtrage** - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) + ![Journal de filtrage \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + À cause des restrictions imposées par le DNR, nous ne pouvons pas indiquer exactement quelle règle a fonctionné, mais nous fournirons une "règle présumée qui a été déclenchée" sur la base de notre moteur. Pour obtenir des informations précises, vous devrez installer vous-même la version "décompressée" de l'extension dans votre navigateur. Vous trouverez des instructions détaillées sur la manière de procéder dans un [article séparé] (/adguard-browser-extension/solving-problems/debug-rules/). -- _Tracking protection_ (formerly known as _Stealth mode_) +- _Protection contre le suivi_ (anciennement connu sous le nom de _Mode furtif_) - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) + ![Protection contre le suivi \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + Il n'y a pas de section _Cookies_, ainsi que d'_Autodestruction des cookies propriétaires_ et d'_Autodestruction des cookies tiers_ puisque nous ne pouvons pas définir le TTL des cookies à l'aide de règles déclaratives. -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- _La protection contre l’hameçonnage et les logiciels malveillants_ n’est plus disponible dans les paramètres généraux. Pour vous protéger des sites web malveillants et des escroqueries, activez les filtres de _Sécurité_ appropriés dans l'onglet _Filtres_. - ![Security \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) + ![Sécurité \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) ## Limitations -### Maximum number of rules and filters +### Nombre maximal de règles et de filtres -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +Manifest V3 impose des limites aux règles statiques et regex par extension. Les utilisateurs peuvent recevoir des notifications lorsque ces limites sont dépassées. -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) +![Limites des règles \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) +![Trop d'extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +Fondamentalement, Manifest V3 divise les règles en règles statiques (intégrées) et dynamiques, avec des limites strictes en place. -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +Les **Règles statiques :** minimum **30 000** règles par extension, avec une limite cumulée de **330 000** pour toutes les extensions installées par un seul utilisateur. -For regex rules, the limit is set at **1,000 per extension**. +Pour les règles regex, la limite est fixée à **1 000 par extension**. -The maximum number of simultaneously enabled filters is **50**. +Le nombre maximum de filtres activés simultanément est de **50**. -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +Les **Règles dynamiques :** un plafond strict de **5 000** règles est imposé, ce qui inclut un maximum de 1 000 règles d'expression régulière. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> **Les règles converties** sont des règles qui ont été transformées +> au \[format DNR] à l'aide du [convertisseur déclaratif][github-declarative-converter]. +> Au cours de ce processus de conversion, certaines règles peuvent écraser d'autres (`$badfilter`), certaines peuvent être combinées (`$removeparam`), +> résultant en une liste de règles avec un ordre légèrement différent. > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> À partir de cette liste de règles converties, nous n'utiliserons que 5 000 règles. Le reste d’entre eux sera affiché dans l’éditeur, mais pas appliqué. -Here's how a rule with a basic modifier is converted to a declarative rule: +Voici comment une règle avec un modificateur de base est convertie en règle déclarative : ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +est convertie en ```json [ @@ -94,14 +94,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +D'autres exemples peuvent être trouvés sur [GitHub][github-declarative-converter-examples]. -### Network rule modifiers +### Modificateurs de règles de réseau -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +Les modificateurs de règles de réseau ont des limites : certains d'entre eux ne peuvent pas être implémentés dans MV3, ou ne peuvent être implémentés qu'avec des restrictions. -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +Vous trouverez plus de détails sur les limitations sur [GitHub][github-declarative-converter]. +Pour plus d'informations sur les modificateurs, veuillez vous référer à notre [Base de connaissances](/general/ad-filtering/create-own-filters). [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md index 23251b3d6cb..97c028bd185 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md @@ -1,98 +1,98 @@ --- -title: How to debug rules in AdGuard for Chrome MV3 +title: Comment déboguer les règles dans AdGuard pour Chrome MV3 sidebar_position: 2 --- -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. +Dans [AdGuard pour Chrome MV3](/adguard-browser-extension/mv3-version), le journal de filtrage ne montre que les règles approximatives qui ont été appliquées, que nous appelons "règles supposées". Cela est dû au fait que le navigateur ne fournit pas de détails sur les règles déclaratives spécifiques utilisées, à moins que l'extension ne soit dans un format "décompressé". Pour obtenir des informations précises, vous devrez installer vous-même la version décompressée de l'extension dans votre navigateur. -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. +Ces instructions sont également destinées aux cas problématiques où vous souhaitez modifier de manière statique les règles fournies avec l'extension. Dans la plupart des cas, l’utilisation de _règles utilisateur_ dans l’extension devrait être suffisante. -## Prerequisites +## Prérequis -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) +1. **Git :** [Installer Git](https://git-scm.com/book/fr/v2/Mise-en-place-de-l-installation-de-Git) -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) +2. **Node :** [Installer Node.js](https://nodejs.org/en/download/package-manager) -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) +3. **Yarn :** [Installer Yarn](https://classic.yarnpkg.com/lang/en/docs/install) -## How to clone extension +## Comment cloner une extension -1. Clone the repository: +1. Clonez le dépôt : ```bash git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git ``` -2. Navigate to the directory: +2. Accédez au répertoire : ```bash cd AdguardBrowserExtension ``` -3. Switch to the `v5.0` branch: +3. Passez à la branche 'v5.0' : ```bash git checkout v5.0 ``` -4. Install dependencies: +4. Installez les dépendances : ```bash yarn install ``` -## How to build extension +## Comment construire une extension -1. Switch to the `v5.0` branch: +1. Passez à la branche 'v5.0' : ```bash git checkout v5.0 ``` -2. Run the following command in the terminal: +2. Exécutez la commande suivante dans le terminal : ```bash yarn dev chrome-mv3 ``` -3. The built extension will be located in the directory: +3. L'extension construite sera située dans le répertoire : ```bash ./build/dev/chrome-mv3 ``` -## How to install unpacked in the browser +## Comment installer le décompressé dans le navigateur -1. Turn on developer mode: +1. Activez le mode développeur : - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) + ![Mode développeur](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) -2. Click _Load unpacked_: +2. Cliquez sur _Charger décompressé_ : - ![Load unpacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) + ![Charger décompressé](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) -3. Select the extension directory and click `Select`: +3. Sélectionnez le répertoire de l’extension et cliquez sur 'Sélectionner' : - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) + ![Sélectionner](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) -That’s it! +Voilà ! -## How to debug rules +## Comment déboguer les règles -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. +1. Recherchez et modifiez la règle dont vous avez besoin dans le répertoire `./Extension/filters/chromium-mv3` dans les fichiers `.txt`. -2. Convert the rules from txt to declarative form: +2. Convertissez les règles du format txt au format déclaratif : ```bash yarn convert-declarative ``` -3. Build the extension again: +3. Construisez à nouveau l'extension : ```bash yarn dev chrome-mv3 ``` -4. Reload the extension in the browser: +4. Rechargez l’extension dans le navigateur : - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) + ![Recharger l'extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md index a7485f7661a..94d3789f896 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md @@ -1,5 +1,5 @@ --- -title: Free vs. full version +title: Version gratuite vs version complète sidebar_position: 9 --- @@ -11,22 +11,22 @@ Cet article parle de AdGuard pour iOS, un bloqueur de contenus multifonctionnel :::note -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. +AdGuard pour iOS avec Premium activé et AdGuard Pro bloquent les publicités sur les smartphones et tablettes Apple. Auparavant, leurs fonctionnalités se différenciaient à cause de certaines modifications apportées aux politiques d’examen de l’App Store dans le passé, mais maintenant AdGuard avec un abonnement acheté et AdGuard Pro sont identiques dans leurs fonctionnalités. ::: -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. +AdGuard Premium pour iOS présente plusieurs différences par rapport à la version gratuite, notamment des paramètres DNS personnalisés. Grâce à ces paramètres, vous pouvez bloquer les publicités non seulement dans Safari mais également dans d'autres applications, protéger vos enfants du contenu réservé aux adultes en ligne et protéger vos informations personnelles contre le vol. Il y a aussi d’autres différences. Examinons-les en détail. -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. +1. Le module **Protection DNS** crypte votre trafic DNS pour renforcer la confidentialité. Il fonctionne sur toutes les applications et tous les navigateurs, pas seulement Safari, offrant une large protection contre les publicités et les traqueurs. - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. + - **Serveurs DNS personnalisés :** choisissez un des serveurs DNS populaires dans notre liste ou ajoutez votre propre serveur personnalisé. - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. + - **Protection famille :** Internet n’est pas toujours adapté aux enfants. Avec AdGuard Premium, vous pouvez passer à des fournisseurs DNS qui bloquent le contenu pour adultes et autres contenus inappropriés pour assurer la sécurité de vos enfants en ligne. - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. + - **Surveillance et configuration flexible :** le journal d'activité récent vous permet d'afficher toutes les requêtes DNS envoyées par votre appareil et de gérer facilement votre trafic en ajoutant des sites web à la liste de blocage ou à la liste d'autorisation d'un simple clic. -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. +2. **La protection avancée** vous permet d'utiliser des règles de filtrage avancées pour bloquer les publicités plus complexes qui ne seraient pas bloquées autrement. -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. +3. **Plus d'options de filtrage :** lors de l'achat d'AdGuard Premium, vous avez accès à des filtres personnalisés et à une catégorie de filtres de sécurité, où vous pouvez choisir parmi plus de 50 filtres, y compris ceux d'AdGuard et d'autres listes populaires. -Access these features by [purchasing a license](https://adguard.com/license.html). +Accédez à ces fonctionnalités en [achetant une licence](https://adguard.com/license.html). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..b9445190960 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -1,54 +1,54 @@ --- -title: Documentation for admins +title: Documentation pour les administrateurs sidebar_position: 5 --- -This page describes the features and details of AdGuard’s central management of policies and preferences. +Cette page décrit les caractéristiques et les détails de la gestion centrale des politiques et des préférences d'AdGuard. -## 1. Download the MSI {#msi-download} +## 1. Téléchargez le MSI {#msi-download} -Download the [AdGuard MSI x86](https://cdn.adtidy.org/distr/windows/AdGuard_x86.msi) +Téléchargez le [MSI AdGuard x86](https://cdn.adtidy.org/distr/windows/AdGuard_x86.msi) -Download the [AdGuard MSI x64](https://cdn.adtidy.org/distr/windows/AdGuard_x64.msi) +Téléchargez le [AdGuard MSI x64](https://cdn.adtidy.org/distr/windows/AdGuard_x64.msi) -## 2. Configure the settings for your network {#settings-configuring} +## 2. Configurez les paramètres de votre réseau {#settings-configuring} -On machines that are joined to an Active Directory domain, policy settings may also be stored in the registry under `HKEY_LOCAL_MACHINE` in the following path: `Software\Policies\AdGuard\`. +Sur les ordinateurs qui sont joints à un domaine Active Directory, les paramètres de stratégie peuvent également être stockés dans le registre sous `HKEY_LOCAL_MACHINE` dans le chemin suivant : 'Software\Policies\AdGuard\'. -The only supported policy is `LicenseKey`. If this policy is set, AdGuard will prefer it over what user can enter in the interface. This license key will be used for checking license status. +La seule politique prise en charge est `LicenseKey`. Si cette politique est définie, AdGuard la privilégiera par rapport à ce que l'utilisateur peut saisir dans l'interface. Cette clef de licence sera utilisée pour vérifier l'état de la licence. -## 3. Make sure that AdGuard servers are available {#servers-available} +## 3. Assurez-vous que les serveurs AdGuard sont disponibles {#servers-available} -AdGuard connects to two hosts: `api.adguard.org` and `filters.adtidy.org`. Make sure that both servers are available. +AdGuard se connecte à deux hôtes : `api.adguard.org` et `filters.adtidy.org`. Assurez-vous que les deux serveurs sont disponibles. -## 4. Push the MSI out to your network {#msi-push} +## 4. Envoyez le MSI vers votre réseau {#msi-push} -If you usually use SMS or other tools, use them to push out the AdGuard MSI just as you would normally do with any other installation bundle. +Si vous utilisez habituellement des SMS ou d'autres outils, utilisez-les pour envoyer le MSI AdGuard comme vous le feriez normalement avec n'importe quel autre paquet d'installation. -Otherwise, you can run the MSI on the target machine directly (and silently) with this command: `Msiexec /q /i AdGuard.msi` +Sinon, vous pouvez exécuter le MSI directement (et silencieusement) sur la machine cible avec cette commande : `Msiexec /q /i AdGuard.msi` -If you need to roll out an update, use this command: `Msiexec /q /i AdGuard.msi REINSTALL=ALL REINSTALLMODE=vomus` +Si vous devez déployer une mise à jour, utilisez cette commande : `Msiexec /q /i AdGuard.msi REINSTALL=ALL REINSTALLMODE=vomus` -:::note +::note -You must run these commands with admin privileges. +Vous devez exécuter ces commandes avec des privilèges d'administration. ::: -If you want to install AdGuard on a Windows 7 computer, make sure that it has .NET 4 Client Profile installed: https://www.microsoft.com/en-us/download/details.aspx?id=24872 +Si vous souhaitez installer AdGuard sur un ordinateur Windows 7, assurez-vous qu'il dispose du profil client .NET 4 installé : https://www.microsoft.com/en-us/download/details.aspx?id=24872 :::note -If you have installed AdGuard for Windows from an MSI file, AdGuard will not be updated automatically. To allow manual updates: +Si vous avez installé AdGuard pour Windows à partir d'un fichier MSI, AdGuard ne sera pas mis à jour automatiquement. Pour autoriser les mises à jour manuelles : -- In versions released after v7.16, delete the `ForbidCheckUpdates` parameter or set its value to `NO` (case-insensitive) in the registry under `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard`. +- Dans les versions publiées après v7.16, supprimez le paramètre `ForbidCheckUpdates` ou définissez sa valeur sur `NON` (insensible à la casse) dans le registre sous `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard`. -- In v7.16 and earlier versions, set to `YES` (case-insensitive) the `AllowCheckUpdates` parameter for the `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard` key on x86 OS or `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adguard` key on x64 OS. Any other value or no value for this parameter will disable automatic updates. +- Dans les versions v7.16 et antérieures, définissez sur `OUI` (insensible à la casse) le paramètre `AllowCheckUpdates` pour la clé `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard` sur les systèmes d'exploitation x86 ou la clé `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adguard` sur les systèmes d'exploitation x64. Toute autre valeur ou aucune valeur pour ce paramètre désactivera les mises à jour automatiques. -Please note that such installation of the application and manual updates are not recommended and can cause technical problems. +Veuillez noter que cette installation de l'application et les mises à jour manuelles ne sont pas recommandées et peuvent entraîner des problèmes techniques. ::: -## 5. Test your installation {#installation-test} +## 5. Testez votre installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +Sur une machine cible, lancez AdGuard. Ouvrez l'écran de licence pour vérifier qu'il utilise la licence spécifiée. Vous devrez peut-être cliquer sur "Actualiser le statut" pour faire en sorte qu'AdGuard valide la clef de licence. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b3a901651a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -1,45 +1,45 @@ --- -title: Browser Assistant +title: Assistant de navigateur sidebar_position: 3 --- -AdGuard Assistant’s primary function is to manage filtering directly from the browser. It has existed for quite a long time, and its form and content have changed. More precisely, it used to be a mere userscript incorporated into AdGuard for Windows app and became a full-fledged browser extension. Now it yields more benefits. +La fonction principale de l'Assistant AdGuard est de gérer le filtrage directement depuis le navigateur. Il existe depuis assez longtemps, et sa forme et son contenu ont évolué. Plus précisément, il s’agissait auparavant d’un simple script utilisateur intégré à l’application AdGuard pour Windows qui est ensuite devenu une extension complète de navigateur. Maintenant, il offre plus d’avantages. -![Browser Assistant *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/assistant-menu.png) +![Assistant de navigateur *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/assistant-menu.png) -## Benefits +## Avantages -### Independence +### Indépendance -AdGuard Browser Assistant is a browser extension, it is installed in a browser, so there is no need to wait for the userscript to be injected into the filtered web page, as it was with the preceding one. In other words, it is more autonomous from the main AdGuard app. Still, Browser Assistant needs the installed AdGuard for Windows, because there is no point in using the extension without the app. +L'Assistant de navigateur AdGuard est une extension de navigateur, qui est installée dans le navigateur, il ne faut donc pas attendre que le script utilisateur soit injecté dans la page web filtrée, comme c'était le cas avec sa version précédente. En autres termes, il est plus autonome par rapport à l'application AdGuard principale. Néanmoins, l'Assistant de navigateur a besoin qu'AdGuard pour Windows soit installé, car il n'y a aucun intérêt à utiliser l'extension sans l'application. -### Compatibility with the main app +### Compatibilité avec l'application principale -If you got into the habit of using our previous [AdGuard Ad Blocker extension](/adguard-browser-extension/compatibility), you might like the solution that we have developed for the new Browser Assistant. +Si vous avez pris l'habitude d'utiliser notre extension [AdGuard Ad Blocker](/adguard-browser-extension/compatibility) précédente, vous aimerez peut-être la solution que nous avons développée pour le nouvel assistant de navigateur. -Background information: +Informations de base : -In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. +Dans les anciennes versions de l'Extension de navigation AdGuard (avant la v3.5), si vous l'aviez installée avec l'application AdGuard pour Windows, l'extension assumait les fonctions d'Assistant, arrêtait de filtrer les annonces elle-même et s'en remettait à l'application pour le faire. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +L’extension et l’application fonctionnaient en conjonction, mais parfois l’intégration échouait. La protection fournie normalement par le programme de bureau s'arrêtait sur certains sites, où seule l'extension moins puissante fournissait alors une protection. -When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. +Lors de l'utilisation de l'Assistant de navigateur, tous ces problèmes n'ont pas d'importance car il ne peut pas y avoir de conflits en essence. Le rôle de l'Assistant de navigateur est bien défini et il ne peut pas entraver le fonctionnement de l'application principale, donc il n'y a pas besoin de s'inquiéter. -## Separate tab in Settings +## Un onglet séparé dans les paramètres -The new Browser Assistant has its own tab in AdGuard for Windows settings, along with Stealth Mode, Browsing security, Parental Control and others. There you will find a link to download the extension for your default browser. Besides, there is a checkbox to enable the legacy Assistant. +Le nouvel Assistant de navigateur a son propre onglet dans les paramètres d'AdGuard pour Windows, accompagné du Mode furtif, de la Navigation sécurisée, du Contrôle parental et d'autres. Là, vous trouverez un lien pour télécharger l'extension pour votre navigateur par défaut. De plus, il y a une case à cocher pour activer l'Ancien assistant. -![Settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) +![Paramètres *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) -## Legacy Assistant +## Ancien Assistant -Legacy Assistant is the previous version of Assistant, which is a mere userscript, not a browser extension. Basically, there are two cases when you might want to pick it instead of the new Browser Assistant: +L'ancien assistant est la version précédente de l'Assistant, qui n'est qu'un simple script utilisateur, pas une extension de navigateur. En gros, il y a deux cas où vous pourriez vouloir le choisir au lieu du nouvel Assistant de navigateur : -1. The new Assistant is not available for your browser. -1. You are used to the green shield icon and want to leave things as they were. +1. Le nouvel Assistant n'est pas disponible pour votre navigateur. +1. Vous êtes habitué à l'icône du bouclier vert et souhaitez laisser les choses telles qu'elles étaient. -## How to install AdGuard Browser Assistant +## Comment installer l'Assistant de navigateur AdGuard -If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. +Si vous souhaitez installer l'Assistant de navigateur pour votre navigateur par défaut, vous pouvez le faire directement à partir des paramètres de l'application, mais vous avez également la possibilité de l'installer pour d'autres navigateurs. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +L'Assistant de navigateur AdGuard est disponible pour tous les navigateurs populaires : Chrome, Firefox, Edge, Opera et Yandex. Pour installer celui dont vous avez besoin (ou plusieurs, ce n'est pas interdit mais même encouragé), allez sur [notre site web](https://adguard.com/adguard-assistant/overview.html), cliquez sur l'icône du navigateur et ensuite sur le bouton *Installer*. Voilà ! diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index f5357746b5d..7bd955178a4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ L'Assistant AdGuard est un ancien assistant que vous pouvez utiliser si le [nouv C'est une extension personnalisée conçue pour lutter contre la technique de réinsertion des publicités bloquées — ce qu'on appelle le contournement des bloqueurs de publicités/réinjection de publicités. Les deux sont des méthodes anti-bloqueur de publicité avancées qui continuent de gagner en popularité parmi les annonceurs. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra est essentiellement un miniprogramme qui modifie le fonctionnement des pages de telle sorte qu'il devient beaucoup plus difficile pour les sites d'utiliser les méthodes susmentionnées pour contourner les bloqueurs. **Bloqueur AdGuard de fenêtres pop-up** -Cette extension empêche l'ouverture de fenêtres pop-up lorsque vous consultez des pages web. Certaines fenêtres pop-up sont considérées comme utiles — elles peuvent contenir des paramètres pour l'administration du site ou des informations de référence supplémentaires affichées lorsque l'on clique sur un lien. C'est pourquoi vous pouvez désactiver le Bloqueur si nécessaire. Cette extension ne fonctionne pas non plus sur les sites web ajoutés à la liste d'exceptions d'AdGuard. Elle est désactivée par défaut, mais vous pouvez l'activer dans les paramètres de l'application. You will find more detailed information about this extension in our Knowledge Base. +Cette extension empêche l'ouverture de fenêtres pop-up lorsque vous consultez des pages web. Certaines fenêtres pop-up sont considérées comme utiles — elles peuvent contenir des paramètres pour l'administration du site ou des informations de référence supplémentaires affichées lorsque l'on clique sur un lien. C'est pourquoi vous pouvez désactiver le Bloqueur si nécessaire. Cette extension ne fonctionne pas non plus sur les sites web ajoutés à la liste d'exceptions d'AdGuard. Elle est désactivée par défaut, mais vous pouvez l'activer dans les paramètres de l'application. Vous trouverez des informations plus détaillées sur cette extension dans notre Base de connaissances. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust vous permet de voir la réputation de chaque site web en fonction d ### Réseau -L'avant-dernier module est consacré au filtrage du réseau, et vous y trouverez des options supplémentaires liées au réseau. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Ce sont des précautions supplémentaires importantes pour mieux filtrer votre espace web. La plupart des sites web utilisent désormais HTTPS, et il en va de même pour la publicité. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +L'avant-dernier module est consacré au filtrage du réseau, et vous y trouverez des options supplémentaires liées au réseau. Deux d'entre eux sont activés par défaut : _Activer le filtrage du trafic_ et _Filtrer HTTPS_. Ce sont des précautions supplémentaires importantes pour mieux filtrer votre espace web. La plupart des sites web utilisent désormais HTTPS, et il en va de même pour la publicité. Sur de nombreux sites, comme youtube.com, facebook.com et x.com, c'est impossible de supprimer les publicités sans filtrage HTTPS. Gardez donc la fonctionnalité _Filtrer HTTPS_ activée, sauf si vous avez de bonnes raisons de ne pas le faire. ![Paramètres réseau \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3701beb0f..29bc5dcca2c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Paramètres_ est la section qui nécessite un maximum d'attention. C'est ici qu ### Paramètres généraux -Ici, vous pouvez définir la langue et le thème (Sombre ou Clair), activer le lancement d'AdGuard au démarrage du système et les mises à jour automatiques silencieuses, choisir la chaîne de mise à jour et filtrer l'intervalle de vérification des mises à jour. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Ici, vous pouvez définir la langue et le thème (Sombre ou Clair), activer le lancement d'AdGuard au démarrage du système et les mises à jour automatiques silencieuses, choisir la chaîne de mise à jour et filtrer l'intervalle de vérification des mises à jour. Les paramètres sont également l'endroit où aller si AdGuard pour Windows ne fonctionne pas correctement et si l'équipe d'assistance vous a demandé de [collecter les _journaux de débogage_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Paramètres avancés \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Il existe plusieurs sites web dont l'accès doit être restreint à partir d'un Le module vérifie le contenu des pages web ouvertes dans le navigateur et filtre celles dont le contenu est indésirable pour les enfants : images et textes pour adultes, langage grossier, violence, propagande de drogue, etc. Les paramètres du Contrôle Parental sont protégés par mot de passe pour que l'enfant ne puisse pas contourner les restrictions. Ce module bloque non seulement les directions vers des sites indésirables, mais peut également supprimer des résultats de recherche les liens inappropriés pour les enfants. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Vous pouvez également cocher la case _Bloquer le téléchargement des fichiers exécutables_ pour empêcher votre enfant de télécharger et d'installer des logiciels sur l'ordinateur. Il existe deux autres options dans le module _Contrôle parental_ : vous pouvez sélectionner un utilisateur Windows spécifique à protéger par le _Contrôle parental_ et définir un mot de passe pour protéger les paramètres AdGuard contre toute modification. +Dans le module _Contrôle Parental_, vous pouvez activer la _Recherche sécurisée_ et gérer la _liste de blocage_ et la _liste d'autorisation_ pour personnaliser le fonctionnement de cette option. Vous pouvez également cocher la case _Bloquer le téléchargement des fichiers exécutables_ pour empêcher votre enfant de télécharger et d'installer des logiciels sur l'ordinateur. Il existe deux autres options dans le module _Contrôle parental_ : vous pouvez sélectionner un utilisateur Windows spécifique à protéger par le _Contrôle parental_ et définir un mot de passe pour protéger les paramètres AdGuard contre toute modification. ![Contrôle parental \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index f676a77123a..d83ad6bc3da 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -5,102 +5,102 @@ sidebar_position: 2 :::info -Cet article parle de AdGuard pour Windows, un bloqueur de contenus multifonctionnel qui protège votre appareil au niveau du système. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +Cet article parle de AdGuard pour Windows, un bloqueur de contenus multifonctionnel qui protège votre appareil au niveau du système. Pour voir comment cela fonctionne, [téléchargez l'application AdGuard](https://agrd.io/download-kb-adblock) ::: ## Configuration requise -**Operating system:** Microsoft Windows 11, 10, 8.1, 8, 7, Vista. +**Système d'exploitation :** Microsoft Windows 11, 10, 8.1, 8, 7, Vista. -**RAM:** at least 512 MB. +**RAM :** au moins 512 Mo. -**Free disk space:** 150 Mbytes. +**Espace disque libre :** 150 Mo. -**Browsers:** Microsoft Edge, Microsoft Internet Explorer (all versions), Opera, Google Chrome, Yandex.Browser, Mozilla Firefox, and many other browsers. +**Navigateurs :** Microsoft Edge, Microsoft Internet Explorer (toutes les versions), Opera, Google Chrome, Yandex.Browser, Mozilla Firefox, et bien d'autres navigateurs. -## AdGuard installation +## Installation d'AdGuard -To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: +Pour utiliser AdGuard sur un PC ou une tablette sous Microsoft Windows, vous devez télécharger le paquet d'installation et lancer le programme d'installation. Effectuez les actions suivantes : -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Accédez au site web [AdGuard](http://adguard.com) dans la barre d'adresse et cliquez sur *Télécharger* [sur la page d'accueil](https://adguard.com/download.html?auto=1). - ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) + ![Téléchargez AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) -2. When the download is finished, press the *Open* button shown in the Downloads bar or click the file name *adguardInstaller.exe*. +2. Lorsque le téléchargement est terminé, appuyez sur le bouton *Ouvrir* affiché dans la barre de téléchargements ou cliquez sur le fichier nommé *adguardInstaller.exe*. - ![Press "Run"](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/click-download.png) + ![Appuyez sur "Exécuter"](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/click-download.png) -3. You’ll see the User Account Control dialogue box requesting to allow the app to make changes to your PC. Click *Yes*. +3. Vous verrez la boîte de dialogue Contrôle de compte d'utilisateur demandant d'autoriser l'application à apporter des modifications à votre PC. Cliquez sur *Oui*. - ![Allow changes *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) + ![Autorisez les modifications *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) -4. Next, choose the folder on your PC for the app to be installed to. +4. Ensuite, choisissez le dossier sur votre PC où l’application doit être installée. - ![Choose folder *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/install-wizard.png) + ![Choissez le dossier *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/install-wizard.png) - If you do not agree with the default installation path, press *Browse*, select the folder for AdGuard installation in the *Browse For Folder* window, and confirm your choice by clicking *OK*. You can also install AdGuard to a new folder by clicking *Make New Folder* and entering its name. To create a desktop shortcut for AdGuard, check the *Create a desktop shortcut* box. Press *Install* to proceed with installation. + Si vous n'êtes pas d'accord avec le chemin d'installation par défaut, appuyez sur *Parcourir*, sélectionnez le dossier pour l'installation d'AdGuard dans la fenêtre *Parcourir un dossier*, et confirmez votre choix en cliquant sur *OK*. Vous pouvez également installer AdGuard dans un nouveau dossier en cliquant sur *Créer un nouveau dossier* et en saisissant son nom. Pour créer un raccourci de bureau pour AdGuard, cochez la case *Créer un raccourci bureau*. Appuyez sur *Installer* pour continuer l'installation. - ![Start installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/start-install.png) + ![Démarrez l'installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/start-install.png) -5. Wait for the installation to complete and click *Finish*. +5. Attendez la fin de l’installation et cliquez sur *Terminer*. - ![Complete installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/finish-install.png) + ![Terminez l'installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/finish-install.png) - Congratulations! You have successfully installed AdGuard on your computer. On the screen you will see the main window where you can change the app’s settings. + Félicitations ! Vous avez installé AdGuard sur votre ordinateur. Sur l'écran, vous verrez la fenêtre principale où vous pouvez changer les paramètres de l'application. -## How to uninstall AdGuard for Windows {#uninstall} +## Comment désinstaller AdGuard pour Windows {#uninstall} -### Regular method +### Méthode normale -If you need to uninstall or reinstall AdGuard, do the following: +Si vous devez désinstaller ou réinstaller AdGuard, procédez comme suit : -- For Microsoft Windows 10 & 11: Open *Start Menu* by clicking *Start*, and select *Settings*. Click the *Apps* icon in the window that opens. Select *Apps and Features* from the list on the left in the *Apps* window. Select *AdGuard* from the list of your installed apps and click *Uninstall*. Click *Uninstall* in the dialogue box that opens to confirm. +- Pour Microsoft Windows 10 & 11 : ouvrez le *Menu Démarrer* en cliquant sur *Démarrer*, puis sélectionnez *Paramètres*. Cliquez sur l'icône *Applications* dans la fenêtre qui s'ouvre. Sélectionnez *Applications et fonctionnalités* dans la liste à gauche de la fenêtre *Applications*. Sélectionnez *AdGuard* dans la liste de vos applications installées et cliquez sur *Désinstaller*. Cliquez sur *Désinstaller* dans la boîte de dialogue qui s'ouvre pour confirmer. -![Windows 10 & 11 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win10-uninstall.png) +![Désinstallation de Windows 10 & 11 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win10-uninstall.png) -- For Microsoft Windows 8: Right-click the *empty space* in the lower left corner of the task bar and select *Control Panel*. Click *Uninstall a program* in the *Programs* section, then select *AdGuard* from the list of installed apps and press the *Uninstall* button located right above the list. Confirm the action by clicking *Uninstall AdGuard* in the window that opens. +- Pour Microsoft Windows 8 : Faites un clic droit sur l'*espace vide* dans le coin inférieur gauche de la barre des tâches et sélectionnez *Panneau de configuration*. Cliquez sur *Désinstaller un programme* dans la section *Programmes*, puis sélectionnez *AdGuard* dans la liste des applications installées et appuyez sur le bouton *Désinstaller* situé juste au-dessus de la liste. Confirmez l'action en cliquant sur *Désinstaller AdGuard* dans la fenêtre qui s'ouvre. -![Windows 8 uninstallation](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win8-uninstall.png) +![Désinstallation de Windows 8](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win8-uninstall.png) -- For Microsoft Windows 8.1: Right-click the *Start button* and select *Control Panel*. Click *Uninstall a program* in the *Programs* section, then select *AdGuard* from the list of installed apps and press the *Uninstall* button located right above the list. Confirm the action by clicking *Uninstall AdGuard* in the window that opens. +- Pour Microsoft Windows 8.1 : Faites un clic droit sur le *bouton Démarrer* et sélectionnez *Panneau de configuration*. Cliquez sur *Désinstaller un programme* dans la section *Programmes*, puis sélectionnez *AdGuard* dans la liste des applications installées et appuyez sur le bouton *Désinstaller* situé juste au-dessus de la liste. Confirmez l'action en cliquant sur *Désinstaller AdGuard* dans la fenêtre qui s'ouvre. -- For Microsoft Windows 7: Open *Start Menu*. In the search box, type *Control Panel*. Click *Uninstall a program* in the *Programs* section, then select *AdGuard* from the list of installed apps and press the *Uninstall* button located right above the list. Confirm the action by clicking *Uninstall AdGuard* in the window that opens. +- Pour Microsoft Windows 7 : ouvrez le *Menu Démarrer*. Dans la barre de recherche, tapez *Panneau de configuration*. Cliquez sur *Désinstaller un programme* dans la section *Programmes*, puis sélectionnez *AdGuard* dans la liste des applications installées et appuyez sur le bouton *Désinstaller* situé juste au-dessus de la liste. Confirmez l'action en cliquant sur *Désinstaller AdGuard* dans la fenêtre qui s'ouvre. -![Windows 7 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win7-uninstall.png) +![Désinstallation de Windows 7 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win7-uninstall.png) -### Advanced method {#advanced} +### Méthode avancée {#advanced} -In case regular uninstall doesn't work for any reason, you can try to use an advanced method. First of all, you need to [download the uninstaller tool](https://cdn.adtidy.org/distr/windows/Uninstall_Utility.zip) created by our developers. Extract the archive to any folder on your PC and run the **Adguard.UninstallUtility.exe** file, and allow the app to make changes to your device. Then follow the instruction below: +Si la désinstallation normale ne fonctionne pas pour une raison quelconque, vous pouvez essayer d'utiliser une méthode avancée. Tout d'abord, vous devez [télécharger l'outil de désinstallation](https://cdn.adtidy.org/distr/windows/Uninstall_Utility.zip) créé par nos développeurs. Extrayez l'archive dans n'importe quel dossier sur votre PC et exécutez le fichier **Adguard.UninstallUtility.exe**, puis autorisez l'application à apporter des modifications à votre appareil. Suivez ensuite les instructions ci-dessous : -- Select *AdGuard Ad Blocker* and *Standard* uninstall type, then click *Uninstall*. +- Sélectionnez *Bloqueur de publicité AdGuard* et le type de désinstallation *Standard*, puis cliquez sur *Désinstaller*. -![Standard uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) +![Désinstallation standard *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) -- Click *OK* once the warning window pops up: +- Cliquez sur *OK* une fois que la fenêtre d'avertissement apparaît : -![Standard uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![Avertissement de désinstallation standard *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) -- Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: +- Attendez que la désinstallation soit terminée — vous verrez la phrase **Désinstallation terminée** et une demande de redémarrer votre ordinateur : -![Uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard_complete.jpg) +![Désinstallation terminée *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard_complete.jpg) :::caution -Follow the next steps only if performing the first two steps wasn’t enough for some reason. We strongly suggest contacting our support before using steps 3-4 of advanced uninstall instruction. +Suivez les étapes suivantes uniquement les deux premières étapes n’étaient pas suffisantes pour une raison quelconque. Nous vous suggérons fortement de contacter notre assistance avant d'utiliser les étapes 3-4 des instructions de désinstallation avancées. ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Sélectionnez le *Bloqueur de publicité AdGuard* et le type de désinstallation *Avancé*, puis cliquez sur *Désinstaller*. Cliquez sur *Oui, continuer* dans la fenêtre pop-up. -![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) +![Désinstallation avancée *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) -- Click *OK* once the warning window pops up: +- Cliquez sur *OK* une fois que la fenêtre d'avertissement apparaît : -![Extended uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![Avertissement de désinstallation avancée *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) -- Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: +- Attendez que la désinstallation soit terminée — vous verrez la phrase **Désinstallation terminée** et une demande de redémarrer votre ordinateur : -![Extended uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) +![Désinstallation avancée terminée *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) -AdGuard is successfully uninstalled! +AdGuard a été désinstallé avec succès ! diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index ca9792de7cb..131e2e3af7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + est convertie en ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4766,6 +4765,7 @@ The following scriptlets also may be used for debug purposes: [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" +[ext-mv3]: #what-product "Extension AdGuard pour Chrome MV3" [ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index c41ca5330d2..6da53f63b90 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 12a06325e98..8662c7fa73d 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -3,74 +3,73 @@ title: Estensione AdGuard Browser per Chrome MV3 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +Poiché le estensioni MV2 vengono gradualmente eliminate dal Chrome Web Store, gli utenti di Chrome potrebbero dover passare alle estensioni MV3, compatibili con il nuovo API Manifest V3 di Chrome. Le nostre riflessioni su questo argomento sono ampiamente discusse sul [nostro blog](https://adguard.com/en/blog/tag/manifest-v3.html). -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +La nostra estensione MV3 blocca in modo efficace gli annunci e i tracker, gestendo al tempo stesso widget sociali, banner e annunci video. La maggior parte degli utenti non noterà alcuna differenza operativa, ma ci sono alcune limitazioni e modifiche di cui essere a conoscenza. -## Where to find our extensions +## Dove trovare le nostre estensioni -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +La **versione MV3** ha sostituito la nostra vecchia estensione nel [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +La **versione beta di MV3** sarà ancora disponibile nel [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +La vecchia estensione beta verrà rinominata [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) e sarà supportata finché Google non la eliminerà gradualmente. -## Main changes in features and settings +## Principali modifiche alle funzionalità e alle impostazioni -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **Nessun aggiornamento automatico o manuale dei filtri.** Le opzioni _Aggiorna automaticamente i filtri_ e _Controlla aggiornamento filtri_ non sono più disponibili nella scheda _Filtri_. Poiché alcune regole sono ora applicate in formato DNR, non possiamo aggiornare i filtri su richiesta, ma solo attraverso l'intero processo di aggiornamento dell'estensione insieme alla revisione negli negozi con app. -- **Filtering log** +- **Registro di filtraggio** - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) + ! [Registro di filtraggio \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + A causa delle restrizioni DNR, non possiamo mostrare esattamente quale regola ha funzionato, ma forniremo una "regola presunta che è stata attivata" in base al nostro motore. Per informazioni più precise, dovrai installare tu stesso la versione "scompattata" dell'estensione nel tuo browser. Troverai istruzioni dettagliate su come farlo in un [articolo separato](/adguard-browser-extension/solving-problems/debug-rules/). -- _Tracking protection_ (formerly known as _Stealth mode_) +- _Protezione dal tracciamento_ (precedentemente nota come _Modalità invisibile_) - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) + ![Protezione dal tracciamento \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + Non sono presenti sezioni _Cookie_, così come _Autodistruzione dei cookie proprietari_ e _Autodistruzione dei cookie di terze parti_, poiché non possiamo impostare il TTL dei cookie utilizzando regole dichiarative. -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- La _protezione da phishing e malware_ non è più disponibile nelle impostazioni generali. Per proteggerti da siti web dannosi e truffe, attiva i filtri _Sicurezza_ appropriati nella scheda _Filtri_. - ![Security \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) + ![Sicurezza \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) -## Limitations +## Limitazioni -### Maximum number of rules and filters +### Quantità massimale di regole e filtri -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +Manifest V3 impone limiti alle regole statiche e regex per estensione. Gli utenti potrebbero ricevere notifiche quando questi limiti vengono superati. -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) +![Limiti regole \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) +![Troppe estensioni \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +Fondamentalmente, Manifest V3 divide le regole in statiche (integrate) e dinamiche, con limiti rigorosi. -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +**Regole statiche:** minimo **30.000** regole per estensione, con un limite cumulativo di **330.000** per tutte le estensioni installate da un singolo utente. -For regex rules, the limit is set at **1,000 per extension**. +Per le regole regex, il limite è impostato a **1.000 per estensione**. -The maximum number of simultaneously enabled filters is **50**. +Il numero massimo di filtri abilitati contemporaneamente è **50**. -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +**Regole dinamiche:** è imposto un limite massimo di **5.000** regole, che include un massimo di 1.000 regole regex. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> Le **regole convertite** sono regole che sono state trasformate +> in \[formato DNR] utilizzando il [convertitore dichiarativo][github-declarative-converter]. +> Durante questo processo di conversione, alcune regole potrebbero sovrascriverne altre (`$badfilter`), alcune potrebbero essere combinate (`$removeparam`), producendo un elenco di regole con un ordine leggermente diverso. > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> Da questo elenco di regole convertite, ne utilizzeremo solo 5.000. Gli altri verranno visualizzati nell'editor, ma non applicati. -Here's how a rule with a basic modifier is converted to a declarative rule: +Ecco come una regola con un modificatore di base viene convertita in una regola dichiarativa: ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +viene convertita in ```json [ @@ -94,14 +93,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +Altri esempi possono essere trovati su [GitHub][github-declarative-converter-examples]. -### Network rule modifiers +### Modificatori delle regole di rete -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +I modificatori delle regole di rete presentano delle limitazioni: alcuni di essi non possono essere implementati in MV3 oppure possono essere implementati solo con delle restrizioni. -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +Ulteriori dettagli sulle limitazioni sono disponibili su [GitHub][github-declarative-converter]. +Per ulteriori informazioni sui modificatori, fare riferimento alla nostra [Knowledge base](/general/ad-filtering/create-own-filters). [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md index 23251b3d6cb..5a62a9b0410 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md @@ -1,98 +1,98 @@ --- -title: How to debug rules in AdGuard for Chrome MV3 +title: Come eseguire il debug delle regole in AdGuard per Chrome MV3 sidebar_position: 2 --- -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. +In [AdGuard per Chrome MV3](/adguard-browser-extension/mv3-version), il registro di filtraggio mostra solo le regole approssimative applicate, che chiamiamo "regole presunte". Ciò accade perché il browser non fornisce dettagli sulle specifiche regole dichiarative utilizzate, a meno che l'estensione non sia in un formato "non compresso". Per informazioni più precise, dovrai installare tu stesso la versione scompattata dell'estensione nel tuo browser. -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. +Queste istruzioni sono pensate anche per i casi problematici in cui si desidera modificare staticamente le regole fornite con l'estensione. Nella maggior parte dei casi, dovrebbe essere sufficiente utilizzare _Regole utente_ nell'estensione. -## Prerequisites +## Prerequisiti -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) +1. **Git:** [Installa Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) +2. **Node:** [Installa Node.js](https://nodejs.org/it/download/package-manager) -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) +3. **Yarn:** [Installa Yarn](https://classic.yarnpkg.com/lang/en/docs/install) -## How to clone extension +## Come clonare l'estensione -1. Clone the repository: +1. Clonare il repositorio: ```bash git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git ``` -2. Navigate to the directory: +2. Passare alla ripartizione: ```bash cd AdguardBrowserExtension ``` -3. Switch to the `v5.0` branch: +3. Passare al ramo `v5.0`: ```bash git checkout v5.0 ``` -4. Install dependencies: +4. Installare le dipendenze: ```bash yarn install ``` -## How to build extension +## Come costruire l'estensione -1. Switch to the `v5.0` branch: +1. Passare al ramo `v5.0`: ```bash git checkout v5.0 ``` -2. Run the following command in the terminal: +2. Eseguire il seguente comando nel terminale: ```bash yarn dev chrome-mv3 ``` -3. The built extension will be located in the directory: +3. L'estensione compilata sarà posizionata nella ripartizione: ```bash ./build/dev/chrome-mv3 ``` -## How to install unpacked in the browser +## Come installare decompresso nel browser -1. Turn on developer mode: +1. Attivare la modalità sviluppatore: - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) + ![Modalita sviluppatore](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) -2. Click _Load unpacked_: +2. Fare clic su _Carica decompresso_: - ![Load unpacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) + ![Carica decompresso](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) -3. Select the extension directory and click `Select`: +3. Selezionare la ripartizione dell'estensione e fare clic su `Seleziona`: - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) + ![Seleziona](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) -That’s it! +Ecco fatto! -## How to debug rules +## Come eseguire il debug delle regole -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. +1. Trova e modifica la regola di cui hai bisogno nella ripartizione `./Extension/filters/chromium-mv3` nei file `.txt`. -2. Convert the rules from txt to declarative form: +2. Convertire le regole dal formato txt alla forma dichiarativa: ```bash yarn convert-declarative ``` -3. Build the extension again: +3. Costruire nuovamente l'estensione: ```bash yarn dev chrome-mv3 ``` -4. Reload the extension in the browser: +4. Ricaricare l'estensione nel browser: - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) + ![Ricarica estensione](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md index 9d6fe420cd3..fac00dc7a9b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md @@ -1,5 +1,5 @@ --- -title: Installation +title: Installazione sidebar_position: 2 --- @@ -17,7 +17,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro **Free disk space:** 500 MB -## Installation +## Installazione Most Android-based apps are distributed via Google Play; however, AdGuard is not presented there, because Google prohibits distribution of network-level ad blockers via Google Play, i.e. apps that block commercials in other apps. You will find more information about Google restrictive policy [in our blog](https://adguard.com/blog/adguard-google-play-removal.html). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 79696704cec..0dc956beefc 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -155,6 +155,6 @@ You should remove Shadowsocks app from filtering before setting up the process ( | Proxy host | *127.0.0.1* | | Proxy port | *7891* | -## Limitations +## Limitazioni 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**. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md index aaab2dd86c5..b7b57487d71 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md @@ -1,5 +1,5 @@ --- -title: Free vs. full version +title: Versione gratuita vs. completa sidebar_position: 9 --- @@ -11,22 +11,22 @@ Questo articolo riguarda AdGuard per iOS, un blocco annunci multifunzionale che :::note -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. +Tanto AdGuard per iOS con Premium abilitato quanto AdGuard Pro bloccano gli annunci su smartphone e tablet Apple. In passato, le due versioni differivano per funzionalità a causa di alcune modifiche apportate alle policy di revisione dell'App Store, ma ora AdGuard con un abbonamento acquistato e AdGuard Pro sono identici per funzionalità. ::: -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. +AdGuard Premium per iOS presenta diverse differenze rispetto alla versione gratuita, tra cui le impostazioni DNS personalizzate. Grazie a queste impostazioni, puoi bloccare gli annunci pubblicitari non solo su Safari, ma anche su altre app, proteggere i tuoi figli dai contenuti per adulti online e proteggere i tuoi dati personali dai furti. Ci sono anche altre differenze. Analizziamoli tutti in dettaglio. -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. +1. Il modulo **Protezione DNS** crittografa il traffico DNS per migliorare la privacy. Funziona su tutte le app e tutti i browser, non solo su Safari, offrendo un'ampia protezione contro annunci pubblicitari e tracker. - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. + - **Server DNS personalizzati:** scegli tra uno dei server DNS più popolari dal nostro elenco oppure aggiungi il tuo server personalizzato. - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. + - **Protezione famiglia:** Internet non è sempre adatto ai bambini. Con AdGuard Premium puoi passare a provider DNS che bloccano contenuti per adulti e altro materiale inappropriato per proteggere i tuoi figli online. - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. + - **Monitoraggio e configurazione flessibile:** il registro delle attività recenti ti consente di visualizzare tutte le richieste DNS inviate dal tuo dispositivo e di gestire facilmente il tuo traffico aggiungendo siti web alla lista nera o alla lista autorizzata con un semplice tocco. -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. +2. **La protezione avanzata** ti consente di utilizzare regole di filtraggio avanzate per bloccare annunci pubblicitari più complessi che altrimenti non verrebbero bloccati. -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. +3. **Ulteriori opzioni di filtraggio:** acquistando AdGuard Premium, avrai accesso a filtri personalizzati e a una categoria di filtri di sicurezza, dove potrai scegliere tra oltre 50 filtri, tra cui quelli di AdGuard e di altri elenchi popolari. -Access these features by [purchasing a license](https://adguard.com/license.html). +Per accedere a queste funzionalità, [acquista una licenza](https://adguard.com/license.html). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..b9144b1e93e 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -1,54 +1,54 @@ --- -title: Documentation for admins +title: Documentazione per admin sidebar_position: 5 --- -This page describes the features and details of AdGuard’s central management of policies and preferences. +Questa pagina descrive le funzionalità e i dettagli della gestione centrale di politiche e preferenze di AdGuard. -## 1. Download the MSI {#msi-download} +## 1. Scarica MSI {#msi-download} -Download the [AdGuard MSI x86](https://cdn.adtidy.org/distr/windows/AdGuard_x86.msi) +Scarica il [AdGuard MSI x86](https://cdn.adtidy.org/distr/windows/AdGuard_x86.msi) -Download the [AdGuard MSI x64](https://cdn.adtidy.org/distr/windows/AdGuard_x64.msi) +Scarica il [AdGuard MSI x64](https://cdn.adtidy.org/distr/windows/AdGuard_x64.msi) -## 2. Configure the settings for your network {#settings-configuring} +## 2. Configura le impostazioni per la tua rete {#settings-configuring} -On machines that are joined to an Active Directory domain, policy settings may also be stored in the registry under `HKEY_LOCAL_MACHINE` in the following path: `Software\Policies\AdGuard\`. +Sulle macchine facenti parte di un dominio Active Directory, le impostazioni sulla politica possono esser archiviate anche nel registro in `HKEY_LOCAL_MACHINE` nel seguente percorso: `Software\Policies\AdGuard\`. -The only supported policy is `LicenseKey`. If this policy is set, AdGuard will prefer it over what user can enter in the interface. This license key will be used for checking license status. +L'unica politica supportata è `LicenseKey`. Se questa è impostata, AdGuard la preferirà a ciò che l'utente può inserire nell'interfaccia. Questa chiave di licenza sarà utilizzata per verificare lo stato della licenza. -## 3. Make sure that AdGuard servers are available {#servers-available} +## 3. Assicurati che i server di AdGuard siano disponibili {#servers-available} -AdGuard connects to two hosts: `api.adguard.org` and `filters.adtidy.org`. Make sure that both servers are available. +AdGuard si connette a due host: `api.adguard.org` e `filters.adtidy.org`. Assicurati che entrambi i server siano disponibili. -## 4. Push the MSI out to your network {#msi-push} +## 4. Invia MSI alla tua rete {#msi-push} -If you usually use SMS or other tools, use them to push out the AdGuard MSI just as you would normally do with any other installation bundle. +Se solitamente utilizzi SMS o altri strumenti, utilizzali per inviare AdGuard MSI, come faresti normalmente con qualsiasi altro pacchetto di installazione. -Otherwise, you can run the MSI on the target machine directly (and silently) with this command: `Msiexec /q /i AdGuard.msi` +Altrimenti, puoi eseguire MSI direttamente (e silenziosamente) sulla macchina di destinazione con questo comando: `Msiexec /q /i AdGuard.msi` -If you need to roll out an update, use this command: `Msiexec /q /i AdGuard.msi REINSTALL=ALL REINSTALLMODE=vomus` +Se necessiti di implementare un aggiornamento, utilizza questo comando: `Msiexec /q /i AdGuard.msi REINSTALL=ALL REINSTALLMODE=vomus` :::note -You must run these commands with admin privileges. +È necessario eseguire questi comandi con privilegi di amministratore. ::: -If you want to install AdGuard on a Windows 7 computer, make sure that it has .NET 4 Client Profile installed: https://www.microsoft.com/en-us/download/details.aspx?id=24872 +Se desideri installare AdGuard su un computer Windows 7, assicurati che sia installato il profilo client .NET 4: https://www.microsoft.com/en-us/download/details.aspx?id=24872 :::note -If you have installed AdGuard for Windows from an MSI file, AdGuard will not be updated automatically. To allow manual updates: +Se hai installato AdGuard per Windows da un file MSI, AdGuard non verrà aggiornato automaticamente. Per consentire aggiornamenti manuali: -- In versions released after v7.16, delete the `ForbidCheckUpdates` parameter or set its value to `NO` (case-insensitive) in the registry under `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard`. +- Nelle versioni rilasciate dopo la v7.16, elimina il parametro `ForbidCheckUpdates` o imposta il suo valore su `NO` (senza distinzione tra minuscole e maiuscole) nel registro sotto `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard`. -- In v7.16 and earlier versions, set to `YES` (case-insensitive) the `AllowCheckUpdates` parameter for the `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard` key on x86 OS or `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adguard` key on x64 OS. Any other value or no value for this parameter will disable automatic updates. +- Nelle versioni v7.16 e precedenti, imposta a `YES` (non sensibile al maiuscolo/minuscolo) il parametro `AllowCheckUpdates` per la chiave `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard` su sistemi operativi x86 o la chiave `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adguard` su sistemi operativi x64. Qualsiasi altro valore o nessun valore per questo parametro disattiverà gli aggiornamenti automatici. -Please note that such installation of the application and manual updates are not recommended and can cause technical problems. +Si prega di notare che tale installazione dell'applicazione e aggiornamenti manuali non sono consigliati e possono causare problemi tecnici. ::: -## 5. Test your installation {#installation-test} +## 5. Prova la tua installazione {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +Su una macchina di destinazione, avvia AdGuard. Apri la schermata della licenza per verificare che utilizzi quella specificata. Potresti dover cliccare su "Aggiorna stato", per far convalidare la chiave di licenza ad AdGuard. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..3695de00e9b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -3,43 +3,43 @@ title: Browser Assistant sidebar_position: 3 --- -AdGuard Assistant’s primary function is to manage filtering directly from the browser. It has existed for quite a long time, and its form and content have changed. More precisely, it used to be a mere userscript incorporated into AdGuard for Windows app and became a full-fledged browser extension. Now it yields more benefits. +La funzione principale di AdGuard Assistant è gestire il filtraggio direttamente dal browser. Esiste da molto tempo e la sua forma e contenuto sono cambiati. Più precisamente, era utilizzata come un semplice userscript incorporato nell'app AdGuard per Windows, ed è diventata un'estensione completa per browser. Ora, produce più vantaggi. ![Browser Assistant *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/assistant-menu.png) -## Benefits +## Vantaggi -### Independence +### Indipendenza -AdGuard Browser Assistant is a browser extension, it is installed in a browser, so there is no need to wait for the userscript to be injected into the filtered web page, as it was with the preceding one. In other words, it is more autonomous from the main AdGuard app. Still, Browser Assistant needs the installed AdGuard for Windows, because there is no point in using the extension without the app. +AdGuard Browser Assistant è un'estensione installata su un browser, quindi non è necessario attendere l'iniezione dell'userscript nella pagina web filtrata, come avveniva in precedenza. In altre parole, è più autonoma dall'app principale di AdGuard. Tuttavia, Browser Assistant nececssita che AdGuard per Windows sia installata, poiché non ha senso utilizzare l'estensione senza l'app. -### Compatibility with the main app +### Compatibilità con l'app principale -If you got into the habit of using our previous [AdGuard Ad Blocker extension](/adguard-browser-extension/compatibility), you might like the solution that we have developed for the new Browser Assistant. +Se hai preso l'abitudine di utilizzare la nostra precedente [estensione AdGuard Ad Blocker](/adguard-browser-extension/compatibility), potrebbe piacerti la soluzione che abbiamo sviluppato per il nuovo Browser Assistant. -Background information: +Informazioni di base: -In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. +Nelle versioni precedenti dell'Estensione di browser AdGuard (prima della v3.5), se l'avevi installata insieme all'app AdGuard per Windows, l'estensione assumeva le funzioni dell'Assistente, smetteva di filtrare e faceva affidamento sull'app per farlo. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +L'estensione e l'app funzionavano insieme, ma a volte l'integrazione falliva. La protezione normalmente fornita dal programma desktop si interrompeva su determinati siti, dove solo l'estensione meno potente poteva fornire protezione. -When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. +Quando si utilizza il Browser Assistant, tutti questi problemi non hanno importanza poiché non possono esserci conflitti in sostanza. Il ruolo del Browser Assistant è ben definito e non può ostacolare il funzionamento dell'app principale, quindi non c'è motivo di preoccuparsi. -## Separate tab in Settings +## Scheda separata in Impostazioni -The new Browser Assistant has its own tab in AdGuard for Windows settings, along with Stealth Mode, Browsing security, Parental Control and others. There you will find a link to download the extension for your default browser. Besides, there is a checkbox to enable the legacy Assistant. +La nuova Browser Assistant ha la propria scheda nelle impostazioni di AdGuard per Windows, insieme alla Modalità Invisibilità, la Sicurezza di Navigazione, il Controllo parentale e altre. Lì troverai un link per scaricare l'estensione per il tuo browser predefinito. Inoltre, è presente una casella per abilitare l'Assistant ereditario. -![Settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) +![Impostazioni *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) -## Legacy Assistant +## Assistant Ereditario -Legacy Assistant is the previous version of Assistant, which is a mere userscript, not a browser extension. Basically, there are two cases when you might want to pick it instead of the new Browser Assistant: +L'Assistant Ereditario è la versione precedente di Assistant, un semplice script utente, non un'estensione del browser. Fondamentalmente, esistono due casi in cui potresti volerlo scegliere, al posto del nuovo Browser Assistant: -1. The new Assistant is not available for your browser. -1. You are used to the green shield icon and want to leave things as they were. +1. Il nuovo Assistant non è disponibile per il tuo browser. +1. Sei abituato all'icona dello scudo verde e desideri lasciare le cose così come sono. -## How to install AdGuard Browser Assistant +## Come Installare AdGuard Browser Assistant -If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. +Se desideri installare Browser Assistant per il tuo browser predefinito, puoi farlo direttamente dalle impostazioni dell'app, ma hai anche la possibilità di installarlo per altri browser. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant è disponibile per tutti i browser più diffusi: Chrome, Firefox, Edge, Opera e Yandex. Per installare quello che ti serve (o molti, non è proibito ma addirittura incoraggiato), vai al [nostro sito web](https://adguard.com/adguard-assistant/overview.html), fai clic sull'icona del browser e poi sul pulsante *Installa*. Ecco fatto! diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 1c13c862fbb..5293eaadd73 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant è l'Assistente legacy che puoi utilizzare se il [nuovo Assist Questa è un'estensione personalizzata progettata per contrastare la tecnica di reinserimento degli annunci bloccati: la cosiddetta elusione dei blocchi di annunci o reiniezione degli annunci. Entrambi sono metodi anti blocco degli annunci avanzati, che continuano a crescere in popolarità tra gli inserzionisti. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra è, essenzialmente, un microprogramma che modifica il funzionamento delle pagine, così che diventi più difficile, per i siti, l'utilizzo dei suddetti metodi per aggirare i bloccatori. **AdGuard Popup Blocker** -Quest'estensione impedisce l'apertura delle finestre popup quando visualizzi le pagine web. Alcuni pop-up sono considerati utili: possono contenere impostazioni per l'amministrazione del sito o informazioni di riferimento aggiuntive mostrate facendo clic su un collegamento. Per questo, puoi disattivare il Blocco, se necessario. Quest'estensione non funziona neanche sui siti web aggiunti all'elenco di eccezioni di AdGuard. È disattivata di default, ma puoi attivarla nelle impostazioni dell'applicazione. You will find more detailed information about this extension in our Knowledge Base. +Quest'estensione impedisce l'apertura delle finestre popup quando visualizzi le pagine web. Alcuni pop-up sono considerati utili: possono contenere impostazioni per l'amministrazione del sito o informazioni di riferimento aggiuntive mostrate facendo clic su un collegamento. Per questo, puoi disattivare il Blocco, se necessario. Quest'estensione non funziona neanche sui siti web aggiunti all'elenco di eccezioni di AdGuard. È disattivata di default, ma puoi attivarla nelle impostazioni dell'applicazione. Troverai delle informazioni più dettagliate su quest'estensione nella nostra Base di conoscenza. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust ti consente di visualizzare la reputazione di ogni sito web, second ### Rete -Il penultimo modulo è dedicato al filtraggio di rete e, qui, troverai le opzioni aggiuntive correlate alla rete. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Queste sono importanti precauzioni aggiuntive, per meglio filtrare il tuo spazio web. Gran parte dei siti, a oggi, utilizzano HTTPS, il che si applica anche agli annunci. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Il penultimo modulo è dedicato al filtraggio di rete e, qui, troverai le opzioni aggiuntive correlate alla rete. Due di esse sono abilitate di default: _Abilita il filtraggio del traffico_ e _Filtra HTTPS_. Queste sono importanti precauzioni aggiuntive, per meglio filtrare il tuo spazio web. Gran parte dei siti, a oggi, utilizzano HTTPS, il che si applica anche agli annunci. Da molti siti, come youtube.com, facebook.com e x.com, è impossibile rimuovere gli annunci senza il filtraggio HTTPS. Quindi, mantieni la funzionalità _Filtra HTTPS_ abiltata, a meno che tu non abbia una valida ragione per non farlo. ![Impostazioni di Rete \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 6c507dd8877..7fd31900faa 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Impostazioni_ è la sezione che richiede maggiore attenzione. Qui, puoi configu ### Impostazioni generali -Qui, puoi impostare la lingua e il tema (Scuro o Chiaro), abilitare l'avvio di AdGuard all'avvio del sistema e silenziare gli aggiornamenti automatici, scegliere il canale d'aggiornamento e filtrare l'intervallo di controllo per gli aggiornamenti. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Qui, puoi impostare la lingua e il tema (Scuro o Chiaro), abilitare l'avvio di AdGuard all'avvio del sistema e silenziare gli aggiornamenti automatici, scegliere il canale d'aggiornamento e filtrare l'intervallo di controllo per gli aggiornamenti. Inoltre, Impostazioni è il posto in cui andare se AdGuard per Windows non funziona correttamente e se il team di supporto ti ha richiesto di [raccogliere i _Registri di debug_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Impostazioni Avanzate \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Esistono numerosi siti web a cui dovrebbe essere limitato l'accesso da un PC uti Il modulo controlla i contenuti delle pagine web aperte nel browser e filtra quelle con contenuti indesiderabili per i bambini: immagini e testi per adulti, linguaggio volgare, violenza, sostanze stupefacenti, etc. Le impostazioni del Controllo Genitori sono protette da password, così che i bambini non possano aggirare le limitazioni. Questo modulo non blocca soltanto le indicazioni ai siti indesiderati, ma può anche eliminare i collegamenti inappropriati per i bambini, dai risultati di ricerca. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Inoltre, puoi anche spuntare la casella _Blocca download file eseguibili_ per impedire ai tuoi figli di scaricare e installare software sul computer. Esistono ancora altre due opzioni nel modulo _Controllo Genitori_: puoi selezionare un utente di Windows specifico da proteggere con il _Controllo Genitori_ e impostare una password per proteggere le impostazioni di AdGuard dalla modifica. +Nel modulo _Parental Control_, puoi abilitare la _Ricerca sicura_ e gestire l'_elenco di blocco_ e l'_elenco consentiti_ per personalizzare il funzionamento d quest'opzione. Inoltre, puoi anche spuntare la casella _Blocca download file eseguibili_ per impedire ai tuoi figli di scaricare e installare software sul computer. Esistono ancora altre due opzioni nel modulo _Controllo Genitori_: puoi selezionare un utente di Windows specifico da proteggere con il _Controllo Genitori_ e impostare una password per proteggere le impostazioni di AdGuard dalla modifica. ![Controllo Genitori \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cdb715bdb0c..2d15920e861 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -1,5 +1,5 @@ --- -title: Installation +title: Installazione sidebar_position: 2 --- @@ -11,96 +11,96 @@ Questo articolo riguarda AdGuard per Windows, un blocco annunci multifunzionale ## Requisiti di sistema -**Operating system:** Microsoft Windows 11, 10, 8.1, 8, 7, Vista. +**Sistema operativo:** Microsoft Windows 11, 10, 8.1, 8, 7, Vista. -**RAM:** at least 512 MB. +**RAM:** almeno 512 MB. -**Free disk space:** 150 Mbytes. +**Spazio libero su disco:** 150 Mbyte. -**Browsers:** Microsoft Edge, Microsoft Internet Explorer (all versions), Opera, Google Chrome, Yandex.Browser, Mozilla Firefox, and many other browsers. +**Browser:** Microsoft Edge, Microsoft Internet Explorer (tutte le versioni), Opera, Google Chrome, Yandex.Browser, Mozilla Firefox e molti altri. -## AdGuard installation +## Installazione AdGuard -To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: +Per utilizzare AdGuard su un PC o tablet su Microsoft Windows, dovresti scaricare il pacchetto d'installazione e avviare il programma d'installazione. Esegui le seguenti azioni: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Vai al sito web di AdGuard [](http://adguard.com) nella barra degli indirizzi e clicca su *Scarica* [nella home page](https://adguard.com/download.html?auto=1). - ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) + ![Scarica AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) -2. When the download is finished, press the *Open* button shown in the Downloads bar or click the file name *adguardInstaller.exe*. +2. Al termine del download, premi il pulsante *Apri* visualizzato nella barra dei download o clicca sul nome del file *adguardInstaller.exe*. - ![Press "Run"](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/click-download.png) + ![Premi "Avvia"](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/click-download.png) -3. You’ll see the User Account Control dialogue box requesting to allow the app to make changes to your PC. Click *Yes*. +3. Vedrai la finestra di dialogo Controllo dell'account utente che richiede di autorizzare l'applicazione ad apportare modifiche al tuo PC. Clicca *Sì*. - ![Allow changes *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) + ![Consenti modifiche *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) -4. Next, choose the folder on your PC for the app to be installed to. +4. Successivamente, seleziona la cartella sul tuo PC in cui installare l'app. - ![Choose folder *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/install-wizard.png) + ![Scegli cartella *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/install-wizard.png) - If you do not agree with the default installation path, press *Browse*, select the folder for AdGuard installation in the *Browse For Folder* window, and confirm your choice by clicking *OK*. You can also install AdGuard to a new folder by clicking *Make New Folder* and entering its name. To create a desktop shortcut for AdGuard, check the *Create a desktop shortcut* box. Press *Install* to proceed with installation. + Se non sei d'accordo con il percorso d'installazione predefinito, clicca su *Sfoglia*, seleziona la cartella per l'installazione di AdGuard nella finestra *Sfoglia Cartelle* e conferma la scelta facendo clic su *OK*. Puoi anche installare AdGuard in una nuova cartella, cliccando su *Crea nuova cartella* e inserendone il nome. Per creare un collegamento sul desktop per AdGuard, spunta la casella *Crea un collegamento sul desktop*. Clicca *Installa* per procedere con l'installazione. - ![Start installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/start-install.png) + ![Avvia installazione *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/start-install.png) -5. Wait for the installation to complete and click *Finish*. +5. Attendi il completamento dell'installazione e clicca su *Fine*. - ![Complete installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/finish-install.png) + ![Installazione completa *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/finish-install.png) - Congratulations! You have successfully installed AdGuard on your computer. On the screen you will see the main window where you can change the app’s settings. + Felicitazioni! Hai installato correttamente AdGuard sul tuo computer. Sullo schermo vedrai la finestra principale, in cui puoi modificare le impostazioni dell'app. -## How to uninstall AdGuard for Windows {#uninstall} +## Come disinstallare AdGuard per Windows {#uninstall} -### Regular method +### Metodo regolare -If you need to uninstall or reinstall AdGuard, do the following: +Se devi disinstallare o reinstallare AdGuard, procedi in questo modo: -- For Microsoft Windows 10 & 11: Open *Start Menu* by clicking *Start*, and select *Settings*. Click the *Apps* icon in the window that opens. Select *Apps and Features* from the list on the left in the *Apps* window. Select *AdGuard* from the list of your installed apps and click *Uninstall*. Click *Uninstall* in the dialogue box that opens to confirm. +- Per Microsoft Windows 10 & 11: Apri il *Menu Start* cliccando su *Start* e seleziona *Impostazioni*. Clicca sull'icona delle *App* nella finestra che si apre. Seleziona *App e Funzionalità* dall'elenco sulla sinistra nella finestra delle *App*. Seleziona *AdGuard* dall'elenco delle app installate e clicca su *Disinstalla*. Clicca su *Disinstalla* nella finestra che si apre, per confermare. -![Windows 10 & 11 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win10-uninstall.png) +![Disinstallazione su Windows 10 & 11 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win10-uninstall.png) -- For Microsoft Windows 8: Right-click the *empty space* in the lower left corner of the task bar and select *Control Panel*. Click *Uninstall a program* in the *Programs* section, then select *AdGuard* from the list of installed apps and press the *Uninstall* button located right above the list. Confirm the action by clicking *Uninstall AdGuard* in the window that opens. +- Per Microsoft Windows 8: clicca con il pulsante destro del mouse sullo *spazio vuoto* nell'angolo in basso a sinistra della barra delle applicazioni e seleziona *Pannello di controllo*. Clicca su *Disinstalla un programma* nella sezione *Programmi*, quindi seleziona *AdGuard* dall'elenco delle app installate e premi il pulsante *Disinstalla*, situato sopra l'elenco stesso. Conferma l'azione cliccando su *Disinstalla AdGuard* nella finestra che si apre. -![Windows 8 uninstallation](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win8-uninstall.png) +![Disinstallazione su Windows 8](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win8-uninstall.png) -- For Microsoft Windows 8.1: Right-click the *Start button* and select *Control Panel*. Click *Uninstall a program* in the *Programs* section, then select *AdGuard* from the list of installed apps and press the *Uninstall* button located right above the list. Confirm the action by clicking *Uninstall AdGuard* in the window that opens. +- Per Microsoft Windows 8.1: Clicca con il tasto destro del mouse sul pulsante *Start* e seleziona *Pannello di controllo*. Clicca su *Disinstalla un programma* nella sezione *Programmi*, quindi seleziona *AdGuard* dall'elenco delle app installate e premi il pulsante *Disinstalla*, situato sopra l'elenco stesso. Conferma l'azione cliccando su *Disinstalla AdGuard* nella finestra che si apre. -- For Microsoft Windows 7: Open *Start Menu*. In the search box, type *Control Panel*. Click *Uninstall a program* in the *Programs* section, then select *AdGuard* from the list of installed apps and press the *Uninstall* button located right above the list. Confirm the action by clicking *Uninstall AdGuard* in the window that opens. +- Per Microsoft Windows 7: Apri il *Menu Start*. Nella casella di ricerca, digita *Pannello di Controllo*. Clicca su *Disinstalla un programma* nella sezione *Programmi*, quindi seleziona *AdGuard* dall'elenco delle app installate e premi il pulsante *Disinstalla*, situato sopra l'elenco stesso. Conferma l'azione cliccando su *Disinstalla AdGuard* nella finestra che si apre. -![Windows 7 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win7-uninstall.png) +![Disinstallazione su Windows 7 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win7-uninstall.png) -### Advanced method {#advanced} +### Metodo avanzato {#advanced} -In case regular uninstall doesn't work for any reason, you can try to use an advanced method. First of all, you need to [download the uninstaller tool](https://cdn.adtidy.org/distr/windows/Uninstall_Utility.zip) created by our developers. Extract the archive to any folder on your PC and run the **Adguard.UninstallUtility.exe** file, and allow the app to make changes to your device. Then follow the instruction below: +Se la disinstallazione normale non dovesse funzionare per qualche motivo, puoi provare a utilizzare un metodo avanzato. Prima di tutto, devi [scaricare lo strumento di disinstallazione](https://cdn.adtidy.org/distr/windows/Uninstall_Utility.zip) creato dai nostri sviluppatori. Estrai l'archivio in qualsiasi cartella sul tuo PC ed esegui il file **Adguard.UninstallUtility.exe** e consenti all'app di apportare modifiche al tuo dispositivo. Poi, segui queste istruzioni: -- Select *AdGuard Ad Blocker* and *Standard* uninstall type, then click *Uninstall*. +- Seleziona *AdGuard Ad Blocker* e il tipo di disinstallazione *Standard*, quindi fai clic su *Disinstalla*. -![Standard uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) +![Disinstallazione standard *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) -- Click *OK* once the warning window pops up: +- Clicca su *OK* quando viene visualizzata la finestra di avviso: -![Standard uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![Avviso di disinstallazione standard *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) -- Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: +- Attendi fino al termine della disinstallazione: ci sarà una frase **Disinstallazione completata** e una richiesta di riavvio del computer: -![Uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard_complete.jpg) +![Disinstallazione terminata *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard_complete.jpg) -:::attenzione +:::caution -Follow the next steps only if performing the first two steps wasn’t enough for some reason. We strongly suggest contacting our support before using steps 3-4 of advanced uninstall instruction. +Segui i prossimi passaggi soltanto se l'esecuzione dei primi due passaggi non è stata sufficiente per qualche motivo. Consigliamo vivamente di contattare il nostro team di supporto prima di utilizzare i passaggi dal 3-4 delle istruzioni di disinstallazione avanzata. ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Seleziona *AdGuard Ad Blocker* e il tipo di disinstallazione *Estesa*, quindi fai clic su *Disinstalla*. Fare clic su *Sì, continua* nel prompt della finestra. -![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) +![Disinstallazione estesa *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) -- Click *OK* once the warning window pops up: +- Clicca su *OK* quando viene visualizzata la finestra di avviso: -![Extended uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![Avviso di disinstallazione estesa *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) -- Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: +- Attendi fino al termine della disinstallazione — ci sarà una frase **Disinstallazione completata** e una richiesta di riavvio del computer: -![Extended uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) +![Disinstallazione estesa terminata *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) -AdGuard is successfully uninstalled! +AdGuard è stato disinstallato con successo! diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 46c5570229f..e1b73207431 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + viene convertita in ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2987,7 +2986,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl - `example.com,example.org###adblock` — hides an element with attribute `id` equals `adblock` at `example.com`, `example.org` and all subdomains. - `~example.com##.textad` — hides an element with the class `textad` at all domains, except `example.com` and its subdomains. -**Limitations** +**Limitazioni** Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. @@ -3078,7 +3077,7 @@ CSS rules may operate differently [depending on the platform](#cosmetic-rules-pr ### Extended CSS selectors {#extended-css-selectors} -- [Limitations](#extended-css-limitations) +- [Limitazioni](#extended-css-limitations) - [Pseudo-class `:has()`](#extended-css-has) - [Pseudo-class `:contains()`](#extended-css-contains) - [Pseudo-class `:matches-css()`](#extended-css-matches-css) @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 36c286c0a1e..d7ad54799cc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ Manifest V3 では、拡張子ごとに静的ルールと正規表現ルール **動的ルール:** ルールの厳密な上限は**5,000**で、これには最大1,000個の正規表現ルールが含まれます。 -この制限を超えた場合、**5,000の変換されたルール**のみが次の順序で適用されます：最初に許可リスト、次にユーザールール、最後にカスタムフィルタ。 +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **変換されたルール**は、[宣言的コンバータ][github-declarative-converter]を使って > \[DNR形式]に変換されたルールです。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..d5fe511ea02 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -19,7 +19,7 @@ In this article, we'll guide you through the process of collecting debug logs, a :::note -AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. +AdGuard は、お客様のプライバシーを保護することに強くコミットしています。 We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. サポートチームにログを送信する前に、機密情報や共有したくない情報が含まれていないかどうか、ログファイルを確認してください。 そのような個人情報が含まれている場合は、削除してからログを送信することをお勧めします。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index c9b87e7d0bc..8f0e4522a16 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -19,7 +19,7 @@ Sometimes a regular log may not be sufficient to identify the origin of the prob :::note -AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. +AdGuard は、お客様のプライバシーを保護することに強くコミットしています。 We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. サポートチームにログを送信する前に、機密情報や共有したくない情報が含まれていないかどうか、ログファイルを確認してください。 そのような個人情報が含まれている場合は、削除してからログを送信することをお勧めします。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 2d1b1e970ec..710763b8ba0 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -131,7 +131,7 @@ If this setting is enabled, AdGuard will redirect DNS-over-HTTPS requests to the If this setting is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. -### Outbound proxy +### アウトバウンドプロキシ #### Show the Filter DNS requests setting diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 1b3851bf94e..a845fd963d8 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -5,7 +5,7 @@ sidebar_position: 3 :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for iOS」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for iOS」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md index 05f9aae3617..64f26c24964 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md @@ -1,5 +1,5 @@ --- -title: Browser Assistant +title: ブラウザアシスタント sidebar_position: 8 --- @@ -9,55 +9,55 @@ sidebar_position: 8 ::: -AdGuard Browser Assistant allows you to manage AdGuard protection directly from your browser. +AdGuard ブラウザ アシスタントを使って、直接ブラウザから AdGuard アプリの保護機能を管理できます。 ![The Assistant window \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/assistant_window.png) ## 仕組み -AdGuard Browser Assistant is a browser extension. It allows you to quickly manage the AdGuard app: +「AdGuard ブラウザアシスタント」はブラウザ拡張機能です。 この拡張機能があると、AdGuard アプリを素早くブラウザで管理できるようになります。具体的には、以下のことができます: -- Enable or disable protection for a specific website (a toggle under the website name) -- Pause protection for 30 seconds -- Disable protection (the pause icon in the upper right corner) -- Manually block an ad -- Open the filtering log -- Report incorrect blocking -- Open AdGuard settings -- View website certificate and manage HTTPS filtering (the lock icon next to the website name) +- 特定のウェブサイトに対する保護をオン・オフにする（ウェブサイト名の下にあるトグル） +- AdGuardによる保護を30秒間一時停止す +- 保護をオフにする（右上隅の一時停止アイコン） +- 手動で広告や要素を選んでブロックする +- フィルタリングログを開く +- 不適切なブロックを報告する +- AdGuard設定を開く +- ウェブサイトの証明書を表示する、HTTPSフィルタリングを管理する（ウェブサイト名の横にあるロック🔓アイコン） ## インストール方法 -When you install AdGuard for Mac, you will be prompted to install Browser Assistant for your default browser. If you skip this step, you can install it later. +AdGuard for Mac をインストールしている時、デフォルトブラウザ用ブラウザアシスタントのインストールが勧められます。 このステップをスキップしても、後でインストールできます。 -**From settings**: +**設定からのインストール方法**: -1. Open the AdGuard menu. -2. Click the gear icon and select _Preferences_. -3. Switch to the _Assistant_ tab. -4. Click _Get the Extension_ next to your default browser. -5. Install Assistant from your browser’s extension store. +1. AdGuard メニューを開きます。 +2. ⚙️アイコンをクリックして、「_設定_」を選択します。 +3. 「_アシスタント_」タブに切り替えます。 +4. デフォルトでお使いのブラウザの横にある「_拡張機能を入手_」をクリックします。 +5. お使いのブラウザの拡張機能ストアからAdGuardアシスタントをインストールします。 ![The Assistant tab](https://cdn.adtidy.org/content/kb/ad_blocker/mac/assistant.png) -**From the website**: +**ウェブサイトからのインストール方法**: -1. Open the [Assistant page](https://adguard.com/adguard-assistant/overview.html). -2. Under your browser name, select _Install_. -3. Install Assistant from your browser’s extension store. +1. [こちらのAdGuardアシスタントページ](https://adguard.com/adguard-assistant/overview.html)を開きます。 +2. お使いのブラウザ名の下にある「_インストール_」を選択します。 +3. お使いのブラウザの拡張機能ストアからAdGuardアシスタントをインストールします。 :::note -In rare cases, a browser may be incompatible with Assistant. To manage AdGuard from your browser, you can install the legacy Assistant instead. +まれに、ブラウザがアシスタントと互換性がない場合があります。 その場合、ブラウザからAdGuardを管理するには、代わりにレガシーアシスタントをインストールしてください。 ::: -## Legacy Assistant +## レガシーアシスタント -The legacy Assistant is the previous version of AdGuard Browser Assistant. It’s a userscript that doesn’t require additional installation. While the legacy Assistant does its job well, it has several drawbacks: +レガシーアシスタントは、AdGuardブラウザアシスタントの旧バージョンです。 追加のインストールを必要としないユーザースクリプトです。 従来のレガシーアシスタントはうまく機能しますが、いくつかの欠点があります: -- It has fewer features than the extension version. -- You have to wait for the userscript to be inserted into a webpage — sometimes it doesn’t load immediately. -- You can’t hide the Assistant icon on the page. +- 拡張機能版よりも機能が少ない +- ユーザースクリプトが Web ページに挿入されるまで待つ必要がある（すぐに読み込まれない場合もあります） +- ページ上のアシスタントアイコンを非表示にすることができません -We recommend that you use the legacy Assistant only if the new Assistant is not available. +新しいAdGuardアシスタントが使用できない場合にのみ、レガシーアシスタントを使用することをお勧めします。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md index 41233269cff..2cfe6d8f7bd 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md @@ -11,31 +11,31 @@ sidebar_position: 4 ## DNS通信を保護 -The _DNS_ section contains one feature, _DNS protection_, with multiple settings: +「_DNS_」セクションには、「_DNS通信保護_」という1つの機能があり、複数の設定があります: -- Providers +- プロバイダ - フィルタ -- Blocklist +- ブラックリスト - ホワイトリスト ![DNS](https://cdn.adtidy.org/content/kb/ad_blocker/mac/dns.png) -If you enable _DNS protection_, DNS traffic will be managed by AdGuard. +「_DNS通信を保護_」を有効にすると、DNSトラフィックはAdGuardによって管理されるようになります。 -### Providers +### プロバイダ -Under _Providers_, you can select a DNS server to encrypt your DNS traffic and block ads and trackers if necessary. We recommend AdGuard DNS. For more advanced configuration, you can [set up a private AdGuard DNS server](https://adguard-dns.io/welcome.html) or add a custom one by clicking the `+` icon in the lower left corner. +「_プロバイダー_」では、DNSサーバーを選択してDNSトラフィックを暗号化し、必要に応じて広告やトラッカーをブロックすることができます。 サーバーは AdGuard DNS がお勧めです。 より高度な設定を行うには、[プライベートAdGuard DNSサーバーを設定する](https://adguard-dns.io/welcome.html)か、左下隅にある`+`アイコンをクリックしてカスタムDNSサーバーを追加することができます。 ### フィルタ -DNS filters apply ad-blocking rules at the DNS level. Such filtering is less precise than regular ad blocking, but it’s particularly useful for blocking an entire domain. To add a DNS filter, click `+`. You can find more DNS filters at [filterlists.com](https://filterlists.com/). +DNSフィルタは、DNSレベルで広告ブロックルールを適用します。 DNSフィルタリングは、通常の広告ブロックよりも精度は落ちるが、ドメイン全体をブロックするのに特に有用です。 DNSフィルタを追加するには、`+`をクリックします。 [filterlists.com](https://filterlists.com) で様々なDNSフィルタを見つけることができます。 -### Blocklist +### ブラックリスト -Domains from this list will be blocked. To add a domain, click `+`. You can add domain names or DNS filtering rules using a [special syntax](https://adguard-dns.io/kb/general/dns-filtering-syntax/). +このリストにあるドメインはブロックされます。 ドメインを追加するには、`+`をクリックします。 また、[専用の構文](https://adguard-dns.io/kb/general/dns-filtering-syntax/)を使ってドメインやDNSフィルタリングルールを追加することもできます。 -To export or import a blocklist, open the context menu. +ブラックリストをエクスポートまたはインポートするには、コンテキストメニューを開きます。 ### ホワイトリスト -Domains from this list aren’t filtered. To add a domain, click `+`. To export or import an allowlist, open the context menu. +このリストにあるドメインはブロックされません。 ドメインを追加するには、`+`をクリックします。 ホワイトリストをエクスポートまたはインポートするには、コンテキストメニューを開きます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md index 437aeeff714..3516e8b914f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md @@ -9,25 +9,25 @@ sidebar_position: 8 ::: -AdGuard allows you to install extensions, or userscripts, to extend the functionality of the browser. AdGuard can work as a cross-browser userscript manager: you don’t have to install the same userscript for each browser. +AdGuardでは、ブラウザの機能を拡張するための拡張機能（ユーザースクリプト）をインストールすることができます。 AdGuardをクロスブラウザ・ユーザースクリプト・マネージャーとして使えます。（各ブラウザに同じユーザースクリプトをインストールする必要がなくなります。） -Some userscripts are pre-installed, others can be installed manually. +ユーザースクリプトには、プリインストールされているものもあれば、手動でインストールできるものもあります。 ![Extensions](https://cdn.adtidy.org/content/kb/ad_blocker/mac/extensions.png) -## AdGuard Assistant (legacy) +## レガシー AdGuard アシスタント (旧バージョン) -This userscript allows you to manage AdGuard protection directly from your browser. While the [new Assistant](/adguard-for-mac/features/browser-assistant) is a browser extension that can be installed from your browser’s store, the legacy Assistant is a userscript that doesn’t require additional installation. Some features are common to both assistants: +このユーザースクリプトを使って、直接ブラウザから AdGuard アプリの保護機能を管理できます。 [新しいアシスタント](/adguard-for-mac/features/browser-assistant)がブラウザのストアからインストールできるブラウザ拡張機能であるのに対し、このレガシーアシスタントは追加のインストールを必要としないユーザースクリプトです。 両アシスタントに共通する機能はこちら: -- Enable or disable protection for a specific website -- Pause protection for 30 seconds -- Manually block an ad -- Report incorrect blocking +- 特定のウェブサイトに対する保護をオン・オフにする +- AdGuardによる保護を30秒間一時停止す +- 手動で広告や要素を選んでブロックする +- 不適切なブロックを報告する -However, the new Assistant is more advanced. It also allows you to manage AdGuard protection for all websites, check the website’s certificate, manage HTTPS filtering, and open the filtering log or the app’s settings. We recommend that you use the legacy Assistant only if the new Assistant is not available. +しかし、新しいアシスタントはより進化しています。 すべてのウェブサイトでのAdGuard保護の管理、ウェブサイトの証明書の確認、HTTPSフィルタリングの管理、フィルタリングログやアプリの設定を開くことが可能です。 新しいAdGuardアシスタントが使用できない場合にのみ、レガシーアシスタントを使用することをお勧めします。 ## AdGuard Extra -This userscript solves the most complex ad blocking issues when regular rules aren’t enough. It also prevents websites from circumventing ad blockers and re-inserting blocked ads. We recommend that you keep it enabled at all times. +このユーザースクリプトは、通常のルールでは不十分で最も複雑な広告ブロック問題を解決します。 また、ウェブサイトが広告ブロッカーを回避し、ブロックされた広告を再度挿入することもも防いでくれます。 常に有効にしておくことをお勧めします。 -To install a userscript, click `+`. You can find userscripts at [greasyfork.org](https://greasyfork.org/). +ユーザースクリプトをインストールするには、「+」をクリックしてください。 [greasyfork.org](https://greasyfork.org) で様々なユーザースクリプトを見つけることができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md index d49110b4ea8..81abdb22ace 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md @@ -13,21 +13,21 @@ sidebar_position: 3 ![Filters](https://cdn.adtidy.org/content/kb/ad_blocker/mac/filters.png) -Filter lists are sets of rules written using a [special syntax](/general/ad-filtering/create-own-filters). AdGuard interprets and implements these rules to block ads, trackers, and annoyances. Some filters (for example, AdGuard Base filter, Tracking Protection filter, or EasyList) are pre-installed, others can be installed additionally. +フィルターリストは、[特別な構文](/general/ad-filtering/create-own-filters)を使って書かれたルールのセットです。 AdGuardは、これらのルールを解釈・実行し、広告、トラッカー、迷惑要素をブロックします。 一部のフィルタ（AdGuard ベースフィルタ、AdGuard 日本語フィルタ、AdGuard トラッキング防止フィルタ、EasyList など）はプリインストールされていますが、その他のフィルタは追加でインストールできます。 -We recommend enabling the following filters: +以下のフィルタを有効にしておくことをお勧めします: - AdGuard ベースフィルタ -- AdGuard Tracking Protection filter and AdGuard URL Tracking filter -- AdGuard Annoyances filter -- Filters for your language +- AdGuard 追跡防止フィルタと AdGuard URL追跡防止フィルタ +- AdGuard 迷惑要素フィルタ +- お使いの言語に応じたフィルタ（AdGuard 日本語フィルタなど） -These filters are important for blocking most ads, trackers, and annoying elements. For more advanced ad blocking, you can use custom filters and user rules. +これらのフィルタは、広告、トラッカー、迷惑要素のほとんどをブロックしてくれます。 より高度な広告ブロックには、カスタムフィルタとユーザールールを使用できます。 -To add a filter, click `+` in the lower left corner of the list. To enable a filter, select its checkbox. +フィルタを追加するには、リストの左下にある`+`をクリックします。 フィルタを有効にするには、そのチェックボックスにチェックを入れます。 ## ユーザールール -In AdGuard for Mac, user rules are located in _Filters_. To create a rule, click `+`. To enable a rule, select its checkbox. To export or import rules, open the context menu. +AdGuard for Mac では、ユーザールールは「_フィルタ_」にあります。 ルールを作成するには、`+`をクリックします。 ルールを有効にするには、そのチェックボックスを選択します。 ルールをエクスポートまたはインポートするには、コンテキストメニューを開きます。 ![User rules: context menu](https://cdn.adtidy.org/content/kb/ad_blocker/mac/rules.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md index 2556e708de0..a04f735a0de 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md @@ -9,9 +9,9 @@ sidebar_position: 2 ::: -## How to open app settings +## アプリ設定を開く方法 -To configure AdGuard for Mac, click the gear icon in the upper right corner of the main window and select _Preferences_. +AdGuard for Mac を設定するには、メインウィンドウの右上隅にある歯車アイコン「⚙️」をクリックし、「_設定_」を選択します。 ![Main window \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/main.png) @@ -19,22 +19,22 @@ To configure AdGuard for Mac, click the gear icon in the upper right corner of t ![General](https://cdn.adtidy.org/content/kb/ad_blocker/mac/general.png) -### Do not block search ads and website self-promoting ads +### 検索広告やウェブサイトの自己宣伝広告をブロックしない -This feature prevents AdGuard from blocking [search ads and self-promotions on websites](/general/ad-filtering/search-ads). This can be useful, for example, when you’re shopping online and want to see discounts offered by some websites. Instead of adding these websites to the allowlist, you can exclude self-promotions and search ads from filtering. +この機能がオンの場合、AdGuardは[ウェブサイト上の検索広告と自己宣伝](/general/ad-filtering/search-ads)をブロックしません。 これは、例えば、オンラインショッピングをしていて、いくつかのウェブサイトで提供されている割引を見たいときに便利です。 これらのウェブサイトをホワイトリストに追加する代わりに、自己宣伝や検索広告をフィルタリングから除外することができます。 -### Activate language-specific filters automatically +### 言語特化フィルタを自動的に有効にする -This feature detects the language of the website you’re visiting and automatically activates appropriate filters for more accurate ad blocking. This is especially helpful if you change languages frequently. +この機能は、あなたが訪問しているウェブサイトの言語を検出し、より正確な広告ブロックに適切なフィルタを自動的に有効にします。 これは特に、言語を頻繁に変更する場合に特に役立血ます。 -### Launch AdGuard at login +### ログイン時にAdGuardを起動する -This feature automatically launches AdGuard automatically after you restart your computer. This helps keep AdGuard protection active without having to manually open the app. +この機能がオンの場合、AdGuardはコンピュータの再起動後に自動的に起動します。 これにより、手動でアプリを開くことなく、AdGuardの保護を有効に保つことができます。 -### Hide menu bar icon +### メニューバーアイコンを非表示にする -This feature hides AdGuard’s icon from the menu bar but keeps AdGuard running in the background. If you want to disable AdGuard completely, click _Quit AdGuard_ in the main window menu. +この機能は、メニューバーからAdGuardのアイコンを非表示にしますが、AdGuardはバックグラウンドで実行し続けます。 AdGuard を完全に無効にしたい場合は、メインウィンドウの⚙️メニューで [_AdGuard を終了する_] をクリックします。 ### ホワイトリスト -Websites added to this list aren’t filtered. You can also access allowlisted websites from _User rules_. +このリストに追加されたウェブサイトはフィルタリングされません。 また、「_ユーザールール_」からも、ホワイトリストにあるウェブサイトにアクセスすることができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md index 128d939dd08..6bcda7cb2de 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md @@ -1,5 +1,5 @@ --- -title: Main window +title: メインウィンドウ sidebar_position: 1 --- @@ -9,6 +9,6 @@ sidebar_position: 1 ::: -The main window of AdGuard for Mac allows you to enable or disable the AdGuard protection. It also gives you a quick overview of the app’s stats: ads, trackers, and threats blocked since you’ve installed AdGuard or since your last stats reset. By clicking the gear icon, you can access settings, check for app and filter updates, contact support, and manage your license. +AdGuard for Mac のメインウィンドウでは、AdGuard による保護をオン・オフにすることができます。 また、AdGuardをインストールしてから（もしくは最後に統計情報をリセットしてから）ブロックされた広告数、トラッカー数、脅威数など、アプリの統計情報の概要も表示されます。 歯車アイコン「⚙️」をクリックすると、設定にアクセスしたり、アプリやフィルタのアップデートをチェックしたり、サポートに連絡したり、ライセンスを管理したりできます。 ![Main window \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/main.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md index 0b68d6e7592..89abe681a7c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md @@ -13,24 +13,24 @@ sidebar_position: 9 ![Network](https://cdn.adtidy.org/content/kb/ad_blocker/mac/network.png) -### Automatically filter applications +### アプリを自動的にフィルタリングする -By default, AdGuard blocks ads and trackers in most browsers ([Tor Browser is an exception](/adguard-for-mac/solving-problems/tor-filtering)). This setting allows AdGuard to block ads in apps as well. +デフォルトでは、AdGuardはほとんどのブラウザで広告とトラッカーをブロックします（[Tor Browserは例外です](/adguard-for-mac/solving-problems/tor-filtering)）。 この設定により、AdGuardはアプリ内の広告もブロックできるようになります。 -To manage filtered apps, click _Applications_. +フィルタリングされているアプリを管理するには、「_アプリ…_」をクリックします。 -### Filter HTTPS protocol +### HTTPSプロトコルをフィルタリングする -This setting allows AdGuard to filter the secure HTTPS protocol, which is currently used by most websites and apps. By default, websites with potentially sensitive information, such as banking services, are not filtered. To manage HTTPS exclusions, click _Exclusions_. +この設定により、AdGuardは、安全なHTTPSプロトコルをフィルタリングできるようになります。・（HTTPSは現在ほとんどのウェブサイトやアプリで使用されています。） デフォルトでは、銀行サービスのような潜在的に機密性の高い情報を含むウェブサイトはフィルタリングされません。 HTTPSの除外を管理するには、「_除外リスト_」をクリックします。 -By default, AdGuard doesn’t filter websites with Extended Validation (EV) certificates. If needed, you can enable the _Filter websites with EV certificates_ option. +デフォルトでは、Extended Validation (EV) 証明書を持つウェブサイトをAdGuardはフィルタリングしません。 必要であれば、「_EV証明書を持つウェブサイトをフィルタリング_」オプションを有効にすることができます。 -## Outbound proxy +## アウトバウンドプロキシ -You can set up AdGuard to route all your device’s traffic through your proxy server. +デバイスのすべてのトラフィックをプロキシサーバー経由でルーティングするよう、AdGuardを設定できます。 -## HTTP proxy +## HTTPプロキシ -You can use AdGuard as an HTTP proxy server. This will allow you to filter traffic on other devices connected to the proxy. +AdGuardをHTTPプロキシサーバーとして使用できます。 これにより、プロキシに接続されている他のデバイスのトラフィックをフィルタリングできるようになります。 -Make sure your Mac and your other device are connected to the same network and enter the proxy port on the device you want to route through your proxy server (usually in the network settings). To filter HTTPS traffic as well, [transfer AdGuard’s proxy certificate](http://local.adguard.org/cert) to this device. [Learn more about installing a proxy certificate](/guides/proxy-certificate) +Macと他のデバイスが同じネットワークに接続されていることを確認し、プロキシサーバーを経由させたいデバイスのプロキシポートを入力します（ポートは通常、ネットワーク設定で確認できます）。 HTTPSトラフィックもフィルタリングするには、このデバイスに[AdGuardのプロキシ証明書を転送](http://local.adguard.org/cert)してください。 [プロキシ証明書のインストールについて詳しくはこちら](/guides/proxy-certificate) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md index 746ca52c483..97c0a321064 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md @@ -1,5 +1,5 @@ --- -title: Security +title: セキュリティ sidebar_position: 6 --- @@ -9,16 +9,16 @@ sidebar_position: 6 ::: -## Phishing and malware protection +## フィッシングやマルウェアからの保護 ![Security](https://cdn.adtidy.org/content/kb/ad_blocker/mac/security.png) -AdGuard has a database of fraudulent, phishing, and malicious domains. If you enable _Phishing and malware protection_, AdGuard will warn you every time you’re about to visit a dangerous website. Even if only some parts of the website are dangerous, AdGuard will check it and display a warning. +AdGuardには、詐欺、フィッシング、悪意のあるドメインのデータベースがあります。 「フィッシングやマルウェアからの保護」を有効にすると、AdGuard は、危険なウェブサイトにアクセスしようとするたびに警告を表示します。 ウェブサイトの一部だけが危険であっても、AdGuardはそれをチェックし、警告を表示します。 -This is safe. As AdGuard checks hash prefixes, not URLs, it doesn’t know what websites you visit. [Learn more about AdGuard’s security checks](/general/browsing-security) +※ AdGuardはURLではなくハッシュプレフィックスをチェックするため、あなたがどのウェブサイトを訪問しているかはAdGuardにはわかりません。 [AdGuardのセキュリティチェックについて詳しくはこちら](/general/browsing-security) :::note -AdGuard is not an antivirus software. It can’t stop you from downloading suspicious files or delete existing viruses. +AdGuard はウイルス対策ソフトではありません。 不審なファイルのダウンロードを阻止したり、既存のウイルスを削除したりすることはできません。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md index 8435da4108d..e9268961995 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md @@ -9,8 +9,8 @@ sidebar_position: 5 ::: -## Advanced privacy protection +## 高度な追跡防止 ![Stealth Mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/stealth.png) -_Advanced privacy protection_ protects your privacy by deleting cookies, UTM tags, online counters, and analytics systems. It doesn’t let websites collect your IP address, device and browser parameters, search queries, and personal information. [Learn more about Stealth Mode settings](/general/stealth-mode) +「_高度な追跡防止_」は、Cookie、UTMタグ、オンラインカウンター、および分析システムを削除することにより、あなたのプライバシーを保護します。 ウェブサイトがあなたのIPアドレス、デバイスやブラウザのパラメータ、検索クエリ、個人情報を収集するのを防ぎます。 [ステルスモード設定の詳細についてはこちら](/general/stealth-mode) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md index 2efccac4ed1..24b596e447d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md @@ -3,15 +3,13 @@ title: 'インストール/アンインストール' sidebar_position: 2 --- -:::info - -この記事は、システムレベルでお使いのデバイスを保護する多機能な広告ブロッカー、「AdGuard for Mac」についてです。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +この記事は、システムレベルでお使いのデバイスを保護する多機能な広告ブロッカー、「AdGuard for Mac」についてです。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 ::: ## 動作環境 -**Operating system version:** macOS 10.15 (64 bit) or higher +**OSバージョン**: macOS 10.15 (64 bit) 以上 **RAM**: 2 GB以上 @@ -21,17 +19,17 @@ sidebar_position: 2 ## インストール方法 -To install AdGuard for Mac on your computer, launch your browser, type *adguard.com* in the address bar, and press **Download** [on the page that opens](https://adguard.com/download.html?auto=1). +AdGuard for Mac をインストールするには、ブラウザで _adguard.com_ を開き、ページ上の「**ダウンロード**」ボタンを押してください。 ![アプリをダウンロード *border](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-1.png) -Wait for *AdguardInstaller.dmg* to download and double-click its icon in the list of downloaded files on the Dock panel. +「*AdguardInstaller.dmg*」がダウンロード完了したら、クリックします。（Finderから開くこともできます。） -![Double-click to open the file](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-2.png) +![ダブルクリックでファイルを開く](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-2.png) 表示されたインストールアプリでAdGuardアイコンをダブルクリックしてください。 -![Double-click the AdGuard icon](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-3.png) +![AdGuardアイコンをダブルクリックします](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-3.png) AdGuard初インストールの際に、OSからの警告が表示されます。 「**開く**」を押してください。 @@ -45,7 +43,7 @@ AdGuard初インストールの際に、OSからの警告が表示されます ![必要なファイルがダウンロードされるまで待ちます](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-6.png) -AdGuardアプリを使用するにはmacOS管理者アカウントのパスワードが必要になります。 Enter the password when prompted in the dialogue box and press **OK**. +AdGuardアプリを使用するにはmacOS管理者アカウントのパスワードが必要になります。 パスワードを入力して「**OK**」を押してください。 ![パスワードを入力します。](https://cdn.adguard.com/public/Adguard/kb/installation/Mac/ja/mac-7.png) @@ -71,16 +69,16 @@ AdGuardアプリを使用するにはmacOS管理者アカウントのパスワ **※この手順は、技術的なことが分かる場合、またはAdGuardサポートに「アドバンスドアンインストール」を案内された場合にのみ使用してください。 また、最初に「通常のアンインストール」手順のステップをすべて行ってください。** -1. After that, delete following AdGuard files: - - /Library/Application Support/AdGuard Software/com.adguard.mac.adguard (folder) - - ~/Library/Preferences/com.adguard.mac.adguard.plist (file) - - ~/Library/Group\ Containers/TC3Q7MAJXF.com.adguard.mac (folder) - - /Library/LaunchDaemons/com.adguard.mac.adguard.adguard-pac.daemon.plist (file) - - /Library/LaunchDaemons/com.adguard.mac.adguard.adguard-tun-helper.daemon.plist (file) - - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-pac.daemon.log (file) - - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log (file) +1. 次に、以下のAdGuardファイルを削除してください: + - /Library/Application Support/AdGuard Software/com.adguard.mac.adguard (フォルダ) + - ~/Library/Preferences/com.adguard.mac.adguard.plist (ファイル) + - ~/Library/Group\ Containers/TC3Q7MAJXF.com.adguard.mac (フォルダ) + - /Library/LaunchDaemons/com.adguard.mac.adguard.adguard-pac.daemon.plist (ファイル) + - /Library/LaunchDaemons/com.adguard.mac.adguard.adguard-tun-helper.daemon.plist (ファイル) + - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-pac.daemon.log (ファイル) + - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log (ファイル) - To do so, open the Terminal app, then enter and execute the following commands: + これらのファイルを削除するには、Terminalアプリを開き、以下のコマンドを入力して実行してください: ```bash sudo rm -R "/Library/Application Support/AdGuard Software/com.adguard.mac.adguard" @@ -94,12 +92,12 @@ AdGuardアプリを使用するにはmacOS管理者アカウントのパスワ sudo rm /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log ``` -1. Run the **Activity Monitor** app. +1. 「**アクティビティモニタ**」アプリを起動します。 1. 検索ツールを使用して「**cfprefsd**」プロセスを見つける ![アクティビティモニタを実行する](https://cdn.adtidy.org/content/kb/ad_blocker/mac/22.jpg) -1. ユーザーで実行されているプロセス（ルートで実行されているものではないほう）を停止します。 そうするにはプロセスをクリックして、左上の「X」をクリックしてください。 Confirm the action in the dialogue window. +1. ユーザーで実行されているプロセス（ルートで実行されているものではないほう）を停止します。 そうするにはプロセスをクリックして、左上の「X」をクリックしてください。 表示されたダイアログで確認してください。 ![確認](https://cdn.adtidy.org/content/kb/ad_blocker/mac/33.jpg) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 9f61bd58f86..e014fc6a6e3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -21,7 +21,7 @@ sidebar_position: 9 ## 高度な設定 -### Network settings +### ネットワーク設定 #### `network.extension.exclude.domains` @@ -71,7 +71,7 @@ sidebar_position: 9 #### `network.https.ech.enabled` -ECH Configs Lists内のconfigsを検索するために、ローカルDNSプロキシを使用します。 If found, encrypts Client Hellos. +ECH Configs Lists内のconfigsを検索するために、ローカルDNSプロキシを使用します。 見つかった場合、Client Hellosを暗号化します。 #### `network.https.enforce.certificate.transparency` @@ -89,7 +89,7 @@ Chrome Certificate Transparency Policy（証明書透過性ポリシー）に基 `true` を設定すると、LoopBack フィルタリングが有効になります。 -### DNS settings +### DNS設定 #### `dns.proxy.bootstrap.ips` @@ -159,7 +159,7 @@ Chrome Certificate Transparency Policy（証明書透過性ポリシー）に基 応答からECH（Encrypted Client Hello）パラメータを削除します。 -### Stealth Mode settings +### ステルスモード設定 #### `stealth.antidpi.http.split.fragment.size` @@ -177,7 +177,7 @@ HTTPメソッドとURLの間に余分なスペースを追加し、「Host: 」 ここでは、断片化が実行される場合に、最初のフラグメントを送信した後の遅延をミリ秒単位で指定できます。 -### Subscription link interception settings (userscripts and filters) +### （ユーザースクリプトとフィルタへの）購読リンクの遮断設定 #### `subscription.link.interception.userscript` diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index a3998273b62..57117cd8265 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Monterey または Big Sur で、「ネットワーク拡張」モードのAdGua #### レガシーAPIを使用したVPNアプリ -AdGuard はシステム設定では VPN として表示されますが、他の VPN ベースのアプリと一緒に動作しても競合は発生しません。 However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +AdGuard はシステム設定では VPN として表示されますが、他の VPN ベースのアプリと一緒に動作しても競合は発生しません。 ただし、App Store以外でダウンロードしたVPNベースのアプリを使用する場合は、古いVPN APIを使用しているリスクがある場合はフィルタリングから除外する必要があります: 1. AdGuardのメニューを開きます。 1. *設定...* を選択します。 @@ -79,9 +79,9 @@ AdGuard はシステム設定では VPN として表示されますが、他の ### Little Snitch 5 との互換性 -現時点では、AdGuard のネットワーク拡張モードは [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html)と互換性がありません。 When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. この問題は Big Sur のバグによって引き起こされており、我々はすでに Apple にその旨を通知しています。 このため、この問題は今後のmacOSアップデートで解決されると思われます。 +現時点では、AdGuard のネットワーク拡張モードは [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html)と互換性がありません。 両方が実行されている場合、AdGuardによってフィルタリングされていなくても、さまざまなアプリの動作に問題が発生するリスクがあります。 この問題は Big Sur のバグによって引き起こされており、我々はすでに Apple にその旨を通知しています。 このため、この問題は今後のmacOSアップデートで解決されると思われます。 -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Apple がバグを修正するまでは、Big Sur で AdGuard を Little Snitch と併用する場合は、 [**自動プロキシ**](#automatic-proxy) フィルタリング モードに切り替えることをお勧めします。 +ただし、Little Snitch で接続監視を無効にしても、Little Snitch 拡張機能がシステムメモリからアンロードされないため、問題は解決されません。 Apple がバグを修正するまでは、Big Sur で AdGuard を Little Snitch と併用する場合は、 [**自動プロキシ**](#automatic-proxy) フィルタリング モードに切り替えることをお勧めします。 ### ローカルプロキシとの互換性問題 @@ -106,7 +106,7 @@ Big Surにおいて、AdGuard for Mac でアップストリームプロキシを [Shadowsocks](https://shadowsocks.org)用のアップストリームプロキシを設定する方法の例です。 -まず第一に、プロキシを動作させるサーバサイドが必要になります。 たいていの場合、このようなJSONファイルを使うことになります（以下の`サーバー`と`パスワード`値はランダムに選んであります）: +まず第一に、プロキシを動作させるサーバサイドが必要になります。 たいていの場合、このようなJSONファイルを使うことになります（以下の`server`と`password`値はランダムに選んであります）: ```json { @@ -121,7 +121,7 @@ Big Surにおいて、AdGuard for Mac でアップストリームプロキシを :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +開始方法の詳細については、[Shadowsocks のウェブサイト](https://shadowsocks.org/guide/what-is-shadowsocks.html)をご覧ください。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 78a76998031..c9ba7207118 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ sidebar_position: 3 ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". これは High Sierra で登場した新しいセキュリティメカニズムであり、サードパーティのシステム拡張のインストールを明示的に許可する必要があります。 AdGuard のインストールを完了するには、 *システム環境設定* → *セキュリティ & プライバシー* → *一般* で拡張機能の読み込みを手動で許可する必要があります。 +macOS High Sierra (またはそれ以降のバージョン) に AdGuard をインストールしているときに、「システム拡張がブロックされました」というメッセージが表示される場合があります。 これは High Sierra で登場した新しいセキュリティメカニズムであり、サードパーティのシステム拡張のインストールを明示的に許可する必要があります。 AdGuard のインストールを完了するには、 *システム環境設定* → *セキュリティ & プライバシー* → *一般* で拡張機能の読み込みを手動で許可する必要があります。 ![設定で拡張機能のインストールを許可する](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 55ea51f3f8c..f8c88572066 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ Monterey では、iCloud プライベート リレーが登場しました。 Ma 1. iCloud プライベートリレーは、ライブラリレベル（AdGuard が動作するソケットレベルに到達する前）で接続に適用されます。 2. iCloud プライベートリレーは QUIC を使用しますが、HTTP/3 フィルタリングはまだ利用できないため、AdGuard はQUICをフィルタリングできません。 -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. その結果、AdGuard は iCloud プライベートリレー のトラフィックを含む QUIC をブロックしてしまいます。そうしないと、広告をブロックすることは不可能になるからです。 4. iCloud プライベートリレーを使用し、AdGuard を「split-tunnel」モードに切り替えると、Safari で Web サイトを開くことができなくなります。 5. Monterey でこの問題を回避するには、「デフォルトルート」ルールを適用します。 プライベートリレーはそのルールを検出すると、自動的に無効になります。 つまり、AdGuard は Monterey 上でシームレスに動作しますが、その場合、iCloud プライベート リレーは無効になります。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1abaf8f36e8..f5cb777d34b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ sidebar_position: 5 :::note リマインダー -AdGuard for Safari は無料で [App Store からダウンロード](https://apps.apple.com/app/adguard-for-safari/id1440147259)できます。 A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari は無料で [App Store からダウンロード](https://apps.apple.com/app/adguard-for-safari/id1440147259)できます。 詳しいセットアップ手順は、[こちらのナレッジベース記事](/adguard-for-safari/installation/)にあります。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index d8de647ee77..7c366181d49 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: ユーザールール sidebar_position: 4 --- -ユーザールールは、広告ブロックの効果をカスタマイズするために使用することができます。 ユーザールールは、手動で追加することも、インポートすることも、ページ上の要素をブロックしたときに自動的に作成することもできます。 To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +ユーザールールは、広告ブロックの効果をカスタマイズするために使用することができます。 ユーザールールは、手動で追加することも、インポートすることも、ページ上の要素をブロックしたときに自動的に作成することもできます。 独自のフィルタリングルールを追加するには、[専用の構文](/general/ad-filtering/create-own-filters)を使ってください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index 08d581bd52a..d6b303e0d46 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -1,5 +1,5 @@ --- -title: How to collect logs in AdGuard for Safari +title: AdGuard for Safari のログを収集する方法 sidebar_position: 4 --- @@ -9,9 +9,9 @@ sidebar_position: 4 ::: -AdGuard for Safari で発生した問題を分析および診断するために、AdGuardのお客様サポートサービスはログファイルを必要とする場合があります。 このようなログファイルには、エラーやその他のソフトウェア・イベントの記録が含まれます。 Below are brief instructions on how to collect logs and send them to support if necessary. +AdGuard for Safari で発生した問題を分析および診断するために、AdGuardのお客様サポートサービスはログファイルを必要とする場合があります。 このようなログファイルには、エラーやその他のソフトウェア・イベントの記録が含まれます。 以下は、ログを収集し、必要に応じてAdGuardサポートに送信する方法についての簡単な説明です。 -### How to collect logs +### ログを収集する方法 1. AdGuard for Safari アプリを開きます。 2. 下にスクロールし、「_ログをエクスポートする_」をクリックします。 @@ -21,10 +21,10 @@ AdGuard for Safari で発生した問題を分析および診断するために :::note -AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/safari.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. +AdGuard は、お客様のプライバシーを保護することに強くコミットしています。 [プライバシーポリシー](https://adguard.com/privacy/safari.html)を厳守し、ユーザーの個人情報を収集することは一切ありません。 サポートチームにログを送信する前に、機密情報や共有したくない情報が含まれていないかどうか、ログファイルを確認してください。 そのような個人情報が含まれている場合は、削除してからログを送信することをお勧めします。 ::: -1. Open the [AdGuard for Safari GitHub repo](https://github.com/AdguardTeam/AdGuardForSafari/issues) and click _New issue_. -2. Send the log file to devteam@adguard.com. Include the time of the bug and attach a link to your issue or its number (it appears as #number next to the title). - Alternatively, you can upload the log file to Google Drive and send it to devteam@adguard.com. Add the file link to your GitHub issue. +1. [AdGuard for Safari の GitHub リポジトリ](https://github.com/AdguardTeam/AdGuardForSafari/issues)を開き、「_New issue_」をクリックします。 +2. ログファイルを devteam@adguard.com に送信してください。 メールにバグの発生時刻とissueへのリンクまたはissue番号（番号はissueタイトルの横に#○○として表示されます）を記載してください。 + もう一つの方法として、ログファイルをGoogle Driveにアップロードして、devteam@adguard.com にリンクを送りください。 GitHub のissueにもファイルへのリンクを追加してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..f48467e087c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -1,54 +1,54 @@ --- -title: Documentation for admins +title: 管理者向けドキュメンテーション sidebar_position: 5 --- -This page describes the features and details of AdGuard’s central management of policies and preferences. +このページでは、AdGuard のポリシーと環境設定の一元管理の機能と詳細について説明しています。 -## 1. Download the MSI {#msi-download} +## 1. MSIをダウンロードする {#msi-download} -Download the [AdGuard MSI x86](https://cdn.adtidy.org/distr/windows/AdGuard_x86.msi) +[AdGuard MSI x86 をダウンロード](https://cdn.adtidy.org/distr/windows/AdGuard_x86.msi) -Download the [AdGuard MSI x64](https://cdn.adtidy.org/distr/windows/AdGuard_x64.msi) +[AdGuard MSI x64 をダウンロード](https://cdn.adtidy.org/distr/windows/AdGuard_x64.msi) -## 2. Configure the settings for your network {#settings-configuring} +## 2. お使いのネットワーク用の設定を構成する {#settings-configuring} -On machines that are joined to an Active Directory domain, policy settings may also be stored in the registry under `HKEY_LOCAL_MACHINE` in the following path: `Software\Policies\AdGuard\`. +Active Directoryドメインに参加しているマシンでは、ポリシー設定はレジストリ`HKEY_LOCAL_MACHINE`の下のパスに格納されることができます： `Software\Policies\AdGuard\` -The only supported policy is `LicenseKey`. If this policy is set, AdGuard will prefer it over what user can enter in the interface. This license key will be used for checking license status. +サポートされているポリシーは `LicenseKey` のみです。 このポリシーが設定されている場合、AdGuardは、ユーザーがインターフェイスに入力できる内容よりも、このポリシーを優先します。 このライセンスキーは、ライセンスステータスの確認に使用されます。 -## 3. Make sure that AdGuard servers are available {#servers-available} +## 3. AdGuardサーバーが利用可能であることを確認する {#servers-available} -AdGuard connects to two hosts: `api.adguard.org` and `filters.adtidy.org`. Make sure that both servers are available. +AdGuardは、`api.adguard.org` と `filters.adtidy.org` という2つのホストに接続します。 両方のサーバーが利用可能であることを確認してください。 -## 4. Push the MSI out to your network {#msi-push} +## 4. MSIをお使いのネットワークにプッシュする {#msi-push} -If you usually use SMS or other tools, use them to push out the AdGuard MSI just as you would normally do with any other installation bundle. +通常、SMS またはその他のツールを使用している場合は、他のインストー ルバンドルと同様に、それらを使用して AdGuard MSI をプッシュします。 -Otherwise, you can run the MSI on the target machine directly (and silently) with this command: `Msiexec /q /i AdGuard.msi` +そうでない場合は、こちらのコマンドを使用して、ターゲットマシンで直接（そしてsilentに）MSIを実行することができます： `Msiexec /q /i AdGuard.msi` -If you need to roll out an update, use this command: `Msiexec /q /i AdGuard.msi REINSTALL=ALL REINSTALLMODE=vomus` +アップデートを展開する必要がある場合は、こちらのコマンドを使用します： `Msiexec /q /i AdGuard.msi REINSTALL=ALL REINSTALLMODE=vomus` :::note -You must run these commands with admin privileges. +これらのコマンドは管理者権限で実行する必要があります。 ::: -If you want to install AdGuard on a Windows 7 computer, make sure that it has .NET 4 Client Profile installed: https://www.microsoft.com/en-us/download/details.aspx?id=24872 +AdGuard を Windows 7 搭載コンピュータにインストールする場合は、.NET 4 Client Profile がインストールされていることを確認してください: https://www.microsoft.com/en-us/download/details.aspx?id=24872 :::note -If you have installed AdGuard for Windows from an MSI file, AdGuard will not be updated automatically. To allow manual updates: +AdGuard for Windows を MSI ファイルからインストールした場合、AdGuard は自動的に更新されません。 手動アップデートを許可するには： -- In versions released after v7.16, delete the `ForbidCheckUpdates` parameter or set its value to `NO` (case-insensitive) in the registry under `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard`. +- v7.16以降のバージョンでは、レジストリの`HKEY_LOCAL_MACHINE`にある`ForbidCheckUpdates`パラメータを削除するか、その値を`NO`（大文字と小文字の区別なし）に設定します。 -- In v7.16 and earlier versions, set to `YES` (case-insensitive) the `AllowCheckUpdates` parameter for the `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard` key on x86 OS or `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adguard` key on x64 OS. Any other value or no value for this parameter will disable automatic updates. +- v7.16 以前のバージョンでは、x86 OS の `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard` キーまたは x64 OS の `HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adguard` キーの `AllowCheckUpdates` パラメータを `YES` (大文字と小文字の区別なし) に設定します。 それ以外の値、またはこのパラメータに値がない場合、自動アップデートは無効になります。 -Please note that such installation of the application and manual updates are not recommended and can cause technical problems. +※このようなアプリのインストールや手動アップデートは推奨されておらず、技術的な問題を引き起こす可能性があることにご注意ください。 ::: -## 5. Test your installation {#installation-test} +## 5. インストールをテストする {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +ターゲットマシンでAdGuardを起動します。 指定したライセンスが使用されていることを確認するために、ライセンス画面を開いてください。 AdGuardにライセンスキーを検証させるには、「ステータスを更新」をクリックする必要があるかもしれません。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..9c166190f2a 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -1,45 +1,45 @@ --- -title: Browser Assistant +title: ブラウザアシスタント sidebar_position: 3 --- -AdGuard Assistant’s primary function is to manage filtering directly from the browser. It has existed for quite a long time, and its form and content have changed. More precisely, it used to be a mere userscript incorporated into AdGuard for Windows app and became a full-fledged browser extension. Now it yields more benefits. +AdGuard アシスタントの主な機能は、直接ブラウザからフィルタリングの管理を可能にすることです。 AdGuard アシスタントは結構前から存在していて、その形も内容も変化してきました。 より正確に言いますと、もともと AdGuard for Windows アプリに組み込まれた単なるユーザースクリプトでしたが、現在は本格的なブラウザ拡張機能となっています。 便利な機能も前より多くなっています。 -![Browser Assistant *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/assistant-menu.png) +![ブラウザアシスタント *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/assistant-menu.png) -## Benefits +## メリット -### Independence +### 独立性 -AdGuard Browser Assistant is a browser extension, it is installed in a browser, so there is no need to wait for the userscript to be injected into the filtered web page, as it was with the preceding one. In other words, it is more autonomous from the main AdGuard app. Still, Browser Assistant needs the installed AdGuard for Windows, because there is no point in using the extension without the app. +AdGuard ブラウザアシスタントはブラウザ拡張機能であり、ブラウザにインストールされるため、前みたいにユーザースクリプトがフィルタリングされるウェブページに挿入されるのを待つ必要はありません。 言い換えれば、メインのAdGuardアプリから独立しています。 それでも、ブラウザアシスタントが使いものになるには、AdGuard for Windows がパソコンにインストールされている必要があります。メインのアプリなしで拡張機能を使用しても意味がないためです。 -### Compatibility with the main app +### メインのAdGuardアプリとの互換性 -If you got into the habit of using our previous [AdGuard Ad Blocker extension](/adguard-browser-extension/compatibility), you might like the solution that we have developed for the new Browser Assistant. +以前の[AdGuard広告ブロッカー拡張機能](/adguard-browser-extension/compatibility)の使用習慣があれば、新しいブラウザアシスタントのために私たちが開発した解決策を気に入るかもしれません。 -Background information: +背景についての解説: -In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. +前のAdGuardブラウザ拡張機能のバージョン（v3.5以前）では、AdGuard for Windows アプリと一緒にインストールしている場合、拡張機能がアシスタントの機能を担い、フィルタリングを停止し、フィルタリングをアプリに依存していました。 -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +拡張機能とアプリは連携して機能していましたが、時々統合が失敗することがありました。 AdGuardのデスクトップアプリ版が通常提供する保護機能は、特定のサイトで停止してしまったりして、そこでより弱いブラウザ拡張機能版だけが保護機能を提供したりしました。 -When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. +ブラウザアシスタントを使用すると、根本的に競合がないため、これらの問題を気にする必要がなくなります。 ブラウザアシスタントの役割は明確であり、メインアプリの機能を妨げることはできないため、心配しなくて済みます。 -## Separate tab in Settings +## 設定のでの専用タブ -The new Browser Assistant has its own tab in AdGuard for Windows settings, along with Stealth Mode, Browsing security, Parental Control and others. There you will find a link to download the extension for your default browser. Besides, there is a checkbox to enable the legacy Assistant. +ステルスモード、ブラウジングセキュリティ、ペアレンタルコントロールなどと一緒に、AdGuard for Windows 設定において新しいブラウザアシスタントの専用タブがあります。 そこには、お使いのデフォルトブラウザ用AdGuardアシスタント拡張機能をダウンロードするためのリンクがあります。 さらに、レガシー版アシスタントを有効にするチェックボックスもあります。 -![Settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) +![設定 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) -## Legacy Assistant +## レガシー版アシスタント -Legacy Assistant is the previous version of Assistant, which is a mere userscript, not a browser extension. Basically, there are two cases when you might want to pick it instead of the new Browser Assistant: +レガシー版アシスタントはAdGuardアシスタントの旧バージョンであり、ブラウザ拡張機能ではなく、単なるユーザースクリプトです。 新しいブラウザーアシスタントの代わりにレガシー版を使った方がいいケースは、基本的に以下の2つだけです: -1. The new Assistant is not available for your browser. -1. You are used to the green shield icon and want to leave things as they were. +1. 新しいアシスタントをお使いのブラウザでご利用いただけない場合 +1. ページの右下に表示される緑色の盾アイコンに慣れていて、そのままにしておきたい場合 -## How to install AdGuard Browser Assistant +## AdGuard ブラウザアシスタントをインストールする方法 -If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. +お使いのデフォルトブラウザにブラウザアシスタントをインストールしたい場合は、AdGuardアプリの設定から直接インストールできます。さらに、設定からは他のブラウザ版アシスタントをインストールすることもできます。 -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard ブラウザアシスタントは、Chrome、Firefox、Edge、Opera、Yandex など、すべての一般的なブラウザで利用できます。 各ブラウザ用のアシスタントをインストールするには、[こちらのAdGuardページ](https://adguard.com/adguard-assistant/overview.html)にアクセスし、対象ブラウザのアイコンをクリックして、*インストール*ボタンをクリックします。 　 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 3f1a71b6959..1ad3b4d15b3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard アシスタントは、[新しいアシスタント](/adguard-for-windo これは、ブロックされた広告を再度挿入する手法（いわゆる広告ブロッカー回避や広告再投入という技術）への対処法として設計されたカスタム拡張機能です。 どちらも、広告主の間で人気が高まり続けている高度な広告ブロッカー対策手法です。 -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra は、基本的にミニプログラムで、サイトがブロッカーを回避するために上記の方法を使用することがより困難になるように、ページの動作方法を変更します。 **AdGuard ポップアップブロッカー** -この拡張機能は、ウェブページ閲覧時にポップアップウィンドウが開かないようにしてくれます。 ポップアップの中には、サイト管理のための設定や、リンクをクリックしたときに表示される追加参考情報が含まれているような、役に立つとされるポップアップもたまにあります。 そのため、必要に応じてAdGuard ポップアップブロッカーをオフにすることができます。 また、この拡張機能は、AdGuard の除外リストに追加されたウェブサイトでも機能しません。 デフォルトではオフになっていますが、アプリの設定でオンにすることができます。 You will find more detailed information about this extension in our Knowledge Base. +この拡張機能は、ウェブページ閲覧時にポップアップウィンドウが開かないようにしてくれます。 ポップアップの中には、サイト管理のための設定や、リンクをクリックしたときに表示される追加参考情報が含まれているような、役に立つとされるポップアップもたまにあります。 そのため、必要に応じてAdGuard ポップアップブロッカーをオフにすることができます。 また、この拡張機能は、AdGuard の除外リストに追加されたウェブサイトでも機能しません。 デフォルトではオフになっていますが、アプリの設定でオンにすることができます。 この拡張機能についての詳細情報はKnowledge Base（ナレッジベース）をご確認ください。 **Web of Trust** @@ -41,7 +41,7 @@ Web of Trustを使って、各ウェブサイトの、ユーザーの意見に ### ネットワーク -このモジュールはネットワークフィルタリング専用のもので、ネットワーク関連の追加オプションがあります。 Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. これらは、あなたのウェブスペースをより良くフィルタリングするための重要な追加予防措置です。 現在、ほとんどのウェブサイトがHTTPSを使用しており、広告も同様です。 From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +このモジュールはネットワークフィルタリング専用のもので、ネットワーク関連の追加オプションがあります。 このうち、「トラフィックフィルタリングを有効にする」と「HTTPS をフィルタリングする」は、デフォルトで有効になっています。 これらは、あなたのウェブスペースをより良くフィルタリングするための重要な追加予防措置です。 現在、ほとんどのウェブサイトがHTTPSを使用しており、広告も同様です。 youtube.com、facebook.com、x.comなど多くのサイトでは、HTTPSフィルタリングなしでは広告を削除することができません。 そのため、特別な理由がない限り、「HTTPSをフィルタリングする」機能は有効にしておいてください。 ![ネットワーク設定 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 44c504170ba..4a204ba76c6 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ sidebar_position: 2 ### 一般設定 -ここでは、言語とカラーテーマ（ダーク・ライト）の設定、システム起動時のAdGuardの起動と自動アップデートの有効化、アップデートチャネルの選択、フィルタ更新チェック間隔の指定などを行うことができます。 Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +ここでは、言語とカラーテーマ（ダーク・ライト）の設定、システム起動時のAdGuardの起動と自動アップデートの有効化、アップデートチャネルの選択、フィルタ更新チェック間隔の指定などを行うことができます。 また、AdGuard for Windows が正常に動作せず、サポートチームから[「デバッグログ」を収集する](/adguard-for-windows/solving-problems/adguard-logs.md)ように依頼された場合も、「設定」が役に立ちます。 ![高度な設定 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ AdGuard for Windows の「DNS通信を保護」モジュールでは、広告と このモジュールは、ブラウザで開かれたウェブページの内容をチェックし、子供にとって好ましくない内容（大人向けの画像やテキスト、下品な言葉、暴力、薬物の宣伝など）のものをフィルタリングします。 ペアレンタルコントロールの設定はパスワードで保護されているため、子供が自分で制限をオフにすることはできません。 このモジュールは、好ましくないサイトへの誘導をブロックするだけでなく、検索結果から子供に不適切なリンクを削除することもできます。 -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. 「実行形式ファイルのダウンロードをブロック」を有効にしますと、お子様のコンピュータへのソフトウェアのダウンロードとインストールを防ぎます。 _ペアレンタルコントロール_モジュールにはさらに 2 つのオプションがあります。_ペアレンタルコントロール_で保護対象の特定の Windows ユーザーを指定するオプションと、AdGuard 設定が変更されないようにパスワードを設定するオプションです。 +_ペアレンタルコントロール_モジュールでは、「_セーフサーチ_」を有効にし、「_ブラックリスト_」と「_ホワイトリスト_」を管理して、この機能の動作をカスタマイズすることができます。 「実行形式ファイルのダウンロードをブロック」を有効にしますと、お子様のコンピュータへのソフトウェアのダウンロードとインストールを防ぎます。 _ペアレンタルコントロール_モジュールにはさらに 2 つのオプションがあります。_ペアレンタルコントロール_で保護対象の特定の Windows ユーザーを指定するオプションと、AdGuard 設定が変更されないようにパスワードを設定するオプションです。 ![ペアレンタルコントロール \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index aca84f40f78..15ad8c42e3c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 ::: @@ -19,88 +19,88 @@ sidebar_position: 2 **ブラウザ:** Microsoft Edge、Microsoft Internet Explorer (全バージョン)、Opera、Google Chrome、Yandex.Browser、Mozilla Firefox、およびその他のブラウザ。 -## AdGuard installation +## AdGuard for Windows インストール方法 Microsoft Windowsを搭載したPCやタブレットでAdGuardを使用するには、インストールパッケージをダウンロードして、インストールプログラムを起動する必要があります。 以下の操作を行ってください: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. [AdGuard ホームページ](http://adguard.com)にアクセスし、[*ダウンロード*](https://adguard.com/download.html?auto=1)をクリックします。 - ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) + ![AdGuardをダウンロード](https://cdn.adguard.com/public/Adguard/kb/installation/Win/ja/W1-ja.png) -2. When the download is finished, press the *Open* button shown in the Downloads bar or click the file name *adguardInstaller.exe*. +2. ダウンロードが完了しましたら、ダウンロードバーにある「*開く*」ボタンを押すか、「*adguardInstaller.exe*」というファイルを押してください。 - ![Press "Run"](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/click-download.png) + ![「実行」を押す](https://cdn.adguard.com/public/Adguard/kb/installation/Win/ja/W2-ja.png) -3. You’ll see the User Account Control dialogue box requesting to allow the app to make changes to your PC. Click *Yes*. +3. ユーザーアカウント制御のダイアログボックスが表示され、アプリがPCに変更を加えることを許可するよう求められた場合は、 「*はい*」をクリックしてください。 - ![Allow changes *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) + ![変更を許可 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/allow-changes.png) -4. Next, choose the folder on your PC for the app to be installed to. +4. 次に、PC上でAdGuardのインストール先を選びます。 - ![Choose folder *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/install-wizard.png) + ![フォルダを選択 *border](https://cdn.adguard.com/public/Adguard/kb/installation/Win/ja/W3-ja.png) - If you do not agree with the default installation path, press *Browse*, select the folder for AdGuard installation in the *Browse For Folder* window, and confirm your choice by clicking *OK*. You can also install AdGuard to a new folder by clicking *Make New Folder* and entering its name. To create a desktop shortcut for AdGuard, check the *Create a desktop shortcut* box. Press *Install* to proceed with installation. + デフォルトのインストール先を変更したい場合は、「*参照*」を押して、「*フォルダを参照*」ウィンドウでAdGuardをインストールするフォルダを選択し、「*OK*」をクリックして選択を確定してください。 また、「*新規フォルダを作成*」をクリックしてフォルダ名を入力することで、AdGuardを新しいフォルダにインストールすることもできます。 AdGuardのデスクトップショートカットを作成するには、「*デスクトップにショートカットを作成*」にチェックを入れます。 「*インストール*」を押して、インストールを続行します。 - ![Start installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/start-install.png) + ![インストール開始 *border](https://cdn.adguard.com/public/Adguard/kb/installation/Win/ja/W4-ja.png) -5. Wait for the installation to complete and click *Finish*. +5. インストールが完了しましたら、「*終了*」を押します。 - ![Complete installation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/finish-install.png) + ![インストール完了 *border](https://cdn.adguard.com/public/Adguard/kb/installation/Win/ja/W5-ja.png) - Congratulations! You have successfully installed AdGuard on your computer. On the screen you will see the main window where you can change the app’s settings. + これで、 お使いのコンピュータへのAdGuardインストールは完了です。 画面には、アプリの設定を変更できるメインウィンドウが表示されます。 ## AdGuard for Windows をアンインストールする方法 {#uninstall} ### 通常方法 -If you need to uninstall or reinstall AdGuard, do the following: +AdGuardをアンインストールまたは再インストールする必要がある場合は、以下の操作を行ってください。 - 【Microsoft Windows 10・11 の場合】 「*スタート*」をクリックして*スタートメニュー*を開き、「*設定*」を選択します。 開いたウィンドウで*アプリ*アイコンをクリックします。 *アプリ*ウィンドウの左側のリストから、「*アプリと機能*」を選択します。 「*AdGuard*」をリストから選択し、「*アンインストール*」をクリックします。 開いたダイアログボックスで「*アンインストール*」をクリックして確認します。 -![Windows 10 & 11 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win10-uninstall.png) +![Windows 10 と 11 でのアンインストール *border](https://cdn.adguard.com/public/Adguard/kb/installation/Win/ja/W7-ja.png) -- For Microsoft Windows 8: Right-click the *empty space* in the lower left corner of the task bar and select *Control Panel*. *プログラム*セクションで*プログラムのアンインストール*をクリックし、インストールされているアプリのリストから*AdGuard*を選択して、リストの真上にある*アンインストール*ボタンを押します。 開いたウィンドウで「*AdGuardのアンインストール*」をクリックして動作を確認します。 +- 【Microsoft Windows 8の場合】 タスクバーの左下にある*空のスペース*を右クリックし、*コントロールパネル*を選択します。 *プログラム*セクションで*プログラムのアンインストール*をクリックし、インストールされているアプリのリストから*AdGuard*を選択して、リストの真上にある*アンインストール*ボタンを押します。 開いたウィンドウで「*AdGuardのアンインストール*」をクリックして動作を確認します。 -![Windows 8 uninstallation](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win8-uninstall.png) +![Windows 8 でのアンインストール](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win8-uninstall.png) -- For Microsoft Windows 8.1: Right-click the *Start button* and select *Control Panel*. *プログラム*セクションで*プログラムのアンインストール*をクリックし、インストールされているアプリのリストから*AdGuard*を選択して、リストの真上にある*アンインストール*ボタンを押します。 開いたウィンドウで「*AdGuardのアンインストール*」をクリックして動作を確認します。 +- 【Microsoft Windows 8.1の場合】 *スタートボタン*を右クリックし、*コントロールパネル*を選択します。 *プログラム*セクションで*プログラムのアンインストール*をクリックし、インストールされているアプリのリストから*AdGuard*を選択して、リストの真上にある*アンインストール*ボタンを押します。 開いたウィンドウで「*AdGuardのアンインストール*」をクリックして動作を確認します。 - 【Microsoft Windows 7の場合】 *スタートメニュー*を開きます。 検索ボックスに「*コントロールパネル*」と入力します。 *プログラム*セクションで*プログラムのアンインストール*をクリックし、インストールされているアプリのリストから*AdGuard*を選択して、リストの真上にある*アンインストール*ボタンを押します。 開いたウィンドウで「*AdGuardのアンインストール*」をクリックして動作を確認します。 -![Windows 7 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win7-uninstall.png) +![Windows 7 でのアンインストール *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win7-uninstall.png) ### アドバンスド方法 {#advanced} -In case regular uninstall doesn't work for any reason, you can try to use an advanced method. First of all, you need to [download the uninstaller tool](https://cdn.adtidy.org/distr/windows/Uninstall_Utility.zip) created by our developers. Extract the archive to any folder on your PC and run the **Adguard.UninstallUtility.exe** file, and allow the app to make changes to your device. Then follow the instruction below: +何らかの理由で通常のアンインストールがうまくいかない場合は、アドバンスド方法を試してみてください。 まず、AdGuardのエンジニアが作成した[アンインストーラーツールをダウンロード](https://cdn.adtidy.org/distr/windows/Uninstall_Utility.zip)する必要があります。 アーカイブをお使いのPCの任意のフォルダに解凍し、「**Adguard_Uninstall_Utility.exe**」ファイルを実行して、パソコンに変化を与えることを許可してください。 その後、以下の手順に行なってください: -- Select *AdGuard Ad Blocker* and *Standard* uninstall type, then click *Uninstall*. +- *AdGuard Ad Blocker*と *Standard*uninstall type を選択し、*Uninstall* をクリックします。 -![Standard uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) +![通常のアンインストール *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard.jpg) -- Click *OK* once the warning window pops up: +- 警告ウィンドウが表示されたら、 *OK* をクリックします。 -![Standard uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![通常のアンインストール *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) -- Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: +- アンインストールが完了するまで待ちます。 **Uninstall complete**（アンインストールが完了しました）と表示され、コンピュータを再起動するよう促されます: -![Uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard_complete.jpg) +![アンインストール完了 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_standard_complete.jpg) :::caution -Follow the next steps only if performing the first two steps wasn’t enough for some reason. We strongly suggest contacting our support before using steps 3-4 of advanced uninstall instruction. +【注意】 最初の2つのステップを実行しても十分ではなかった場合にのみ、ステップ3と4を行なってください。 高度なアンインストール手順のステップ3～4を使用する前に、AdGuardサポートに連絡することを強くお勧めします。 ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- *AdGuard Ad Blocker* と *Extended* uninstall type を選択し、*Uninstall* をクリックします。 ウィンドウのプロンプトで *Yes, continue* をクリックします。 -![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) +![拡張アンインストール *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) -- Click *OK* once the warning window pops up: +- 警告ウィンドウが表示されたら、 *OK* をクリックします。 -![Extended uninstall warning *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) +![拡張アンインストール警告 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_warning.jpg) -- Wait until uninstall is finished — there will be a phrase **Uninstall complete** and a prompt to restart your computer: +- アンインストールが完了するまで待ちます。 **Uninstall complete**（アンインストールが完了しました）と表示され、コンピュータを再起動するよう促されます: -![Extended uninstall finished *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) +![拡張アンインストール完了 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended_complete.jpg) -AdGuard is successfully uninstalled! +AdGuardのアンインストール完了です！ diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 55eebf9eeab..0f0c40626d4 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -1,63 +1,63 @@ --- -title: AdGuard filters +title: AdGuard フィルタ sidebar_position: 2 --- :::info -この記事では、AdGuard製品にプリインストールされているAdGuard開発のフィルタについて説明しています。 To check them out, you can [download the AdGuard app](https://agrd.io/download-kb-adblock) +この記事では、AdGuard製品にプリインストールされているAdGuard開発のフィルタについて説明しています。 フィルタを実際に使ってみるには、[AdGuardアプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 ::: -この記事は、AdGuard製品やその他の広告ブロックソフト（uBlock Originなど）で使用するためにAdGuardが作成したフィルターについてです。 Filters are sets of rules in text format used by AdGuard apps and programs to filter out advertising and privacy-threatening content such as banners, pop-ups, or trackers. Filters contain lists of rules based on their purpose. Language filters include rules for corresponding language segments of the Internet (e.g., German filter). Task-based filters group rules that fulfil a specific task, such as Social media filter or Tracking Protection filter. Enabling or disabling a filter makes it easier to work with the entire list of rules at once. +この記事は、AdGuard製品やその他の広告ブロックソフト（uBlock Originなど）で使用するためにAdGuardが作成したフィルターについてです。 フィルタは、バナー、ポップアップ、トラッカーなどの広告やプライバシーを脅かすコンテンツをフィルタリングするために、AdGuardのアプリやプログラムで使用されるテキスト形式のルールセットです。 フィルタには、目的に応じたルールのリストが含まれています。 言語フィルタには、対応するインターネットの言語セグメントに対するルールが含まれています（例：ドイツ語フィルタ）。 目的別フィルタ（SNSフィルタやトラッキング防止フィルタなど）は、特定の目的を果たすルールをグループ化したものです。 フィルタの有効化または無効化は、ルールリスト全体を一度に扱うことを簡単にします。 -## AdGuard filters +## AdGuard フィルタ -- **Base filter** removes ads from websites with English content. Originally based on [EasyList](https://easylist.to/) and modified by us. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_2_Base/filter.txt) -- **Tracking Protection filter** — comprehensive list of various online counters and web analytics tools. Use it to hide your actions online and avoid tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_3_Spyware/filter.txt) -- **URL Tracking filter** enhances privacy by removing tracking parameters from URLs. When a user opts to block tracking parameters in Stealth Mode, this filter will be enabled automatically. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_17_TrackParam/filter.txt) -- **Social media filter** removes numerous "Like" and "Tweet" buttons and other social media integrations on popular websites. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_4_Social/filter.txt) -- **Annoyances filter** blocks irritating elements on web pages. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_14_Annoyances/filter.txt). Includes the following AdGuard filters (all of them can be enabled separately from the Annoyances filter): +- **AdGuard ベースフィルタ**は、英語コンテンツのウェブサイトから広告を削除します。 元々は[EasyList](https://easylist.to/)をベースに、私たちが手を加えたものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_2_Base/filter.txt) +- **AdGuard 追跡防止フィルタ**は、さまざまなオンラインカウンターとウェブ解析ツールの包括的なリストです。 オンライン上で自分の行動を隠し、追跡を避けるために使えます。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_3_Spyware/filter.txt) +- **AdGuard URL追跡防止フィルタ**は、URLからトラッキング（追跡）パラメーターを除去し、プライバシーを向上させます。 ユーザーがAdGuardの「ステルスモード」でトラッキングパラメーターのブロックを選択すると、このフィルタは自動的に有効になります。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_17_TrackParam/filter.txt) +- **AdGuard SNS用フィルタ**は、人気ウェブサイトにある「いいね！」や「ツイート」ボタンなどのソーシャルメディア統合要素を削除します。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_4_Social/filter.txt) +- **AdGuard 迷惑要素フィルタ**は、ウェブページ上の刺激的な要素をブロックします。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_14_Annoyances/filter.txt) 以下のAdGuardフィルタが含まれています（以下のフィルタは、迷惑要素フィルタとは別に、一つ一つを有効にすることもできます）: - - **Cookie Notices** blocks cookie notices on web pages. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_18_Annoyances_Cookies/filter.txt) - - **Popups** blocks all kinds of pop-ups that are not necessary for websites' operation. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_19_Annoyances_Popups/filter.txt) - - **Mobile App Banners** blocks banners that promote mobile apps of websites. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_20_Annoyances_MobileApp/filter.txt) - - **Widgets** blocks third-party widgets: online assistants, live support chats, etc. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_22_Annoyances_Widgets/filter.txt) - - **Other Annoyances** blocks elements that do not fall under the popular categories of annoyances. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_21_Annoyances_Other/filter.txt) + - **Cookie通知フィルタ** は、Web ページ上の Cookie 通知をブロックします。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_18_Annoyances_Cookies/filter.txt) + - **ポップアップフィルタ**は、Webサイトの動作に関係ないすべてのポップアップをブロックします。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_19_Annoyances_Popups/filter.txt) + - **モバイルアプリバナーフィルタ**は、ウェブサイトのモバイルアプリを宣伝するバナーをブロックします。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_20_Annoyances_MobileApp/filter.txt) + - **ウィジェットフィルタ**は、サードパーティのウィジェット（オンラインアシスタント、ライブサポートチャット）などをブロックします:。 [ルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_22_Annoyances_Widgets/filter.txt) + - **その他の迷惑要素フィルタ**は、一般的な迷惑要素に該当しない迷惑な要素をWebページ上でブロックします。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_21_Annoyances_Other/filter.txt) -- **Filter unblocking search ads and self-promotions** unblocks ads that may be useful to users. Learn more about this filter on [this page](../search-ads). [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_10_Useful/filter.txt) -- **Russian filter** removes ads from websites in Russian. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_1_Russian/filter.txt) -- **German filter** removes ads from websites in German. Originally based on the [EasyList Germany](https://easylist.to/) filter and subsequently modified by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_6_German/filter.txt) -- **French filter** removes ads from websites in French. Originally based on the [Liste FR](https://forums.lanik.us/viewforum.php?f=91) filter and subsequently modified by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_16_French/filter.txt) -- **Japanese filter** removes ads from websites in Japanese. Originally based on the [Fanboy’s Japanese](https://www.fanboy.co.nz/fanboy-japanese.txt) filter and subsequently modified by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_7_Japanese/filter.txt) -- **Dutch filter** removes ads from websites in Dutch. Originally based on the [EasyList Dutch](https://easylist.to/) filter and subsequently modified by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_8_Dutch/filter.txt) -- **Spanish/Portuguese filter** removes ads from websites in Spanish and Portuguese. Originally based on the [Fanboy’s Spanish/Portuguese](https://www.fanboy.co.nz/fanboy-espanol.txt) filter and subsequently modified by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_9_Spanish/filter.txt) -- **Turkish filter** removes ads from websites in Turkish. Created by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_13_Turkish/filter.txt) -- **Chinese filter** removes ads from websites in Chinese. Originally based on the [EasyList China](https://github.com/easylist/easylistchina) filter and subsequently modified by us according to the complaints from users. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_224_Chinese/filter.txt) -- **Ukrainian filter** removes ads from websites in Ukrainian. Learn more about this filter on [this page](https://adguard.com/en/blog/ukrainian-filter.html). [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_23_Ukrainian/filter.txt) -- **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) -- **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) -- **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) +- **検索広告と自己宣伝のブロック解除フィルタ**は、ユーザーにとって有益と思われる広告のブロックを解除します。 このフィルタの詳細については、 [このページ](../search-ads)をご覧ください。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_10_Useful/filter.txt) +- **AdGuard ロシア語フィルタ**は、ロシア語のウェブサイトから広告を削除します。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_1_Russian/filter.txt) +- **AdGuard ドイツ語フィルタ**は、ドイツ語のウェブサイトから広告を削除します。 元々は[EasyList Germany](https://easylist.to/)フィルタがベースになっており、その後ユーザーからのクレームを元に当社で修正しているものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_6_German/filter.txt) +- **AdGuard フランス語フィルタ**は、フランス語のウェブサイトから広告を削除します。 元々は[Liste FR](https://forums.lanik.us/viewforum.php?f=91)フィルタがベースになっており、その後ユーザーからのクレームを元に当社で修正しているものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_16_French/filter.txt) +- **AdGuard 日本語フィルタ**は、日本語のウェブサイトから広告を削除します。 元々は[Fanboy’s Japanese](https://www.fanboy.co.nz/fanboy-japanese.txt)フィルタがベースになっており、その後ユーザーからのクレームを元にAdGuardが修正しているものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_7_Japanese/filter.txt) +- **AdGuard オランダ語フィルタ**は、オランダ語のウェブサイトから広告を削除します。 元々は[EasyList Dutch](https://easylist.to/)フィルタがベースになっており、その後ユーザーからのクレームを元に当社で修正しているものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_8_Dutch/filter.txt) +- **AdGuard スペイン語/ポルトガル語フィルタ**は、スペイン語およびポルトガル語のウェブサイトから広告を削除します。 元々は[Fanboy’s Spanish/Portuguese](https://www.fanboy.co.nz/fanboy-espanol.txt)フィルタがベースになっており、その後ユーザーからのクレームを元に当社で修正しているものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_9_Spanish/filter.txt) +- **AdGuard トルコ語フィルタ**は、トルコ語のウェブサイトから広告を削除します。 ユーザーからのクレームに応じてAdGuardが作成しました。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_13_Turkish/filter.txt) +- **AdGuard 中国フィルタ**は、中国語のウェブサイトから広告を削除します。 元々は[EasyList China](https://github.com/easylist/easylistchina)フィルタがベースになっており、その後ユーザーからのクレームを元にAdGuardが修正しているものです。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_224_Chinese/filter.txt) +- **AdGuard ウクライナ語フィルタ**は、ウクライナ語のウェブサイトから広告を削除します。 このフィルタの詳細については、 [このページ](https://adguard.com/en/blog/ukrainian-filter.html)をご覧ください。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_23_Ukrainian/filter.txt) +- **実験的フィルタ**は、潜在的に競合を引き起こし、ウェブサイトの作業を混乱させる可能性のある新しいフィルタリングルールをテストするために使用されています。 これらのルールが問題なく動けば、メインフィルタに追加されます。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) +- **AdGuard モバイル広告フィルタ**は、モバイルデバイス上の広告をブロックします。 すべての既知のモバイル広告ネットワークが含まれています。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) +- **AdGuard DNSフィルタ**は、数フィルタ（AdGuardベースフィルタ、SNS用フィルタ、スパイウェアフィルタ、モバイル広告フィルタ、EasyList、EasyPrivacy）で構成され、DNSレベルの広告ブロックとの互換性が向上するように簡素化されたフィルタです。 このフィルタは[AdGuard DNS](https://adguard-dns.io/kb)サーバーでも使用され、広告やトラッキングをブロックします。 [含まれているルールを見る](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) +- **AdGuard 臨時修正フィルタ**は、MV3対応版 AdGuard ブラウザ拡張機能をアップデートする必要なく、人気Webサイトでのコンテンツフィルタリング問題をすばやく解決するためのフィルタです。 [含まれているルールを見る](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) -## AdGuard Filters Policy +## AdGuard フィルタポリシー -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +AdGuardフィルタポリシーは、AdGuardフィルタがブロックすべきものとブロックすべきでないもの、およびフィルタのルールの追加と削除の規則を定義します。 詳細については、[AdGuardフィルタポリシーの全文](../filter-policy)をお読みください。 -## Contributing to AdGuard filters +## AdGuardフィルタに貢献する -We are blessed with a unique community that not only loves AdGuard but also gives back. Many people volunteer in various ways to make AdGuard's user experience better for everybody. You are welcome to join the band and make a difference. We will do our part and happily reward the most active community. So, what can you do? +AdGuard を愛するだけでなく、貢献もしてくれるユニークなコミュニティに大変恵まれております。 AdGuardのユーザーエクスペリエンスをより良いものにするために、多くの人々がさまざまな形でボランティアとして協力してくださっています。 あなたもに参加して変化を起こしてください。 私たちからは、最も活発なコミュニティメンバーに喜んで報酬を与えております。 そこで、実際何をすることで貢献いただけるのでしょうか。 -### Report Issues +### 問題を報告する -We rely on the community to let us know about issues with our filters. It helps us use our time more efficiently and keep filters constantly updated. To submit a report, please use this [web reporting tool](https://agrd.io/report). +私たちAdGuardは、フィルタに関する問題を知らせてくれるコミュニティに依存しています。 そのおかげで、時間をより効率的に使い、フィルタを常に最新の状態に保つことができております。 報告するには、[こちらのウェブ報告ツール](https://agrd.io/report)をご利用ください。 -### Suggest Filtering Rules +### フィルタリングルールを提案する -You will find many open issues in the [GitHub filter repository](https://github.com/AdguardTeam/AdguardFilters/issues). Each one refers to a problem with a website, such as a missed ad or a false positive. Pick an issue and suggest your own rules in the comments. AdGuard filter engineers will review your suggestions and, if approved, add your rules to AdGuard filters. +[GitHub フィルタリポジトリ](https://github.com/AdguardTeam/AdguardFilters/issues)には、未解決の問題が多数あります。 問題はそれぞれ、広告の見逃しや誤検出など、ウェブサイト関連問題になっています。 好きなissueを選んで、コメントで独自のルールを提案してください。 AdGuardフィルタエンジニアがご提案を確認して承認した場合、ご指摘のルールはAdGuardのフィルタに追加されます。 -Here is the [official documentation](../create-own-filters) on the syntax of AdGuard filtering rules. Please read it carefully: it will help you create your own filtering rules. +[AdGuardフィルタリングルールの構文に関する公式ドキュメントはこちら](../create-own-filters)です。 注意深くお読みください。独自のフィルタリングルールを作成する際の重要な情報が含まれています。 -### Other ways to contribute +### その他の貢献方法 -Here is [a dedicated page](https://adguard.com/contribute.html) for people willing to contribute to AdGuard in other ways. +その他の方法でAdGuardに貢献してくださる方のための[専用ページはこちら](https://adguard.com/contribute.html)です。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index b64e87d902e..bb4cbe0435e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1,5 +1,5 @@ --- -title: How to create your own ad filters +title: 自分の広告フィルタを作成する方法 sidebar_position: 5 toc_min_heading_level: 2 toc_max_heading_level: 4 @@ -7,7 +7,7 @@ toc_max_heading_level: 4 :::info -この記事では、AdGuard製品で使用できるカスタムフィルタリングルールの作成方法を紹介しています。 To test your rules, you can [download the AdGuard app](https://agrd.io/download-kb-adblock) +この記事では、AdGuard製品で使用できるカスタムフィルタリングルールの作成方法を紹介しています。 ルールを実用テストするには、[AdGuardアプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 ::: @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md index 3f4f42d5000..62d3d3620cf 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -18,87 +18,87 @@ AdGuard はユーザースクリプトマネージャとして、ウェブサイ ### AdGuard Extra -An extension that blocks ads in difficult cases when the usual filter-based approach is not enough. AdGuard Extra comes pre-installed with all premium AdGuard versions, so you don't need to do anything to enable it. However, if you want to use it alongside AdGuard Browser Extension or any other ad blocker, you'll need to use an additional extension. Learn more about this userscript and how to install it on [GitHub](https://github.com/AdguardTeam/AdGuardExtra). +通常のフィルタベースアプローチでは不十分な場合に、広告をブロックしてくれる拡張機能。 AdGuard Extraは、AdGuardのすべてのプレミアム版にプリインストールされているため、有効にするために何もする必要はありません。 ただし、AdGuard ブラウザ拡張機能やその他の広告ブロッカーと一緒に使用したい場合は、追加の拡張機能を使用する必要があります。 このユーザースクリプトの詳細とインストール方法については[GitHub](https://github.com/AdguardTeam/AdGuardExtra)をご覧ください。 ![AdGuard Extra](https://cdn.adtidy.org/content/kb/ad_blocker/general/adguard-extra.png) -### AdGuard Popup Blocker +### AdGuard ポップアップブロッカー -The name speaks for itself: it blocks pop-ups — one of the most annoying types of ads on web pages. Learn more about this userscript, its key features, and how to install it on [GitHub](https://github.com/AdguardTeam/PopupBlocker). +その名の通り、ウェブページ上の最も迷惑な広告カテゴリのひとつであるポップアップ広告をブロックします。 このユーザースクリプトの詳細、主な機能、インストール方法については[GitHub](https://github.com/AdguardTeam/PopupBlocker)をご覧ください。 -![AdGuard Popup Blocker](https://cdn.adtidy.org/content/kb/ad_blocker/general/popup-blocker-installation.png) +![AdGuard ポップアップブロッカー](https://cdn.adtidy.org/content/kb/ad_blocker/general/popup-blocker-installation.png) -### AdGuard Assistant (legacy version) +### AdGuard アシスタント (レガシー版) -This custom extension is designed to control filtering directly from the browser page (manual blocking, exclusion of the site, etc.). +このカスタム拡張機能は、ブラウザのページから直接フィルタリングを制御することを可能にします（手動ブロック、サイトの除外などの管理）。 :::note -This version of Assistant is legacy and there is no point in using it on new systems, since it has been replaced with the full-fledged [Browser Assistant](https://adguard.com/adguard-assistant/overview.html). But the legacy Assistant might be of help if there is no Browser Assistant for your browser. If this is your case, your can learn how to install AdGuard Assistant on [GitHub](https://github.com/AdguardTeam/AdguardAssistant). +このバージョンのアシスタントはレガシー版であり、現在、本格的な新 [AdGuard ブラウザアシスタント](https://adguard.com/adguard-assistant/overview.html)に置き換えられているため、新しいシステムやデバイスで使用する意味はありません。 しかし、お使いのブラウザにAdGuardブラウザアシスタントがない場合は、レガシー版アシスタントが役に立つかもしれません。 このような場合は、[GitHub](https://github.com/AdguardTeam/AdguardAssistant)でAdGuard アシスタントのインストール方法をご確認いただけます。 ::: -### Disable AMP +### AMPを無効化 -A script that is only pre-installed in AdGuard for Android. It disables AMP (Accelerated Mobile Pages) on the Google search results page. Learn more about this userscript and how to install it on [GitHub](https://github.com/AdguardTeam/DisableAMP). +Android版AdGuardにのみプリインストールされているスクリプト。 Google 検索結果ページで AMP (Accelerated Mobile Pages) を無効にします。 このユーザースクリプトの詳細とインストール方法については[GitHub](https://github.com/AdguardTeam/DisableAMP)をご覧ください。 -![Disable AMP](https://cdn.adtidy.org/content/kb/ad_blocker/general/disable-amp-installation.png) +![AMPを無効化](https://cdn.adtidy.org/content/kb/ad_blocker/general/disable-amp-installation.png) -## Top picks outside AdGuard{#top-picks} +## AdGuard以外でおすすめのスクリプト -These userscripts are not developed by AdGuard and therefore we can't give a 100% guarantee that they are safe and/or work at all times. However, in our experience they deserve a recommendation as they've all earned their good reputation. +これらのユーザースクリプトは、AdGuardによって開発されたものではないため、安全性および/または機能性することを100%保証することはできません。 しかし、私たちの経験では、以下のものは全部、良い評判を得ているので、推薦に値します。 ### Don't track me Google -This script removes Google's tracking feature from the links in Google search results. It speeds up the loading of search results and allows you to right-click or tap to copy the link URL. +このスクリプトは、Googleの検索結果のリンクからGoogleのトラッキング機能を削除します。 検索結果の読み込みを高速化し、右クリックやタップでリンクURLをコピーできるようにします。 -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. +ソースコードは[GitHubで公開されています](https://github.com/Rob--W/dont-track-me-google)。 このユーザースクリプトは[GreasyForkから](https://greasyfork.org/en/scripts/428243-don-t-track-me-google)ダウンロードし、AdGuard CoreLibsベースのアプリにインストールすることができます。 ### microShield -A userscript for people who visit Korean websites and some international websites. The microShield userscript blocks Ad-Shield advertisement and anti-adblock. Its original source code is available at [asdefuser](https://github.com/seia-soto/userscripts/tree/master/sources/asdefuser) and [AdShield Defuser](https://github.com/seia-soto/adshield-defuser). This userscript can be installed in AdGuard CoreLibs-based apps, Violentmonkey, Tampermonkey, and [quoid/userscripts](https://github.com/quoid/userscripts). Learn more about microShield and how to install it on [GitHub](https://github.com/List-KR/microShield). +韓国のウェブサイトや一部の国際ウェブサイトを訪問する人のためのユーザースクリプト。 microShield ユーザースクリプトは、Ad-Shield 広告とアンチアドブロック（広告ブロック対策技術）をブロックします。 オリジナルのソースコードは、 [asdefuser](https://github.com/seia-soto/userscripts/tree/master/sources/asdefuser) および [AdShield Defuser](https://github.com/seia-soto/adshield-defuser)で確認できます。 このユーザースクリプトは、AdGuard CoreLibsベースのアプリ、Violentmonkey、Tampermonkey、および[quoid/userscripts](https://github.com/quoid/userscripts)にインストールできます。 microShieldの詳細とインストール方法については、[GitHub](https://github.com/List-KR/microShield)をご覧ください。 -## Where can you get more userscripts?{#more-userscripts} +## さらに多くのユーザースクリプトはどこで入手できますか？ -As userscripts are mainly created by enthusiasts, you should be cautious when installing them. Any script from an unknown source carries a potential risk. Yet, there is a great variety of interesting scripts that, if installed carefully and responsibly, can really make using some websites more convenient. +ユーザースクリプトは主に愛好家によって作成されるため、インストールする際には注意が必要です。 未知のソースからのスクリプトは、潜在的なリスクを伴います。 しかし、注意深く責任を持ってインストールすれば、ウェブサイトの利用をより便利にしてくれる興味深いスクリプトは実に多種多様です。 -Here we will describe some of the most popular userscript catalogs. +以下で、最も人気なユーザースクリプト・カタログのいくつかをご紹介します。 ### Userscript.Zone -[Userscript.Zone](https://www.userscript.zone) is a website that allows searching for userscripts by entering a matching URL or domain. The website is easy to use and has a high credibility, since only scripts from moderated pages are displayed. +[Userscript.Zone](https://www.userscript.zone)は、一致するURLまたはドメインを入力してユーザースクリプトを検索できるウェブサイトです。 このウェブサイトは使いやすく、モデレートされたページのスクリプトだけが表示されるため、信頼性も高いです。 ### Greasy Fork -[Greasy Fork](https://greasyfork.org/) is a userscript catalog by Stylish creators. The scripts in this catalog undergo moderation, so their credibility is much higher. +[Greasy Fork](https://greasyfork.org/)は、Stylishのクリエイターによるユーザースクリプトのカタログです。 このカタログに掲載されているスクリプトは、モデレーションを受けているため、その信頼性はさらに高いです。 ### OpenUserJS.org -[OpenUserJS.org](https://openuserjs.org/) is an open source userscript catalog written in nodeJS. It doesn't have moderation so stay alert to any suspicious scripts. +[OpenUserJS.org](https://openuserjs.org/)はnodeJSで書かれたオープンソースのユーザースクリプトカタログです。 モデレーションがないので、不審なスクリプトに注意してください。 -### Community +### コミュニティ -If you like the idea of personifying your browser with the help of userscripts, and you have any questions, you can ask them on one of these websites: +ユーザースクリプトの助けを借りてブラウザを擬人化するというアイデアが好きな方で、何か質問がある場合は以下のウェブサイトのいずれかで質問することができます: - [Stackoverflow](https://stackoverflow.com/questions/tagged/userscripts) - [FreeNode](https://webchat.freenode.net/#greasemonkey) - [Reddit](https://www.reddit.com/r/userscripts/) -## Development +## 開発者向け -### Request license +### AdGuardライセンスをリクエストする -If you are developing your own custom script and want to test how it works with AdGuard, request a beta license key for the app. +独自のカスタムスクリプトを開発中で、AdGuardとの連携をテストしたい場合は、AdGuardアプリのベータ版ライセンスキーをリクエストしてください。 -To get it, please send an email to devteam@adguard.com with the following information: +ご希望の方は、以下の情報を明記の上、devteam@adguard.com にご連絡ください: -**Subject:** Userscript author license request +**件名:** Userscript author license request -**Body:** Please tell us about the userscripts you are working on. +**本文:** 現在取り組んでいるユーザースクリプトについて教えてください（できれば英語でお願いします）。 -Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%20license%20request&Body=Hello%2C%0A%0AMy%20userscript%28s%29%3A%20LINK). +よかったらこちらの[mailtoリンク](mailto:devteam@adguard.com?Subject=Userscript%20author%20license%20request&Body=Hello%2C%0A%0AMy%20userscript%28s%29%3A%20LINK)もお使いください。 -### Compatibility +### 互換性 #### Metadata block @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +これらのプロパティは、AdGuardによって無視されます: ```text @unwrap @@ -142,7 +142,7 @@ These properties will be simply ignored by AdGuard. #### Supported GM functions -AdGuard supports both old GM\_ functions and new GM4 API that use GM object. +AdGuard は、古い GM\_ 関数と、GM オブジェクトを使用する新しい GM4 API の両方をサポートしています。 ##### Values @@ -169,9 +169,9 @@ GM_addStyle GM_log ``` -[Here](https://wiki.greasespot.net/GM.info) you can find more information about Greasemonkey API. +Greasemonkey APIについての詳細は[こちら](https://wiki.greasespot.net/GM.info)をご覧ください。 -### Example +### 例: ```javascript // ==UserScript== @@ -210,19 +210,19 @@ GM_log )}(); ``` -## Userstyles +## ユーザースタイル -AdGuard products provide limited support for userstyles. `@var` and `@advanced` metadata tags are not supported, as well as any value of the `@preprocessor` metadata tag except `default`. +AdGuard製品では、ユーザースタイルを限定的にサポートしています。 `@var` および `@advanced` メタデータタグはサポートされていません。また、 `@preprocessor` メタデータタグの任意の値 ( `default`を除く) もサポートされていません。 ### Metadata -The metadata block is written using CSS-style comments, starting with `===UserStyle===` and ending with `===/UserStyle===`. All metadata tags that are supported for userscripts are also supported for userstyles, although some of them have no meaning and are ignored. `@var` and `@advanced` tags are not supported. The only supported value of the `@preprocessor` tag is `default`. +メタデータブロックは、 `===UserStyle===` で始まり、 `===/UserStyle===`で終わる CSS スタイルのコメントを使用して記述されます。 ユーザースクリプトでサポートされているすべてのメタデータタグは、ユーザースタイルでもサポートされています。（一部のタグ意味ないため無視されますが。） `@var` および `@advanced` タグはサポートされていません。 `@preprocessor` タグでサポートされている値は、 `default` のみです。 ### Content -The content of a userstyle is plain CSS with support for the [`@-moz-document` at-rule](https://developer.mozilla.org/en-US/docs/Web/CSS/@document). The `media-document()` function is not supported. The userstyle will only be applied to pages that match one or more of the `@-moz-document` rules. If the userstyle does not contain any `@-moz-document` rules, it will not be applied. +ユーザースタイルのコンテンツは、 [`@-moz-document` @-rule](https://developer.mozilla.org/en-US/docs/Web/CSS/@document)をサポートするプレーン CSS です。 `media-document()` 関数はサポートされていません。 ユーザースタイルは、 `@-moz-document` ルールの 1 つ以上に一致するページにのみ適用されます。 ユーザースタイルに `@-moz-document` ルールが全く含まれていない場合は、そのユーザースタイルは適用されません。 -### Example +### 例: ```css /* ==UserStyle== diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 61c829b4695..16361b98a76 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -1,76 +1,74 @@ --- -title: AdGuard Browser Extension for Chrome MV3 +title: Chrome MV3용 AdGuard 브라우저 확장 프로그램 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +MV2 확장프로그램이 Chrome 웹 스토어에서 사라지면서, Chrome 사용자들은 Chrome의 새로운 API인 매니페스트 V3에 호환되는 MV3 확장 프로그램으로 전환해야 할 수도 있습니다. 이 주제에 대한 저희의 생각은 [블로그](https://adguard.com/en/blog/tag/manifest-v3.html)에서 폭넓게 다루었습니다. -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +AdGuard MV3 확장 프로그램은 광고와 추적기를 효과적으로 차단하는 동시에 소셜 위젯, 배너, 영상 광고를 빈틈없이 관리합니다. 대부분의 사용자는 기능상의 차이를 느끼지 못할 것입니다만, 알아두어야 할 몇 가지 제한 사항과 변경점들이 있습니다. -## Where to find our extensions +## 확장 프로그램을 찾을 수 있는 위치 -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +[Chrome 웹 스토어](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg)에 있던 기존의 확장 프로그램은 **MV3 버전**으로 대체되었습니다. -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +**MV3의 베타 버전**은 여전히 [Chrome 웹 스토어](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf)에서 이용하실 수 있습니다. -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +기존의 베타 확장프로그램은 [**Adguard 광고 차단기 MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl)로 이름이 변경되어 Google 지원이 종료될 때까지 유지될 것입니다. -## Main changes in features and settings +## 기능 및 설정의 주요 변경 사항 -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **자동 및 수동 필터 업데이트 불가**. **필터 자동 업데이트** 및 **필터 업데이트 확인** 기능이 **필터** 탭에서 사라집니다. 일부 규칙이 DNR 형태로 적용됨에 따라, 저희는 요청에 따라 필터를 업데이트할 수 없게 되었습니다. 스토어의 검토를 거쳐 확장 프로그램을 업데이트하는 모든 과정을 거쳐야만 합니다. -- **Filtering log** +- **필터링 로그** - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) + ![필터링 로그 \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + DNR 제한으로 인해 구체적으로 어떤 규칙이 적용되었는지 표시할 수 없게 되었는데, 대신에 저희의 엔진을 바탕으로 '작동되었을 것으로 추정되는 규칙'을 제공할 예정입니다. 정확한 정보를 얻기 위해서는 '압축 해제된' 형태의 확장 프로그램을 브라우저에 직접 설치해야 합니다. 이 작업을 수행하는 방법에 대한 자세한 설명은 [별도의 문서](/adguard-browser-extension/solving-problems/debug-rules/)에서 확인하실 수 있습니다. -- _Tracking protection_ (formerly known as _Stealth mode_) +- **추적 보호** (이전 명칭으로는 **스텔스 모드**) - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) + ![추적 보호 \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + 선언적 규칙을 사용하여 쿠키의 TTL을 설정할 수 없게 되었기 때문에, **쿠키**를 비롯한 **퍼스트 파티 쿠키 자동 파괴**, **서드파티 쿠키 자동 파괴** 섹션이 사라졌습니다. -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- 일반 설정에서 **피싱, 멀웨어 보호**를 더 이상 사용할 수 없습니다. 악성 웹사이트와 사기로부터 보호받기 위해서는 **필터** 탭에서 적절한 **보안** 필터를 활성화하세요. - ![Security \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) + ![보안 \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) ## 제한 -### Maximum number of rules and filters +### 최대 규칙 및 필터 수 -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +매니페스트 V3은 확장 프로그램마다 고정 및 정규식 규칙에 제한을 둡니다. 이러한 제한을 넘었을 경우에 사용자는 알림을 받을 수 있습니다. -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) +![규칙 제한 \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) +![너무 많은 확장 프로그램 \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +기본적으로, 매니페스트 V3은 규칙을 고정(내장) 규칙과 동적 규칙으로 구분하여 엄격한 제한을 두고 있습니다. -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +**고정 규칙:** 확장 프로그램당 최소 **30,000** 규칙이고, 개별 사용자가 설치한 모든 확장 프로그램에 대한 누적 한도는 **330,000**입니다. -For regex rules, the limit is set at **1,000 per extension**. +정규식 규칙에 대해서는 한도가 **확장 프로그램당 1,000**으로 설정되어 있습니다. -The maximum number of simultaneously enabled filters is **50**. +동시에 최대로 활성화 가능한 필터의 수는 **50**개 입니다. -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +**동적 규칙:** 최대 1,000개의 정규식 규칙을 포함한 **5,000** 규칙의 엄격한 한도가 적용됩니다. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> **변환된 규칙**은 [선언적 변환기][github-declarative-converter]를 이용해 \[DNR 형식]으로 변환된 규칙입니다. +> 변환 과정에서 일부 규칙들은 다른 규칙의 (`$badfilter`)를 덮어쓸 수도 있고, (`$removeparam`)와 결합될 수도 있는데, 그 결과 순서가 약간 다른 규칙 목록이 생성됩니다. > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> 변환된 규칙 목록에서는 5,000개의 규칙만 사용합니다. 나머지는 편집기에 표시는 되지만 적용되지 않습니다. -Here's how a rule with a basic modifier is converted to a declarative rule: +여기에서는 기본적인 변경자가 있는 규칙이 어떻게 선언적 규칙으로 변환되는지 보여줍니다: ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +이 아래와 같이 변환됩니다. ```json [ @@ -94,14 +92,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +더 많은 예시들은 [GitHub][github-declarative-converter-examples]에서 찾아볼 수 있습니다. -### Network rule modifiers +### 네트워크 규칙 수정자 -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +네트워크 규칙 수정자에는 한계가 있습니다: 어떤 것들은 MV3에 적용될 수 없거나, 또는 제한적으로만 구현할 수 있습니다. -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +한계에 대한 구체적인 내용은 [GitHub][github-declarative-converter]에서 찾아볼 수 있습니다. +수정자에 대한 더 많은 정보를 얻고 싶다면, [지식 창고](/general/ad-filtering/create-own-filters)를 참고하세요. [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md index 4ece00ffd5b..47d55f3539e 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md @@ -1,98 +1,98 @@ --- -title: How to debug rules in AdGuard for Chrome MV3 +title: Chrome MV3에서 AdGuard 규칙을 디버그하는 방법 sidebar_position: 2 --- -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. +[Chrome MV3용 AdGuard](/adguard-browser-extension/mv3-version) 에서, 필터링 로그는 적용된 규칙들 중에서 '추정 규칙'이라고 부르는 대략적인 것들만 보여줍니다. 이는 확장 프로그램이 '압축 해제'된 형식이 아닌 경우, 브라우저에서 어떤 규칙을 사용하였는지 구체적으로 알려주지 않기 때문입니다. 정확한 정보를 얻기 위해서는, 브라우저에 확장 프로그램의 압축 해제된 버전을 직접 설치해야 합니다. -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. +이 설명서는 확장 프로그램과 함께 제공되는 고정 규칙을 바꾸고 싶은 경우와 같은 곤란한 상황에도 도움이 될 것입니다. 대부분의 경우에는 확장 프로그램의 **사용자 규칙**을 활용하는 것으로도 충분할 것입니다. -## Prerequisites +## 전제 조건 -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) +1. **Git:** [Git 설치](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) +2. **Node:** [Node.js 설치](https://nodejs.org/en/download/package-manager) -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) +3. **Yarn:** [Yarn 설치](https://classic.yarnpkg.com/lang/en/docs/install) -## How to clone extension +## 확장 프로그램을 복제하는 방법 -1. Clone the repository: +1. 레포지터리를 복제합니다: ```bash git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git ``` -2. Navigate to the directory: +2. 디렉토리로 이동합니다: ```bash cd AdguardBrowserExtension ``` -3. Switch to the `v5.0` branch: +3. `v5.0` 브랜치로 전환합니다: ```bash git checkout v5.0 ``` -4. Install dependencies: +4. 종속성 설치: ```bash yarn install ``` -## How to build extension +## 확장 프로그램을 빌드하는 방법 -1. Switch to the `v5.0` branch: +1. `v5.0` 브랜치로 전환합니다: ```bash git checkout v5.0 ``` -2. Run the following command in the terminal: +2. 터미널에서 다음 명령을 실행하세요: ```bash yarn dev chrome-mv3 ``` -3. The built extension will be located in the directory: +3. 빌드된 확장 프로그램은 다음 디렉토리에 있습니다: ```bash ./build/dev/chrome-mv3 ``` -## How to install unpacked in the browser +## 브라우저에서 압축 해제된 버전을 설치하는 방법 -1. Turn on developer mode: +1. 개발자 모드를 켜세요: - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) + ![개발자 모드](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) -2. Click _Load unpacked_: +2. \*\*압축해제된 확장 프로그램을 로드합니다.\*\*를 클릭하세요: ![Load unpacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) -3. Select the extension directory and click `Select`: +3. 확장 프로그램 디렉토리를 선택하고 **선택**을 클릭합니다: - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) + ![선택](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) -누르세요. +다 되었습니다! -## How to debug rules +## 규칙을 디버그하는 방법 -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. +1. `./Extension/filters/chromium-mv3` 디렉토리의 `.txt` 파일에서 필요한 규칙을 찾아 수정하세요. -2. Convert the rules from txt to declarative form: +2. txt에서 규칙을 선언적 형식으로 변경합니다: ```bash yarn convert-declarative ``` -3. Build the extension again: +3. 확장프로그램을 다시 빌드하세요: ```bash yarn dev chrome-mv3 ``` -4. Reload the extension in the browser: +4. 브라우저에서 확장프로그램을 다시 불러오세요: - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) + ![확장 프로그램 다시 로드](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md index 7dc93068cc5..f8019635b17 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md @@ -11,22 +11,22 @@ sidebar_position: 9 :::note -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. +iOS용 AdGuard(프리미엄 구독) 및 AdGuard Pro는 Apple 스마트폰 및 태블릿에서 광고를 차단합니다. 과거에는 App Store 리뷰 정책의 일부 변경으로 인해 기능이 달랐지만, 이제 AdGuard 유료 버전과 AdGuard Pro의 기능은 동일합니다. ::: -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. +iOS용 프리미엄 AdGuard는 사용자 정의 DNS 설정을 포함하여 무료 버전과 몇 가지 차이점이 있습니다. 이러한 설정을 사용하면 Safari뿐만 아니라 다른 앱에서도 광고를 차단하고, 온라인 성인 콘텐츠로부터 자녀를 보호하며, 개인 정보를 유출되지 않도록 안전하게 보호할 수 있습니다. 다른 차이점도 있습니다. 이 차이점을 좀 더 자세히 살펴보겠습니다. -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. +1. **DNS 보호** 모듈은 DNS 트래픽을 암호화하여 개인정보 보호를 강화합니다. Safari뿐만 아니라 모든 앱과 브라우저에서 작동하여 광고와 추적기로부터 기기를 보호합니다. - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. + - **사용자 정의 DNS 서버:** 목록에서 인기 있는 DNS 서버 중 하나를 선택하거나 사용자 정의 서버를 추가하세요. - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. + - **자녀 보호:** 인터넷이 항상 어린이 친화적인 것은 아닙니다. AdGuard 프리미엄을 사용하면 성인용 및 부적절한 콘텐츠를 차단하는 DNS 제공업체로 전환하여 자녀를 온라인에서 안전하게 보호할 수 있습니다. - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. + - **모니터링 및 유연한 구성:** 최근 활동 로그를 통해 기기에서 전송한 모든 DNS 요청을 확인하고 탭 한 번으로 차단 목록 또는 허용 목록에 웹사이트를 추가하여 트래픽을 손쉽게 관리할 수 있습니다. -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. +2. **고급 보호** 기능은 고급 필터링 규칙을 사용하여 다른 방법으로는 차단되지 않는 더 복잡한 광고를 차단할 수 있습니다. -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. +3. **더 많은 필터 옵션:** AdGuard 프리미엄을 구매하면 사용자 정의 필터와 보안 필터 카테고리를 이용할 수 있으며, AdGuard 및 기타 인기 목록을 포함한 50개 이상의 필터 중에서 선택할 수 있습니다. -Access these features by [purchasing a license](https://adguard.com/license.html). +[라이선스를 구매](https://adguard.com/license.html)하면 이러한 기능을 이용할 수 있습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 52ad71b170c..c3f1ee6640a 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + 이 아래와 같이 변환됩니다. ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4766,6 +4765,7 @@ The following scriptlets also may be used for debug purposes: [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" +[ext-mv3]: #what-product "Chrome MV3용 AdGuard 브라우저 확장 프로그램" [ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/intro.md b/i18n/ko/docusaurus-plugin-content-docs/current/intro.md index d90f0f6468e..ca622623b4d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/intro.md @@ -1,23 +1,23 @@ --- -title: Overview +title: 톺아보기 sidebar_position: 1 slug: / --- -## What is AdGuard Ad Blocker? +## AdGuard 광고 차단기란 무엇인가요? -AdGuard is one of the leaders on the market of ad-blocking software with 15+ years of experience, almost a dozen products for various platforms, and over 375 million user installs. Unlike other ad-blocking solutions, most of which are browser-based, we offer standalone apps for all major platforms, both desktop and mobile. AdGuard apps are more powerful than browser extensions, can block more and do it more efficiently: +AdGuard는 15년 이상의 경험, 다양한 플랫폼을 위한 여러 제품, 3억 7,500만 명 이상 사용자의 설치를 자랑하는 광고 차단 소프트웨어 시장의 선두주자 중 하나입니다. 대부분이 브라우저 기반인 다른 광고 차단 솔루션과 달리 저희는 데스크탑과 모바일 모두의 주요 플랫폼에 대한 독립형 앱을 제공합니다. AdGuard 앱은 브라우저 확장 프로그램보다 더 강력하며 더 많은 것을 차단하고 더 효율적이게 작동합니다. - [Windows용 AdGuard](/adguard-for-windows/features/home-screen) - [Mac용 AdGuard](/adguard-for-mac/features/main) - [Android용 AdGuard](/adguard-for-android/features/protection/ad-blocking) - [iOS용 AdGuard](/adguard-for-ios/features/safari-protection) -But we also develop and maintain free browser extensions for all popular browsers: +또한 저희는 모든 인기 브라우저들을 위한 무료 브라우저 확장 프로그램도 개발 및 유지 관리 중입니다. - [AdGuard 확장 프로그램](/adguard-browser-extension/features/filters) - [Safari용 AdGuard](/adguard-for-safari/features/general) -## Not just ad blocking +## 광고 차단뿐이 아닙니다 -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard 광고 차단기는 광고 차단 외에도 다양한 기능을 수행합니다. 온라인 추적기로부터 사용자를 보호하고 다양한 방법으로 개인정보를 보호합니다. 특정 제품의 경우 AdGuard는 더욱 포괄적인 보호를 위한 DNS 필터링, 부적절한 콘텐츠로부터 자녀를 보호하는 자녀 보호 기능, 인터넷 트래픽을 더 자세히 제어할 수 있는 필터링 로그 등과 같은 기능을 제공할 수도 있습니다. 지식창고에서 이 기능에 대한 자세한 정보를 확인할 수 있습니다. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 753297d45c9..7188a512d08 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -1,76 +1,76 @@ --- -title: AdGuard Browser Extension for Chrome MV3 +title: Extensão de navegador AdGuard para Chrome MV3 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +Como as extensões MV2 estão sendo eliminadas gradualmente na Chrome Web Store, os usuários do Chrome talvez precisem mudar para extensões MV3 compatíveis com a nova API do Manifest V3 do Chrome. Nossos pensamentos sobre esse tópico são amplamente discutidos em [nosso blog](https://adguard.com/pt_br/blog/tag/manifest-v3.html). -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +Nossa extensão MV3 bloqueia anúncios e rastreadores de forma eficaz, além de gerenciar perfeitamente widgets sociais, banners e anúncios em vídeo. A maioria dos usuários não notará nenhuma diferença operacional, mas há algumas limitações e mudanças que você precisa conhecer. -## Where to find our extensions +## Onde encontrar nossas extensões -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +A **versão MV3** substituiu nossa antiga extensão na [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +A **versão beta do MV3** ainda estará disponível na [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +A antiga extensão beta será renomeada para [**Bloqueador de anúncios AdGuard MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) e terá suporte até que o Google a desative. -## Main changes in features and settings +## Principais alterações nos recursos e configurações -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **Nenhuma atualização automática ou manual de filtros.** As opções _Atualizar filtros automaticamente_ e _Verificar atualização de filtros_ não estão mais disponíveis na aba _Filtros_. Como algumas das regras agora são aplicadas na forma de DNR, não podemos atualizar os filtros por solicitação, somente por meio do processo completo de atualização da extensão junto com a revisão nas lojas. -- **Filtering log** +- **Registro de filtragem** - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) + ![Registro de filtragem \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + Devido às restrições do DNR, não podemos mostrar exatamente qual regra funcionou, mas forneceremos uma “regra presumida que foi acionada” com base em nosso mecanismo. Para obter informações precisas, você precisará instalar o formato “descompactado” da extensão no seu navegador. Você encontrará instruções detalhadas sobre como fazer isso em um [artigo separado](/adguard-browser-extension/solving-problems/debug-rules/). -- _Tracking protection_ (formerly known as _Stealth mode_) +- _Proteção de rastreamento_ (anteriormente conhecido como _Modo furtivo_) - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) + ![Proteção contra rastreamento \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + Não há nenhuma seção _Cookies_, juntamente com _Autodestruição de cookies primários_ e _Autodestruição de cookies de terceiros_, pois não podemos definir o TTL dos cookies usando regras declarativas. -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- _Proteção contra phishing e malware_ não está mais disponível nas configurações gerais. Para se proteger de sites maliciosos e golpes, ative os filtros de _Segurança_ apropriados na aba _Filtros_. - ![Security \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) + ![Segurança \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) ## Limitações -### Maximum number of rules and filters +### Número máximo de regras e filtros -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +O Manifest V3 impõe limites em regras estáticas e regex por extensão. Os usuários podem receber notificações quando esses limites forem excedidos. -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) +![Limites de regras \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) +![Muitas extensões \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +Basicamente, o Manifest V3 divide as regras em estáticas (integradas) e dinâmicas, com limites rígidos. -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +**Regras estáticas:** mínimo de **30.000** regras por extensão, com um limite cumulativo de **330.000** para todas as extensões instaladas por um único usuário. -For regex rules, the limit is set at **1,000 per extension**. +Para regras regex, o limite é definido como **1.000 por extensão**. -The maximum number of simultaneously enabled filters is **50**. +O número máximo de filtros ativados simultaneamente é **50**. -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +**Regras dinâmicas:** é imposto um limite estrito de **5.000** regras, que inclui um máximo de 1.000 regras regex. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> **Regras convertidas** são regras que foram transformadas +> para o \[formato DNR] usando o [conversor declarativo][github-declarative-converter]. +> Durante esse processo de conversão, algumas regras podem substituir outras (`$badfilter`), algumas podem ser combinadas (`$removeparam`), +> resultando em uma lista de regras com uma ordem ligeiramente diferente. > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> Dessa lista de regras convertidas, usaremos apenas 5.000 regras. Os demais serão exibidos no editor, mas não serão aplicados. -Here's how a rule with a basic modifier is converted to a declarative rule: +Veja como uma regra com um modificador básico é convertida em uma regra declarativa: ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +é convertido para ```json [ @@ -94,14 +94,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +Mais exemplos podem ser encontrados no [GitHub][github-declarative-converter-examples]. -### Network rule modifiers +### Modificadores de regras de rede -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +Os modificadores de regras de rede têm limitações: alguns deles não podem ser implementados no MV3 ou só podem ser implementados com restrições. -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +Mais detalhes sobre as limitações podem ser encontrados no [GitHub][github-declarative-converter]. +Para obter mais informações sobre modificadores, consulte nossa [Base de conhecimento](/general/ad-filtering/create-own-filters). [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 0e30fbb1a40..0f13b080933 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + é convertido para ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4766,6 +4765,7 @@ The following scriptlets also may be used for debug purposes: [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" +[ext-mv3]: #what-product "Extensão de navegador AdGuard para Chrome MV3" [ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index d25d49e46d2..d43172a8163 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 256a9ca2015..e3086e1a93e 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ Manifest V3 делит правила на статические (встрое **Динамические правила:** установлено строгое ограничение в **5000** правил, включая не более 1000 правил с регулярными выражениями. -Если этот лимит превышен, будут применены только **5000 преобразованных правил** в следующем порядке: сначала правила Белого списка, затем пользовательские правила и только потом Собственные фильтры. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Преобразованные правила** — это правила, которые были преобразованы > в \[формат DNR] с помощью [декларативного конвертера][github-declarative-converter]. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 9222f328d34..c7f53b6f52d 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Ограничения -- Правила `$hls` разрешены только [**в доверенных фильтрах**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - Правила `$hls` применимы только к HLS-плейлистам, т. е. к тексту в кодировке UTF-8, начинающемуся со строки `#EXTM3U`. Никакие другие ответы не будут модифицированы этими правилами. - Правила с `$hls` не применяются к ответам размером больше 10 МБ. @@ -2249,7 +2249,7 @@ Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, :::caution Ограничения -Этот тип правил может быть использован [**только в доверенных фильтрах**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. Чтобы избежать потенциальных проблем с безопасностью, `$removeheader` не может убрать следующие заголовки: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Правила с модификатором `$removeparam` предназначены для того, чтобы убирать параметры запроса из URL-адресов. Обратите внимание, что такие правила применяются только к запросам `GET`, `HEAD`, `OPTIONS` и иногда к `POST`. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Синтаксис** **Базовый синтаксис** @@ -2488,8 +2486,9 @@ $removeparam=/^(utm_content|utm_campaign|utm_referrer)=/ :::caution Ограничения -- Правила с модификатором `$removeparam` могут быть использованы [**только в доверенных фильтрах**](#trusted-filters). -- Правила с `$removeparam` совместимы с [базовыми модификаторами](#basic-rules-basic-modifiers), [модификаторами типа контента](#content-type-modifiers), а также с модификаторами `$important` и `$app`. Правила с любыми другими модификаторами считаются некорректными и не будут применены. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Правила с любыми другими модификаторами считаются некорректными и не будут применены. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2507,19 +2506,19 @@ $removeparam=/^(utm_content|utm_campaign|utm_referrer)=/ You will need some knowledge of regular expressions to use `$replace` modifier. -**Функции** +**Features** -- Правила с `$replace` применяются к любому текстовому ответу, но не применяются к binary (`media`, `image`, `object` и т. д.). +- `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- Правила с `$replace` обладают более высоким приоритетом, чем другие базовые правила (**включая** правила исключений). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. -- Правила исключений уровня document с модификаторами `$content` или `$document` отменяют срабатывание правил `$replace`, даже если запрос им соответствует. -- Прочие правила исключений уровня document (с модификаторами `$generichide`, `$elemhide` или `$jsinject`) применяются вместе с правилами `$replace`. Это означает, что вы можете изменять содержимое страницы при помощи правила `$replace` и одновременно отменять косметические правила. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. +- Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. `$replace` value can be empty in the case of exception rules. See examples section for further information. **Несколько правил, соответствующих одному запросу** -In case if multiple `$replace` rules match a single request, we will apply each of them. **Правила будут применяться в алфавитном порядке.** +In case if multiple `$replace` rules match a single request, we will apply each of them. **The order is defined alphabetically.** **Синтаксис** @@ -2529,11 +2528,11 @@ In general, `$replace` syntax is similar to replacement with regular expressions replace = "/" regexp "/" replacement "/" modifiers ``` -- **`regexp`** — регулярное выражение. -- **`replacement`** — строка, которая будет использована для замены строки в соответствии с `regexp`. -- **`modifiers `** — флаги регулярных выражений. Например, `i` — поиск без учёта регистра, или `s` — режим одной строки. +- **`regexp`** — a regular expression. +- **`replacement`** — a string that will be used to replace the string corresponding to `regexp`. +- **`modifiers`** — a regular expression flags. For example, `i` — insensitive search, or `s` — single-line mode. -In the `$replace` value, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` for it. Например, экранированная запятая будет выглядеть так: `\,`. +In the `$replace` value, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` for it. For example, an escaped comma looks like this: `\,`. **Примеры** @@ -2541,11 +2540,11 @@ In the `$replace` value, two characters must be escaped: comma `,` and dollar si ||example.org^$replace=/()[\s\S]*<\/VAST>/\$1<\/VAST>/i ``` -У этого правила три части: +There are three parts in this rule: -- `regexp` (регулярное выражение) — `()(.|\s)*<\/VAST>` -- `replacement` (замена) — `\$1<\/VAST>` где `$` экранируется -- `modifiers` (флаги регулярных выражений) — `i` для поиска без учёта регистра +- `regexp` — `()(.|\s)*<\/VAST>`; +- `replacement` — `\$1<\/VAST>` where `$` is escaped; +- `modifiers` — `i` for insensitive search. You can see how this rule works here: http://regexr.com/3cesk @@ -2555,57 +2554,57 @@ You can see how this rule works here: http://regexr.com/3cesk 2. `||example.org^$replace=/Z/Y/` 3. `@@||example.org/page/*$replace=/Z/Y/` -- Правила 1 и 2 будут применены ко всем запросам, отправленным к `example.org`. -- Правило 2 отключено для запросов, соответствующих `||example.org/page/`, **но правило 1 при этом всё равно работает!** +- Both rule 1 and 2 will be applied to all requests sent to `example.org`. +- Rule 2 is disabled for requests matching `||example.org/page/`, **but rule 1 still works!** **Disabling `$replace` rules** -- `@@||example.org^$replace` отключит все правила с `$replace`, где есть `||example.org^`. -- `@@||example.org^$document` или `@@||example.org^$content` отключит все правила с `$replace`, **исходящие** со страниц домена `example.org`, **включая саму эту страницу**. +- `@@||example.org^$replace` will disable all `$replace` rules matching `||example.org^`. +- `@@||example.org^$document` or `@@||example.org^$content` will disable all `$replace` rules **originated from** pages of `example.org` **including the page itself**. :::caution Ограничения -Правила с модификатором `$replace` могут быть использованы [**только в доверенных фильтрах**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: :::info Совместимость -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Другие расширения не могут модифицировать содержимое страниц на сетевом уровне, поэтому там эти правила не работают. +Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`$urltransform`** {#urltransform-modifier} -Правила `$urltransform` позволяют изменять URL-адрес запроса, заменяя текст, соответствующий регулярному выражению. +The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. -**Функции** +**Features** - `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. -- `$urltransform` не будет применяться, если исходный URL-адрес заблокирован другими правилами. -- `$urltransform` будет применяться перед правилами `$removeparam`. +- `$urltransform` will not be applied if the original URL is blocked by other rules. +- `$urltransform` will be applied before `$removeparam` rules. -Значение `$urltransform` может быть пустым для правил исключений. +The `$urltransform` value can be empty for exception rules. **Несколько правил, соответствующих одному запросу** -Если несколько правил `$urltransform` соответствуют одному запросу, мы применим каждое из них. **Правила будут применяться в алфавитном порядке.** +If multiple `$urltransform` rules match a single request, we will apply each of them. **The order is defined alphabetically.** **Синтаксис** -Синтаксис `$urltransform` аналогичен замене регулярными выражениями [в Perl](http://perldoc.perl.org/perlrequick.html#Search-and-replace). +`$urltransform` syntax is similar to replacement with regular expressions [in Perl](http://perldoc.perl.org/perlrequick.html#Search-and-replace). ```text urltransform = "/" regexp "/" replacement "/" modifiers ``` -- **`regexp`** — регулярное выражение. -- **`replacement`** — строка, которая будет использована для замены строки в соответствии с `regexp`. -- **`modifiers `** — флаги регулярных выражений. Например, `i` — поиск без учёта регистра, или `s` — режим одной строки. +- **`regexp`** — a regular expression. +- **`replacement`** — a string that will be used to replace the string corresponding to `regexp`. +- **`modifiers`** — a regular expression flags. For example, `i` — insensitive search, or `s` — single-line mode. -В значении `$urltransform` необходимо экранировать два символа: запятую `,` и знак доллара `$`. Use the backslash character `\` for this. Например, экранированная запятая будет выглядеть так: `\,`. +In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Изменение происхождения** +**Changing the origin** :::info Совместимость @@ -2621,26 +2620,26 @@ As stated above, normally `$urltransform` rules are only allowed to change the p ||example.org^$urltransform=/(pref\/).*\/(suf)/\$1\$2/i ``` -У этого правила три части: +There are three parts in this rule: - `regexp` — `(pref\/).*\/(suf)`; -- `replacement` — `\$1\$2`, где `$` экранирован; -- `modifiers` (флаги регулярных выражений) — `i` для поиска без учёта регистра +- `replacement` — `\$1\$2` where `$` is escaped; +- `modifiers` — `i` for insensitive search. -**Несколько правил с `$urltransform`** +**Multiple `$urltransform` rules** 1. `||example.org^$urltransform=/X/Y/` 2. `||example.org^$urltransform=/Z/Y/` 3. `@@||example.org/page/*$urltransform=/Z/Y/` -- Правила 1 и 2 будут применены ко всем запросам, отправленным к `example.org`. -- Правило 2 отключено для запросов, соответствующих `||example.org/page/`, **но правило 1 при этом всё равно работает!** +- Both rule 1 and 2 will be applied to all requests sent to `example.org`. +- Rule 2 is disabled for requests matching `||example.org/page/`, **but rule 1 still works!** -**Повторное сопоставление правил после преобразования URL** +**Re-matching rules after transforming the URL** After applying all matching `$urltransform` rules, the transformed request will be matched against all other rules: -Например, со следующими правилами: +E.g., with the following rules: ```adblock ||example.com^$urltransform=/firstpath/secondpath/ @@ -2649,16 +2648,16 @@ After applying all matching `$urltransform` rules, the transformed request will the request to `https://example.com/firstpath` will be blocked. -**Отключение правил с `$urltransform`** +**Disabling `$urltransform` rules** -- `@@||example.org^$urltransform` отключит все правила с `$urltransform`, где есть `||example.org^`. -- `@@||example.org^$urltransform=/Z/Y/` отключит правило с `$urltransform=/Z/Y/` для любого запроса, соответствующего `||example.org^`. +- `@@||example.org^$urltransform` will disable all `$urltransform` rules matching `||example.org^`. +- `@@||example.org^$urltransform=/Z/Y/` will disable the rule with `$urltransform=/Z/Y/` for any request matching `||example.org^`. -Правила с `$urltransform` также можно отключить, используя правила-исключения `$document` и `$urlblock`. Но базовые правила исключений без модификаторов не могут этого сделать. Например, `@@||example.com^` не отключит `$urltransform=/X/Y/` для запросов к **example.com**, а `@@||example.com^$urlblock` отключит. +`$urltransform` rules can also be disabled by `$document` and `$urlblock` exception rules. Но базовые правила исключений без модификаторов не могут этого сделать. For example, `@@||example.com^` will not disable `$urltransform=/X/Y/` for requests to **example.com**, but `@@||example.com^$urlblock` will. :::caution Ограничения -Правила с модификатором `$urltransform` могут быть использованы [**только в доверенных фильтрах**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2670,7 +2669,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -Модификатор `noop` не делает ничего и используется только для того, чтобы улучшить читаемость правил. Он состоит из последовательности символов нижнего подчёркивания (`_`) произвольной длины и может фигурировать в правиле так часто, как это необходимо. +`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. **Примеры** @@ -2681,43 +2680,43 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad :::info Совместимость -Правила с модификатором `noop` не поддерживаются в AdGuard Content Blocker. +Rules with `noop` modifier are not supported by AdGuard Content Blocker. ::: #### **`$empty` (устаревший)** {#empty-modifier} -:::caution Скоро устареет +:::caution Deprecation notice -Этот модификатор считается устаревшим. Вместо него теперь используется [модификатор `$redirect`](#redirect-modifier). Правила с `$empty` всё ещё поддерживаются и преобразуются в `$redirect=nooptext`, но в будущем перестанут поддерживаться. +This modifier is deprecated in favor of the [`$redirect` modifier](#redirect-modifier). Rules with `$empty` are still supported and being converted into `$redirect=nooptext` now but the support shall be removed in the future. ::: -Обычно заблокированный запрос выглядит для браузера как ошибка сервера. В случае применения модификатора `$empty` AdGuard эмулирует пустой ответ сервера со статусом `200 OK`. +Usually, blocked requests look like a server error to browser. If you use `$empty` modifier, AdGuard will emulate a blank response from the server with`200 OK` status. **Примеры** -- `||example.org^$empty` возвращает пустой ответ для всех запросов к домену `example.org` и всех его поддоменов. +- `||example.org^$empty` returns an empty response to all requests to `example.org` and all subdomains. :::info Совместимость -Правила с модификатором `$empty` не поддерживаются в AdGuard Content Blocker, AdGuard для iOS и AdGuard для Safari. +Rules with `$empty` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: #### **`$mp4` (устаревший)** {#mp4-modifier} -:::caution Скоро устареет +:::caution Deprecation notice -Этот модификатор считается устаревшим. Вместо него теперь используется [модификатор `$redirect`](#redirect-modifier). Правила с `$mp4` всё ещё поддерживаются и преобразуются в `$redirect=noopmp4-1s,media`, но в будущем перестанут поддерживаться. +This modifier is deprecated in favor of the [`$redirect` modifier](#redirect-modifier). Rules with `$mp4` are still supported and being converted into `$redirect=noopmp4-1s,media` now but the support shall be removed in the future. ::: -В качестве ответа на заблокированный запрос AdGuard возвращает короткую видео-заглушку. +As a response to blocked request AdGuard returns a short video placeholder. **Примеры** -- `||example.com/videos/$mp4` блокирует загрузку видео с адресов `||example.com/videos/*` и заменяет ответ на видео-заглушку. +- `||example.com/videos/$mp4` blocks all video downloads from `||example.com/videos/*` and changes the response to a video placeholder. :::info Совместимость @@ -2751,8 +2750,8 @@ The base priority of any rule is 1. If the calculated priority is a floating-poi :::info Совместимость -- The concept of priority has been introduced in [TSUrlFilter][] v2.1.0 and [CoreLibs][] v1.13. До этого в AdGuard не было специального алгоритма вычисления приоритетов, и обработка конфликтов могла отличаться в зависимости от продукта и версии AdGuard. -- AdGuard для iOS, Safari и AdGuard Content Blocker зависят от реализации браузера и не могут следовать указанным здесь правилам. +- The concept of priority has been introduced in [TSUrlFilter][] v2.1.0 and [CoreLibs][] v1.13. Before that AdGuard didn't have any special priority computation algorithm and collisions handling could be different depending on AdGuard product and version. +- AdGuard for iOS, Safari, and AdGuard Content Blocker rely on the browsers implementation and they cannot follow the rules specified here. ::: @@ -2766,18 +2765,18 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve -- [`$app`](#app-modifier) с приложениями, исключаемыми с помощью `~` -- [`$denyallow`](#denyallow-modifier) -- [`$domain`](#domain-modifier) с доменами, исключаемыми с помощью `~` -- [`$match-case`](#match-case-modifier) -- [`$method`](#method-modifier) с методами, исключаемыми с помощью `~` +- [`$app`](#app-modifier) with negated applications using `~`, +- [`$denyallow`](#denyallow-modifier), +- [`$domain`](#domain-modifier) with negated domains using `~`, +- [`$match-case`](#match-case-modifier), +- [`$method`](#method-modifier) with negated methods using `~`, - [`$strict-first-party`](#strict-first-party-modifier), - [`$strict-third-party`](#strict-third-party-modifier), -- [`$third-party`](#third-party-modifier) -- [`$to`](#to-modifier) -- ограниченные модификаторы [сontent-type](#content-type-modifiers) с `~` +- [`$third-party`](#third-party-modifier), +- [`$to`](#to-modifier), +- restricted [content-types](#content-type-modifiers) with `~`. -При работе с исключаемым доменом, приложением, методом или типом содержимого мы добавляем **1 балл** за существование самого модификатора, независимо от количества исключаемых доменов или типов содержимого. Это связано с тем, что область действия правила и так бесконечно широка. Put simply, by prohibiting multiple domains, content-types, methods or apps, the scope of the rule becomes only minimally smaller. +When dealing with a negated domain, app, method, or content-type, we add **1 point** for the existence of the modifier itself, regardless of the quantity of negated domains or content-types. This is because the rule's scope is already infinitely broad. Put simply, by prohibiting multiple domains, content-types, methods or apps, the scope of the rule becomes only minimally smaller. #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} @@ -2785,59 +2784,59 @@ All valid content types: -- [`$document`](#document-modifier) -- [`$font`](#font-modifier) -- [`$image`](#image-modifier) -- [`$media`](#media-modifier) -- [`$object`](#object-modifier) -- [`$other`](#other-modifier) -- [`$ping`](#ping-modifier) -- [`$script`](#script-modifier) -- [`$stylesheet`](#stylesheet-modifier) -- [`$subdocument`](#subdocument-modifier) -- [`$websocket`](#websocket-modifier) -- [`$xmlhttprequest`](#xmlhttprequest-modifier) +- [`$document`](#document-modifier), +- [`$font`](#font-modifier), +- [`$image`](#image-modifier), +- [`$media`](#media-modifier), +- [`$object`](#object-modifier), +- [`$other`](#other-modifier), +- [`$ping`](#ping-modifier), +- [`$script`](#script-modifier), +- [`$stylesheet`](#stylesheet-modifier), +- [`$subdocument`](#subdocument-modifier), +- [`$websocket`](#websocket-modifier), +- [`$xmlhttprequest`](#xmlhttprequest-modifier); This also includes rules that implicitly add all content types: - [`$all`](#all-modifier); -Или правила, которые неявно добавляют модификатор `$document`: +Or rules that implicitly add the modifier `$document`: -- [`$popup`](#popup-modifier) +- [`$popup`](#popup-modifier); -Или некоторые специальные исключения, которые неявно добавляют `$document,subdocument`: +Or some specific exceptions that implicitly add `$document,subdocument`: -- [`$content`](#content-modifier) -- [`$elemhide`](#elemhide-modifier) -- [`$extension`](#extension-modifier) -- [`$genericblock`](#genericblock-modifier) -- [`$generichide`](#generichide-modifier) -- [`$jsinject`](#jsinject-modifier) -- [`$specifichide`](#specifichide-modifier) -- [`$urlblock`](#urlblock-modifier) +- [`$content`](#content-modifier), +- [`$elemhide`](#elemhide-modifier), +- [`$extension`](#extension-modifier), +- [`$genericblock`](#genericblock-modifier), +- [`$generichide`](#generichide-modifier), +- [`$jsinject`](#jsinject-modifier), +- [`$specifichide`](#specifichide-modifier), +- [`$urlblock`](#urlblock-modifier); -Или методы, разрешённые модификатором [`$method`](#method-modifier). +Or allowed methods via [`$method`](#method-modifier). -Или правила с [`$header`](#header-modifier). +Or rules with [`$header`](#header-modifier). -Наличие любых модификаторов content-type добавляет `(50 + 50 / N)`, где `N` — количество модификаторов, например: `||example.com^$image,script` добавит `50 + 50 / 2 = 50 + 25 = 75` к общему весу правила. +The presence of any content-type modifiers adds `(50 + 50 / N)`, where `N` is the number of modifiers present, for example: `||example.com^$image,script` will add `50 + 50 / 2 = 50 + 25 = 75` to the total weight of the rule. The `$all` also belongs to this category, because it implicitly adds all content type modifiers, e.g., `$document,subdocument,image,script,media,` + `$popup`. -К этой категории относится и `$popup`, так как в нём неявно добавляется модификатор `$document`. Аналогично, конкретные исключения добавляют `$document,subdocument`. +The `$popup` also belongs to this category, because it implicitly adds the modifier `$document`. Similarly, specific exceptions add `$document,subdocument`. -Если в правиле есть модификатор `$method` с разрешёнными методами, то он добавляет `(50 + 50 / N)`, где `N` — количество разрешённых методов, например: `||example.com^$method=GET|POST|PUT` добавит `50 + 50 / 3 = 50 + 16,6 = 67` к общему весу правила. +If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -Если в правиле есть модификатор `$header`, то он добавляет `50`. +If there is a `$header` modifier in the rule, it adds `50`. #### `$domain` или `$app` с разрешёнными доменами или приложениями {#priority-category-3} -Домены или приложения, указанные с помощью `$domain` и `$app` соответственно, добавят `100 + 100 / N`, где `N` — количество значений модификатора, например: `||example.com^$domain=example.com|example.org|example.net` добавит `100 + 100 / 3 = 135` или `||example.com^$app=org.example.app1|org.example.app2` добавит `100 + 100 / 2 = 100 + 51 = 151` или `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` добавит `100 + 100/1` (часть $domain) и `100 + 100/2` (часть $app) — в сумме `350`. +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`. -Значения модификаторов regexps или tld будут интерпретироваться как обычные записи вида `example.com` и считаться по одному, например: `||example.com^$domain=example.*` будет добавлено `100 + 100 / 1 = 200` или `||example.com^$domain=example.*|adguard.*` будет добавлено `100 + 100 / 2 = 150`. +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`. #### Правила `$redirect` {#priority-category-6} @@ -2846,42 +2845,42 @@ The `$all` also belongs to this category, because it implicitly adds all content - [`$redirect`](#redirect-modifier), - [`$redirect-rule`](#redirect-rule-modifier). -Каждое из них добавляет `10^3` к приоритету правила. +Each of which adds `10^3` to rule priority. #### Особые исключения {#priority-category-4} -- [`$content`](#content-modifier) -- [`$elemhide`](#elemhide-modifier) -- [`$extension`](#extension-modifier) -- [`$genericblock`](#genericblock-modifier) -- [`$generichide`](#generichide-modifier) -- [`$jsinject`](#jsinject-modifier) -- [`$specifichide`](#specifichide-modifier) -- [`$urlblock`](#urlblock-modifier) +- [`$content`](#content-modifier), +- [`$elemhide`](#elemhide-modifier), +- [`$extension`](#extension-modifier), +- [`$genericblock`](#genericblock-modifier), +- [`$generichide`](#generichide-modifier), +- [`$jsinject`](#jsinject-modifier), +- [`$specifichide`](#specifichide-modifier), +- [`$urlblock`](#urlblock-modifier); -Каждое из них добавляет `10^4` к приоритету. +Each of which adds `10^4` to the priority. -As well as exception with [`$document modifier`](#document-modifier): because it's an alias for `$elemhide,content,jsinject,urlblock,extension`. Оно добавит `10^4` для каждого модификатора из [верхнего списка](#priority-category-4), `10^4 * 5` в сумме. +As well as exception with [`$document modifier`](#document-modifier): because it's an alias for `$elemhide,content,jsinject,urlblock,extension`. It will add `10^4` for each modifier from [the top list](#priority-category-4), `10^4 * 5` in total. In addition, each of these exceptions implicitly adds the two allowed content-type modifiers `$document,subdocument`. #### Правила белого списка {#priority-category-5} -Модификатор `@@` добавляет `10^5` к приоритету правила. +Modifier `@@` adds `10^5` to rule priority. #### Правила `$important` {#priority-category-7} -Модификатор [`$important`](#important-modifier) добавляет `10^6` к приоритету правила. +Modifier [`$important`](#important-modifier) adds `10^6` to rule priority. #### Правила, для которых нет веса приоритета {#priority-category-extra} -[Прочие модификаторы](#advanced-capabilities), которые должны выполнять дополнительную пост- или предобработку запросов, ничего не добавляют к приоритету правил. +[Other modifiers](#advanced-capabilities), which are supposed to perform additional post- or pre-processing of requests, do not add anything to the rules priority. :::note -Модификатор [`$replace`](#replace-modifier) имеет приоритет над всеми блокирующими правилами категорий 1–3, а также над правилами исключений из категорий 3–5, **, кроме** [`$content`](#content-modifier), поскольку исключение с модификатором `$content` отменяет все правила `$replace`. +The [`$replace`](#replace-modifier) modifier takes precedence over all blocking rules of categories 1-3, as well as exception rules from categories 3-5, **except** [`$content`](#content-modifier), because an exception with the `$content` modifier overrides all `$replace` rules. ::: @@ -2889,29 +2888,29 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty 1. `||example.com^` - Вес правила без модификаторов: `1`. + Weight of the rule without modifiers: `1`. 1. `||example.com^$match-case` - Вес правила: базовый вес + вес модификатора из [категории 1](#priority-category-1): `1 + 1 = 2`. + Rule weight: base weight + weight of the modifier from [category 1](#priority-category-1): `1 + 1 = 2`. 1. `||example.org^$removeparam=p` - Вес правила: базовый вес + 0, так как $removeparam [не участвует](#priority-category-extra) в расчёте приоритета: `1 + 0 = 1`. + Rule weight: base weight + 0, since $removeparam [is not involved](#priority-category-extra) in the priority calculation: `1 + 0 = 1`. 1. `||example.org^$document,redirect=nooptext` - Вес правила: базовый вес + допустимый тип содержимого, [категория 3](#priority-category-3) + $redirect из [категория 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`. + Rule weight: base weight + allowed content type, [category 3](#priority-category-3) + $redirect from [category 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`. 1. `@@||example.org^$removeparam=p,document` - Вес правила: базовый вес + правило белого списка, [категория 5](#priority-category-5) + 0, потому что $removeparam [не участвует](#priority-category-extra) в расчёте приоритета + разрешённый тип контента, [категория 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`. + Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + 0 because $removeparam [is not involved](#priority-category-extra) in the priority calculation + allowed content type, [category 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`. 1. `@@||example.com/ad/*$domain=example.org|example.net,important` - Вес правила: базовый вес + правило белого списка, [категория 5](#priority-category-5) + важное правило, [категория 7](#priority-category-7) + разрешённые домены, [категория 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`. + Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + important rule, [category 7](#priority-category-7) + allowed domains, [category 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`. -1. `@@||example.org^$document` без дополнительных модификаторов — это псевдоним для `@@|||example.com^$elemhide,content,jsinject,urlblock,extension` +1. `@@||example.org^$document` without additional modifiers is an alias for `@@||example.com^$elemhide,content,jsinject,urlblock,extension` Rule weight: base weight + specific exceptions, [category 4](#priority-category-4) + two allowed content types (document and subdocument), [category 2](#priority-category-2): `1 + 10000 * 4 + (50 + 50 / 2) = 40076`. @@ -2919,13 +2918,13 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty Rule weight: base weight + allowed content type, [category 2](#priority-category-2) + allowed domain, [category 3](#priority-category-3) + denyallow, [category 1](#priority-category-1): `1 + (50 + 50/1) + (100 + 100 / 1) + 1 = 303`. -1. `||example.com^$all` — псевдоним для `||example.com^$document,subdocument,image,script,media и т. д. + $popup` +1. `||example.com^$all` — alias to `||example.com^$document,subdocument,image,script,media,etc. + $popup` - Вес правила: базовый вес + всплывающее окно ([категория 1](#priority-category-1)) + разрешённые типы контента ([категория 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`. + Rule weight: base weight + popup ([category 1](#priority-category-1)) + allowed content types ([category 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`. ## Другие правила {#non-basic-rules} -Базовых правил может быть недостаточно для блокировки рекламы. Иногда для этого требуется скрыть какой-нибудь элемент или изменить часть HTML-кода страницы, при этом ничего не сломав. Для этого предназначены правила, описанные в данном разделе. +However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. | Категории \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | | --------------------------------------------- |:------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| @@ -2947,15 +2946,15 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty :::info -Для работы с косметическими правилами необходимы знания HTML и CSS. So, if you want to learn how to make such rules, we recommend to get acquainted with [this documentation](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/What_is_CSS). +Work with non-basic rules requires the basic knowledge of HTML and CSS. So, if you want to learn how to make such rules, we recommend to get acquainted with [this documentation](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/What_is_CSS). ::: ### Правила скрытия элементов {#cosmetic-elemhide-rules} -Правила скрытия элементов предназначены, как это следует из их названия, для скрытия элементов веб-страниц. По сути это аналогично применению стиля `{ display: none; }` к выбранному элементу. +Element hiding rules are used to hide the elements of web pages. It is similar to applying `{ display: none; }` style to selected element. -Правила скрытия элементов работают по-разному, и их приоритет меняется [в зависимости от платформы](#cosmetic-rules-priority). +Element hiding rules may operate differently [depending on the platform](#cosmetic-rules-priority). #### Синтаксис @@ -2964,66 +2963,66 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty domains = [domain0, domain1[, ...[, domainN]]] ``` -- **`selector`** — [CSS-селектор](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), задающий элементы, которые должны быть скрыты. -- **`domains`** — ограничение на домены, на страницах которых будет применено правило. +- **`selector`** — [CSS selector](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), defines the elements to be hidden. +- **`domains`** — domain restriction for the rule. -Если вы хотите ограничить область действия одним или более доменами, просто перечислите их через запятую. Например: `example.org,example.com##selector`. +If you want to limit the rule application area to certain domains, just enter them separated with commas. For example: `example.org,example.com##selector`. -Это правило будет работать также на всех поддоменах `example.org` и `example.com`. +This rule will be also applied to all subdomains of `example.org` and `example.com`. -Если вы хотите, чтобы правило не применялось к определённым доменам, начните доменное имя со знака `~`. Например: `~example.org##selector`. +Если вы хотите, чтобы правило не применялось к определённым доменам, начните доменное имя со знака `~`. For example: `~example.org##selector`. -Вы можете использовать оба подхода в одном правиле. Например, правило `example.org,~subdomain.example.org##domain` будет работать для домена `example.org` и всех его поддоменов, **кроме `subdomain.example.org`**. +You can use both approaches in a single rule. For example, `example.org,~subdomain.example.org##domain` will work for `example.org` and all subdomains, **except `subdomain.example.org`**. :::note -Правила скрытия не зависят друг от друга. Если в фильтре есть правило `example.org##selector` и вы добавляете правило `~example.org##selector`, то оба этих правила будут применены независимо друг от друга. +Element hiding rules are not dependent on each other. If there is a rule `example.org##selector` in the filter and you add `~example.org##selector` both rules will be applied independently. ::: **Примеры** -- `example.com##div.textad` скроет элемент `div` с классом `textad` на домене `example.com` и всех его поддоменах. -- `example.com,example.org###adblock` скроет элемент с атрибутом `id` равным `adblock` на доменах `example.com`, `example.org` и всех их поддоменах. -- `~example.com##.textad` скроет элемент с классом `textad` на всех доменах, кроме `example.com` и всех его поддоменов. +- `example.com##div.textad` — hides a `div` with the class `textad` at `example.com` and all subdomains. +- `example.com,example.org###adblock` — hides an element with attribute `id` equals `adblock` at `example.com`, `example.org` and all subdomains. +- `~example.com##.textad` — hides an element with the class `textad` at all domains, except `example.com` and its subdomains. **Ограничения** -Safari не поддерживает одновременно разрешённые и запрещённые домены. поэтому правила вида `example.org,~foo.example.org##.textad` не работают в AdGuard для Safari. +Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Исключения** -Исключения могут отключать некоторые правила на определённых доменах. Они очень похожи на обычные правила-исключения, только вместо `##` нужно использовать `#@#`. +Exceptions can disable some rules on particular domains. They are very similar to usual exception rules, but instead of `##` you have to use `#@#`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock ##.textad ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com#@#.textad ``` -В некоторых случаях может потребоваться отключение всех запрещающих правил. Например, на время тестирования. Для этого воспользуйтесь правилом исключения без указания домена. Это полностью отключит соответствующее правило CSS elemhide для ВСЕХ доменов: +Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. It will completely disable matching CSS elemhide rule on ALL domains: ```adblock #@#.textad ``` -Правило такого вида даст аналогичный результат: +The same can be achieved by adding this rule: ```adblock *#@#.textad ``` -Применять такие исключения рекомендуется только в случае, когда изменить само правило скрытия невозможно. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions. ### CSS-правила {#cosmetic-css-rules} -Иногда недостаточно просто скрыть какой-либо элемент, чтобы заблокировать рекламу. Например, блокировка рекламного элемента может просто сломать вёрстку сайта. Для таких случаев AdGuard позволяет использовать гораздо более гибкие правила, чем обычные правила скрытия. С помощью таких правил вы можете добавить на страницу практически любой CSS-стиль. +Sometimes, simple hiding of an element is not enough to deal with advertising. For example, blocking an advertising element can just break the page layout. In this case AdGuard can use rules that are much more flexible than hiding rules. With these rules you can basically add any CSS styles to the page. **Синтаксис** @@ -3032,9 +3031,9 @@ example.com#@#.textad domains = [domain0, domain1[, ...[, domainN]]] ``` -- **`selector`** — [CSS-селектор](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), определяющий элементы, к которым мы хотим применить стиль. -- **`domains`** — ограничение на домены, на страницах которых будет применено правило. Строится по тем же правилам, что и в случае [правил скрытия элементов](#cosmetic-elemhide-rules). -- **`style`** — CSS-стиль, который мы хотим применить к выбранным элементам. +- **`selector`** — [CSS selector](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), that defines the elements we want to apply the style to. +- **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). +- **`style`** — CSS style, that we want to apply to selected elements. **Примеры** @@ -3042,95 +3041,95 @@ domains = [domain0, domain1[, ...[, domainN]]] example.com#$#body { background-color: #333!important; } ``` -Это правило применит стиль `background-color: #333!important;` к элементу `body` для домена `example.com` и всех его поддоменов. +This rule will apply a style `background-color: #333!important;` to the `body` element at `example.com` and all subdomains. **Исключения** -По аналогии с правилами скрытия существует специальный тип правил, отключающий действие выбранного правила CSS-стилей для определённых доменов. Синтаксис правил-исключений практически такой же, только маркер `#$#` заменяется на `#@$#`. +Just like with element hiding, there is a type of rules that disable the selected CSS style rule for particular domains. Exception rule syntax is almost the same, you just have to change `#$#` to `#@$#`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock #$#.textad { visibility: hidden; } ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com#@$#.textad { visibility: hidden; } ``` -Применять такие исключения рекомендуется только в случае, когда невозможно изменить само CSS-правило. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the CSS rule itself. In other cases it is better to change the original rule, using domain restrictions. :::caution Ограничения -Запрещено использование стилей, которые могут приводить к загрузке каких-либо ресурсов. Это означает, что нельзя использовать атрибуты типа ``. +Styles that lead to loading any resource are forbidden. Basically, it means that you cannot use any `` type of value in the style. ::: :::info Совместимость -CSS-правила не поддерживаются в AdGuard Content Blocker. +CSS rules are not supported by AdGuard Content Blocker. -CSS-правила работают по-разному, и их приоритет меняется [в зависимости от платформы](#cosmetic-rules-priority). +CSS rules may operate differently [depending on the platform](#cosmetic-rules-priority). ::: ### Расширенные CSS-селекторы {#extended-css-selectors} - [Ограничения](#extended-css-limitations) -- [Псевдокласс `:has()`](#extended-css-has) -- [Псевдокласс `:contains()`](#extended-css-contains) +- [Pseudo-class `:has()`](#extended-css-has) +- [Pseudo-class `:contains()`](#extended-css-contains) - [Псевдокласс `:matches-css()`](#extended-css-matches-css) -- [Псевдокласс `:matches-attr()`](#extended-css-matches-attr) -- [Псевдокласс `:matches-property()`](#extended-css-property) -- [Псевдокласс `:xpath()`](#extended-css-xpath) -- [Псевдокласс `:nth-ancestor()`](#extended-css-nth-ancestor) -- [Псевдокласс `:upward()`](#extended-css-upward) -- [Псевдокласс `:remove()` и псевдосвойство `remove`](#remove-pseudos) -- [Псевдокласс `:is()`](#extended-css-is) -- [Псевдокласс `:not()`](#extended-css-not) -- [Псевдокласс `:if-not()` (удалён)](#extended-css-if-not) +- [Pseudo-class `:matches-attr()`](#extended-css-matches-attr) +- [Pseudo-class `:matches-property()`](#extended-css-property) +- [Pseudo-class `:xpath()`](#extended-css-xpath) +- [Pseudo-class `:nth-ancestor()`](#extended-css-nth-ancestor) +- [Pseudo-class `:upward()`](#extended-css-upward) +- [Pseudo-class `:remove()` and pseudo-property `remove`](#remove-pseudos) +- [Pseudo-class `:is()`](#extended-css-is) +- [Pseudo-class `:not()`](#extended-css-not) +- [Pseudo-class `:if-not()` (removed)](#extended-css-if-not) -Возможностей CSS 3.0 не всегда хватает для блокировки рекламы. Чтобы решить эту проблему, AdGuard расширяет возможности CSS, добавляя поддержку новых псевдоэлементов. Мы разработали отдельную [библиотеку с открытым исходным кодом](https://github.com/AdguardTeam/ExtendedCss) для выбора нестандартных элементов и применения CSS-стилей с расширенными свойствами. +CSS 3.0 is not always enough to block ads. To solve this problem AdGuard extends CSS capabilities by adding support for the new pseudo-elements. We have developed a separate [open-source library](https://github.com/AdguardTeam/ExtendedCss) for non-standard element selecting and applying CSS styles with extended properties. -Идея расширенных возможностей заключается в возможности сопоставлять элементы DOM с селекторами на основе их собственного представления (стиль, текстовое содержимое и т. д.) или отношений с другими элементами. Также есть возможность применять стили с нестандартными свойствами CSS. +The idea of extended capabilities is an opportunity to match DOM elements with selectors based on their own representation (style, text content, etc.) or relations with other elements. There is also an opportunity to apply styles with non-standard CSS properties. -**Область применения** +**Application area** -Расширенные селекторы можно применять в любом косметическом правиле, будь то [правила скрытия](#cosmetic-elemhide-rules) или [CSS-правила](#cosmetic-css-rules). +Extended selectors can be used in any cosmetic rule, whether they are [element hiding rules](#cosmetic-elemhide-rules) or [CSS rules](#cosmetic-css-rules). :::info Совместимость -Правила с расширенными CSS-селекторами не поддерживаются в AdGuard Content Blocker. +Rules with extended CSS selectors are not supported by AdGuard Content Blocker. ::: **Синтаксис** -Независимо от того, какие CSS-псевдоклассы вы используете в правилах, вы можете использовать специальные маркеры для принудительного применения этих правил с помощью ExtendedCss. Рекомендуется использовать эти маркеры для всех косметических расширенных CSS-правил, чтобы их было легче отличить. +Regardless of the CSS pseudo-classes you are using in the rule, you can use special markers to force applying these rules by ExtendedCss. It is recommended to use these markers for all extended CSS cosmetic rules so that it was easier to find them. -Синтаксис расширенных CSS-правил: +The syntax for extended CSS rules: -- `#?#` — для скрытия элементов, `#@?#` — для исключений -- `#$?#` — для CSS-стилей, `#@$?#` — для исключений +- `#?#` — for element hiding, `#@?#` — for exceptions +- `#$?#` — for CSS rules, `#@$?#` — for exceptions -**Настоятельно рекомендуем** использовать эти маркеры каждый раз, когда вы используете расширенный CSS-селектор. +We **strongly recommend** using these markers any time when you use an extended CSS selector. **Примеры** -- `example.org#?#div:has(> a[target="_blank"][rel="nofollow"])` — это правило блокирует все элементы `div`, которые содержат дочерний элемент со ссылкой с атрибутами `[target="_blank"][rel="nofollow"]`. При этом правило будет работать только для домена `example.org` и всех его поддоменов. -- `example.com#$?#h3:contains(cookies) { display: none!important; }` — это правило устанавливает стиль `display: none!important` для всех элементов `h3`, которые содержат слово `cookies`. При этом правило будет работать только для домена `example.com` и всех его поддоменов. -- `example.net#?#.banner:matches-css(width: 360px)` — это правило блокирует все элементы `.banner`, которые содержат стиль `width: 360px`. При этом правило будет работать только для домена `example.net` и всех его поддоменов. -- `example.net#@?#.banner:matches-css(width: 360px)` — это правило отменяет действие предыдущего правила. +- `example.org#?#div:has(> a[target="_blank"][rel="nofollow"])` — this rule blocks all `div` elements containing a child node that has a link with the attributes `[target="_blank"][rel="nofollow"]`. The rule applies only to `example.org` and its subdomains. +- `example.com#$?#h3:contains(cookies) { display: none!important; }` — this rule sets the style `display: none!important` to all `h3` elements that contain the word `cookies`. The rule applies only to `example.com` and all its subdomains. +- `example.net#?#.banner:matches-css(width: 360px)` — this rule blocks all `.banner` elements with the style property `width: 360px`. The rule applies only to `example.net` and its subdomains. +- `example.net#@?#.banner:matches-css(width: 360px)` — this rule will disable the previous rule. -Вы можете применять стандартные CSS-селекторы с помощью библиотеки ExtendedCss, используя маркер правила `#?#`. Например, `#?#div.banner`. +You can apply standard CSS selectors using the ExtendedCss library by using the rule marker `#?#`, e.g. `#?#div.banner`. -Больше [об отладке расширенных селекторов](#selectors-debugging-mode). +Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Некоторые псевдоклассы не требуют селектора перед ними. [Универсальный селектор](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` облегчает чтение расширенного селектора, хотя и не влияет на поведение при подборе. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3138,11 +3137,11 @@ Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still #### Ограничения ExtendedCss {#extended-css-limitations} -1. [CSS-комментарии](https://developer.mozilla.org/en-US/docs/Web/CSS/Comments) и [at-rules](https://developer.mozilla.org/en-US/docs/Web/CSS/At-rule) не поддерживаются. +1. CSS [comments](https://developer.mozilla.org/en-US/docs/Web/CSS/Comments) and [at-rules](https://developer.mozilla.org/en-US/docs/Web/CSS/At-rule) are not supported. -2. У конкретного псевдокласса могут быть свои ограничения: [`:has()`](#extended-css-has-limitations), [`:xpath()`](#extended-css-xpath-limitations), [`:nth-ancestor()`](#extended-css-nth-ancestor-limitations), [`:upward()`](#extended-css-upward-limitations), [`:is()`](#extended-css-is-limitations), [`:not()`](#extended-css-not-limitations), and [`:remove()`](#extended-css-remove-limitations). +2. Specific pseudo-class may have its own limitations: [`:has()`](#extended-css-has-limitations), [`:xpath()`](#extended-css-xpath-limitations), [`:nth-ancestor()`](#extended-css-nth-ancestor-limitations), [`:upward()`](#extended-css-upward-limitations), [`:is()`](#extended-css-is-limitations), [`:not()`](#extended-css-not-limitations), and [`:remove()`](#extended-css-remove-limitations). -#### Псевдокласс `:has()` {#extended-css-has} +#### Pseudo-class `:has()` {#extended-css-has} Draft CSS 4.0 specification describes the [`:has()` pseudo-class](https://www.w3.org/TR/selectors-4/#relational). Unfortunately, [it is not yet supported](https://caniuse.com/css-has) by all popular browsers. @@ -3168,8 +3167,8 @@ Synonyms `:-abp-has()` is supported by ExtendedCss for better compatibility. [target]:has(selector) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `selector` — необходимый, стандартный или расширенный CSS-селектор +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selector` — required, standard or extended CSS selector The pseudo-class `:has()` selects the `target` elements that fit to the `selector`. Also the `selector` can start with a combinator. @@ -3179,8 +3178,8 @@ A selector list can be set in `selector` as well. In this case **all** selectors Usage of the `:has()` pseudo-class is [restricted for some cases (2, 3)](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54): -- запретить `:has()` внутри псевдоселекторов, принимающих только составные селекторы; -- запретить `:has()` после обычных псевдоэлементов. +- disallow `:has()` inside the pseudos accepting only compound selectors; +- disallow `:has()` after regular pseudo-elements. Native `:has()` pseudo-class does not allow `:has()`, `:is()`, `:where()` inside `:has()` argument to avoid increasing the `:has()` invalidation complexity ([case 1](https://bugs.chromium.org/p/chromium/issues/detail?id=669058#c54)). But ExtendedCss did not have such limitation earlier and filter lists already contain such rules, so we have not added this limitation to ExtendedCss and allow to use `:has()` inside `:has()` as it was possible before. To use it, just force ExtendedCss usage by setting `#?#`/`#$?#` rule marker. @@ -3239,13 +3238,13 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a ``` -:::danger Старый синтаксис +:::danger Old syntax [Backward compatible syntax for `:has()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-has) is supported but **not recommended**. ::: -#### Псевдокласс `:contains()` {#extended-css-contains} +#### Pseudo-class `:contains()` {#extended-css-contains} The `:contains()` pseudo-class principle is very simple: it allows to select the elements that contain specified text or which content matches a specified regular expression. Regexp flags are supported. @@ -3265,12 +3264,12 @@ Synonyms `:-abp-contains()` and `:has-text()` are supported for better compatibi [target]:contains(match) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `match` — требуется, строка или регулярное выражение для соответствия элементу `textContent`. Также поддерживаются флаги регулярных выражений. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `match` — required, string or regular expression for matching element `textContent`. Regular expression flags are supported. **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3294,19 +3293,19 @@ div:contains(/it .*banner/gi) :::note -Выбран только `div` с `id=match`, так как следующий элемент не содержит текст, а `banner` — это часть кода, а не текст. +Only the `div` with `id=match` is selected because the next element does not contain any text, and `banner` is a part of code, not a text. ::: -:::danger Старый синтаксис +:::danger Old syntax -[Синтаксис обратной совместимости для `:contains()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-contains) поддерживается, но **не рекомендуется**. +[Backward compatible syntax for `:contains()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-contains) is supported but **not recommended**. ::: #### Псевдокласс `:matches-css()` {#extended-css-matches-css} -Псевдокласс `:matches-css()` позволяет сопоставить элемент по свойствам его текущего стиля. Работа псевдокласса основана на использовании метода [`Window.getComputedStyle()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle). +The `:matches-css()` pseudo-class allows to match the element by its current style properties. The work of the pseudo-class is based on using the [`Window.getComputedStyle()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle) method. **Синтаксис** @@ -3314,20 +3313,20 @@ div:contains(/it .*banner/gi) [target]:matches-css([pseudo-element, ] property: pattern) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `pseudo-element` — необязательный, допустимый стандартный псевдоэлемент, например, `before`, `after`, `first-line` и т. д. -- `property` — требуется, название CSS-свойства, которое будет проверено у элемента -- `pattern` — требуется, шаблон значений, который использует то же простое сопоставление с подстановочными знаками, что и в основных правилах фильтрации URL-адресов, или регулярное выражение. Для этого типа соответствия AdGuard не обращает внимание на регистр. В случае с регулярными выражениями шаблон будет выглядеть так: `/regexp/`. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. +- `property` — required, a name of CSS property to check the element for +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. -**Экранирование и снятие специальных символов** +**Special characters escaping and unescaping** -Для **нерегулярных выражений** паттерны `(`,`)`,`[`,`]` должны быть **без экранирования**, например, `:matches-css(background-image:url(data:*))`. +For **non-regexp** patterns `(`,`)`,`[`,`]` must be **unescaped**, e.g. `:matches-css(background-image:url(data:*))`. -Для **регулярных выражений** паттерны `\` должны быть **экранированы**, например, `:matches-css(background-image: /^url\\("data:image\\/gif;base64.+/)`. +For **regexp** patterns `\` should be **escaped**, e.g. `:matches-css(background-image: /^url\\("data:image\\/gif;base64.+/)`. **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3340,7 +3339,7 @@ div:contains(/it .*banner/gi)
``` -`div`-элементы с псевдоэлементом `::before` и с указанным свойством `content` могут быть выбраны любым из этих расширенных селекторов: +the `div` elements with pseudo-element `::before` and with specified `content` property can be selected by any of these extended selectors: ```adblock ! паттерн строки @@ -3355,25 +3354,25 @@ div:matches-css(before, content: /block me/) :::caution Ограничения -Паттерны регулярных выражений **не поддерживают** флаги. +Regexp patterns **do not support** flags. ::: :::info Совместимость -Устаревшие псевдоклассы `:matches-css-before()` и `:matches-css-after()` больше не рекомендуются, но по-прежнему поддерживаются для лучшей совместимости. +Obsolete pseudo-classes `:matches-css-before()` and `:matches-css-after()` are no longer recommended but still are supported for better compatibility. ::: -:::danger Старый синтаксис +:::danger Old syntax -[Синтаксис обратной совместимости для `:matches-css()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-matches-css) поддерживается, но **не рекомендуется**. +[Backward compatible syntax for `:matches-css()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-matches-css) is supported but **not recommended**. ::: -#### Псевдокласс `:matches-attr()` {#extended-css-matches-attr} +#### Pseudo-class `:matches-attr()` {#extended-css-matches-attr} -Псевдокласс `:matches-attr()` позволяет выбрать элемент по его атрибутам, особенно если они рандомизированы. +The `:matches-attr()` pseudo-class allows selecting an element by its attributes, especially if they are randomized. **Синтаксис** @@ -3381,38 +3380,38 @@ div:matches-css(before, content: /block me/) [target]:matches-attr("name"[="value"]) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `name` — требуется, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления имени атрибута -- `value` — необязательный, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления значения атрибута +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `name` — required, simple string *or* string with wildcard *or* regular expression for attribute name matching +- `value` — optional, simple string *or* string with wildcard *or* regular expression for attribute value matching **Экранирование специальных символов** -Для паттернов **регулярных выражений** `"` и `\` должны быть **экранированы**, например, `div:matches-attr(class=/[\\w]{5}/)`. +For **regexp** patterns `"` and `\` should be **escaped**, e.g. `div:matches-attr(class=/[\\w]{5}/)`. **Примеры** -`div:matches-attr("ad-link")` выбирает элемент `div#target1`: +`div:matches-attr("ad-link")` selects the element `div#target1`: ```html
``` -`div:matches-attr("data-*"="adBanner")` выбирает элемент `div#target2`: +`div:matches-attr("data-*"="adBanner")` selects the element `div#target2`: ```html
``` -`div:matches-attr(*unit*=/^click$/)` выбирает элемент `div#target3`: +`div:matches-attr(*unit*=/^click$/)` selects the element `div#target3`: ```html
``` -`*:matches-attr("/.{5,}delay$/"="/^[0-9]*$/")` выбирает элемент `#target4`: +`*:matches-attr("/.{5,}delay$/"="/^[0-9]*$/")` selects the element `#target4`: ```html @@ -3423,13 +3422,13 @@ div:matches-css(before, content: /block me/) :::caution Ограничения -Паттерны регулярных выражений **не поддерживают** флаги. +Regexp patterns **do not support** flags. ::: -#### Псевдокласс `:matches-property()` {#extended-css-property} +#### Pseudo-class `:matches-property()` {#extended-css-property} -Псевдокласс `:matches-property()` позволяет выбирать элемент, сопоставляя его свойства. +The `:matches-property()` pseudo-class allows selecting an element by matching its properties. **Синтаксис** @@ -3437,23 +3436,23 @@ div:matches-css(before, content: /block me/) [target]:matches-property("name"[="value"]) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `name` — требуется, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления имени свойства элемента -- `value` — необязательный, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления значения свойства элемента +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `name` — required, simple string *or* string with wildcard *or* regular expression for element property name matching +- `value` — optional, simple string *or* string with wildcard *or* regular expression for element property value matching **Экранирование специальных символов** -Для паттернов **регулярных выражений** `"` и `\` должны быть экранированы, например, `div:matches-property(prop=/[\\w]{4}/)`. +For **regexp** patterns `"` and `\` must be escaped, e.g. `div:matches-property(prop=/[\\w]{4}/)`. :::note -Паттерны регулярных выражений поддерживаются в `name` для любого свойства в цепочке, например, `prop./^unit[\\d]{4}$/.type`. +Regexp patterns are supported in `name` for any property in chain, e.g. `prop./^unit[\\d]{4}$/.type`. ::: **Примеры** -Элемент с такими свойствами: +An element with such properties: ```javascript divProperties = { @@ -3473,7 +3472,7 @@ divProperties = { }; ``` -может быть выбран любым из этих расширенных селекторов: +can be selected by any of these extended selectors: ```adblock div:matches-property(check.track) @@ -3487,24 +3486,24 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip Для разработчиков фильтров +:::tip For filter maintainers -Чтобы проверить свойства конкретного элемента, сделайте следующее: +To check properties of a specific element, do the following: -1. Проверьте элемент страницы или выберите его в Инструментах разработчика браузера во вкладке `Элементы` -1. Запустите `console.dir($0)` во вкладке `Консоль` +1. Inspect the page element or select it in `Elements` tab of browser DevTools +1. Run `console.dir($0)` in `Console` tab ::: :::caution Ограничения -Паттерны регулярных выражений **не поддерживают** флаги. +Regexp patterns **do not support** flags. ::: -#### Псевдокласс `:xpath()` {#extended-css-xpath} +#### Pseudo-class `:xpath()` {#extended-css-xpath} -Псевдокласс `:xpath()` позволяет выбирать элементы согласно выражению XPath. +The `:xpath()` pseudo-class allows selecting an element by evaluating an XPath expression. **Синтаксис** @@ -3512,27 +3511,27 @@ div:matches-property(memoizedProps._owner.src=/ad/) [target]:xpath(expression) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор -- `expression` — требуется, допустимое XPath выражение +- `target`- optional, standard or extended CSS selector +- `expression` — required, valid XPath expression ##### Ограничения `:xpath()` {#extended-css-xpath-limitations} -`target` можно опустить, поэтому использовать его необязательно. Для любого другого псевдокласса это будет означать «применить ко *всем* узлам DOM», но в случае `:xpath()` это просто означает «применить к *целым* документам», и такое применение значительно замедляет выбор элементов. Вот почему такие правила, как `#?#:xpath(expression)`, ограничены поиском внутри тега `body`. Например, правило `#?#:xpath(//div[@data-st-area=\'Advert\'])` парсится как `#?#body:xpath(//div[@data-st- area=\'Advert\'])`. +`target` can be omitted so it is optional. For any other pseudo-class that would mean "apply to *all* DOM nodes", but in case of `:xpath()` it just means "apply to the *whole* document", and such applying slows elements selecting significantly. That's why rules like `#?#:xpath(expression)` are limited to looking inside the `body` tag. For example, rule `#?#:xpath(//div[@data-st-area=\'Advert\'])` is parsed as `#?#body:xpath(//div[@data-st-area=\'Advert\'])`. -Расширенные селекторы с `target`, определённым как *любой* селектор, — `*:xpath(expression)` — всё ещё можно использовать, но не рекомендуется. Поэтому следует уточнить `target`. +Extended selectors with defined `target` as *any* selector — `*:xpath(expression)` — can still be used but it is not recommended, so `target` should be specified instead. -Корректно работает только в конце селектора, за исключением псевдокласса [:remove()](#remove-pseudos). +Works properly only at the end of selector, except for [pseudo-class :remove()](#remove-pseudos). **Примеры** -`:xpath(//*[@class="banner"])` выбирает элемент `div#target1`: +`:xpath(//*[@class="banner"])` selects the element `div#target1`: ```html ``` -`:xpath(//*[@class="inner"]/..)` выбирает элемент `div#target2`: +`:xpath(//*[@class="inner"]/..)` selects the element `div#target2`: ```html @@ -3541,9 +3540,9 @@ div:matches-property(memoizedProps._owner.src=/ad/) ``` -#### Псевдокласс `:nth-ancestor()` {#extended-css-nth-ancestor} +#### Pseudo-class `:nth-ancestor()` {#extended-css-nth-ancestor} -Псевдокласс `:nth-ancestor()` позволяет искать *n-ного* предка по отношению к ранее выбранному элементу. +The `:nth-ancestor()` pseudo-class allows to lookup the *nth* ancestor relative to the previously selected element. ```text subject:nth-ancestor(n) @@ -3563,11 +3562,11 @@ subject:nth-ancestor(n) ##### Ограничения `:nth-ancestor()` {#extended-css-nth-ancestor-limitations} -Псевдокласс `:nth-ancestor()` не поддерживается внутри аргумента псевдокласса [`:not()`](#extended-css-not). +The `:nth-ancestor()` pseudo-class is not supported inside the argument of the [`:not()` pseudo-class](#extended-css-not). **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3584,9 +3583,9 @@ subject:nth-ancestor(n) ``` -`.child:nth-ancestor(1)` выбирает элемент `div#target1`, `div[class="inner"]:nth-ancestor(3)` выбирает элемент `div#target2`. +`.child:nth-ancestor(1)` selects the element `div#target1`, `div[class="inner"]:nth-ancestor(3)` selects the element `div#target2`. -#### Псевдокласс `:upward()` {#extended-css-upward} +#### Pseudo-class `:upward()` {#extended-css-upward} The `:upward()` pseudo-class allows to lookup the ancestor relative to the previously selected element. @@ -3596,10 +3595,10 @@ The `:upward()` pseudo-class allows to lookup the ancestor relative to the previ subject:upward(ancestor) ``` -- `subject` — стандартный или расширенный CSS-селектор, необходим -- `ancestor` — требуется, спецификация для предка элемента, выбранного `subject`, может быть задана как: - - *число* >= 1 и < 256 для указания расстояния до нужного предка, то же, что и [`:nth-ancestor()`](#extended-css-nth-ancestor) - - *стандартный CSS-селектор* для поиска ближайшего предка +- `subject` — обязателен. Стандартный или расширенный CSS-селектор +- `ancestor` — required, specification for the ancestor of the element selected by `subject`, can be set as: + - *number* >= 1 and < 256 for distance to the needed ancestor, same as [`:nth-ancestor()`](#extended-css-nth-ancestor) + - *standard CSS selector* for matching closest ancestor ##### Ограничения `:upward()` {#extended-css-upward-limitations} @@ -3607,7 +3606,7 @@ The `:upward()` pseudo-class is not supported inside the argument of the [`:not( **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3626,7 +3625,7 @@ The `:upward()` pseudo-class is not supported inside the argument of the [`:not( `.inner:upward(div[data])` selects the element `div#target1`, `.inner:upward(div[id])` selects the element `div#target2`, `.child:upward(1)` selects the element `div#target1`, `.inner:upward(3)` selects the element `div#target2`. -#### Псевдокласс `:remove()` и псевдосвойство `remove` {#remove-pseudos} +#### Pseudo-class `:remove()` and pseudo-property `remove` {#remove-pseudos} Sometimes, it is necessary to remove a matching element instead of hiding it or applying custom styles. In order to do it, you can use the `:remove()` pseudo-class as well as the `remove` pseudo-property. @@ -3642,7 +3641,7 @@ selector:remove() selector { remove: true; } ``` -- `subject` — обязателен. Стандартный или расширенный CSS-селектор +- `selector` — required, standard or extended CSS selector ##### Ограничения `:remove()` и `remove` {#extended-css-remove-limitations} @@ -3650,7 +3649,7 @@ The `:remove()` pseudo-class is limited to work properly only at the end of sele For applying the `:remove()` pseudo-class to any element, the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` should be used. Otherwise such extended selector may be considered as invalid, e.g. `.banner > :remove()` is not valid for removing any child element of `banner` class element, so it should look like `.banner > *:remove()`. -Если используется псевдокласс `:remove()` или псевдосвойство `remove`, все свойства стиля игнорируются, кроме псевдосвойства [`debug`](#selectors-debug-mode). +If the `:remove()` pseudo-class or the `remove` pseudo-property is used, all style properties are ignored except for the [`debug` pseudo-property](#selectors-debug-mode). **Примеры** @@ -3664,13 +3663,13 @@ div[class]:has(> a > img) { remove: true; } :::note -Правила с псевдосвойством `remove` должны использовать маркер `#$?#`: `$` для синтаксиса правил CSS-стиля, `?` для синтаксиса ExtendedCss. +Rules with the `remove` pseudo-property must use `#$?#` marker: `$` for CSS-style rule syntax, `?` for ExtendedCss syntax. ::: -#### Псевдокласс `:is()` {#extended-css-is} +#### Pseudo-class `:is()` {#extended-css-is} -Псевдокласс `:is()` позволяет сопоставить любой элемент, который может быть выбран любым из переданных ему селекторов. Некорректные селекторы пропускаются, и псевдокласс работает с допустимыми селекторами без каких-либо ошибок. Наша реализация [нативного`:is()` псевдокласса](https://developer.mozilla.org/en-US/docs/Web/CSS/:is). +The `:is()` pseudo-class allows to match any element that can be selected by any of selectors passed to it. Invalid selectors are skipped and the pseudo-class deals with valid ones with no error thrown. Our implementation of the [native `:is()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:is). **Синтаксис** @@ -3678,20 +3677,20 @@ div[class]:has(> a > img) { remove: true; } [target]:is(selectors) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `selectors` — [*щадящий список*](https://drafts.csswg.org/selectors-4/#typedef-forgiving-selector-list) стандартных и расширенных селекторов. Для расширенных селекторов поддерживаются только составные селекторы, а не сложные. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selectors` — [*forgiving selector list*](https://drafts.csswg.org/selectors-4/#typedef-forgiving-selector-list) of standard or extended selectors. For extended selectors, only compound selectors are supported, not complex. ##### Ограничения `:is()` {#extended-css-is-limitations} -Правила с псевдоклассом `:is()` должны использовать [нативную реализацию `:is()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is), если они используют маркер `##` и если это возможно, то есть без других расширенных селекторов внутри. To force applying ExtendedCss rules with `:is()`, use `#?#`/`#$?#` marker explicitly. +Rules with the `:is()` pseudo-class must use the [native implementation of `:is()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is) if rules use `##` marker and it is possible, i.e. with no other extended selectors inside. To force applying ExtendedCss rules with `:is()`, use `#?#`/`#$?#` marker explicitly. If the `:is()` pseudo-class argument `selectors` is an extended selector, due to the way how the `:is()` pseudo-class is implemented in ExtendedCss v2.0, it is impossible to apply it to the top DOM node which is `html`, i.e. `#?#html:is()` does not work. So if `target` is not defined or defined as the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, the extended pseudo-class applying is limited to **`html`'s children**, e.g. rules `#?#:is(...)` and `#?#*:is(...)` are parsed as `#?#html *:is(...)`. Please note that there is no such limitation for a standard selector argument, i.e. `#?#html:is(.locked)` works fine. -[Сложные селекторы](https://www.w3.org/TR/selectors-4/#complex) с расширенными псевдоклассами не поддерживаются в качестве аргумента `selectors` для псевдокласса `:is()` — разрешены только [составные](https://www.w3.org/TR/selectors-4/#compound). Ознакомьтесь с примерами, чтобы разобраться в деталях. +[Complex selectors](https://www.w3.org/TR/selectors-4/#complex) with extended pseudo-classes are not supported as `selectors` argument for `:is()` pseudo-class, only [compound ones](https://www.w3.org/TR/selectors-4/#compound) are allowed. Check examples below for more details. **Примеры** -`#container *:is(.inner, .footer)` выбирает только элемент `div#target1`: +`#container *:is(.inner, .footer)` selects only the element `div#target1`: ```html @@ -3704,7 +3703,7 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to ``` -Из-за ограничений `:is(*:not([class]) > .banner)'` не работает, но `:is(*:not([class]):has(> .banner))` можно использовать вместо него для выбора элемента `div#target2`: +Due to limitations `:is(*:not([class]) > .banner)'` does not work but `:is(*:not([class]):has(> .banner))` can be used instead of it to select the element `div#target2`: ```html @@ -3714,9 +3713,9 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to ``` -#### Псевдокласс `:not()` {#extended-css-not} +#### Pseudo-class `:not()` {#extended-css-not} -Псевдокласс `:not()` позволяет выбрать элементы, которые *не соответствуют* селекторам, переданным в качестве аргумента. Неправильные селекторы аргументов не допускаются, и будет выдана ошибка. Наша реализация [псевдокласса`:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not). +The `:not()` pseudo-class allows to select elements which are *not matched* by selectors passed as argument. Invalid argument selectors are not allowed and error is to be thrown. Our implementation of the [`:not()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:not). **Синтаксис** @@ -3724,22 +3723,22 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to [target]:not(selectors) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `selectors` — список стандартных или расширенных селекторов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selectors` — list of standard or extended selectors ##### Ограничения `:not()` {#extended-css-not-limitations} -Правила с псевдоклассом `:not()` должны использовать [нативную реализацию `:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not), если они используют маркер `##` и если это возможно, то есть без других расширенных селекторов внутри. Чтобы принудительно применить правила ExtendedCss с `:not()`, используйте маркер `#?#`/`#$?#` явно. +Rules with the `:not()` pseudo-class must use the [native implementation of `:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not) if rules use `##` marker and it is possible, i.e. with no other extended selectors inside. To force applying ExtendedCss rules with `:not()`, use `#?#`/`#$?#` marker explicitly. -Если `selectors` аргумент псевдокласса `:not()` — расширенный селектор, то из-за того, как псевдокласс `:not()` реализован в ExtendedCss 2.0, его невозможно применить к верхнему узлу DOM, который является `html`, т.е. `#?#html:not()` не работает. Таким образом, если `target` не определён или определён как [универсальный селектор](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, применение расширенного псевдокласса ограничено **дочерними `html`-элементами**, например, правила `#?#:not(...)` и `#?#*:not(...)` парсятся как `#?#html *:not(...)`. Обратите внимание, что для стандартного аргумента селектора такого ограничения нет, т.е. `#?#html:not(.locked)` работает нормально. +If the `:not()` pseudo-class argument `selectors` is an extended selector, due to the way how the `:not()` pseudo-class is implemented in ExtendedCss v2.0, it is impossible to apply it to the top DOM node which is `html`, i.e. `#?#html:not()` does not work. So if `target` is not defined or defined as the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, the extended pseudo-class applying is limited to **`html`'s children**, e.g. rules `#?#:not(...)` and `#?#*:not(...)` are parsed as `#?#html *:not(...)`. Please note that there is no such limitation for a standard selector argument, i.e. `#?#html:not(.locked)` works fine. -Псевдокласс `:not()` рассматривается как стандартный псевдокласс CSS внутри аргумента псевдокласса [`:upward()`](#extended-css-upward), поскольку `:upward()` поддерживает только стандартные селекторы. +The `:not()` is considered as a standard CSS pseudo-class inside the argument of the [`:upward()` pseudo-class](#extended-css-upward) because `:upward()` supports only standard selectors. -«Восходящие» псевдоклассы [`:nth-ancestor()`](#extended-css-nth-ancestor) и [`:upward()`](#extended-css-upward) не поддерживаются внутри аргумента `selectors` для псевдокласса `:not()`. +"Up-looking" pseudo-classes which are [`:nth-ancestor()`](#extended-css-nth-ancestor) and [`:upward()`](#extended-css-upward) are not supported inside `selectors` argument for `:not()` pseudo-class. **Примеры** -`#container > *:not(h2, .text)` выбирает только элемент `div#target1`: +`#container > *:not(h2, .text)` selects only the element `div#target1`: ```html @@ -3750,33 +3749,33 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to ``` -#### Псевдокласс `:if-not()` (удалён) {#extended-css-if-not} +#### Pseudo-class `:if-not()` (removed) {#extended-css-if-not} :::danger Уведомление об удалении -Псевдокласс `:if-not()` удалён и больше не поддерживается. Правила с ним не работают. +The `:if-not()` pseudo-class is removed and is no longer supported. Правила с ним не работают. ::: -Этот псевдокласс изначально был сокращением для `:not(:has())`. Он поддерживался ExtendedCss для лучшей совместимости с подписками на некоторые фильтры. +This pseudo-class was basically a shortcut for `:not(:has())`. It was supported by ExtendedCss for better compatibility with some filters subscriptions. ### Приоритет косметических правил {#cosmetic-rules-priority} -То, как применяются правила **скрытия элементов** и **CSS-правила**, зависит от платформы. +The way **element hiding** and **CSS rules** are applied is platform-specific. -**В AdGuard для Windows, Mac и Android** мы используем таблицу стилей, встроенную в страницу. Приоритет у косметических правил такой же, как и у любых других таблиц стилей CSS на сайтах. Но есть ограничение: [правила скрытия элементов](#cosmetic-elemhide-rules) и [CSS-правила](#cosmetic-css-rules) не могут обходить встроенные стили. В таких случаях рекомендуется использовать расширенные селекторы или HTML-фильтрацию. +**In AdGuard for Windows, Mac, and Android**, we use a stylesheet injected into the page. The priority of cosmetic rules is the same as any other websites' CSS stylesheet. But there is a limitation: [element hiding](#cosmetic-elemhide-rules) and [CSS rules](#cosmetic-css-rules) cannot override inline styles. In such cases, it is recommended to use extended selectors or HTML filtering. -**В Браузерном расширении AdGuard** используются так называемые «пользовательские таблицы стилей». Их приоритет выше, даже чем у встроенных стилей. +**In AdGuard Browser Extension**, the so called "user stylesheets" are used. They have higher priority than even the inline styles. -**Расширенные CSS-селекторы** используют для работы JavaScript и добавляют встроенные стили сами, поэтому могут игнорировать любой стиль. +**Extended CSS selectors** use JavaScript to work and basically add an inline style themselves, therefore they can override any style. ## Правила фильтрации HTML {#html-filtering-rules} -В большинстве случаев для фильтрации рекламы достаточно базовых и косметических правил. Но иногда необходимо изменить HTML-код самой страницы перед её загрузкой. Для этого применяются правила фильтрации HTML-контента. Они позволяют указать, какие HTML-элементы необходимо вырезать из страницы перед тем, как страница попадёт в браузер. +In most cases, the basis and cosmetic rules are enough to filter ads. But sometimes it is necessary to change the HTML-code of the page itself before it is loaded. This is when you need filtering rules for HTML content. They allow to indicate the HTML elements to be cut out before the browser loads the page. :::info Совместимость -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Такие правила не работают в расширениях для других браузеров, потому что они не могут модифицировать содержимое страниц на сетевом уровне. +HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3792,46 +3791,46 @@ pseudoClasses = pseudoClass *pseudoClass pseudoClass = ":" pseudoName [ "(" pseudoArgs ")" ] ``` -- **`tagName`** — имя элемента в нижнем регистре, например, `div` или `script`. -- **`domains`** — ограничение на домены, на страницах которых будет применено правило. Те же принципы, что и в [синтаксисе правил скрытия элементов](#cosmetic-elemhide-rules). -- **`attributes`** — список атрибутов, ограничивающих выбор элементов. `name` — имя атрибута, `value` — подстрока, которая содержится в значении атрибута. -- **`pseudoName`** — имя псевдокласса. -- **`pseudoArgs`** — аргументы псевдокласса, записанного в виде функции. -- **`combinator`** — оператор, который работает аналогично [CSS-комбинатору дочерних элементов](https://developer.mozilla.org/ru/docs/Web/CSS/Child_combinator): селектор справа от комбинатора будет относиться только к элементу, прямой родительский элемент которого соответствует селектору слева от комбинатора. +- **`tagName`** — name of the element in lower case, for example, `div` or `script`. +- **`domains`** — domain restriction for the rule. Same principles as in [element hiding rule syntax](#cosmetic-elemhide-rules). +- **`attributes`** — a list of attributes that limit the selection of elements. `name` — attribute name, `value` — substring, that is contained in attribute value. +- **`pseudoName`** — the name of a pseudo-class. +- **`pseudoArgs`** — the arguments of a function-style pseudo-class. +- **`combinator`** — an operator that works similarly to the [CSS child combinator](https://developer.mozilla.org/en-US/docs/Web/CSS/Child_combinator): that is, the `selector` on the right of the `combinator` will only match an element whose direct parent matches the `selector` on the left of the `combinator`. ### Примеры -**HTML-код:** +**HTML code:** ```html ``` -**Правило:** +**Rule:** ```adblock example.org$$script[data-src="banner"] ``` -Это правило удалит из кода страниц все элементы `script` со значением `data-src`, содержащим подстроку `banner`. При этом правило будет работать только для домена `example.org` и всех его поддоменов. +This rule removes all `script` elements with the attribute `data-src` containing the substring `banner`. The rule applies only to `example.org` and all its subdomains. ### Специальные атрибуты -Помимо обычных атрибутов, значение которых проверяется у каждого элемента, существует набор специальных атрибутов правила, которые изменяют способ работы правила. Ниже мы перечислим все эти атрибуты: +In addition to usual attributes, which value is every element checked for, there is a set of special attributes that change the way a rule works. Below there is a list of these attributes: #### `tag-content` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available. ::: -Пожалуй, наиболее часто используемый специальный атрибут. Он ограничивает выбор теми элементами, внутренний HTML-код которых (innerHTML) содержит указанную подстроку. +This is the most frequently used special attribute. It limits selection with those elements whose innerHTML code contains the specified substring. -Используйте `""` для экранирования `"`, например: `$$script[tag-content="alert(""this is ad"")"]` +You must use `""` to escape `"`, for instance: `$$script[tag-content="alert(""this is ad"")"]` -Например, рассмотрим такой HTML-код: +For example, take a look at this HTML code: ```html ``` -Следующее правило удалит все `script` элементы с подстрокой `banner` в их коде: +Following rule will delete all `script` elements with a `banner` substring in their code: ```adblock $$script[tag-content="banner"] @@ -3847,45 +3846,45 @@ $$script[tag-content="banner"] :::caution Ограничения -Специальный атрибут `tag-content` не должен появляться в селекторе слева от комбинатора `>`. +The `tag-content` special attribute must not appear in a selector to the left of a `>` combinator. ::: #### `wildcard` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available. ::: This special attribute works almost like `tag-content` and allows you to check the innerHTML code of the document. Rule will check if HTML code of the element fits to the [search pattern](https://en.wikipedia.org/wiki/Glob_(programming)). -Используйте `""` для экранирования `"`, например: `$$script[wildcard=""banner""]` +You must use `""` to escape `"`, for instance: `$$script[wildcard=""banner""]` -Например: `$$script[wildcard="*banner*text*"]` +For example: `$$script[wildcard="*banner*text*"]` -Оно проверяет, что код элемента содержит две последовательные подстроки `banner` и `text`. +It checks if the element code contains the two consecutive substrings `banner` and `text`. :::caution Ограничения -Специальный атрибут `wildcard` не должен появляться в селекторе слева от комбинатора `>`. +The `wildcard` special attribute must not appear in a selector to the left of a `>` combinator. ::: #### `max-length` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class with a regular expression where it is available. ::: -Задает максимальную длину содержимого HTML-элемента. Если этот параметр задан и длина содержимого превышает заданное значение, правило не применяется к элементу. +Specifies the maximum length for content of HTML element. If this parameter is set and the content length exceeds the value, a rule does not apply to the element. -**Значение по умолчанию** +**Default value** -Если этот параметр не задан, то `max-length` считается равным 8192. +If this parameter is not specified, the `max-length` is considered to be 8192. Например: @@ -3893,23 +3892,23 @@ This special attribute works almost like `tag-content` and allows you to check t $$div[tag-content="banner"][max-length="400"] ``` -Это правило удалит все элементы `div`, код которых содержит подстроку `banner` и длина которых не превышает `400` символов. +This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which does not exceed `400` characters. :::caution Ограничения -Специальный атрибут `max-length` не должен появляться в селекторе слева от комбинатора `>`. +The `max-length` special attribute must not appear in a selector to the left of a `>` combinator. ::: #### `min-length` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class with a regular expression where it is available. ::: -Задаёт минимальную длину содержимого HTML-элемента. Если этот параметр задан, и длина содержимого меньше заданного значения — правило не применяется к элементу. +Specifies the minimum length for content of HTML element. If this parameter is set and the content length is less than preset value, a rule does not apply to the element. Например: @@ -3917,11 +3916,11 @@ $$div[tag-content="banner"][max-length="400"] $$div[tag-content="banner"][min-length="400"] ``` -Это правило удалит все элементы `div`, код которых содержит подстроку `banner` и длина которых превышает `400` символов. +This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which exceeds `400` characters. :::caution Ограничения -Специальный атрибут `min-length` не должен появляться в селекторе слева от комбинатора `>`. +The `min-length` special attribute must not appear in a selector to the left of a `>` combinator. ::: @@ -3941,9 +3940,9 @@ $$div[tag-content="banner"][min-length="400"] :contains(/reg(ular)?ex(pression)?/) ``` -:::note Совместимость +:::note Compatibility -`:-abp-contains()` и `:has-text()` являются синонимами `:contains()`. +`:-abp-contains()` and `:has-text()` are synonyms for `:contains()`. ::: @@ -3953,43 +3952,43 @@ The `:contains()` pseudo-class is supported by AdGuard for Windows, Mac, and And ::: -Требует, чтобы внутренний HTML-код элемента содержал указанный текст или соответствовал указанному регулярному выражению. +Requires that the inner HTML of the element contains the specified text or matches the specified regular expression. :::caution Ограничения -Псевдокласс `:contains()` не должен появляться в селекторе слева от комбинатора `>`. +A `:contains()` pseudo-class must not appear in a selector to the left of a `>` combinator. ::: ### Исключения -По аналогии с правилами скрытия, существует специальный тип правил, отключающий действие выбранного правила HTML-фильтрации для определённых доменов. Синтаксис правил-исключений такой же, только маркер `$$` заменяется на `$@$`. +Similar to hiding rules, there is a special type of rules that disable the selected HTML filtering rule for particular domains. The syntax is the same, you just have to change `$$` to `$@$`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock $$script[tag-content="banner"] ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com$@$script[tag-content="banner"] ``` -В некоторых случаях может потребоваться отключение всех запрещающих правил. Например, на время тестирования. Для этого воспользуйтесь правилом исключения без указания домена. +Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. ```adblock $@$script[tag-content="banner"] ``` -Применять такие исключения рекомендуется только в случае, когда изменить само правило скрытия невозможно. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions. ## Правила JavaScript {#javascript-rules} -AdGuard поддерживает специальный тип правил, позволяющий вставить любой JavaScript-код на страницы сайтов. +AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. -Мы **настоятельно рекомендуем** использовать [скриптлеты](#scriptlets) вместо JavaScript-правил везде, где это возможно. JS-правила должны помочь в процессе отладки, но в качестве долгосрочного решения следует использовать скриптлеты. +We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. **Синтаксис** @@ -3997,60 +3996,60 @@ AdGuard поддерживает специальный тип правил, п rule = [domains] "#%#" script ``` -- **`domains`** — ограничение на домены, на страницах которых будет применено правило. Строится по тем же правилам, что и в случае [правил скрытия элементов](#cosmetic-elemhide-rules). -- **`script`** — произвольный JavaScript-код **в одну строку**. +- **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). +- **`script`** — arbitrary JavaScript code **in one string**. **Примеры** -- `example.org#%#window.__gaq = undefined;` выполняет код `window.__gaq = undefined;` на всех страницах сайта `example.org` и всех его поддоменах. +- `example.org#%#window.__gaq = undefined;` executes the code `window.__gaq = undefined;` on all pages at `example.org` and all subdomains. **Исключения** -По аналогии с правилами скрытия, существует специальный тип правил, отключающий действие выбранного javascript-правила фильтрации для определённых доменов. Синтаксис правил-исключений такой же, только маркер `#%#` заменяется на `#@%#`. +Similar to hiding rules, there is a special type of rules that disable the selected javascript rule for particular domains. The syntax is the same, you just have to change `#%#` to `#@%#`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock #%#window.__gaq = undefined; ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com#@%#window.__gaq = undefined; ``` -В некоторых случаях может потребоваться отключение всех запрещающих правил. Например, на время тестирования. Для этого воспользуйтесь правилом исключения без указания домена. +Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. ```adblock #@%#window.__gaq = undefined; ``` -Применять такие исключения рекомендуется только в случае, когда изменить само правило скрытия невозможно. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions. :::caution Ограничения -Правила JavaScript можно использовать [**только в доверенных фильтрах**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: :::info Совместимость -JavaScript-правила не поддерживаются в AdGuard Content Blocker. +JavaScript rules are not supported by AdGuard Content Blocker. ::: ## Правила скриптлета {#scriptlets} -Скриптлет — это функция JavaScript с расширенными возможностями для блокировки контента. Такие функции могут использоваться в декларативной манере в правилах фильтрации AdGuard. +Scriptlet is a JavaScript function that provides extended capabilities for content blocking. These functions can be used in a declarative manner in AdGuard filtering rules. :::note -AdGuard поддерживает множество различных скриптлетов. Чтобы добиться совместимости между различными блокировщиками, мы также поддерживаем синтаксис uBO и ABP. +AdGuard supports a lot of different scriptlets. In order to achieve cross-blocker compatibility, we also support syntax of uBO and ABP. ::: -**Синтаксис правил блокировки** +**Blocking rules syntax** ```text [domains]#%#//scriptlet(name[, arguments]) @@ -4074,9 +4073,9 @@ AdGuard поддерживает множество различных скри example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') ``` -**Синтаксис правил исключений** +**Exception rules syntax** -Правила исключений могут отключать некоторые скриптлеты на определённых доменах. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: +Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: ```text [domains]#@%#//scriptlet([name[, arguments]]) @@ -4125,57 +4124,57 @@ AdGuard поддерживает множество различных скри example.com#@%#//scriptlet() ``` -Подробнее [об отладке скриптлетов](#debug-scriptlets). +Learn more about [how to debug scriptlets](#debug-scriptlets). -Более подробную информацию о скриптлетах можно найти [на GitHub](https://github.com/AdguardTeam/Scriptlets#scriptlets). +More information about scriptlets can be found [on GitHub](https://github.com/AdguardTeam/Scriptlets#scriptlets). :::info Совместимость -Скриптлеты не поддерживаются в AdGuard Content Blocker. +Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Предыдущие версии поддерживали только правила исключений, которые отключали определённые скриптлеты. +The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. ::: ### Доверенные скриптлеты {#trusted-scriptlets} -Доверенные скриптлеты — это [скриптлеты](#scriptlets) с расширенной функциональностью. У них тот же синтаксис и ограничения. У имён доверенных скриптлетов есть префикс `trust-`, например, `trust-set-cookie`, чтобы их было легко отличить от обычных скриптлетов. +Trusted scriptlets are [scriptlets](#scriptlets) with extended functionality. It means the same syntax and restrictions. Trusted scriptlet names are prefixed with `trusted-`, e.g. `trusted-set-cookie`, to be easily distinguished from common scriptlets. :::note -Доверенные скриптлеты несовместимы с другими блокировщиками рекламы, кроме AdGuard. +Trusted scriptlets are not compatible with other ad blockers except AdGuard. ::: :::caution Ограничения -Доверенные скриптлеты можно использовать [**только в доверенных фильтрах**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: :::info Совместимость -Доверенные скриптлеты не поддерживаются в AdGuard Content Blocker. +Trusted scriptlets rules are not supported by AdGuard Content Blocker. ::: -Подробнее [об отладке скриптлетов](#debug-scriptlets). +Learn more about [how to debug scriptlets](#debug-scriptlets). -Более подробную информацию о доверенных скриптлетах можно найти [на GitHub](https://github.com/AdguardTeam/Scriptlets#trusted-scriptlets). +More information about trusted scriptlets can be found [on GitHub](https://github.com/AdguardTeam/Scriptlets#trusted-scriptlets). ## Модификаторы для небазовых правил {#non-basic-rules-modifiers} -Поведение любого правила можно изменить, используя модификаторы, описанные ниже. +Each rule can be modified using the modifiers described in the following paragraphs. -**Синтаксис** {#non-basic-rules-modifiers-syntax} +**Syntax** {#non-basic-rules-modifiers-syntax} ```text rule = "[$" modifiers "]" [rule text] modifiers = modifier0[, modifier1[, ...[, modifierN]]] ``` -- **`modifier`** — набор модификаторов, описанных ниже. -- **`rule text`** — правило, которое нужно модифицировать. +- **`modifier`** — set of the modifiers described below. +- **`rule text`** — a rule to be modified. For example, `[$domain=example.com,app=test_app]##selector`. @@ -4204,8 +4203,8 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` - `[$app=org.example.app]example.com##.textad` hides a `div` with the class `textad` at `example.com` and all subdomains in requests sent from the `org.example.app` Android app. - `[$app=~org.example.app1|~org.example.app2]example.com##.textad` hides a `div` with the class `textad` at `example.com` and all subdomains in requests sent from any app except `org.example.app1` and `org.example.app2`. -- `[$app=com.apple.Safari]example.org#%#//scriptlet('prevent-setInterval', 'check', '!300')` применяет скриптлет `prevent-setInterval` только в браузере Safari на Mac. -- `[$app=org.example.app]#@#.textad` отключает все правила `##.textad` для всех доменов при использовании `org.example.app`. +- `[$app=com.apple.Safari]example.org#%#//scriptlet('prevent-setInterval', 'check', '!300')` applies scriptlet `prevent-setInterval` only in Safari browser on Mac. +- `[$app=org.example.app]#@#.textad` disables all `##.textad` rules for all domains while using `org.example.app`. :::info Совместимость @@ -4220,13 +4219,13 @@ Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard fo **Примеры** - `[$domain=example.com]##.textad` — hides a `div` with the class `textad` at `example.com` and all subdomains. -- `[$domain=example.com|example.org]` скроет элемент с атрибутом `id` равным `adblock` на доменах `example.com`, `example.org` и всех их поддоменах. -- `[$domain=~example.com]##.textad` скроет элементы `div` с классом `textad` на всех доменах, кроме `example.com` и всех его поддоменов. +- `[$domain=example.com|example.org]###adblock` — hides an element with attribute `id` equals `adblock` at `example.com`, `example.org` and all subdomains. +- `[$domain=~example.com]##.textad` — this rule hides `div` elements of the class `textad` for all domains, except `example.com` and its subdomains. There are 2 ways to specify domain restrictions for non-basic rules: -1. «классический»: обозначить ограничение на домены перед маской и атрибутами правила: `example.com##.textad`; -2. с помощью модификаторов: обозначить ограничение на домены через модификатор `$domain`: `[$domain=example.com]##.textad`. +1. the "classic" way is to specify domains before rule mask and attributes: `example.com##.textad`; +2. the modifier approach is to specify domains via `$domain` modifier: `[$domain=example.com]##.textad`. But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. @@ -4294,8 +4293,8 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic **Примеры** - `[$url=||example.com/content/*]##div.textad` hides a `div` with the class `textad` at addresses like `https://example.com/content/article.html` and even `https://subdomain.example.com/content/article.html`. -- `[$url=||example.org^]###adblock` скрывает элемент с атрибутом `id` равным `adblock` в запросах к `example.org` и всем его поддоменам. -- `[$url=/\[a-z\]+\\.example\\.com^/]##.textad` скрывает `div` с классом `textad` в запросах ко всем доменам, соответствующим регулярному выражению `[a-z]+\.example\.com^`. +- `[$url=||example.org^]###adblock` hides an element with attribute `id` equal to `adblock` at `example.org` and its subdomains. +- `[$url=/\[a-z\]+\\.example\\.com^/]##.textad` hides `div` elements of the class `textad` for all domains matching the regular expression `[a-z]+\.example\.com^`. #### `$url` modifier limitations {#non-basic-url-modifier-limitations} @@ -4319,9 +4318,9 @@ If you maintain a third-party filter that is known to AdGuard, you might be inte We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: -- [включать содержимое отдельного файла в фильтр](#include-directive) -- [применять правила в зависимости от типа блокировщика](#conditions-directive) -- [уточнять блокировщик контента для применения правил в Safari](#safari-affinity-directive) +- [including a file](#include-directive) +- [applying rules conditionally by ad blocker type](#conditions-directive) +- [content blocker specifying for rules applying in Safari](#safari-affinity-directive) :::note @@ -4333,7 +4332,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Включение файла {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. Она поддерживает только файлы из того же источника, чтобы удостовериться, что разработчик фильтров является владельцем указанного файла. Включённый файл также может содержать директивы препроцессора (даже другие`!#include`-директивы). Блокировщики должны принимать во внимание случай рекурсивного использования `!#include` и внедрять защитный механизм. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Синтаксис** @@ -4341,17 +4340,17 @@ The `!#include` directive allows to include contents of a specified file into th !#include file_path ``` -где `file_path` — абсолютный или относительный путь к файлу одного и того же источника, который должен быть включён. +where `file_path` is a same origin absolute or relative file path to be included. -Файлы должны находиться на том же домене, но могут быть расположены в другой директории. +The files must originate from the same domain, but may be located in a different folder. -Если включённый файл не найден или недоступен, не будут работать обновления всего фильтра. +If included file is not found or unavailable, the whole filter update should fail. -Для локальных собственных фильтров ограничение на тот же источник не распространяется. +Same-origin limitation should be disabled for local custom filters. **Примеры** -URL фильтра: `https://example.org/path/filter.txt` +Filter URL: `https://example.org/path/filter.txt` ```adblock ! Корректный (тот же источник): @@ -4367,17 +4366,17 @@ URL фильтра: `https://example.org/path/filter.txt` #### Условия {#conditions-directive} -Разработчики фильтров могут использовать условия, чтобы подставлять нужные правила, в зависимости от типа блокировщика. Директива с условием, начинающаяся с директивы `!#if`, должна явно прерываться директивой `!#endif`. Условия поддерживают все основные логические операторы. +Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. -Есть два возможных сценария: +There are two possible scenarios: -1. Если блокировщик рекламы встречает директиву `!#if` и не встречает директиву `!#else`, то он компилирует код между директивами `!#if` и `!#endif` только в том случае, если указанное условие истинно. +1. When an ad blocker encounters an `!#if` directive and no `!#else` directive, it will compile the code between `!#if` and `!#endif` directives only if the specified condition is true. -1. Если существует директива `!#else`, код между `!#if` и `!#else` будет скомпилирован, если условие истинно; в противном случае будет скомпилирован код между `!#else` и `!#endif`. +1. If there is an `!#else` directive, the code between `!#if` and `!#else` will be compiled if the condition is true; otherwise, the code between `!#else` and `!#endif` will be compiled. :::note -Пробелы имеют значение. `!#if` — это корректная директива, в то время как `!# if` — не корректная. +Whitespaces matter. `!#if` is a valid directive, while `!# if` is not. ::: @@ -4401,25 +4400,25 @@ false_conditions_rules_list где: -- `!#if (условия)` — начало блока при выполнении условий -- `conditions` — точно так же, как и в случае с некоторыми популярными языками программирования, условия препроцессинга основаны на константах, объявляемых блокировщиками. Разработчики блокировщиков самостоятельно определяют, какие именно константы объявлять. Возможные значения: - - `adguard` объявляется всегда; даёт разработчикам фильтров понять, что это один из продуктов AdGuard; должно быть достаточно в 95% случаев - - специфичные для конкретных продуктов константы, которые нужны в редких случаях, когда правило должно работать (или не работать — тогда перед константой используйте `!`) только для конкретного продукта: - - `adguard_app_windows` — AdGuard для Windows - - `adguard_app_mac` — AdGuard для Mac - - `adguard_app_android` — AdGuard для Android - - `adguard_app_ios` — AdGuard для iOS - - `adguard_ext_safari` — AdGuard для Safari - - `adguard_ext_chromium` — Браузерное расширение AdGuard для Chrome (и браузеры на основе Chrome, например, новый Microsoft Edge) - - `adguard_ext_firefox` — Браузерное расширение AdGuard для Firefox - - `adguard_ext_edge` — Браузерное расширение AdGuard для Edge Legacy - - `adguard_ext_opera` — Браузерное расширение AdGuard для Opera - - `adguard_ext_android_cb` — AdGuard Content Blocker для мобильных браузеров Samsung и Яндекс +- `!#if (conditions)` — start of the block when conditions are true +- `conditions` — just like in some popular programming languages, preprocessor conditions are based on constants declared by ad blockers. Authors of ad blockers define on their own what exact constants they declare. Possible values: + - `adguard` always declared; shows maintainers that this is one of AdGuard products; should be enough in 95% of cases + - product-specific constants for cases when you need a rule to work (or not work — then `!` should be used before constant) in a specific product only: + - `adguard_app_windows` — AdGuard for Windows + - `adguard_app_mac` — AdGuard for Mac + - `adguard_app_android` — AdGuard for Android + - `adguard_app_ios` — AdGuard for iOS + - `adguard_ext_safari` — AdGuard for Safari + - `adguard_ext_chromium` — AdGuard Browser Extension for Chrome (and chromium-based browsers, e.g. new Microsoft Edge) + - `adguard_ext_firefox` — AdGuard Browser Extension for Firefox + - `adguard_ext_edge` — AdGuard Browser Extension for Edge Legacy + - `adguard_ext_opera` — AdGuard Browser Extension for Opera + - `adguard_ext_android_cb` — AdGuard Content Blocker for mobile Samsung and Yandex browsers - `ext_ublock` — special case; this one is declared when a uBlock version of a filter is compiled by the [FiltersRegistry][] - - `cap_html_filtering` — продукты, поддерживающие правила HTML-фильтрации: AdGuard для Windows, AdGuard для Mac и AdGuard для Android -- `!#else` — начало блока, когда условия ложны -- `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — списки правил -- `!#endif` — конец блока + - `cap_html_filtering` — products that support HTML filtering rules: AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +- `!#else` — start of the block when conditions are false +- `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — lists of rules +- `!#endif` — end of the block **Примеры** @@ -4453,32 +4452,32 @@ domain.com##div.ad The `!#else` directive is supported by the [FiltersDownloader][gh-filters-downloader] v1.1.20 or later. -It is already supported for filter lists compiled by the [FiltersRegistry][], but it still may not be supported by AdGuard products when adding a filter list with `!#else` as a custom one. Следующие продукты будут поддерживать его в указанных версиях или более поздних версиях: +It is already supported for filter lists compiled by the [FiltersRegistry][], but it still may not be supported by AdGuard products when adding a filter list with `!#else` as a custom one. The following products will support it in the mentioned versions or later: - AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13; -- Браузерное расширение AdGuard 4.2.208; +- AdGuard Browser Extension v4.2.208; - AdGuard v1.11.16 for Safari. ::: #### Правила фильтрации в Safari {#safari-affinity-directive} -Лимит каждого блокировщика контента Safari — 150 000 активных правил. Но в AdGuard для Safari и AdGuard для iOS мы разделили правила на 6 блокировщиков контента, тем самым увеличив лимит правил до 900 000. +Safari's limit for each content blocker is 150,000 active rules. But in AdGuard for Safari and AdGuard for iOS, we've split the rules into 6 content blockers, thus increasing the rule limit to 900,000. -Какие фильтры содержатся в каждом блокировщике контента: +Here is the composition of each content blocker: -- AdGuard General — Блокировка рекламы, Языковые -- AdGuard Privacy — Антитрекинг -- AdGuard Social — Виджеты социальных сетей, Раздражители -- AdGuard Security — Безопасность -- AdGuard Other — Другие -- AdGuard Custom — Собственные +- AdGuard General — Ad Blocking, Language-specific +- AdGuard Privacy — Privacy +- AdGuard Social — Social Widgets, Annoyances +- AdGuard Security — Security +- AdGuard Other — Other +- AdGuard Custom — Custom -Пользовательские правила и белый список добавляются в каждый блокировщик контента. +User rules and allowlist are added to every content blocker. :::caution -Основной недостаток использования нескольких блокировщиков контента в том, что правила из разных блокировщиков применяются независимо друг от друга. На правила блокировки это не влияет, но с правилами разблокировки могут быть проблемы. Если правило блокировки есть в одном блокировщике контента, а исключение — в другом, то исключение не сработает. Разработчики фильтров используют `!#safari_cb_affinity`, чтобы указать, к какому блокировщику контента принадлежат правила. +The main disadvantage of using multiple content blockers is that rules from different blockers are applied independently. Blocking rules are not affected by this, but unblocking rules may cause problems. If a blocking rule is in one content blocker and an exception is in another, the exception will not work. Filter maintainers use `!#safari_cb_affinity` to define Safari content blocker affinity for the rules inside of the directive block. ::: @@ -4492,17 +4491,17 @@ rules_list где: -- `!#safari_cb_affinity(content_blockers)` — начало блока -- `content_blockers` — список блокировщиков контента, разделённых запятой. Возможные значения: - - `general` — блокировщик контента AdGuard General - - `privacy` — блокировщик контента AdGuard Privacy - - `social` — блокировщик контента AdGuard Social - - `security` — блокировщик контента AdGuard Security - - `other` — блокировщик контента AdGuard Other - - `custom` — блокировщик контента AdGuard Custom - - `all` — специальное ключевое слово, которое означает, что правила должны быть включены во **все** блокировщики контента -- `rules_list` — список правил -- `!#safari_cb_affinity` — конец блока +- `!#safari_cb_affinity(content_blockers)` — start of the block +- `content_blockers` — comma-separated list of content blockers. Possible values: + - `general` — AdGuard General content blocker + - `privacy` — AdGuard Privacy content blocker + - `social` — AdGuard Social content blocker + - `security` — AdGuard Security content blocker + - `other` — AdGuard Other content blocker + - `custom` — AdGuard Custom content blocker + - `all` — special keyword that means that the rules must be included into **all** content blockers +- `rules_list` — list of rules +- `!#safari_cb_affinity` — end of the block **Примеры** @@ -4530,13 +4529,13 @@ example.org#@#.adBanner !+ HINT_NAME1(PARAMS) HINT_NAME2(PARAMS) ``` -Можно применить несколько подсказок. +Multiple hints can be applied. #### Подсказка `NOT_OPTIMIZED` -Для каждого фильтра AdGuard существуют две версии: полная и оптимизированная. Оптимизированная версия намного легче и не содержит правил, которые не используются вообще или используются редко. +For each filter, AdGuard compiles two versions: full and optimized. Optimized version is much more lightweight and does not contain rules which are not used at all or used rarely. -Частота использования правил определяется собранной [статистикой по рекламным фильтрам](../tracking-filter-statistics). Но оптимизация основана также на исходной конфигурации для каждого фильтра. Например, вот так это выглядит для Базового фильтра: +Rules usage frequency comes from the collected [filter rules statistics](../tracking-filter-statistics). But filters optimization is based on more than that — some filters have specific configuration. This is how it looks like for Base filter: ```text "filter": Базовый фильтр AdGuard, @@ -4548,27 +4547,27 @@ example.org#@#.adBanner где: -- **filter** — идентификатор фильтра -- **percent** — ожидаемый процент оптимизации `~= (количество правил в оптимизированном фильтре) / (количество правил в исходном фильтре) * 100` -- **minPercent** — нижняя граница значения `percent` -- **maxPercent** — верхняя граница значения `percent` -- **Strict** — если `percent < minPercent` или `percent > maxPercent` и включён режим Strict, то компиляция фильтра должна завершиться неудачно, в противном случае должны использоваться оригинальные правила +- **filter** — filter identifier +- **percent** — expected optimization percent `~= (rules count in optimized filter) / (rules count in original filter) * 100` +- **minPercent** — lower bound of `percent` value +- **maxPercent** — upper bound of `percent` value +- **strict** — if `percent < minPercent` OR `percent > maxPercent` and strict mode is on then filter compilation should fail, otherwise original rules must be used -Другими словами, `percent` — это «уровень сжатия». Например, для Базового фильтра он настроен на 40%. Это означает, что алгоритм оптимизации должен убрать 60% правил. +In other words, `percent` is the "compression level". For instance, for the Base filter it is configured to 40%. It means that optimization algorithm should strip 60% of rules. -В итоге, вот так выглядят версии Базового фильтра для Браузерного расширения AdGuard для Chrome: +Eventually, here are the two versions of the Base filter for AdGuard Browser Extension: -- полная: https://filters.adtidy.org/extension/chromium/filters/2.txt -- оптимизированная: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt +- full: https://filters.adtidy.org/extension/chromium/filters/2.txt +- optimized: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt -**Если вы хотите добавить правило, которое не должно удаляться при оптимизации, используйте подсказку `NOT_OPTIMIZED`:** +**If you want to add a rule which should not be removed at optimization use the `NOT_OPTIMIZED` hint:** ```adblock !+ NOT_OPTIMIZED ||example.org^ ``` -**А такое правило не будет оптимизировано только для AdGuard для Android:** +**And this rule will not be optimized only for AdGuard for Android:** ```adblock !+ NOT_OPTIMIZED PLATFORM(android) @@ -4577,27 +4576,27 @@ example.org#@#.adBanner #### Подсказки `PLATFORM` и `NOT_PLATFORM` -Записи этого типа позволяют указывать платформу, для которой применяется правило. Ниже представлен список используемых платформ и ссылки на Базовый фильтр для каждой из них: +Used to specify the platforms to apply the rules. List of existing platforms and links to Base filter, for example, for each of them: -- `windows` — AdGuard для Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) +- `windows` — AdGuard for Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) -- `mac` — AdGuard для Mac — [https://filters.adtidy.org/mac_v2/filters/2.txt](https://filters.adtidy.org/mac_v2/filters/2.txt) +- `mac` — AdGuard for Mac — [https://filters.adtidy.org/mac_v2/filters/2.txt](https://filters.adtidy.org/mac_v2/filters/2.txt) -- `android` — AdGuard для Android — [https://filters.adtidy.org/android/filters/2.txt](https://filters.adtidy.org/android/filters/2.txt) +- `android` — AdGuard for Android — [https://filters.adtidy.org/android/filters/2.txt](https://filters.adtidy.org/android/filters/2.txt) -- `ios` — AdGuard для iOS — [https://filters.adtidy.org/ios/filters/2.txt](https://filters.adtidy.org/ios/filters/2.txt) +- `ios` — AdGuard for iOS — [https://filters.adtidy.org/ios/filters/2.txt](https://filters.adtidy.org/ios/filters/2.txt) -- `ext_chromium` — Браузерное расширение AdGuard для Chrome — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) +- `ext_chromium` — AdGuard Browser Extension for Chrome — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) -- `ext_chromium` — Браузерное расширение AdGuard для Chrome MV3 — [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) +- `ext_chromium_mv3` — AdGuard Browser Extension for Chrome MV3 — [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) -- `ext_ff` — Браузерное расширение AdGuard для Firefox — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) +- `ext_ff` — AdGuard Browser Extension for Firefox — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) -- `ext_edge` — Браузерное расширение AdGuard для Edge — [https://filters.adtidy.org/extension/edge/filters/2.txt](https://filters.adtidy.org/extension/edge/filters/2.txt) +- `ext_edge` — AdGuard Browser Extension for Edge — [https://filters.adtidy.org/extension/edge/filters/2.txt](https://filters.adtidy.org/extension/edge/filters/2.txt) -- `ext_opera` — Браузерное расширение AdGuard для Opera — [https://filters.adtidy.org/extension/opera/filters/2.txt](https://filters.adtidy.org/extension/opera/filters/2.txt) +- `ext_opera` — AdGuard Browser Extension for Opera — [https://filters.adtidy.org/extension/opera/filters/2.txt](https://filters.adtidy.org/extension/opera/filters/2.txt) -- `ext_safari` — AdGuard для Safari — [https://filters.adtidy.org/extension/safari/filters/2.txt](https://filters.adtidy.org/extension/safari/filters/2.txt) +- `ext_safari` — AdGuard for Safari — [https://filters.adtidy.org/extension/safari/filters/2.txt](https://filters.adtidy.org/extension/safari/filters/2.txt) - `ext_android_cb` — AdGuard Content Blocker — [https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt](https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt) @@ -4621,79 +4620,79 @@ Except for AdGuard for Safari, AdGuard Content Blocker, and AdGuard for iOS, thi ## Отладка правил фильтрации -Хоть самые простые правила фильтрации и возможно придумать «в голове», для чего-то чуть более сложного вам потребуются дополнительная помощь в их отладке и повторении. Есть инструменты, которые помогут вам в этом. Вы можете использовать «Инструменты разработчика» в Chrome и их аналоги в других браузерах, но большинство продуктов AdGuard предоставляют и другой инструмент — Журнал фильтрации. +It may be possible to create simple filtering rules "in your head" but for anything even slightly more complicated you will need additional tools to debug and iterate them. There are tools to assist you with that. You can use DevTools in Chrome and its analogs in other browsers but most AdGuard products provide another one — Filtering log. ### Журнал фильтрации -Журнал фильтрации — продвинутый инструмент, который полезен в основном разработчикам фильтров. В нём отображаются все веб-запросы, проходящие через AdGuard, даётся исчерпывающая информация по каждому из них, предлагаются различные опции сортировки и другие полезные возможности. +Filtering log is an advanced tool that will be helpful mostly to filter developers. It lists all web requests that pass through AdGuard, gives you exhaustive information on each of them, offers multiple sorting options, and has other useful features. -В зависимости от того, какой продукт AdGuard вы используете, журнал фильтрации может находиться в разных местах. +Depending on which AdGuard product you are using, Filtering log can be located in different places. -- В **AdGuard для Windows** вы найдёте его во вкладке настроек *Антибаннер* или через меню трея -- В **AdGuard для Mac** он располагается в разделе *Настройки → Дополнительно → Журнал фильтрации* -- В **AdGuard для Android** его можно найти в разделе *Статистика → Недавняя активность*. *Доступ к недавней активности* также можно получить из *Помощника* -- В **Браузерном расширении AdGuard** он находится во вкладке настроек *Дополнительно*, а также доступен по клику правой кнопкой мыши по иконке расширения. Только веб-браузеры на основе Chromium и Firefox отображают применённые **правила скрытия элементов** (включая CSS, ExtCSS) и **JS-правила и скриптлеты** в своих Журналах фильтрации +- 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 web browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs :::note -В **AdGuard для iOS** и в **AdGuard для Safari** Журнал фильтрации отсутствует из-за особенностей реализации блокировщиков контента в Safari. AdGuard сам не видит веб-запросы и поэтому не может отображать их. +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. ::: ### Режим отладки селекторов {#selectors-debug-mode} -Иногда может понадобиться проверить производительность того или иного селектора или таблицы стилей. Чтобы сделать это без непосредственного взаимодействия с JavaScript, вы можете использовать свойство стиля `debug`. Когда `ExtendedCss` встречает это свойство, он включает режим отладки для конкретного селектора или для всех селекторов, в зависимости от значения `debug`. +Sometimes, you might need to check the performance of a given selector or a stylesheet. In order to do it without interacting with JavaScript directly, you can use a special `debug` style property. When `ExtendedCss` meets this property, it enables the debugging mode either for a single selector or for all selectors, depending on the `debug` value. -Откройте консоль браузера, находясь на веб-странице, чтобы посмотреть статистику по времени, затраченному на применение селектора(-ов). В режиме отладки следующая статистика отображается в виде объекта, где каждый из отлаживаемых селекторов является ключом, а значение — объектом с такими свойствами: +Open the browser console while on a web page to see the timing statistics for selector(s) that were applied there. Debugging mode displays the following stats as object where each of the debugged selectors are keys, and value is an object with such properties: -**Всегда выводится:** +**Always printed:** - `selectorParsed` — text of the parsed selector, may differ from the input one -- `timings` — список узлов DOM, соответствующих селектору - - `appliesCount` — общее количество раз, когда на странице был применён селектор - - `appliesTimings` — время, которое ушло на применение селектора на странице, для каждого из случаев применения этого селектора (в миллисекундах) - - `meanTiming` — среднее время, ушедшее на применение селектора на странице - - `standardDeviation` — стандартное отклонение - - `timingsSum` — общее время, ушедшее на все применения селектора на текущей странице +- `timings` — list of DOM nodes matched by the selector + - `appliesCount` — total number of times that the selector has been applied on the page + - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) + - `meanTiming` — mean time that it took to apply the selector on the page + - `standardDeviation` — standard deviation + - `timingsSum` — total time it took to apply the selector on the page across all instances -**Выводится только для удалённых псевдоэлементов:** +**Printed only for remove pseudos:** -- `removed` — флаг, сигнализирующий об удалении элементов +- `removed` — flag to signal if elements were removed -**Выводится, если элементы не удалены:** +**Printed if elements are not removed:** -- `matchedElements` — список узлов DOM, соответствующих селектору -- `styleApplied` — объявление обработанного стиля правила, связанного с селектором +- `matchedElements` — list of DOM nodes matched by the selector +- `styleApplied` — parsed rule style declaration related to the selector **Примеры** -**Отладка конкретного селектора:** +**Debugging a single selector:** -Когда значение свойства `debug` равно `true`, информация только по этому селектору будет отображена в консоли браузера. +When the value of the `debug` property is `true`, only information about this selector will be shown in the browser console. ```adblock #$?#.banner { display: none; debug: true; } ``` -**Включение глобальной отладки:** +**Enabling global debug:** -Когда значение свойства `debug` равно `global`, в консоли будет отображаться информация по всем CSS-селекторам, которые были применены на данной странице, для всех правил из любого из включённых фильтров. +When the value of the `debug` property is `global`, the console will display information about all extended CSS selectors that have matches on the current page, for all the rules from any of the enabled filters. ```adblock #$?#.banner { display: none; debug: global; } ``` -**Тестирование расширенных селекторов без AdGuard** +**Testing extended selectors without AdGuard** -ExtendedCss может быть выполнен на любой странице без использования какого-либо продукта AdGuard. Для этого скопируйте и запустите следующий код в консоли браузера: +ExtendedCss can be executed on any page without using any AdGuard product. In order to do that you should copy and execute the following code in a browser console: ```js !function(e,t,d){C=e.createElement(t),C.src=d,C.onload=function(){alert("ExtendedCss loaded successfully")},s=e.getElementsByTagName(t)[0],s?s.parentNode.insertBefore(C,s):(h=e.getElementsByTagName("head")[0],h.appendChild(C))}(document,"script","https://AdguardTeam.github.io/ExtendedCss/extended-css.min.js"); ``` -Или установите пользовательский скрипт [ExtendedCssDebugger](https://github.com/AdguardTeam/Userscripts/blob/master/extendedCssDebugger/extended-css.debugger.user.js). +Alternatively, install the [ExtendedCssDebugger userscript](https://github.com/AdguardTeam/Userscripts/blob/master/extendedCssDebugger/extended-css.debugger.user.js). -Теперь вы можете использовать `ExtendedCss` глобально и запустить его метод [`query()`](https://github.com/AdguardTeam/ExtendedCss#extended-css-query) как `Document.querySelectorAll()`. +Now you can now use the `ExtendedCss` from global scope, and run its method [`query()`](https://github.com/AdguardTeam/ExtendedCss#extended-css-query) as `Document.querySelectorAll()`. **Примеры** @@ -4706,9 +4705,9 @@ ExtendedCss.query(selector); ### Отладка скриптлетов {#debug-scriptlets} -Если вы используете браузерное расширение AdGuard и хотите отладить правило [скриптлета](#scriptlets) или [доверенного скриптлета](#trusted-scriptlets), то можете получить дополнительную информацию, открыв журнал фильтрации. В этом случае скриптлеты перейдут в режим отладки и будут записывать больше информации в браузерную консоль. +If you are using AdGuard Browser Extension and want to debug a [scriptlet](#scriptlets) or a [trusted scriptlet](#trusted-scriptlets) rule, you can get additional information by opening the Filtering log. In that case, scriptlets will switch to debug mode and there will be more information in the browser console. -Следующие скриптлеты разработаны специально для отладки: +The following scriptlets are especially developed for debug purposes: - [`debug-current-inline-script`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#debug-current-inline-script) - [`debug-on-property-read`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#debug-on-property-read) @@ -4718,14 +4717,14 @@ ExtendedCss.query(selector); - [`log-eval`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#log-eval) - [`log`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#log) -Следующие скриптлеты тоже могут быть использованы для отладки: +The following scriptlets also may be used for debug purposes: - [`json-prune`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#json-prune) - [`prevent-fetch`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-fetch) - [`prevent-requestAnimationFrame`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-requestanimationframe) - [`prevent-setInterval`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-setinterval) - [`prevent-setTimeout`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-settimeout) -- [`prevent-window-open`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-window-open) со специальным параметром `replacement` +- [`prevent-window-open`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-window-open) with specified `replacement` parameter - [`prevent-xhr`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-xhr) - [`trusted-replace-fetch-response`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-trusted-scriptlets.md#trusted-replace-fetch-response) - [`trusted-replace-xhr-response`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-trusted-scriptlets.md#trusted-replace-xhr-response) @@ -4748,7 +4747,7 @@ ExtendedCss.query(selector); - ✅ — полностью поддерживается - ✅ * — поддерживается, но надёжность может быть разной или могут возникнуть ограничения; ознакомьтесь с описанием модификатора для получения подробной информации -- 🧩 — может быть уже реализован в nightly или бета-версиях, но пока не поддерживается в релизных версиях +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ⏳ — feature that is planned to be implemented but is not yet available in any product - ❌ — не поддерживается - 👎 — устарел; всё ещё поддерживается, но в будущем будет удалён diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 996e43fb7b9..5f4d337e055 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 6c6913c7a74..0db94f5602c 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -18,7 +18,7 @@ AdGuard'ı *Yerel VPN* filtreleme modunda kullanıyorsanız, diğer VPN uygulama - Switch to the *Automatic proxy* mode. When you do that, AdGuard will no longer use local VPN and will reconfigure iptables instead - Switch to the *Manual proxy* mode. To do this, go to *Settings* → *Filtering* → *Network* → *Routing mode* -:::note Uyumluluk +:::note Compatibility The *Automatic proxy* mode is only accessible on rooted devices. For *Manual proxy*, rooting is required on devices running on Android 10 or later. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index b4317368ba8..620a75fef55 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::dikkat Kısıtlamalar -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Diğer yanıtlar bu kurallar tarafından değiştirilmeyecektir. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::dikkat Kısıtlamalar -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Söz dizimi** **Temel söz dizimi** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::dikkat Kısıtlamalar -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2541,7 +2540,7 @@ In the `$replace` value, two characters must be escaped: comma `,` and dollar si ||example.org^$replace=/()[\s\S]*<\/VAST>/\$1<\/VAST>/i ``` -There are three parts in this rule: +Bu kuralın üç bölümü vardır: - `regexp` — `()(.|\s)*<\/VAST>`; - `replacement` — `\$1<\/VAST>` where `$` is escaped; @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::dikkat Kısıtlamalar -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2581,7 +2580,7 @@ The `$urltransform` rules allow you to modify the request URL by replacing text **Özellikler** -- `$urltransform` kuralları normalde yalnızca URL'nin yol ve sorgu bölümleri için geçerlidir, bir istisna için aşağıya bakın. +- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2613,7 +2612,7 @@ This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard f ::: -Yukarıda belirtildiği gibi, normalde `$urltransform` kurallarının yalnızca URL'nin yol ve sorgu bölümlerini değiştirmesine izin verilir. Ancak, kuralın `regexp` öğesinin `^http` dizesiyle başlıyorsa, URL'nin tamamı aranır ve kural tarafından değiştirilebilir. URL dönüşümü bir HTTP yönlendirmesi yoluyla gerçekleştirilemiyorsa (örneğin, isteğin yöntemi `POST` ise) böyle bir kural uygulanmayacaktır. +As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). **Örnekler** @@ -2621,7 +2620,7 @@ Yukarıda belirtildiği gibi, normalde `$urltransform` kurallarının yalnızca ||example.org^$urltransform=/(pref\/).*\/(suf)/\$1\$2/i ``` -There are three parts in this rule: +Bu kuralın üç bölümü vardır: - `regexp` — `(pref\/).*\/(suf)`; - `replacement` — `\$1\$2` where `$` is escaped; @@ -2638,7 +2637,7 @@ There are three parts in this rule: **Re-matching rules after transforming the URL** -Tüm eşleşen `$urltransform` kurallarını uyguladıktan sonra, dönüştürülen istek diğer tüm kurallarla eşleştirilecektir: +After applying all matching `$urltransform` rules, the transformed request will be matched against all other rules: E.g., with the following rules: @@ -2647,7 +2646,7 @@ E.g., with the following rules: ||example.com/secondpath^ ``` -`https://example.com/firstpath` adresine yapılan istek engellenecektir. +the request to `https://example.com/firstpath` will be blocked. **Disabling `$urltransform` rules** @@ -2658,7 +2657,7 @@ E.g., with the following rules: :::dikkat Kısıtlamalar -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2798,7 +2797,7 @@ All valid content types: - [`$websocket`](#websocket-modifier), - [`$xmlhttprequest`](#xmlhttprequest-modifier); -This also includes rules that implicitly add all content types: +Bu, tüm içerik türlerini dolaylı olarak ekleyen kuralları da içerir: - [`$all`](#all-modifier); @@ -2861,7 +2860,7 @@ Each of which adds `10^3` to rule priority. - [`$specifichide`](#specifichide-modifier), - [`$urlblock`](#urlblock-modifier); -Each of which adds `10^4` to the priority. +Bunların her biri önceliğe `10^4` ekler. As well as exception with [`$document modifier`](#document-modifier): because it's an alias for `$elemhide,content,jsinject,urlblock,extension`. It will add `10^4` for each modifier from [the top list](#priority-category-4), `10^4 * 5` in total. @@ -3044,7 +3043,7 @@ example.com#$#body { background-color: #333!important; } This rule will apply a style `background-color: #333!important;` to the `body` element at `example.com` and all subdomains. -**Exceptions** +**İstisnalar** Just like with element hiding, there is a type of rules that disable the selected CSS style rule for particular domains. Exception rule syntax is almost the same, you just have to change `#$#` to `#@$#`. @@ -3096,7 +3095,7 @@ CSS 3.0 is not always enough to block ads. To solve this problem AdGuard extends The idea of extended capabilities is an opportunity to match DOM elements with selectors based on their own representation (style, text content, etc.) or relations with other elements. There is also an opportunity to apply styles with non-standard CSS properties. -**Application area** +**Uygulama alanı** Extended selectors can be used in any cosmetic rule, whether they are [element hiding rules](#cosmetic-elemhide-rules) or [CSS rules](#cosmetic-css-rules). @@ -3855,7 +3854,7 @@ The `tag-content` special attribute must not appear in a selector to the left of :::caution Kullanımdan kaldırma bildirimi -Bu özel özellik gelecekte desteklenmeyebilir. Prefer using the `:contains()` pseudo-class where it is available. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available. ::: @@ -3941,7 +3940,7 @@ veya :contains(/reg(ular )?ex(pression)?/) ``` -:::note Uyumluluk +:::note Compatibility `:-abp-contains()` and `:has-text()` are synonyms for `:contains()`. @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::dikkat Kısıtlamalar -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4050,7 +4049,7 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Engelleme kuralları söz dizimi** +**Blocking rules syntax** ```text [domains]#%#//scriptlet(name[, arguments]) @@ -4074,7 +4073,7 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') ``` -**İstisna kuralları söz dizimi** +**Exception rules syntax** Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::dikkat Kısıtlamalar -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4401,8 +4400,8 @@ false_conditions_rules_list where: -- `!#if (conditions)` — koşullar doğru olduğunda bloğun başlangıcı -- `conditions` — just like in some popular programming languages, preprocessor conditions are based on constants declared by ad blockers. Authors of ad blockers define on their own what exact constants they declare. Olası değerler: +- `!#if (conditions)` — start of the block when conditions are true +- `conditions` — just like in some popular programming languages, preprocessor conditions are based on constants declared by ad blockers. Authors of ad blockers define on their own what exact constants they declare. Possible values: - `adguard` always declared; shows maintainers that this is one of AdGuard products; should be enough in 95% of cases - product-specific constants for cases when you need a rule to work (or not work — then `!` should be used before constant) in a specific product only: - `adguard_app_windows` — AdGuard for Windows @@ -4416,9 +4415,9 @@ where: - `adguard_ext_opera` — AdGuard Browser Extension for Opera - `adguard_ext_android_cb` — AdGuard Content Blocker for mobile Samsung and Yandex browsers - `ext_ublock` — special case; this one is declared when a uBlock version of a filter is compiled by the [FiltersRegistry][] - - `cap_html_filtering` — HTML filtreleme kurallarını destekleyen ürünler: Windows için AdGuard, Mac için AdGuard ve Android için AdGuard -- `!#else` — koşullar yanlış olduğunda bloğun başlangıcı -- `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — kural listeleri + - `cap_html_filtering` — products that support HTML filtering rules: AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +- `!#else` — start of the block when conditions are false +- `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — lists of rules - `!#endif` — end of the block **Örnekler** @@ -4467,12 +4466,12 @@ Safari's limit for each content blocker is 150,000 active rules. But in AdGuard Here is the composition of each content blocker: -- AdGuard Genel — Reklam Engelleme, Dile Özgü -- AdGuard Gizlilik — Gizlilik -- AdGuard Sosyal — Sosyal Ağ Araçları, Can Sıkıcı Öğeler -- AdGuard Güvenliği — Güvenlik -- AdGuard Diğer — Diğer -- AdGuard Özel — Özel +- AdGuard General — Ad Blocking, Language-specific +- AdGuard Privacy — Privacy +- AdGuard Social — Social Widgets, Annoyances +- AdGuard Security — Security +- AdGuard Other — Other +- AdGuard Custom — Custom User rules and allowlist are added to every content blocker. @@ -4493,7 +4492,7 @@ rules_list where: - `!#safari_cb_affinity(content_blockers)` — start of the block -- `content_blockers` — comma-separated list of content blockers. Olası değerler: +- `content_blockers` — comma-separated list of content blockers. Possible values: - `general` — AdGuard General content blocker - `privacy` — AdGuard Privacy content blocker - `social` — AdGuard Social content blocker @@ -4548,18 +4547,18 @@ Rules usage frequency comes from the collected [filter rules statistics](../trac where: -- **filter** — filtre tanımlayıcısı -- **yüzde** — beklenen iyileştime yüzde `~= (iyileştirilmiş filtrede kurallar sayılır) / (orijinal filtrede kurallar sayılır) * 100` -- **minPercent** — `yüzde` değerinin alt sınırı -- **maxPercent** — `yüzde` değerinin üst sınırı -- **strict** — `percent < minPercent` VEYA `percent > maxPercent` ve strict modu açıksa filtre derlemesi başarısız olmalıdır, aksi takdirde orijinal kurallar kullanılmalıdır +- **filter** — filter identifier +- **percent** — expected optimization percent `~= (rules count in optimized filter) / (rules count in original filter) * 100` +- **minPercent** — lower bound of `percent` value +- **maxPercent** — upper bound of `percent` value +- **strict** — if `percent < minPercent` OR `percent > maxPercent` and strict mode is on then filter compilation should fail, otherwise original rules must be used In other words, `percent` is the "compression level". For instance, for the Base filter it is configured to 40%. It means that optimization algorithm should strip 60% of rules. Eventually, here are the two versions of the Base filter for AdGuard Browser Extension: -- tam: https://filters.adtidy.org/extension/chromium/filters/2.txt -- iyileştirilmiş: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt +- full: https://filters.adtidy.org/extension/chromium/filters/2.txt +- optimized: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt **If you want to add a rule which should not be removed at optimization use the `NOT_OPTIMIZED` hint:** @@ -4579,27 +4578,27 @@ Eventually, here are the two versions of the Base filter for AdGuard Browser Ext Used to specify the platforms to apply the rules. List of existing platforms and links to Base filter, for example, for each of them: -- `windows` — Windows için AdGuard — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) +- `windows` — AdGuard for Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) -- `mac` — Mac için AdGuard — [https://filters.adtidy.org/mac_v2/filters/2.txt](https://filters.adtidy.org/mac_v2/filters/2.txt) +- `mac` — AdGuard for Mac — [https://filters.adtidy.org/mac_v2/filters/2.txt](https://filters.adtidy.org/mac_v2/filters/2.txt) -- `android` — Android için AdGuard — [https://filters.adtidy.org/android/filters/2.txt](https://filters.adtidy.org/android/filters/2.txt) +- `android` — AdGuard for Android — [https://filters.adtidy.org/android/filters/2.txt](https://filters.adtidy.org/android/filters/2.txt) -- `ios` — iOS için AdGuard — [https://filters.adtidy.org/ios/filters/2.txt](https://filters.adtidy.org/ios/filters/2.txt) +- `ios` — AdGuard for iOS — [https://filters.adtidy.org/ios/filters/2.txt](https://filters.adtidy.org/ios/filters/2.txt) -- `ext_chromium` — Chrome için AdGuard Tarayıcı Uzantısı — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) +- `ext_chromium` — AdGuard Browser Extension for Chrome — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) -- `ext_chromium_mv3` — Chrome için AdGuard Tarayıcı Uzantısı MV3— [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) +- `ext_chromium_mv3` — AdGuard Browser Extension for Chrome MV3 — [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) -- `ext_ff` — Firefox için AdGuard Tarayıcı Uzantısı — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) +- `ext_ff` — AdGuard Browser Extension for Firefox — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) -- `ext_edge` — Edge için AdGuard Tarayıcı Uzantısı — [https://filters.adtidy.org/extension/edge/filters/2.txt](https://filters.adtidy.org/extension/edge/filters/2.txt) +- `ext_edge` — AdGuard Browser Extension for Edge — [https://filters.adtidy.org/extension/edge/filters/2.txt](https://filters.adtidy.org/extension/edge/filters/2.txt) -- `ext_opera` — Opera için AdGuard Tarayıcı Uzantısı — [https://filters.adtidy.org/extension/opera/filters/2.txt](https://filters.adtidy.org/extension/opera/filters/2.txt) +- `ext_opera` — AdGuard Browser Extension for Opera — [https://filters.adtidy.org/extension/opera/filters/2.txt](https://filters.adtidy.org/extension/opera/filters/2.txt) -- `ext_safari` — Safari için AdGuard — [https://filters.adtidy.org/extension/safari/filters/2.txt](https://filters.adtidy.org/extension/safari/filters/2.txt) +- `ext_safari` — AdGuard for Safari — [https://filters.adtidy.org/extension/safari/filters/2.txt](https://filters.adtidy.org/extension/safari/filters/2.txt) -- `ext_android_cb` — AdGuard İçerik Engelleyici — [https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt](https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt) +- `ext_android_cb` — AdGuard Content Blocker — [https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt](https://filters.adtidy.org/extension/android-content-blocker/filters/2.txt) - `ext_ublock` — uBlock Origin — [https://filters.adtidy.org/extension/ublock/filters/2.txt](https://filters.adtidy.org/extension/ublock/filters/2.txt) @@ -4629,10 +4628,10 @@ 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. -- **Windows için AdGuard'da**, *Reklam Engelleyici* sekmesinde veya tepsi menüsünde bulabilirsiniz -- **Mac için AdGuard'da**, *Ayarlar → Gelişmiş → Filtreleme günlüğü* öğesinde bulunur -- **Android için AdGuard'da**, bunu *İstatistik → Son etkinlik* altında bulabilirsiniz. *Son etkinlik* ayrıca *Asistandan* da erişilebilir -- **AdGuard Tarayıcı Uzantısında**, *Diğer* ayarlar sekmesinden veya uzantı simgesine sağ tıklayarak erişilebilir. Only Chromium- and Firefox-based web 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 web browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs :::not @@ -4725,7 +4724,7 @@ The following scriptlets also may be used for debug purposes: - [`prevent-requestAnimationFrame`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-requestanimationframe) - [`prevent-setInterval`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-setinterval) - [`prevent-setTimeout`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-settimeout) -- Belirtilen `replacement` parametresiyle [`prevent-window-open`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-window-open) +- [`prevent-window-open`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-window-open) with specified `replacement` parameter - [`prevent-xhr`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-xhr) - [`trusted-replace-fetch-response`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-trusted-scriptlets.md#trusted-replace-fetch-response) - [`trusted-replace-xhr-response`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-trusted-scriptlets.md#trusted-replace-xhr-response) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index 5cecce4dc80..40dee40b998 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -3,74 +3,72 @@ title: Chrome 版 AdGuard 浏览器扩展 MV3 sidebar_position: 5 --- -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). +由于 Chrome 浏览器 Web Store 逐步淘汰 MV2 扩展，Chrome 浏览器用户可能需要改用与 Chrome 浏览器新 API Manifest V3 兼容的 MV3 扩展。 我们在[博客](https://adguard.com/zh_cn/blog/tag/manifest-v3.html)上详细讨论此主题。 -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. +我们的 MV3 扩展程序有效拦截广告和跟踪器，同时无缝管理社交小部件、横幅和视频广告。 大多数用户不会注意到任何操作差异，但需要注意一些限制和变化。 -## Where to find our extensions +## 在哪里下载我们的扩展 -The **MV3 version** has replaced our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). +**MV3 版本**已取代了 [Chrome Web 商店](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg)中的旧扩展程序。 -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). +**MV3 的 Beta 测试版**仍可以在 [Chrome Web 商店](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf)中找到。 -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. +旧的 Beta 测试版扩展将更名为 [**AdGuard 广告拦截器 MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl)，并且将一直受到支持，直到 Google 淘汰它。 -## Main changes in features and settings +## 功能和设置的主要变化 -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. +- **没有自动和手动过滤器更新**。「过滤器」选项卡中不再有「自动更新过滤器」和「检查过滤器更新」选项。 由于某些规则现在以 DNR 形式应用，因此我们无法根据请求更新过滤器，只能通过更新扩展程序以及商店中的评论的完整过程来更新。 -- **Filtering log** +- **过滤日志** ![过滤日志 \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “assumed rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](/adguard-browser-extension/solving-problems/debug-rules/). + 由于 DNR 限制，我们无法准确显示哪个规则有效，但我们将显示基于引擎数据的“假设的规则”。 如需获取准确信息，需要自行在浏览器中安装扩展程序的“解压”版本。 查看[另一篇文章](/adguard-browser-extension/solving-problems/debug-rules/)了解有关如何执行此操作的详细说明。 -- _Tracking protection_ (formerly known as _Stealth mode_) +- **跟踪保护**（以前称为「隐形模式」） ![跟踪保护 \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. + 由于我们无法使用声明性规则设置 Cookie 的 TTL，因此没有「Cookie」部分，以及「自销毁第一方 Cookie」和「自销毁第三方 Cookies」。 -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate _Security_ filters in the _Filters_ tab. +- 常规设置中不再提供**网络钓鱼和恶意软件保护**。 要保护自己免受恶意网站和诈骗的侵害，请在「过滤器」选项卡中启用适当的「安全」过滤器。 ![安全 \*border](https://cdn.adtidy.org/content/blog/mv3/new/security.png) ## 限制 -### Maximum number of rules and filters +### 规则和过滤器的数量限制 -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. +Manifest V3 对每个扩展的静态规则和正则表达式规则施加限制。 超出这些数量限制后，用户会收到通知。 ![规则数量限制 \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) ![扩展数量太多 \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. +基本上，Manifest V3 将规则分为静态（内置）和动态，并有严格的限制。 -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. +**静态规则**：每个扩展程序至少 **30,000** 个规则，单个用户安装的所有扩展程序的累计限制为 **330,000** 个。 -For regex rules, the limit is set at **1,000 per extension**. +正则表达式规则，**每个扩展**的限制设置为 **1,000**。 -The maximum number of simultaneously enabled filters is **50**. +同时启用的过滤器的最大数量为 **50** 个。 -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. +**动态规则**：严格限制 **5,000** 个规则，其中包括最多 1,000 个正则表达式规则。 -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. -> **Converted rules** are rules that have been transformed -> to [DNR format] using the [declarative converter][github-declarative-converter]. -> During this conversion process, some rules may overwrite others (`$badfilter`), some may be combined (`$removeparam`), -> resulting in a list of rules with a slightly different order. +> **转换后的规则**是使用[声明性转换器][github-declarative-converter]转换为 \[DNR 格式]的规则。 +> 在转换过程中，一些规则会覆盖其他规则（`$badfilter`），一些规则会合并（`$removeparam`），从而导致规则列表的顺序略有不同。 > -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. +> 在转换后的规则列表中，我们将仅使用 5,000 个规则。 其余规则将显示在编辑器中，但无法被应用。 -Here's how a rule with a basic modifier is converted to a declarative rule: +以下是带有基本修饰符的规则如何转换为声明性规则： ```adblock ||example.org^$script,third-party,domain=example.com ``` -is converted to +转换为 ```json [ @@ -94,14 +92,14 @@ is converted to ] ``` -More examples can be found on [GitHub][github-declarative-converter-examples]. +在 [GitHub][github-declarative-converter-examples] 上找到更多示例。 -### Network rule modifiers +### 网络规则修饰符 -Network rule modifiers have limitations: some of them cannot be implemented in MV3, or can only be implemented with restrictions. +网络规则修饰符存在限制：其中一些无法在 MV3 中实现，或者受到一定的限制。 -More details about the limitations can be found on [GitHub][github-declarative-converter]. -For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters). +有关这些限制的更多详细信息，请访问 [GitHub][github-declarative-converter]。 +有关修饰符的更多信息，请参阅我们的[知识库](/general/ad-filtering/create-own-filters)。 [DNR format]: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md index 6df7c6951e3..2c0a41a30cf 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md @@ -1,98 +1,98 @@ --- -title: How to debug rules in AdGuard for Chrome MV3 +title: 在 Chrome MV3 的 AdGuard 中调试规则 sidebar_position: 2 --- -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. +在 [用于 Chrome MV3 的 AdGuard](/adguard-browser-extension/mv3-version) 中，过滤日志仅显示所应用的近似规则，我们称之为“假设的规则”。 原因是，除非扩展名为“解压”格式，否则浏览器无法提供关于特定声明式规则的详细信息。 如需获取准确信息，需要自行在浏览器中安装扩展程序的“解压”版本。 -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. +此说明对于有问题的情况也很有用，比如，在用户要更改扩展中静态包含的规则的情况下。 在大多数情况下，使用扩展中的「用户规则」就足够了。 -## Prerequisites +## 先决条件 -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) +1. **Git**：[安装 Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) +2. **Node**：[安装 Node.js](https://nodejs.org/en/download/package-manager) -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) +3. **Yarn**：[安装 Yarn](https://classic.yarnpkg.com/lang/en/docs/install) -## How to clone extension +## 克隆扩展的方式 -1. Clone the repository: +1. 克隆存储库： ```bash git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git ``` -2. Navigate to the directory: +2. 转到目录： ```bash cd AdguardBrowserExtension ``` -3. Switch to the `v5.0` branch: +3. 切换到 `v5.0` 分支： ```bash git checkout v5.0 ``` -4. Install dependencies: +4. 安装依赖项： ```bash yarn install ``` -## How to build extension +## 建构扩展的方式 -1. Switch to the `v5.0` branch: +1. 切换到 `v5.0` 分支： ```bash git checkout v5.0 ``` -2. Run the following command in the terminal: +2. 在终端中运行以下命令： ```bash yarn dev chrome-mv3 ``` -3. The built extension will be located in the directory: +3. 构建的扩展将放置在以下目录中： ```bash ./build/dev/chrome-mv3 ``` -## How to install unpacked in the browser +## 在浏览器中安装解压包 -1. Turn on developer mode: +1. 开启「开发者模式」： - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) + ![开发者模式](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) -2. Click _Load unpacked_: +2. 单击「加载已解压的扩展程序」： - ![Load unpacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) + ![加载已解压的扩展程序](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) -3. Select the extension directory and click `Select`: +3. 选择扩展目录并点击「选择」： - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) + ![选择](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) 完成！ -## How to debug rules +## 调试规则 -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. +1. 在 `./Extension/filters/chromium-mv3` 目录中的 `.txt` 文件中找到并修改需要的规则。 -2. Convert the rules from txt to declarative form: +2. 将规则从 TXT 格式转换为声明形式： ```bash yarn convert-declarative ``` -3. Build the extension again: +3. 再次构建扩展： ```bash yarn dev chrome-mv3 ``` -4. Reload the extension in the browser: +4. 在浏览器中重新加载扩展： - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) + ![加载扩展](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 9cd3a2c504f..2b3aa498bf9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -15,7 +15,7 @@ sidebar_position: 1 ![开发者模式 \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) -4. Click `background.html`. +4. 点击`background.html`。 ![背景 \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/background1.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md index 31b55a65b95..a7a12dec377 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md @@ -19,7 +19,7 @@ sidebar_position: 3 :::note -「高级保护」仅适用于 iOS 15 及更高版本。 If you are using earlier versions of iOS, you will see the _YouTube ad blocking_ module in the app instead of the _Advanced protection_. +「高级保护」仅适用于 iOS 15 及更高版本。 如果您使用的是早期版本的 iOS，您将在应用程序中看到「_YouTube 广告拦截_」模块，而不是「_高级保护_」。 ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md index c4949abd63a..b8f0504c0aa 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md @@ -29,7 +29,7 @@ sidebar_position: 1 所有过滤器均按主题类别分组。 要查看这些类别的完整列表（不要与内容拦截器混淆），请通过点击盾牌图标打开「保护」部分，然后转到「Safari 保护」→「过滤器」。 -![Filter groups \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/filters_group_en.jpeg) +![过滤器类型 \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/filters_group_en.jpeg) 共有 8 个类别，每个类别都包含多个过滤器，这些过滤器都有一个共同的目的，即阻止广告、社交媒体小工具、Cookie 通知、保护用户免受在线诈骗。 要确定哪些筛选器适合您的需要，请阅读它们的说明，并根据标签进行导航 (`ads`、`privacy`、`recommended` 等等)。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 53a37eaa5ba..209ea649a1e 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -本文介绍我们在 AdGuard 中开发并预装的过滤器。 To check them out, you can [download the AdGuard app](https://agrd.io/download-kb-adblock) +本文介绍我们在 AdGuard 中开发并预装的过滤器。 要查看过滤器运行情况，请[下载 AdGuard 应用程序](https://agrd.io/download-kb-adblock)。 ::: @@ -17,7 +17,7 @@ sidebar_position: 2 - **防跟踪保护过滤器** — 各种在线计数器和网络分析工具的综合列表。 用它来隐藏用户在网上的活动，避免跟踪。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_3_Spyware/filter.txt) - **URL 跟踪过滤器**从网址中移除跟踪参数加强隐私保护。 当用户选择在隐身模式下拦截跟踪参数时，此过滤器将自动启用。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_17_TrackParam/filter.txt) - **社交媒体过滤器**此过滤器移除社交媒体小工具「点赞」和「分享」按钮及类似的元素。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_4_Social/filter.txt) -- **恼人广告过滤器**屏蔽网页上的恼人元素。 [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_14_Annoyances/filter.txt). Includes the following AdGuard filters (all of them can be enabled separately from the Annoyances filter): +- **恼人广告过滤器**屏蔽网页上的恼人元素。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_14_Annoyances/filter.txt)。 包括以下 AdGuard 过滤器（以下过滤器都可以与烦恼过滤器分开启用）： - **Cookie 通知**在网页上拦截 Cookie 通知。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_18_Annoyances_Cookies/filter.txt) - **弹出窗口**拦截各种对网站运行没有必要的弹窗。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_19_Annoyances_Popups/filter.txt) @@ -33,16 +33,16 @@ sidebar_position: 2 - **荷兰语过滤器**删除荷兰语网站上的广告。 最初是基于 [EasyList Dutch](https://easylist.to/) 过滤器，随后我们根据用户的反馈进行修改。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_8_Dutch/filter.txt) - **西班牙语/葡萄牙语过滤器**删除西班牙语和葡萄牙语网站上的广告。 最初是基于 [Fanboy’s Spanish/Portuguese](https://www.fanboy.co.nz/fanboy-espanol.txt) 过滤器，随后我们根据用户的反馈进行修改。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_9_Spanish/filter.txt) - **土耳其语过滤器**删除土耳其语网站上的广告。 由我们根据用户的反馈创建。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_13_Turkish/filter.txt) -- **中文过滤器**删除中文网站上的广告。 Originally based on the [EasyList China](https://github.com/easylist/easylistchina) filter and subsequently modified by us according to the complaints from users. [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_224_Chinese/filter.txt) -- **Ukrainian filter** removes ads from websites in Ukrainian. Learn more about this filter on [this page](https://adguard.com/en/blog/ukrainian-filter.html). [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_23_Ukrainian/filter.txt) +- **中文过滤器**删除中文网站上的广告。 最初是基于 [EasyList China](https://github.com/easylist/easylistchina) 过滤器，随后我们根据用户的反馈进行修改。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_224_Chinese/filter.txt) +- **乌克兰过滤器**删除乌克兰语网站上的广告。 在[此页](https://adguard.com/en/blog/ukrainian-filter.html)上了解更多关于此过滤器的信息。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_23_Ukrainian/filter.txt) - **实验性过滤器**，此过滤器设计用于在将某些有风险的过滤规则添加到基本过滤器之前对其进行测试。 如果这些规则执行没有任何问题，它们会被添加到主过滤器中。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **移动广告过滤器**拦截移动设备上的广告。 包含所有已知的移动广告网络。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS 过滤器** — 此过滤器由其他几个过滤器 (AdGuard 基础过滤器、社交媒体过滤器、防跟踪保护过滤器、移动广告过滤器、EasyList 和 EasyPrivacy) 组成，并经过简化，以便更好地与 DNS 级别的广告拦截兼容。 [AdGuard DNS](https://adguard-dns.io/kb) 服务器使用此过滤器来拦截广告和跟踪器。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) +- **快速修复的 AdGuard 过滤器**，无需更新 MV3 扩展即可快速解决网站过滤问题。 [查看规则](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard 过滤器政策 -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. 阅读全文 [AdGuard 过滤政策](../filter-policy)了解详细信息。 +我们的过滤政策定义 AdGuard 过滤器应该和不应该阻止的内容，以及从过滤器中添加和删除规则的规定。 阅读全文 [AdGuard 过滤政策](../filter-policy)了解详细信息。 ## 为 AdGuard 过滤器做贡献 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 0ecb385fd6e..7fabd0dc8c9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2432,7 +2430,7 @@ With these rules, specified UTM parameters will be removed from any request save $xmlhttprequest,removeparam=p1case2 ``` - is converted to + 转换为 ```bash [ @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index f441bac20e3..faeba3b0fd6 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,14 @@ AdGuard 广告拦截的过滤器包含以下过滤器： - AdGuard 基础过滤器 - AdGuard 移动广告过滤器 - 按语言原则划分的地区过滤器，包括中文、荷兰语、法语、德语、日语、俄语、西班牙语/葡萄牙语、土耳其语和乌克兰语 -- AdGuard Quick Fixes filter +- 快速修复的 AdGuard 过滤器 ### 过滤器的用途 - **基础过滤器**旨在拦截英语网站和没有单独过滤器的网站上的广告。 它还包含适用于所有网站（无论网站的语言）的一般过滤规则。 - **移动广告过滤器**拦截移动版网站和移动应用程序中的广告。 没有基于语言的细分。 - **地区过滤器**遵循与**基础过滤器**相同的政策，但仅限于特定语言的网站。 -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. +- **快速修复的 AdGuard 过滤器**，无需更新 MV3 扩展即可快速解决网站过滤问题。 广告拦截过滤器的主要目标在于拦截网站、应用程序和某些可以从互联网上加载广告的设备上的所有类型广告。广告类型如下： @@ -64,7 +64,7 @@ AdGuard 广告拦截的过滤器包含以下过滤器： - 插播广告。移动设备上覆盖应用程序或网络浏览器界面的全屏广告。 - 占据较大空间或在背景中格外显眼并吸引访问者注意力的残留广告（几乎无法辨别或难以察觉的广告除外）。 - Anti-adblock 广告。当主要广告被屏蔽时，网站上显示的替代广告。 -- Bait elements that are used by multiple known adblock detection scripts to detect an ad blocker presence for different goals including changing the way ads are shown, fingerprinting, etc. +- 一些知名脚本会使用诱饵元素来检测广告拦截程序。这样做有多种目的，包括改变广告显示方式、指纹识别等等。 - 网站自身的广告，如果它已被一般过滤规则屏蔽（请参阅*限制及例外*）。 - 阻止网站使用的反屏蔽脚本（请参阅*限制及例外*）。 - 恶意软件注入的广告，如果提供了有关其加载方法或复制步骤的详细信息。 @@ -116,7 +116,7 @@ AdGuard 跟踪保护过滤器包含以下过滤器： - 跟踪 Cookie - 跟踪像素 - 浏览器的跟踪 API -- Detection of the ad blocker for tracking purposes +- 检测广告拦截程序以进行跟踪 - Google 浏览器的隐私沙盒功能及其用于跟踪的分叉（Google Topics API、受保护受众 API） **URL 跟踪过滤器**旨在移除网址中的跟踪参数。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..bb19cd218b8 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -1,64 +1,64 @@ --- -title: How ad blocking works +title: 广告拦截的工作方式 sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard 有众多广告拦截服务以适用于各种平台且各产品都有独特功能。 所有产品的共同点是拦截广告和跟踪器。 本文将由浅入深描述广告拦截的工作方式。 :::note -We don't cover DNS filtering here. It's a different way of blocking ads, with its own advantages and disadvantages. Follow this link to [learn more about DNS filtering](https://adguard-dns.io/kb/general/dns-filtering#how-does-dns-filtering-work). +此处我们未涵盖 DNS 过滤。 这是不同的广告拦截方式，有其自己的利弊。 请跟随此链接[以了解更多关于 DNS 过滤的信息](https://adguard-dns.io/kb/general/dns-filtering#how-does-dns-filtering-work)。 ::: - + -## General principle +## 一般原则 -Filter lists, also called filters, lie at the core of any ad blocker. Filters are literally lists of rules written in a special syntax. Ad blockers can understand this complex syntax. They interpret filtering rules and perform actions on web traffic based on what the rules tell them to do: block specific elements, alter web pages in certain ways, etc. +过滤器列表，也称为过滤器，是任何广告拦截器的核心。 实际上，过滤器是用特殊语法编写的规则列表。 广告拦截器能“理解”此复杂的语法。 它们解释过滤规则并基于告知它们要做什么的规则执行网络流量动作：拦截特定元素，以某些方式更改网页等。 -![How ad blocking works](https://cdn.adtidy.org/public/Adguard/Blog/manifestv3/adblockingworks.png) +![广告拦截的工作方式](https://cdn.adtidy.org/public/Adguard/Blog/manifestv3/adblockingworks.png) -## Filter lists +## 过滤器列表 -To better understand ad blocking, it's important to know the underlying principles of how filters work. +要更好的了解广告过滤，知晓过滤器工作原理尤为重要。 -Filtering rules that make up filters are not created automatically. They are developed by filter maintainers, including professionals and volunteers, who use browser developer consoles and other tools (such as the AdGuard's filtering log) to determine which rules will block a particular ad or tracker. This description of the process is very simplistic — some ads are particularly hard to block and require multiple rules, multiple iterations, and the use of complex syntax. +构成过滤器的过滤规则不会自动创建。 它们是由包括专业和业余维护者在内的过滤器维护者开发的，他们使用浏览器开发者控制台和其它工具（如 AdGuard 过滤日志）以确定拦截特定广告或跟踪器的规则。 此过程描述非常简单：某些广告难以拦截且需要多重规则，多次迭代并使用复杂语法。 -And even when a rule finally gets added to a filter, it doesn't mean that it stays there forever. Ads change, ways to serve the same ads on the same websites change, and the filter rules have to change, too. Sometimes rules become obsolete, a new ad appears, or a new filtering rule is needed to block the same ad. Filters are often maintained by one person, but even for a team of maintainers, it's impossible to constantly monitor the entire web. That's why many ad blockers have tools to help users easily report any filter-related issues they encounter. +即使规则最终添加到过滤器中，也不意味着它会永远存在。 因为广告在变，相同网站上提供相同广告的方式在变，过滤规则也须改变。 有时规则会过时，会出现新广告，或者需要新的过滤规则阻止同一广告。 过滤器通常由个人维护，但即使是维护人员团队，也不可能持续监视整个网络。 这就是为什么许多广告拦截器都有工具以帮助用户轻松报告他们遇到的任何与过滤器相关的问题。 -![Filter update scheme](https://cdn.adtidy.org/public/Adguard/Blog/manifestv3/filtersupdates.png) +![过滤器更新方案](https://cdn.adtidy.org/public/Adguard/Blog/manifestv3/filtersupdates.png) -AdGuard users [have access to a special web reporting tool](https://reports.adguard.com/new_issue.html). Thanks to user complaints, filter developers can focus on correcting their filter lists and not on scouring the Internet for new and old unblocked ads. +AdGuard 用户[可以访问专门的网络报告工具](https://reports.adguard.com/new_issue.html)。 归功于用户的报告，过滤器开发者才可致力于他们的过滤器列表维护且不用刷网页寻找那些新旧未拦截的广告。 -Filters can do more than just block ads. There are filters that block tracking, social media widgets, and annoyances such as cookie notices. Different users may choose different combinations of filters to match their personal preferences. There are websites like [filterlists.com](https://filterlists.com/) that are dedicated to filter lists and have huge databases. +过滤器不仅可拦截广告，还能做更多。 过滤器还可以拦截跟踪器，社交媒体小工具及其他烦人的元素，如 Cookie 通知。 不同的用户可以选择不同的过滤器组合以匹配个人首选。 不少网站，如 [filterlists.com](https://filterlists.com/)，有专门的过滤器列表和巨大的数据库。 -We develop and maintain [our own set of filter lists](../adguard-filters) that can be used with AdGuard or other ad blockers. +我们开发并维护[自己的过滤器列表集合](../adguard-filters)以供 AdGuard 或其它广告拦截器使用。 -## Types of filtering rules +## 过滤规则类型 -There are many types of filtering rules that serve different purposes. Depending on the ad blocker you use, and especially on your OS, some types of rules may not be supported. +过滤规则的类型众多，用途不尽相同。 依赖于用户所用的广告拦截器，特别是操作系统，某些规则类型可能不受支持。 -### Basic filtering rules +### 基本过滤规则 -To be displayed on a web page or in an app, the ad has to be loaded from a server first. To do so, the browser or the app needs to send a web request. The most basic way of preventing an ad from appearing on your screen is to block this request so it never reaches the server, and thus there's no reply. +要在网页或应用程序中托管广告，必须首先从服务器加载它们。 为此，浏览器或应用程序要发送网络请求。 阻止广告出现在屏幕上的最基本方式就是拦截相应的请求防止其到达服务器，从而不会有“广告”响应。 -Basically, all AdGuard Ad Blocker products can block web requests according to the active filter rules. This method is very effective at stopping the ad, but it has some drawbacks. The most obvious one is: whatever place an ad was taking up will be left empty or occupied by an ad leftover. +基本上，所有 AdGuard 广告拦截产品都可依据活动的过滤规则拦截网络请求。 此方式对阻止广告非常有效，但其有些弊端。 最明显的就是：在进行拦截后，广告占据的位置就会残留有空白或被其它广告占据。 -### Cosmetic filtering rules +### 修饰过滤规则 -Every web page has a Document Object Model (DOM), an HTML document containing the structure and elements of this page. As ads are also page elements, they get recorded in the DOM. Ad blockers can remove parts of the DOM, while filtering rules help them understand which parts are ads and should be removed, and which parts should be left intact. +各网页都有 Document Object Model（英文简称：DOM，中文：文档对象模型），一种包含网页结构和元素的 HTML 文档。 广告也是网页元素，所以都会记录到 DOM 内。 在过滤规则协助广告拦截器了解哪些部件是广告且需要移除，哪些部件是要保留之时，广告拦截器可移除部分 DOM 内容。 -This method allows you to avoid above-mentioned blank spaces and ad leftovers, as well as perform other more complicated tasks. +此方式允许用户避免以上提及的空白和广告残留，以及执行更多其它更负责的任务。 -### HTML filtering rules +### HTML 过滤规则 -In most cases, it's enough to use the above-mentioned basic and cosmetic rules to filter ads. But when it is necessary to change the HTML code of the page itself before it is loaded, you need filtering rules for HTML content. These rules allow you to specify the HTML elements to be cut out before the browser even loads the page. +在大多数情况下，以上提及的基本规则和修饰规则足以过滤广告。 不过，如果需要在加载页面之前更改页面的 HTML 代码，就需要针对 HTML 内容制定过滤规则。 这些规则允许在浏览器加载网页之前移除特定的 HTML 元素。 -These rules are quite complicated and require the ad blocker to be granted certain access rights, so not all platforms support them. Currently, these rules work only in the AdGuard Firefox add-on and in the AdGuard apps for Windows, Mac, and Android. +这些规则相当复杂，需要授予广告拦截器一定的访问权限，因此并非所有平台都支持这些规则。 当前这些规则仅工作于 AdGuard Firefox 附件以及运行于 Windows、Mac、Android 系统上的 AdGuard 应用程序。 :::info -There are other types of filtering rules, but they require more advanced technical knowledge to understand how they work. If you are interested, [check out our comprehensive guide on filtering rules in the linked article](../create-own-filters). +还有其它类型的过滤规则，但用户需要有更高级的技术知识以理解其工作方式。 如果有兴趣， [请查看相应文章](../create-own-filters)了解过滤规则的综合指南。 ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md index d67553c15c4..71d8d635929 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md @@ -1,37 +1,37 @@ --- -title: Search ads and self-promotion +title: 搜索广告和网站自宣传 sidebar_position: 3 --- -**Disclosure.** While AdGuard provides an option to show some ads, we do not have any 'acceptable ads' program like Adblock Plus and some other ad blockers, where they take money for leaving certain ads unblocked. This isn't our way of doing business. We do not get paid for showing any of the ads, and we do not use the term 'acceptable' for a reason: the ads we might show may be, in fact, useful and not just 'acceptable'. All of this applies only to search ads and self-promotion ads. +**重要信息**。尽管 AdGuard 提供「允许搜索广告和网站自宣传」的选项，但这并不意味着我们有一个“可接受的广告”计划（正如 Adblock Plus 和其他一些拦截器）。有些软件会付费以将某些类型的广告排除在拦截之外。 这不是我们做生意的方式。 我们没有付费托管任何广告，而且我们不使用“可接受”一词并非巧合：我们有选项让用户展示广告，因为这些广告可能有用而不仅仅是“可接受”。 这些设置仅适用于搜索广告和网站自宣传。 -You can turn off the display of these ads at any time. Furthermore, we will explain which ads qualify for this definition. +用户可以随时关闭上述功能。 以下我们解释「允许搜索广告和网站自宣传」功能包括的广告。 -### Search ads +### 搜索广告 -Search ads are ads that you see among search query results when using online search engines, such as Google, Bing, DuckDuckGo, etc. +搜索广告是用户在使用 Google、Bing、DuckDuckGo 等搜索引擎时在搜索结果中看到的广告。 -![Search ads](https://cdn.adtidy.org/content/kb/ad_blocker/general/googlead.jpg) +![搜索广告](https://cdn.adtidy.org/content/kb/ad_blocker/general/googlead.jpg) -These ads are always contextual: they are targeted to match the keywords you used in the query. This helps you find exactly what you are searching for. Moreover, search ads (because they go through manual moderation) are often more relevant and helpful than the rest of the search results. +这些广告始终与上下文相关：它们有针对性地匹配用户在查询中使用的关键字。 这可以帮用户找到想要搜索的内容。 此外，搜索广告（要经过人工审核）往往比其他搜索结果更相关、更有帮助。 -Another argument in defense of search ads is that they are much less intrusive than many other ad formats. +支持搜索广告显示的另一个论点是，它们比许多其他广告格式的侵入性要小得多。 -### What is websites' self-promotion? +### 什么是网站自推销？ -In principle, when an ad on a website promotes this particular website or closely related websites, social media, and so on, such an ad is considered a self-promoting one. +原则上，当网站上的广告推广该网站或紧密相关的网站、社交媒体等时，这种广告被视为自我推广广告。 -![Search ads](https://cdn.adtidy.org/content/kb/ad_blocker/general/echodot.jpg) +![搜索广告](https://cdn.adtidy.org/content/kb/ad_blocker/general/echodot.jpg) -Our general stance here is very similar to the EasyList policy regarding self-promotion ads. According to our [filter policy](../filter-policy), we should not block these ads; however, we should not make an exception if such an ad gets blocked by some rule 'alongside' a regular ad. +我们对这类广告的想法与 EasyList 对自我推广广告的政策非常相似。 根据我们的[过滤政策](../filter-policy)，我们不应该拦截这类广告。同时，如果此类广告与常规广告一起被规则屏蔽，我们也不应将其作为例外情况处理。 -Partly, this is due to ethical reasons, but mostly because such ads are rarely too intrusive and are often useful for the visitor of the website (who is supposedly interested in this website's content). +部分原因是出于伦理原因，但主要是因为这样的广告很少过于干扰，并且通常对访问网站的访客（用户很可能对该网站的内容感兴趣）是有用的。 -By enabling 'Search ads and self-promotion', AdGuard users can unblock some of these self-promotion ads. +启用「搜索广告和网站自宣传」，AdGuard 用户可以解除对部分网站自宣传广告的屏蔽。 -### What ads are on the list? +### 拦截的广告 -When you enable 'Search ads and self-promotion', search ads from the following search engines are shown: +启用「搜索广告和网站自宣传」后，将显示以下搜索引擎的搜索广告： - Google - Yahoo @@ -41,8 +41,8 @@ When you enable 'Search ads and self-promotion', search ads from the following s - DuckDuckGo - StartPage -As well as all self-promotional ads that satisfy our filter policy. +以及所有符合我们过滤规则的网站自宣传广告。 -### Summary +### 总结 -Allowing 'Search ads and self-promotion' is a 100% optional feature that may be helpful in some cases. If you don't like it, you can turn it off at any time. It does not, and never will, include any ad types or individual ads that do not fall into one of the two categories described above. +允许「搜索广告和网站自宣传」是一项完全可选的功能，它在某些情况下可能会有所帮助。 如果有用户不想看到此类广告，可以随时将其关闭。 此选项不包括（也永远不会包括）任何不属于上述两类中的任何广告类型或单个广告。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md index 58f60bbc9d6..70ff5f5a0e4 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md @@ -1,45 +1,45 @@ --- -title: Tracking filter rules statistics +title: 跟踪过滤规则统计 sidebar_position: 4 --- :::note -The *Send statistics for ad filters usage* option is disabled by default. Nothing will be sent unless a user manually enables it to help us improve our blocking filters. +「*发送广告过滤器使用情况*」选项默认是禁用的。 除非用户手动开启该选项以帮助我们改进拦截过滤器，软件什么信息也不会发送。 ::: -### Why do we need ad filters? +### 为什么广告过滤器很重要？ -Let's start by defining what ad filters are. Thanks to these filters, AdGuard removes ads from websites. They are manually compiled based on your complaints about ads on websites. Ad filters are an essential element of AdGuard — their quality determines the overall quality of AdGuard ad blocking. +让我们先从广告过滤器的定义开始。 有了广告过滤器的帮助，AdGuard 才能移除网站上的广告。 它们是基于用户对网站广告的投诉而手动编译的。 广告过滤器是 AdGuard 的重要元素，它们的品质确定 AdGuard 拦截广告的整体效果。 -However, there is a downside. Over the years, more and more ad filters have been appearing. And the more ad filters are there, the more memory AdGuard consumes, thus slowing down the rendering of web pages. At the same time, some of the filters start to expire, gradually becoming a dead weight that has no use, only consumes memory, and slows down the program. +然而，有个缺点。 多年来，广告过滤器的数量越来越多。 而且广告过滤器越多，AdGuard 占用的内存也就越多，从而降低网页的渲染速度。 同时，一些过滤器慢慢过期，逐渐成为无用的累赘，只会占据内存，并降低程序的运行速度。 -### Why do we need statistics? +### 为什么统计数据很重要？ -We want to solve the problem of outdated filtering rules once and for all. But we need your help to do so. By gathering statistics on used filtering rules, we detect and remove the rules that are no longer used. As a result, it will help all those who use AdGuard. +我们希望一劳永逸地解决过滤规则过期的问题。 不过，我们需要大家的帮助。 收集使用的过滤规则的统计数据，让我们检测并移除不再使用的规则。 结果，我们能帮助安装 AdGuard 的新用户。 -If your computer is powerful enough, it won’t really affect you. But the difference will be very noticeable for users of low-power netbooks or tablets. +如果用户有一台足够强大的计算机，本问题就不会真正影响他。 不过，对于低功耗笔记本电脑和平板电脑的用户来说，差异将非常明显。 -### What kind of statistics will be sent? +### 统计数据包括什么信息？ -If you enable the *Send statistics for ad filters usage* option, the following information is sent periodically: +如用户开启「*发送广告过滤器使用情况*」，软件将定期发送以下信息： -- Extension version -- Browser type (Chrome/Firefox/Opera/Yandex.Browser/Safari). -- List of enabled ad filters. -- The list that consists of the following elements: - - *The domain name of the website* - - *The number of recent page views* - - *The list of filtering rules and Filter ID which were activated on this website* - - *The domain name of blocked requests is sent for URL rules* The list is created based on the website's visit statistics since the last time statistical data was sent. +- 扩展版本 +- 浏览器类型（Chrome/Firefox/Opera/Yandex.Browser/Safari） +- 启用的广告过滤器列表 +- 列表由以下元素组成： + - *网站域名* + - *最近的页面浏览量* + - *在网站上激活的过滤规则和过滤器 ID 的列表* + - 「*被阻止发送请求至URL的域名规则*」 该列表是根据网站自上次发送统计数据以来的访问统计数据创建的 -The collected statistics will be sent periodically to our server for analysis and filter optimization. +收集的统计数据将定期发送到我们的服务器以便我们分析和优化过滤器。 -It's important to note that all the statistics we get are averaged and anonymized. We don't use these statistics for any purpose other than optimizing the filters, and we do not sell this data to third parties. You can read about it in our [Privacy policy](https://adguard.com/privacy.html). +请注意，我们获得的所有统计数据都是平均且匿名处理的。 我们不会将统计数据用作除优化过滤器之外的其它用途，我们也不会销售它们给第三方。 用户可以在我们的[隐私政策](https://adguard.com/privacy.html)中阅读相关内容。 -### What does tracking filter rules statistics fraught with? +### 跟踪过滤规则统计会导致什么？ -For the vast majority of users, the change in computer speed will not be really noticeable. However, netbook and tablet users may notice a slight slowdown. +对于绝大多数用户来说，电脑速度的变化其实并不明显。 不过，上网本和平板电脑用户可能会注意到速度略有放缓。 -Periodically, we will send the gathered statistics to the server. The size of the transmitted data is not very large and is comparable to the size of an average web page. +我们将定期向服务器发送收集到的统计数据。 传输的数据大小不是很大，与普通网页的大小相当。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 3bf0770abeb..3ecd468e6c4 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -1,77 +1,77 @@ --- -title: What is HTTPS filtering +title: 什么是 HTTPS 过滤 sidebar_position: 1 --- -### What is HTTPS? +### 什么是 HTTPS？ -HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. +HTTPS（安全超文本传输协议）是 HTTP 协议的扩展，支持加密以提高安全性。 该协议用于安全传输有价值的信息，如个人数据、信用卡详细信息等。 -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +使用 HTTPS 非常有利，因为加密流量可以防止第三方窃听，我们非常关注这一点。 近年来，HTTPS 的接受度一直在增长，主要是因为 [ Google 鼓励](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html)，也因为免费证书颁发机构 [Let's Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt) 的出现。 -The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. +下图描述普通 HTTP 协议和安全 HTTPS 协议之间的区别。 -![What is HTTPS?](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https.png) +![什么是 HTTPS？](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https.png) -### What is a security certificate? +### 什么是安全证书？ -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +简而言之，HTTPS 意味着数据加密。 但仍然存在一个问题：如何确定已与正确的网站建立加密连接？ 这就是安全证书发挥作用的时候。 证书可以证明网站的真实身份。 如网站无此类证书，或证书包含不正确的信息，浏览器将不允许建立安全连接。 重要的是，网站使用的证书必须由浏览器信任的证书颁发机构 (CA) 颁发。 此种 CA 确保 SSL 证书确实颁发给网站的所有者。 -### Why does AdGuard need to be able to filter HTTPS? +### 为什么 AdGuard 要能够过滤 HTTPS？ -当前大部分网站使用 HTTPS，广告亦是如此。 Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +当前大部分网站使用 HTTPS，广告亦是如此。 以下是一些热门网站，如果没有 HTTPS 过滤，将无法删除广告：youtube.com、facebook.com 和 x.com。 -### How does HTTPS filtering work? +### HTTPS 过滤的工作方式? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +如果工作方式很容易的话，HTTPS 就不会那么安全了。 当浏览器尝试连接到服务器时，AdGuard 会建立两个安全连接：一个与浏览器（或另一个应用程序）建立连接，另一个与服务器建立连接。 浏览器必须信任 AdGuard 及其创建的连接。 为此，AdGuard 生成一个特殊（且唯一）的根证书并将其安装到系统中，并在需要时安装到某些浏览器中（例如，Firefox 浏览器）。 AdGuard 可以看到安全连接内发生的情况，并完成自己的工作，即拦截广告和跟踪器。 -For better understanding, we have depicted this process: +以下查看处理过程： -![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) +![HTTPS 过滤的工作方式](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) -### Does my traffic remain encrypted and secure? +### 用户流量是否保持加密且安全？ -Of course! Your connection with a remote server remains encrypted and secure. AdGuard, just like your browser, checks the server’s certificate before deciding whether to filter it or not. +当然！ 用户与远程服务器的连接保持加密且安全。 AdGuard 与用户的浏览器一样，会在决定是否过滤服务器证书之前检查服务器的证书。 -However, HTTPS filtering has its drawbacks. The most important one is that it hides from the browser the actual certificate of the website. Instead, the browser sees the certificate issued by AdGuard. +然而，HTTPS 过滤也有其缺点。 最重要的一点是它向浏览器隐藏网站的实际证书。 浏览器看到的是 AdGuard 颁发的证书。 -Because of this, we have taken additional measures to improve connection security. +因此，我们采取了额外的措施以提高连接安全性。 -### Financial websites and websites with sensitive personal data +### 金融网站和含有敏感个人数据的网站 -By default, AdGuard doesn’t filter any information on websites of banks, payment systems, or websites with valuable personal data. We maintain a list of [thousands of exclusions](https://github.com/AdguardTeam/HttpsExclusions). +默认情况下，AdGuard 不会过滤银行网站、支付系统或包含有价值个人数据的网站上的任何信息。 我们维护着[数千个排除项](https://github.com/AdguardTeam/HttpsExclusions)的列表。 -If you believe some website should be added to this list, please [let us know](https://github.com/AdguardTeam/HttpsExclusions/issues/new). +如果您认为某些网站应添加到此列表中，[请告知我们](https://github.com/AdguardTeam/HttpsExclusions/issues/new)。 -### Extended Validation (EV) certificates +### 扩展验证 (EV) 证书 -AdGuard allows you to disable filtering for all websites that use extended validation certificates. +AdGuard 让用户禁用对所有使用扩展验证证书的网站的过滤。 -An EV certificate offers a higher level of security and provides more guarantees than a regular certificate, proving that the website is not fraudulent or fake. +与普通证书相比，EV 证书的安全级别更高，能提供更多保证，确保网站并非欺诈或伪造。 -### Problems related to HTTPS filtering +### 与 HTTPS 过滤有关的问题 -A [2017 study](https://cdn.adtidy.org/public/Adguard/Blog/https/interception-ndss17.pdf) shows that 5 to 10% of HTTPS connections are established by HTTPS-filtering applications. It is usually done by various kinds of antivirus software. The bad news is that 24 out of 26 tested antiviruses reduced, in various ways, the connection security level, while two-thirds created connections prone to hacking. +[2017 年研究](https://cdn.adtidy.org/public/Adguard/Blog/https/interception-ndss17.pdf)显示 5% 到 10% 的 HTTPS 连接是由 HTTPS 过滤应用程序建立的。 它通常是由各种防病毒软件完成的。 坏消息是，26 款经过测试的防病毒软件中有 24 款以各种方式降低连接安全级别，而三分之二的产品创建了容易遭受黑客攻击的连接。 -The researchers came to a simple conclusion: the Internet security community should pay close attention to applications that filter secure connections. And the developers of such software must pay serious attention to the quality of filtering implementations. +研究人员得出一个简单的结论：互联网安全社区应密切关注过滤安全连接的应用程序。 此类软件的开发人员必须认真关注过滤的质量。 -We would like to note that AdGuard was not tested in the above study. We ran estimates according to their set of tests, and at the time of testing, we could have received the maximum score — A\*. However, this score is not perfect. During the study, the researchers identified some issues that were omitted in the final evaluation. +需要强调的是，AdGuard 没有参加上述的研究。 我们根据他们的测试集进行了估算，在测试过程中，我们可以获得最高分 — A\*。 然而，这个分数并不完美。 在研究过程中，研究人员发现一些在最终评估中被忽略的问题。 -Here at AdGuard, we fully agree with those conclusions. Moreover, we would like to be as open with users as possible and talk about the problems we are currently experiencing and the steps we are taking to improve the quality and security of the filtering mechanism. The list of these problems is sorted by priority. +在 AdGuard，我们 100% 同意上述结论。 此外，我们希望尽可能地向用户开放，讨论我们目前遇到的问题以及我们为提高过滤机制的质量和安全性而采取的措施。 这些问题的列表按优先级排序。 -Most of the problems discovered in the above study are related to certificate validation mechanisms. This is what we want to focus on first. We are working on a separate certificate validation library. Moreover, we want to make it open source. A [separate article](../known-issues) lists all the known drawbacks of HTTPS filtering in AdGuard and our plans to fix them. +上述研究中发现的大多数问题都与证书验证机制有关。 这是我们首先要关注的。 我们就开发一个单独的证书验证库。 此外，我们希望将其开源。 [另一篇文章](../known-issues)列出 AdGuard 中 HTTPS 过滤的所有已知缺点以及我们的修复计划。 -#### HTTPS filtering issues on Android 7+ +#### Android 7+ 的 HTTPS 过滤问题 -[Starting from Android 7](https://adguard.com/en/blog/android-nougat-release-and-what-does-it-mean-for-adguard-users.html), developers have to explicitly indicate that their apps trust user-installed certificates. Not everyone wants to, or bothers with it. What does it mean for AdGuard? AdGuard installs a user certificate to be able to filter HTTPS traffic. If an app doesn't trust this certificate, its HTTPS traffic will not be filtered. What to do? +[从 Android 7 开始](https://adguard.com/en/blog/android-nougat-release-and-what-does-it-mean-for-adguard-users.html)，开发人员就必须明确指出他们的应用信任用户安装的证书。 并不是每个人都愿意这样做，或者对此感到烦恼。 这对 AdGuard 意味着什么？ AdGuard 安装用户证书以便能够过滤 HTTPS 流量。 如果应用不信任此证书，则不会过滤其 HTTPS 流量。 该怎么办？ -The first thing worth mentioning is that many apps (even modern ones) still trust user certificates. Nothing has changed in this regard. Almost all browsers also trust such certificates. There may be some exotic browsers that do not, but they are a rare exception to common practice. +首先值得一提的是，许多应用程序（甚至是现代应用程序）仍然信任用户证书。 在这方面没有任何变化。 几乎所有浏览器也都信任此类证书。 可能有一些外来浏览器不这样做，但它们是常见做法的罕见例外。 -Finally, if your device is rooted, you can move the AdGuard certificate to the system storage. This way, you don't have to worry about any permissions a particular app may or may not have — HTTPS traffic will be filtered for modern apps just as well as for older ones. Please keep in mind that in this case, some additional security restrictions (e.g., HPKP or `Expect-CT`) apply to AdGuard. +最后，如果设备已获得 Root 权限，则可以将 AdGuard 证书移至系统存储。 这样，用户不必担心特定应用程序可能具有或不具有的任何权限，HTTPS 流量将针对现代应用程序和旧应用程序进行过滤。 请记住，在这种情况下，一些额外的安全限制（例如 HPKP 或 `Expect-CT`）适用于 AdGuard。 -### How to manually check HTTPS quality? +### 如何手动检查 HTTPS 品质？ -There are several dedicated websites where you can check the quality of your HTTPS connection. These websites check if your browser (or, in our case, your browser plus AdGuard) is susceptible to common vulnerabilities. If you plan to use any program that filters HTTPS, not necessarily AdGuard (e.g., an antivirus), we advise that you check the connection quality on these websites. +有数个专门的网站可用于您检查 HTTPS 连结品质。 这些网站会检查您的浏览器（或者在我们的例子中，您的浏览器加上 AdGuard）是否容易受到常见漏洞的影响。 如果您打算使用任何过滤 HTTPS 的程序，不一定是 AdGuard（例如防病毒软件），我们建议检查这些网站的连接质量。 - [https://www.ssllabs.com/ssltest/viewMyClient.html](https://www.ssllabs.com/ssltest/viewMyClient.html) - [https://www.howsmyssl.com/](https://www.howsmyssl.com/) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md index cae77f9a7a6..64dbfba56f7 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md @@ -55,7 +55,7 @@ The maximum number of simultaneously enabled filters is **50**. **Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. +If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first Allowlist, then User rules, Custom filters, and finally — Quick Fixes filter. > **Converted rules** are rules that have been transformed > to [DNR format] using the [declarative converter][github-declarative-converter]. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 660be2e5d9a..3fb026fd486 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -1519,7 +1519,7 @@ preroll.ts :::caution Restrictions -- `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). +- Rules with the `$hls` modifier can only be used [**in trusted filters**](#trusted-filters). - `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -2249,7 +2249,7 @@ In case of multiple `$removeheader` rules matching a single request, we will app :::caution Restrictions -This type of rules can be used [**only in trusted filters**](#trusted-filters). +This type of rules can only be used [**in trusted filters**](#trusted-filters). 1. In order to avoid compromising the security `$removeheader` cannot remove headers from the list below: - `access-control-allow-origin` @@ -2321,8 +2321,6 @@ Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuar Rules with `$removeparam` modifier are intended to strip query parameters from requests' URLs. Please note that such rules are only applied to `GET`, `HEAD`, `OPTIONS`, and sometimes `POST` requests. -`$removeparam` rules that do not have any [content type modifiers](#content-type-modifiers) will match only requests where content type is `document`. - **Syntax** **Basic syntax** @@ -2488,8 +2486,9 @@ With these rules, specified UTM parameters will be removed from any request save :::caution Restrictions -- Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). -- `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. Rules with the `$removeparam` modifier can only be used [**in trusted filters**](#trusted-filters). +1. `$removeparam` rules are compatible with [basic modifiers](#basic-rules-basic-modifiers), [content-type modifiers](#content-type-modifiers), and with the `$important` and `$app` modifiers. Rules with any other modifiers are considered invalid and will be discarded. +1. `$removeparam` rules without [content type modifiers](#content-type-modifiers) will only match requests where the content type is `document`. ::: @@ -2565,7 +2564,7 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Restrictions -Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$replace` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -2658,7 +2657,7 @@ the request to `https://example.com/firstpath` will be blocked. :::caution Restrictions -Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). +Rules with the `$urltransform` modifier can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4030,7 +4029,7 @@ We recommend to use this kind of exceptions only if it is not possible to change :::caution Restrictions -JavaScript rules can be used [**only in trusted filters**](#trusted-filters). +JavaScript rules can only be used [**in trusted filters**](#trusted-filters). ::: @@ -4149,7 +4148,7 @@ Trusted scriptlets are not compatible with other ad blockers except AdGuard. :::caution Restrictions -Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). +Trusted scriptlets rules can only be used [**in trusted filters**](#trusted-filters). ::: From 91b68eba5994f92a8ac728c8cd3ca7f0d48153f5 Mon Sep 17 00:00:00 2001 From: SeverAnna <141145497+SeverAnna@users.noreply.github.com> Date: Thu, 10 Oct 2024 13:49:56 +0300 Subject: [PATCH 2/2] Update filter-policy.md --- .../current/general/ad-filtering/filter-policy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index bc0244e767f..9b449d8ef19 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -48,7 +48,7 @@ AdGuard-Filter zum Blockieren von Werbung umfassen: - **Der Basisfilter** blockiert Werbung auf englischsprachigen Websites und solchen, für die es keinen eigenen Filter gibt. Er enthält auch allgemeine Filterregeln, die für alle Websites unabhängig von der Sprache gelten - **Filter gegen mobile Werbung** blockiert Werbung auf mobilen Versionen von Websites und in mobilen Apps. Es gibt keine Unterteilung nach Sprachen - **Sprachspezifische Filter** folgen der gleichen Politik wie der **Basisfilter**, sind aber auf Websites in bestimmten Sprachen beschränkt -- Quick-Fixes-Filter zur schnellen Behebung kritischer Probleme bei der Filterung von Inhalten auf beliebten Websites ohne Aktualisierung der MV3-Erweiterung. +- Quick-Fixes-Filter zur schnellen Behebung kritischer Probleme bei der Filterung von Inhalten auf beliebten Websites ohne Aktualisierung der MV3-Erweiterung. Das Ziel von Werbeblockern ist es, alle Arten von Werbung auf Websites, in Apps und auf bestimmten Geräten, die Werbung aus dem Internet laden können, zu blockieren: