Skip to content

Commit

Permalink
Doc: Update po files
Browse files Browse the repository at this point in the history
  • Loading branch information
masaori335 committed Jan 14, 2016
1 parent 3ede19c commit 5146724
Show file tree
Hide file tree
Showing 30 changed files with 12,298 additions and 11,183 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -9,37 +9,29 @@ msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 6.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-01-02 21:32+0000\n"
"POT-Creation-Date: 2016-01-15 00:13+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.1.1\n"
"Generated-By: Babel 2.2.0\n"

#: ../../admin-guide/configuration/session-protocol.en.rst:54
msgid ""
"Each proxy port can be configured in :ts:cv:`proxy.config.http."
"server_ports` to support a subset of these session protocols. For TLS "
"enabled connections this configuration controls which protocols are offered "
"by NPN. Protocol sniffing is use for non-TLS proxy ports to determine which "
"protocol is being used by the client. If the detected protocol is not "
"supported for that proxy port the connection is dropped."
msgstr ""
"それぞれのプロキシーポートでサポートするセッションプロトコルは :ts:cv:"
"`proxy.config.http.server_ports` で設定可能です。TLS が有効な接続では、この"
"設定は NPN でどのプロトコルを提示するかを制御します。プロトコルスニッフィン"
"グは非 TLS のプロキシーポートでクライアントによってどのプロトコルが使われて"
"いるかを判定するためのものです。もし検出されたプロトコルがそのプロキシーポー"
"トで対応されていない場合、接続は破棄されます。"

#: ../../admin-guide/configuration/session-protocol.en.rst:4
#: ../../../admin-guide/configuration/session-protocol.en.rst:23
msgid "Session Protocol"
msgstr "セッションプロトコル"

#: ../../admin-guide/configuration/session-protocol.en.rst:29
#: ../../../admin-guide/configuration/session-protocol.en.rst:25
msgid ""
"|TS| supports some session level protocols in place of or on top of HTTP. "
"These can be provided by a plugin (see :ref:`developer-plugins-new-protocol-"
"plugins`) or be one that is supported directly by |TS|. The `SPDY <http://"
"www.chromium.org/spdy>`_ protocol is the only one currently supported, but "
"it is planned to support HTTP 2 when that is finalized."
msgstr ""

#: ../../../admin-guide/configuration/session-protocol.en.rst:31
msgid ""
"Session protocols are specified by explicit names, based on the `NPN "
"<https://technotes.googlecode.com/git/nextprotoneg.html>`_ names. The core "
Expand All @@ -49,16 +41,39 @@ msgstr ""
"nextprotoneg.html>`_ での名称を元にした明示的な名称によって指定されます。直"
"接サポートされている名称は下記のとおりです。"

#: ../../admin-guide/configuration/session-protocol.en.rst:23
msgid ""
"Traffic Server supports some session level protocols in place of, or on top "
"of HTTP. These can be provided by a plugin (see :ref:`new-protocol-"
"plugins`) or be one that is supported directly by Traffic Server. The `SPDY "
"<http://www.chromium.org/spdy>`_ protocol is the only one currently "
"supported, but it is planned to support HTTP 2 when that is finalized."
msgstr ""
#: ../../../admin-guide/configuration/session-protocol.en.rst:35
msgid "``http/0.9``"
msgstr "``http/0.9``"

#: ../../admin-guide/configuration/session-protocol.en.rst:42
#: ../../../admin-guide/configuration/session-protocol.en.rst:36
msgid "``http/1.0``"
msgstr "``http/1.0``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:37
msgid "``http/1.1``"
msgstr "``http/1.1``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:38
msgid "``http/2``"
msgstr "``http/2``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:39
msgid "``spdy/1``"
msgstr "``spdy/1``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:40
msgid "``spdy/2``"
msgstr "``spdy/2``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:41
msgid "``spdy/3``"
msgstr "``spdy/3``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:42
msgid "``spdy/3.1``"
msgstr "``spdy/3.1``"

