From 38ae181f7f8e9ba91b326a4fc43bd431add7afd4 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Thu, 29 Aug 2019 15:24:17 +0200 Subject: docs --- locale/ru/LC_MESSAGES/messages.po | 400 +++++++++++++++++++++++++++++--------- 1 file changed, 303 insertions(+), 97 deletions(-) (limited to 'locale/ru') diff --git a/locale/ru/LC_MESSAGES/messages.po b/locale/ru/LC_MESSAGES/messages.po index 1fad3bf3..aca8ea91 100644 --- a/locale/ru/LC_MESSAGES/messages.po +++ b/locale/ru/LC_MESSAGES/messages.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: PROJECT VERSION\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" -"POT-Creation-Date: 2019-08-11 11:49+0200\n" +"POT-Creation-Date: 2019-08-29 15:18+0200\n" "PO-Revision-Date: 2017-12-29 11:14+0100\n" "Last-Translator: FULL NAME \n" "Language-Team: ru \n" @@ -324,98 +324,72 @@ msgid "" "circulation during the period of the compromise." msgstr "" -#: docs.html.j2:22 +#: docs.html.j2:37 msgid "Tutorial and manual for operating a merchant" msgstr "" -#: docs.html.j2:23 +#: docs.html.j2:38 msgid "Also available as" msgstr "" -#: docs.html.j2:29 -msgid "Merchant API Tutorial (Command Line)" +#: docs.html.j2:44 +msgid "Merchant API Tutorial" msgstr "" -#: docs.html.j2:31 +#: docs.html.j2:46 msgid "" -"Tutorial for processing Taler payments using the merchant backend's API, " -"with command line (and cURL) examples. Also available as" -msgstr "" - -#: docs.html.j2:42 -msgid "" -"Tutorial for processing Taler payments using the merchant backend's API, " -"with Python 3 examples. Also available as" +"Tutorial for processing Taler payments using the merchant backend API. Also " +"available as" msgstr "" -#: docs.html.j2:58 +#: docs.html.j2:57 msgid "Operator's manual for the GNU Taler exchange. Also available as" msgstr "" -#: docs.html.j2:67 +#: docs.html.j2:66 msgid "Bank Integration" msgstr "" -#: docs.html.j2:69 +#: docs.html.j2:68 msgid "" "Manual for tightly integrating Taler with banking applications. Also " "available as" msgstr "" -#: docs.html.j2:78 +#: docs.html.j2:83 msgid "Back office" msgstr "" -#: docs.html.j2:80 +#: docs.html.j2:85 msgid "Manual to run the back-office Web application. Also available as" msgstr "" -#: docs.html.j2:105 +#: docs.html.j2:110 msgid "Reference for the HTTP-based API for Taler components." msgstr "" -#: docs.html.j2:113 +#: docs.html.j2:118 msgid "" "Description of our taler.net setup and how to contribute. Also available as" msgstr "" -#: docs.html.j2:139 +#: docs.html.j2:144 msgid "The official GNU Taler mailing list." msgstr "" -#: docs.html.j2:147 +#: docs.html.j2:152 msgid "Our IRC channel is #taler on freenode." msgstr "" -#: docs.html.j2:155 +#: docs.html.j2:160 msgid "Our bug tracker for bugs and feature request." msgstr "" -#: docs.html.j2:177 -msgid "Code (Exchange)" -msgstr "" - -#: docs.html.j2:179 -msgid "Documented source code (with Doxygen) for the exchange." -msgstr "" - -#: docs.html.j2:185 -msgid "Code (Merchant backend)" -msgstr "" - -#: docs.html.j2:187 -msgid "Documented source code (with Doxygen) for the merchant." -msgstr "" - -#: docs.html.j2:195 -msgid "TBD: Documented source code (with TypeDoc) for the wallet." -msgstr "" - -#: docs.html.j2:201 +#: docs.html.j2:182 msgid "Git repositories" msgstr "" -#: docs.html.j2:203 +#: docs.html.j2:184 msgid "Git repositories for all of GNU Taler." msgstr "" @@ -629,53 +603,103 @@ msgid "" "feature that we are targeting for Taler 1.0. at this time

