[tor-commits] [translation/communitytpo-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-contentspot

translation at torproject.org translation at torproject.org
Sun May 23 15:45:13 UTC 2021


commit 5fa8fb12848bf15c798b2eba1a28cccae85e11c9
Author: Translation commit bot <translation at torproject.org>
Date:   Sun May 23 15:45:12 2021 +0000

    https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-contentspot
---
 contents+tr.po | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/contents+tr.po b/contents+tr.po
index bcfae994dc..6d731afdcc 100644
--- a/contents+tr.po
+++ b/contents+tr.po
@@ -9667,12 +9667,15 @@ msgid ""
 "challenges-opportunities), and how we're working on onion services usability"
 " and adoption."
 msgstr ""
+"[Tor Browser güvenlik beklentileri](https://blog.torproject.org/tor-brower-"
+"onion-services-challenges-opportunities) ve onion hizmetlerinin "
+"kullanılabilirliği ile benimsenmesi için nasıl çalıştığımızı yazdık."
 
 #: https//community.torproject.org/onion-services/advanced/https/
 #: (content/onion-services/advanced/https/contents+en.lrpage.body)
 msgid ""
 "There are some alternatives you might want to try to address this problem:"
-msgstr ""
+msgstr "Bu sorunu çözmeye için kullanabileceğiniz bazı alternatifler var:"
 
 #: https//community.torproject.org/onion-services/advanced/https/
 #: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9680,6 +9683,9 @@ msgid ""
 "* To avoid using an HTTPS certificate for your onion, the easiest answer is "
 "to write all your content so it uses only relative links."
 msgstr ""
+"* Onion hizmetiniz için bir HTTPS sertifikası kullanmaktan kaçınmanın en "
+"kolay yolu, tüm içeriğinizi yazmanızdır. Böylece yalnız göreli bağlantılar "
+"kullanılır."
 
 #: https//community.torproject.org/onion-services/advanced/https/
 #: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9687,6 +9693,8 @@ msgid ""
 "Then the content will work smoothly no matter what website name it's being "
 "served from."
 msgstr ""
+"Böylece içerik, hangi web sitesinden sunulduğuna bakılmadan sorunsuz "
+"çalışır."
 
 #: https//community.torproject.org/onion-services/advanced/https/
 #: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9694,6 +9702,8 @@ msgid ""
 "* Another option is to use webserver rules to rewrite absolute links on the "
 "fly."
 msgstr ""
+"* Diğer bir seçenek, mutlak bağlantıları anında yeniden yazmak için web "
+"sunucusu kurallarını kullanmaktır."
 
 #: https//community.torproject.org/onion-services/advanced/https/
 #: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9701,6 +9711,8 @@ msgid ""
 "* Or use a reverse proxy in the middle or more specifically EOTK with an "
 "HTTPS certificate."
 msgstr ""
+"* Ya da ortada bir ters vekil sunucu veya daha spesifik olarak HTTPS "
+"sertifikalı EOTK kullanabilirsiniz."
 
 #: https//community.torproject.org/onion-services/advanced/https/
 #: (content/onion-services/advanced/https/contents+en.lrpage.body)



More information about the tor-commits mailing list