#: ../../../admin-guide/configuration/session-protocol.en.rst:44
msgid ""
"The ``http/2`` value is not currently functional, but is included for "
"future use. Both ``spdy/1`` and ``spdy/2`` are obsolete, but are include "
Expand All @@ -68,7 +83,7 @@ msgstr ""
"``spdy/1`` と ``spdy/2`` はどちらも古いですが、完全性のために含められていま"
"す。"

#: ../../admin-guide/configuration/session-protocol.en.rst:46
#: ../../../admin-guide/configuration/session-protocol.en.rst:48
msgid ""
"The session protocols supported on a proxy port are a subset of these "
"values. For convenience some pseudo-values are defined in terms of these "
Expand All @@ -78,47 +93,31 @@ msgstr ""
"トになります。利便性のためにいくつかの擬似的な値が下記の基本的なプロトコルと"
"して定義されています。"

#: ../../admin-guide/configuration/session-protocol.en.rst:33
msgid "``http/0.9``"
msgstr "``http/0.9``"

#: ../../admin-guide/configuration/session-protocol.en.rst:34
msgid "``http/1.0``"
msgstr "``http/1.0``"

#: ../../admin-guide/configuration/session-protocol.en.rst:35
msgid "``http/1.1``"
msgstr "``http/1.1``"

#: ../../admin-guide/configuration/session-protocol.en.rst:36
msgid "``http/2``"
msgstr "``http/2``"

#: ../../admin-guide/configuration/session-protocol.en.rst:52
msgid "``http2`` means ``http/2``"
msgstr "``http2`` は ``http/2`` を意味します。"

#: ../../admin-guide/configuration/session-protocol.en.rst:50
#: ../../../admin-guide/configuration/session-protocol.en.rst:52
msgid "``http`` means ``http/0.9``, ``http/1.0``, and ``http/1.1``"
msgstr ""
"``http`` は ``http/0.9`` 、``http/1.0`` 、 ``http/1.1`` を意味します。"

#: ../../admin-guide/configuration/session-protocol.en.rst:37
msgid "``spdy/1``"
msgstr "``spdy/1``"

#: ../../admin-guide/configuration/session-protocol.en.rst:38
msgid "``spdy/2``"
msgstr "``spdy/2``"

#: ../../admin-guide/configuration/session-protocol.en.rst:40
msgid "``spdy/3.1``"
msgstr "``spdy/3.1``"

#: ../../admin-guide/configuration/session-protocol.en.rst:39
msgid "``spdy/3``"
msgstr "``spdy/3``"

#: ../../admin-guide/configuration/session-protocol.en.rst:51
#: ../../../admin-guide/configuration/session-protocol.en.rst:53
msgid "``spdy`` means ``spdy/3`` and ``spdy/3.1``."
msgstr "``spdy`` は ``spdy/3`` と ``spdy/3.1`` を意味します。"

#: ../../../admin-guide/configuration/session-protocol.en.rst:54
msgid "``http2`` means ``http/2``"
msgstr "``http2`` は ``http/2`` を意味します。"