" msgstr "" -#: features.html.j2:41 +#: features.html.j2:15 +msgid "" +"GNU Taler is a privacy-preserving payment system. " +"Customers can stay anonymous, but merchants can not hide their income " +"through payments with GNU Taler. This helps to avoid tax " +"evasion and money laundering." +msgstr "" + +#: features.html.j2:23 +msgid "" +"The primary use case of GNU Taler is payments; it " +"is not meant as a store of value. Payments are " +"always backed by an existing currency." +msgstr "" + +#: features.html.j2:30 +msgid "" +"Payment are made after exchanging existing money " +"into electronic money with the help of an Exchange service, that " +"is, a payment service provider for Taler." +msgstr "" + +#: features.html.j2:37 +msgid "" +"When making a payment, customers only need a charged wallet. A merchant can " +"accept payments without making their customers register on the merchant's Website." +msgstr "" + +#: features.html.j2:44 +msgid "" +"GNU Taler is immune against many types of fraud, " +"such as phishing of credit card information or chargeback fraud. In case of " +"loss or theft, only the limited amount of money left in the wallet might be " +"gone." +msgstr "" + +#: features.html.j2:60 msgid "Paying with Taler" msgstr "" -#: features.html.j2:42 +#: features.html.j2:62 +msgid "" +"To pay with Taler, customers install an electronic wallet on their device. " +"Before the first payment, the desired currency must be added to the wallet's " +"balance by some other means of payment." +msgstr "" + +#: features.html.j2:70 msgid "" -"

To pay with Taler, customers install an electronic wallet on their " -"device. Before the first payment, the desired currency must be added to the " -"wallet's balance by some other means of payment.

Once the wallet is " -"charged, payments on websites take only one click, are never falsely " -"rejected by fraud detection and do not pose any risk of phishing or identity " -"theft.

Try it yourself with the " -"interactive demo!

" +"Once the wallet is charged, payments on websites take only one click, are " +"never falsely rejected by fraud detection and do not pose any risk of " +"phishing or identity theft." msgstr "" -#: features.html.j2:54 +#: features.html.j2:77 +msgid "Try it yourself with the interactive demo!" +msgstr "" + +#: features.html.j2:83 msgid "Receiving payments with Taler" msgstr "" -#: features.html.j2:55 +#: features.html.j2:85 msgid "" -"

To receive Taler payments, a merchant needs a bank account in the desired " +"To receive Taler payments, a merchant needs a bank account in the desired " "currency. We provide supporting software in various programming languages to " "make the integration painless. The merchant's backend for Taler transaction " "processing can run on the merchant's premises or be hosted by a third party." -"

Merchant integration is simple, and customers can pay for products " -"without even having to register an account.

See how merchant integration works in our developer " -"documentation!