#: ../../../admin-guide/configuration/session-protocol.en.rst:56
msgid ""
"Each proxy port can be configured in :ts:cv:`proxy.config.http."
"server_ports` to support a subset of these session protocols. For TLS "
"enabled connections this configuration controls which protocols are offered "
"by NPN. Protocol sniffing is use for non-TLS proxy ports to determine which "
"protocol is being used by the client. If the detected protocol is not "
"supported for that proxy port the connection is dropped."
msgstr ""
"それぞれのプロキシーポートでサポートするセッションプロトコルは :ts:cv:"
"`proxy.config.http.server_ports` で設定可能です。TLS が有効な接続では、この"
"設定は NPN でどのプロトコルを提示するかを制御します。プロトコルスニッフィン"
"グは非 TLS のプロキシーポートでクライアントによってどのプロトコルが使われて"
"いるかを判定するためのものです。もし検出されたプロトコルがそのプロキシーポー"
"トで対応されていない場合、接続は破棄されます。"
Original file line number Diff line number Diff line change
@@ -0,0 +1,167 @@
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2015, dev@trafficserver.apache.org
# This file is distributed under the same license as the Apache Traffic
# Server package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2016.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 6.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-01-15 00:13+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.2.0\n"

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:4
msgid "Transparent Proxying"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:32
msgid ""
"Transparent Proxying is the ability of a proxy (such as ATS) to intercept "
"connections between clients and servers without being visible."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:35
msgid ""
"The general network structure that will be used in this documentation is "
"shown in the following figure."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:42
msgid "ATS basic traffic flow of Transparent Proxy"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:44
msgid ""
"There must be a gateway device through which all network traffic passes "
"from the client to the Internet (or external cloud). The gateway is "
"responsible for effectively splicing ATS in to selected streams of that "
"traffic. Each traffic stream is split in two, with ATS terminating both "
"sides. That is, stream green-1, red-2, is split in to the green connection "
"and the red connection. Note that ATS may or may not be on the gateway "
"system, the redirected traffic can flow over other network infrastructure."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:53
msgid ""
"Because ATS uses two connections, transparency can be set independently on "
"the client and origin server (Internet / external cloud) side. We will "
"define what is generally called \"transparent proxy\" as two aspects, "
"*inbound transparency* and *outbound transparency*."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:58
msgid ""
"Inbound transparency is a proxy that is transparent to connections that are "
"inbound to the proxy, i.e. a connection initiated by a client which "
"connects to the proxy (green-1). Similarly, outbound transparency is a "
"proxy that is transparent to connections that are outbound from the proxy, "
"i.e. a connection initiated by the proxy to an origin server (red-2)."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:65
msgid ""
"In most situations these two types of transparency are combined, but that "
"is not required. Traffic Server supports transparency independently on the "
"two sides."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:71
msgid ""
"It is critical to note that any transparency requires specialized routing "
"and cannot be done solely by configuring ATS. ATS transparency also "
"requires support from the Linux kernel and therefore currently only works "
"on sufficiently recent Linux kernels that support the following features:"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:77
msgid "TPROXY"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:78
msgid "POSIX capabilities"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:80
msgid ""
"In addition the specialized routing will require using ``iptables`` and in "
"some cases ``ebtables``."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:83
msgid ""
"Standard build procedures should work for transparency support but if not "
"consult these :ref:`more detailed instructions <building-ats-for-"
"transparency>`."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:86
msgid ""
"Transparency is configured per server port, not globally. This is done via "
"the configuration values :ts:cv:`proxy.config.http.server_ports`. In "
"addition, :ts:cv:`proxy.config.reverse_proxy.enabled` must be enabled if "
"the client side is transparent. That should be fixed in a future patch."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:95
msgid ""
"In the first case use the attribute character (replacing the default 'X')"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:98
msgid "**Attribute** **Transparency Style** **Reverse Proxy**"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:101
msgid "="
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:101
msgid "Full transparency: either"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:104
msgid ">"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:104
msgid "Inbound (client) transparency: enabled"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:107
msgid "<"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:107
msgid "Outbound (origin server) transparency: either"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:109
msgid ""
"In the outbound transparent case clients must connect directly to ATS "
"either through an explicit proxy mechanism or by advertising the IP address "
"of the ATS server via DNS as the origin server address."
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:113
msgid "Some tested scenarios --"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:115
msgid ":doc:`transparent-proxy/bridge.en`"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:116
msgid ":doc:`transparent-proxy/router-inline.en`"
msgstr ""

#: ../../../admin-guide/configuration/transparent-proxy.en.rst:117
msgid ":doc:`transparent-proxy/wccp-configuration.en`"
msgstr ""

0 comments on commit 5146724

Please sign in to comment.