" msgstr "" -#: features.html.j2:74 +#: features.html.j2:94 +msgid "" +"Merchant integration is simple, and customers can pay for products without " +"even having to register an account." +msgstr "" + +#: features.html.j2:99 +msgid "See how merchant integration works in our developer documentation!" +msgstr "" + +#: features.html.j2:113 msgid "Practical" msgstr "" -#: features.html.j2:77 +#: features.html.j2:116 msgid "" "Taler is easy to integrate with existing Web applications. Payments are " "cryptographically secured and are confirmed within milliseconds with " "extremely low transaction costs." msgstr "" -#: features.html.j2:87 +#: features.html.j2:126 msgid "Stable" msgstr "" -#: features.html.j2:90 +#: features.html.j2:129 msgid "" "Taler does not introduce a new currency. Taler uses a digital wallet storing " "coins and payment service providers with escrow accounts in existing " @@ -683,44 +707,44 @@ msgid "" "currencies, such as US Dollars, Euros or even Bitcoins." msgstr "" -#: features.html.j2:101 governments.html.j2:58 merchants.html.j2:41 +#: features.html.j2:140 governments.html.j2:58 merchants.html.j2:41 msgid "Secure" msgstr "" -#: features.html.j2:104 +#: features.html.j2:143 msgid "" "By design Taler does not suffer from many classes of security problems such " "as phishing or counterfeit. Thanks to its security features, Taler never " "rejects a legitimate customer due to a fraud-detection false positive." msgstr "" -#: features.html.j2:116 governments.html.j2:25 +#: features.html.j2:155 governments.html.j2:25 msgid "Taxable" msgstr "" -#: features.html.j2:119 +#: features.html.j2:158 msgid "" "When using Taler, merchant's revenue is transparent for tax collection " "authorities. Unlike cash and most digital currencies, Taler helps prevent " "black markets. Taler is not suitable for illegal activities." msgstr "" -#: features.html.j2:129 +#: features.html.j2:168 msgid "Private" msgstr "" -#: features.html.j2:131 +#: features.html.j2:170 msgid "" "When you pay with Taler, your identity does not have to be revealed. Just " "like payments in cash, nobody else can track how you spent your electronic " "money. However, you obtain a legally valid proof of payment." msgstr "" -#: features.html.j2:142 governments.html.j2:88 +#: features.html.j2:181 governments.html.j2:88 msgid "Libre" msgstr "" -#: features.html.j2:145 +#: features.html.j2:184 msgid "" "Taler provides protocols and reference implementations that in principle " "enables anybody to run their own payment infrastructure, be it individuals, " @@ -1276,18 +1300,26 @@ msgstr "" #: gsoc-codeless.html.j2:33 msgid "" -"Merchant has the flexibility to add two types of inventory as follows:
    " -"
  • The merchant can upload digital inventory (like a PDF or HTML page) via " -"the codeless payments frontend and the user can then purchase it and view " -"the version hosted by the codeless payment frontend.
  • The merchant " -"can add any physical inventory available in his stocks. While adding these " -"inventory, the seller is prompted to add minimum quantity of product that is " -"required to be maintained in the stock. Whenever the stocks run below this " -"limit the seller would be notified (currently this feature has not been " -"added but soon email notification would be added).
" +"A merchant has the flexibility to add two types of inventory as follows:" +msgstr "" + +#: gsoc-codeless.html.j2:38 +msgid "" +"The merchant can upload digital inventory (like a PDF or HTML page) via the " +"codeless payments frontend and the user can then purchase it and view the " +"version hosted by the codeless payment frontend." msgstr "" -#: gsoc-codeless.html.j2:42 +#: gsoc-codeless.html.j2:43 +msgid "" +"The merchant can add any physical inventory available in his stocks. While " +"adding these inventory, the seller is prompted to add minimum quantity of " +"product that is required to be maintained in the stock. Whenever the stocks " +"run below this limit the seller would be notified (currently this feature " +"has not been added but soon email notification would be added)." +msgstr "" + +#: gsoc-codeless.html.j2:50 msgid "" "The buyers will access the seller's frontend where the code for the 'Buy " "Now' button is present. When this button is triggered, they are redirected " @@ -1297,7 +1329,7 @@ msgid "" "frontend." msgstr "" -#: gsoc-codeless.html.j2:47 +#: gsoc-codeless.html.j2:55 msgid "" "The other use case of the codeless payment backend is to handle the event " "when the 'Buy Now' button is triggered on the seller's frontend. To perform " @@ -1305,31 +1337,31 @@ msgid "" "successful payment, the users are redirected to the fulfilment page." msgstr "" -#: gsoc-codeless.html.j2:53 +#: gsoc-codeless.html.j2:61 msgid "Dynamic Merchant Instance" msgstr "" -#: gsoc-codeless.html.j2:57 +#: gsoc-codeless.html.j2:65 msgid "Use Case Diagram" msgstr "" -#: gsoc-codeless.html.j2:63 +#: gsoc-codeless.html.j2:71 msgid "Link to the contributions made" msgstr "" -#: gsoc-codeless.html.j2:66 +#: gsoc-codeless.html.j2:74 msgid "Codeless Payment Backend" msgstr "" -#: gsoc-codeless.html.j2:68 +#: gsoc-codeless.html.j2:76 msgid "Documentation to dynamically manage Merchant Instances" msgstr "" -#: gsoc-codeless.html.j2:77 +#: gsoc-codeless.html.j2:85 msgid "Future Work" msgstr "" -#: gsoc-codeless.html.j2:79 +#: gsoc-codeless.html.j2:87 msgid "" "The backend of codeless payment is very robust and can be easily extended as " "per the requirements. It is adaptive to add new features to this framework. " @@ -1338,7 +1370,7 @@ msgid "" "of future work is as follows:" msgstr "" -#: gsoc-codeless.html.j2:84 +#: gsoc-codeless.html.j2:92 msgid "" "To send email notification to the merchant when the stocks run below a " "certain limit. The minimum quantity required to be maintained in the stocks " @@ -1346,7 +1378,7 @@ msgid "" "notification system is designed." msgstr "" -#: gsoc-codeless.html.j2:90 +#: gsoc-codeless.html.j2:98 msgid "" "To add API access to the merchant backend via the codeless payment service. " "Basically, it would be used as a hosting platform for multiple merchants. " @@ -1358,7 +1390,7 @@ msgid "" "codeless payments service." msgstr "" -#: gsoc-codeless.html.j2:96 +#: gsoc-codeless.html.j2:104 msgid "" "Mapping every seller account to a separate merchant backend instance. This " "is not required for a simple version of codeless payments, but as soon as " @@ -1366,7 +1398,7 @@ msgid "" "service then can also double as a hosting service for merchants." msgstr "" -#: gsoc-codeless.html.j2:102 +#: gsoc-codeless.html.j2:110 msgid "" "To add various analytics for the merchant. Various analysis could be " "performed on the orders placed for the respective merchant. Some of the " @@ -1376,7 +1408,7 @@ msgid "" "research have to be done before proceeding to the implementation." msgstr "" -#: gsoc-codeless.html.j2:114 +#: gsoc-codeless.html.j2:122 msgid "Screenshots" msgstr "" @@ -1635,6 +1667,180 @@ msgstr "" msgid "GNU Taler in the Press" msgstr "" +#: principles.html.j2:22 +msgid "GNU Taler: Design Principles" +msgstr "" + +#: principles.html.j2:29 +msgid "" +"When designing GNU Taler, we had the following design principles in mind:" +msgstr "" + +#: principles.html.j2:36 +msgid "1. Free Software implementation" +msgstr "" + +#: principles.html.j2:40 +msgid "" +"... in the are of computing, freedom means not using proprietary software" +msgstr "" + +#: principles.html.j2:42 +msgid "" +"GNU Taler must be Free Software. For merchants, our Free Software reference " +"implementation prevents vendor lock-in. As the software of the payment " +"provider itself is free, countries can deploy the payment system without " +"compromising sovereignty." +msgstr "" + +#: principles.html.j2:51 +msgid "" +"Customers benefit from Free Software as the wallet software can be made to " +"run on a variety of platforms, and the absence of user-hostile features such " +"as tracking or telemetry can easily be assured." +msgstr "" + +#: principles.html.j2:63 +msgid "2. Protect the privacy of buyers" +msgstr "" + +#: principles.html.j2:68 +msgid "You deserve some privacy" +msgstr "" + +#: principles.html.j2:70 +msgid "" +"Privacy should be guaranteed via technical measures, as opposed to mere " +"policies. Especially with micropayments for online content, a disproportion- " +"ate amount of rather private data about buyers would be revealed, if the " +"payment system does not have privacy protections." +msgstr "" + +#: principles.html.j2:78 +msgid "" +"In legislations with data protection regulations (such as the recently " +"introduced GDPR in Europe), merchants benefit from this as well, as no data " +"breach of customers can happen if this information is, by design, not " +"collected in the first place. Obviously some private data, such as the " +"shipping address for a physical delivery, must still be collected according " +"to business needs." +msgstr "" + +#: principles.html.j2:92 +msgid "" +"3. Enable the state to tax income and crack down on illegal business " +"activities" +msgstr "" + +#: principles.html.j2:97 +msgid "Money laundering" +msgstr "" + +#: principles.html.j2:99 +msgid "" +"As a payment system must still be legal to operate and use, it must comply " +"with these requirements. Furthermore, we consider levying of taxes as " +"beneficial to society." +msgstr "" + +#: principles.html.j2:110 +msgid "4. Prevent payment fraud" +msgstr "" + +#: principles.html.j2:115 +msgid "Phishing attack" +msgstr "" + +#: principles.html.j2:117 +msgid "" +"This imposes requirements on the security of the system, as well as on the " +"general design, as payment fraud can also happen through misleading user " +"interface design or the lack of cryptographic evidence for certain processes." +msgstr "" + +#: principles.html.j2:128 +msgid "5. Only disclose the minimal amount of information necessary" +msgstr "" + +#: principles.html.j2:132 +msgid "" +"Privacy by design, privacy by default, General Data Protection Regulation " +"(GDPR) compliant" +msgstr "" + +#: principles.html.j2:134 +msgid "" +"The reason behind this goal is similar to (2). The privacy of buyers is " +"given priority, but other parties such as merchants still benefit from it, " +"for example, by keeping details about the merchant’s financials hidden from " +"competitors." +msgstr "" + +#: principles.html.j2:144 +msgid "6. Be usable" +msgstr "" + +#: principles.html.j2:148 +msgid "Buy with one click" +msgstr "" + +#: principles.html.j2:150 +msgid "" +"Specifically it must be usable for non-expert customers. Usability also " +"applies to the integration with merchants, and informs choices about the " +"architecture, such as encapsulating procedures that require cryptographic " +"operations into an isolated component with a simple API." +msgstr "" + +#: principles.html.j2:162 +msgid "7. Be efficient" +msgstr "" + +#: principles.html.j2:166 +msgid "Energy efficiency" +msgstr "" + +#: principles.html.j2:168 +msgid "" +"Approaches such as proof-of-work are ruled out by this requirement. " +"Efficiency is necessary for GNU Taler to be used for micropayments." +msgstr "" + +#: principles.html.j2:177 +msgid "8. Fault-tolerant design" +msgstr "" + +#: principles.html.j2:181 +msgid "Life Safers" +msgstr "" + +#: principles.html.j2:183 +msgid "" +"Taler should tolerate failure of individual components and systems, " +"including malicious operators compromising core secrets. This manifests in " +"architectural choices such as the isolation of certain components, and " +"auditing procedures." +msgstr "" + +#: principles.html.j2:195 +msgid "9. Foster competition" +msgstr "" + +#: principles.html.j2:199 +msgid "A competitive market" +msgstr "" + +#: principles.html.j2:201 +msgid "" +"It must be relatively easy for competitors to join the systems. While the " +"barriers for this in traditional financial systems are rather high, the " +"technical burden for new competitors to join must be minimized. Another " +"design choice that supports this is to split the whole system into smaller " +"components that can be operated, developed and improved upon independently, " +"instead of having one completely monolithic system." +msgstr "" + #: schemafuzz.html.j2:6 msgid "SchemaFuzz" msgstr "" -- cgit v1.2.3