You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficserver.apache.org by so...@apache.org on 2014/02/27 01:08:00 UTC
[02/58] [abbrv] Doc: Clean up po files
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.po b/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.po
index c52ccb3..b46e391 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -19,15 +19,15 @@ msgstr ""
msgid ""
"The buffered null transform, ``bnull-transform.c``, reads the response "
"content into a buffer and then writes the full buffer out to the client. "
-"Many examples of transformations, such as compression, require you to gather"
-" the full response content in order to perform the transformation."
+"Many examples of transformations, such as compression, require you to "
+"gather the full response content in order to perform the transformation."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:26
msgid ""
"The buffered null transform uses a state variable to keep track of when it "
-"is (a) reading data into the buffer and (b) writing the data from the buffer"
-" to the downstream vconnection."
+"is (a) reading data into the buffer and (b) writing the data from the "
+"buffer to the downstream vconnection."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:30
@@ -51,13 +51,13 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:57
msgid ""
-"The default behavior for transformations is to cache the transformed content"
-" (if desired, you also can tell Traffic Server to cache untransformed "
-"content). Therefore, only responses received directly from an origin server "
-"need to be transformed. Objects served from the cache are already "
-"transformed. To determine whether the response is from the origin server, "
-"the routine transformable checks the response header for the \"200 OK\" "
-"server response."
+"The default behavior for transformations is to cache the transformed "
+"content (if desired, you also can tell Traffic Server to cache "
+"untransformed content). Therefore, only responses received directly from an "
+"origin server need to be transformed. Objects served from the cache are "
+"already transformed. To determine whether the response is from the origin "
+"server, the routine transformable checks the response header for the \"200 "
+"OK\" server response."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:84
@@ -87,8 +87,8 @@ msgid ""
"The ``handle_transform`` function examines the data parameter for the "
"continuation passed to it (the continuation passed to ``handle_transform`` "
"is the transformation vconnection). The data structure keeps track of two "
-"states: copying the data into the buffer (``STATE_BUFFER_DATA``) and writing"
-" the contents of the buffer to the output vconnection "
+"states: copying the data into the buffer (``STATE_BUFFER_DATA``) and "
+"writing the contents of the buffer to the output vconnection "
"(``STATE_OUTPUT_DATA``)."
msgstr ""
@@ -115,8 +115,8 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:134
msgid ""
"Modify the input VIO to tell it how much data has been read (increase the "
-"value of ``ndone``). See the ``handle_buffering`` function for the following"
-" code fragment:"
+"value of ``ndone``). See the ``handle_buffering`` function for the "
+"following code fragment:"
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:142
@@ -128,10 +128,10 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:155
msgid ""
-"The process of passing data through the transformation is illustrated in the"
-" following diagram. The transformation sends ``WRITE_READY`` events when it "
-"needs more data; when data is available, the upstream vconnection reenables "
-"the transformation with an ``IMMEDIATE`` event."
+"The process of passing data through the transformation is illustrated in "
+"the following diagram. The transformation sends ``WRITE_READY`` events when "
+"it needs more data; when data is available, the upstream vconnection "
+"reenables the transformation with an ``IMMEDIATE`` event."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:161
@@ -158,8 +158,8 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-buffered-null-transformation-plugin.en.rst:183
msgid ""
-"The upstream vconnection will probably shut down the write operation when it"
-" receives the ``WRITE_COMPLETE`` event. The handler function of the "
+"The upstream vconnection will probably shut down the write operation when "
+"it receives the ``WRITE_COMPLETE`` event. The handler function of the "
"transformation, ``bnull_transform``, receives an ``IMMEDIATE`` event and "
"calls the ``handle_transform`` function. This time, the state is "
"``STATE_OUTPUT_DATA``, so ``handle_transform`` calls ``handle_output``."
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.po b/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.po
index 7bc1a40..b38fead 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/http-transformation-plugin/sample-null-transformation-plugin.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -20,8 +20,8 @@ msgid ""
"This section provides a step-by-step description of what the null transform "
"plugin does, along with sections of code that apply. For context, you can "
"find each code snippet in the complete source code. Some of the error "
-"checking details are left out - to give the description a step-by-step flow,"
-" only the highlights of the transform are included."
+"checking details are left out - to give the description a step-by-step "
+"flow, only the highlights of the transform are included."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:28
@@ -44,13 +44,13 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:56
msgid ""
-"The default behavior for transformations is to cache the transformed content"
-" (you can also tell Traffic Server to cache untransformed content, if you "
-"want). Therefore, only responses received directly from an origin server "
-"need to be transformed. Objects served from cache are already transformed. "
-"To determine whether the response is from the origin server, the routine "
-"``transformable`` checks the response header for the \"200 OK\" server "
-"response."
+"The default behavior for transformations is to cache the transformed "
+"content (you can also tell Traffic Server to cache untransformed content, "
+"if you want). Therefore, only responses received directly from an origin "
+"server need to be transformed. Objects served from cache are already "
+"transformed. To determine whether the response is from the origin server, "
+"the routine ``transformable`` checks the response header for the \"200 OK\" "
+"server response."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:82
@@ -85,8 +85,8 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:119
msgid ""
-"Initiate a write to the output vconnection of the specified number of bytes."
-" When the write is initiated, the transformation expects to receive "
+"Initiate a write to the output vconnection of the specified number of "
+"bytes. When the write is initiated, the transformation expects to receive "
"``WRITE_READY``, ``WRITE_COMPLETE``, or ``ERROR`` events from the output "
"vconnection. See the ``handle_transform`` function for the following code "
"fragment:"
@@ -107,8 +107,8 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:147
msgid ""
"Modify the input VIO to tell it how much data has been read (increase the "
-"value of ``ndone``). See the ``handle_transform`` function for the following"
-" code fragment:"
+"value of ``ndone``). See the ``handle_transform`` function for the "
+"following code fragment:"
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:156
@@ -121,10 +121,10 @@ msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:173
msgid ""
-"The process of passing data through the transformation is illustrated in the"
-" following diagram. The downstream vconnections send ``WRITE_READY`` events "
-"when they need more data; when data is available, the upstream vconnections "
-"reenable the downstream vconnections. In this instance, the "
+"The process of passing data through the transformation is illustrated in "
+"the following diagram. The downstream vconnections send ``WRITE_READY`` "
+"events when they need more data; when data is available, the upstream "
+"vconnections reenable the downstream vconnections. In this instance, the "
"``TSVIOReenable`` function sends ``TS_EVENT_IMMEDIATE``."
msgstr ""
@@ -142,24 +142,24 @@ msgstr ""
msgid ""
"If the ``handle_transform`` function finds there is no more data to read, "
"then it sets ``nbytes`` to ``ndone`` on the output (downstream) VIO and "
-"wakes up the output vconnection with a reenable. It then triggers the end of"
-" the write operation from the upstream vconnection by sending the upstream "
-"vconnection a ``WRITE_COMPLETE`` event."
+"wakes up the output vconnection with a reenable. It then triggers the end "
+"of the write operation from the upstream vconnection by sending the "
+"upstream vconnection a ``WRITE_COMPLETE`` event."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:203
msgid ""
-"When the upstream vconnection receives the ``WRITE_COMPLETE`` event, it will"
-" probably shut down the write operation."
+"When the upstream vconnection receives the ``WRITE_COMPLETE`` event, it "
+"will probably shut down the write operation."
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:206
msgid ""
"Similarly, when the downstream vconnection has consumed all of the data, it "
"sends the transformation a ``WRITE_COMPLETE`` event. The transformation "
-"handles this event with a shut down (the transformation shuts down the write"
-" operation to the downstream vconnection). See the ``null_plugin`` function "
-"for the following code fragment:"
+"handles this event with a shut down (the transformation shuts down the "
+"write operation to the downstream vconnection). See the ``null_plugin`` "
+"function for the following code fragment:"
msgstr ""
#: ../../sdk/http-transformation-plugin/sample-null-transformation-plugin.en.rst:220
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/index.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/index.en.po b/doc/locale/ja/LC_MESSAGES/sdk/index.en.po
index 63b3cef..7825307 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/index.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/index.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -25,8 +25,8 @@ msgstr ""
#: ../../sdk/index.en.rst:27
msgid ""
-"The *Traffic Server Software Developers Kit* shows you how to create plugins"
-" using the Traffic Server SDK."
+"The *Traffic Server Software Developers Kit* shows you how to create "
+"plugins using the Traffic Server SDK."
msgstr ""
#: ../../sdk/index.en.rst:31
@@ -45,9 +45,9 @@ msgstr ""
#: ../../sdk/index.en.rst:41
msgid ""
"If you find any such issues, you may want to submit a `bug or a patch "
-"<https://issues.apache.org/jira/secure/CreateIssue!default.jspa?pid=12310963>`__."
-" Or find out how to `find bugs <>`__, `create useful bug reports <>`__ or "
-"`patches <>`__."
+"<https://issues.apache.org/jira/secure/CreateIssue!default.jspa?"
+"pid=12310963>`__. Or find out how to `find bugs <>`__, `create useful bug "
+"reports <>`__ or `patches <>`__."
msgstr ""
#: ../../sdk/index.en.rst:46
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po
index c10b5a0..9eda35d 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -29,12 +29,12 @@ msgstr ""
#: ../../sdk/io-guide.en.rst:39
msgid ""
-"To use a vconnection, a user must first get a handle to one. This is usually"
-" accomplished by having it handed to the user; the user may also simply "
-"issue a call that creates a vconnection (such as ``TSNetConnect)``. In the "
-"case of transform plugins, the plugin creates a transformation vconnection "
-"viav ``TSTransformCreate`` and then accesses the output vconnection using "
-"``TSTransformOutputVConnGet``."
+"To use a vconnection, a user must first get a handle to one. This is "
+"usually accomplished by having it handed to the user; the user may also "
+"simply issue a call that creates a vconnection (such as ``TSNetConnect)``. "
+"In the case of transform plugins, the plugin creates a transformation "
+"vconnection viav ``TSTransformCreate`` and then accesses the output "
+"vconnection using ``TSTransformOutputVConnGet``."
msgstr ""
#: ../../sdk/io-guide.en.rst:46
@@ -50,9 +50,9 @@ msgstr ""
msgid ""
"To issue a read or write operation, a user calls ``TSVConnRead`` or "
"``TSVConnWrite``. These two operations both return ``VIO (TSVIO)``. The VIO "
-"describes the operation being performed and how much progress has been made."
-" Transform plugins initiate output to the downstream vconnection by calling "
-"``TSVConnWrite``."
+"describes the operation being performed and how much progress has been "
+"made. Transform plugins initiate output to the downstream vconnection by "
+"calling ``TSVConnWrite``."
msgstr ""
#: ../../sdk/io-guide.en.rst:58
@@ -77,9 +77,9 @@ msgid ""
"common sense: if two write operations were performed on a single "
"vconnection, then the user would not be able to specify which should occur "
"first and the output would occur in an intermingled fashion. Note that both "
-"a read operation and a write operation can happen on a single vconnection at"
-" the same time; the restriction is for more than one operation of the same "
-"type."
+"a read operation and a write operation can happen on a single vconnection "
+"at the same time; the restriction is for more than one operation of the "
+"same type."
msgstr ""
#: ../../sdk/io-guide.en.rst:79
@@ -105,8 +105,8 @@ msgstr ""
#: ../../sdk/io-guide.en.rst:100
msgid ""
-"The ``connp`` is the vconnection the user is writing to and ``contp`` is the"
-" \"user\" - i.e., the continuation that ``connp`` calls back when it has "
+"The ``connp`` is the vconnection the user is writing to and ``contp`` is "
+"the \"user\" - i.e., the continuation that ``connp`` calls back when it has "
"emptied its buffer and is ready for more data."
msgstr ""
@@ -125,8 +125,8 @@ msgstr ""
msgid ""
"When a vconnection calls back its user to indicate that it wants more data "
"(or when some other condition has occurred), it issues a call to "
-"``TSContCall``. It passes the ``TSVIO`` describing the operation as the data"
-" parameter, and one of the values below as the event parameter."
+"``TSContCall``. It passes the ``TSVIO`` describing the operation as the "
+"data parameter, and one of the values below as the event parameter."
msgstr ""
#: ../../sdk/io-guide.en.rst:123
@@ -148,8 +148,8 @@ msgstr ""
msgid ""
"The vconnection has placed data in the buffer passed to an ``TSVConnRead`` "
"operation and it would like to do more IO, but the buffer is now full. When "
-"the user consumes the data from the buffer, this should re-enable the VIO so"
-" it indicates to the vconnection that the buffer has been modified."
+"the user consumes the data from the buffer, this should re-enable the VIO "
+"so it indicates to the vconnection that the buffer has been modified."
msgstr ""
#: ../../sdk/io-guide.en.rst:137
@@ -193,10 +193,10 @@ msgstr ""
msgid ""
"An attempt was made to read past the end of the stream of bytes during the "
"handling of an ``TSVConnRead`` operation. This event occurs when the number "
-"of bytes available for reading from a vconnection is less than the number of"
-" bytes the user specifies should be read from the vconnection in a call to "
-"``TSVConnRead``. A common case where this occurs is when the user specifies "
-"that ``INT64_MAX`` bytes are to be read from a network connection."
+"of bytes available for reading from a vconnection is less than the number "
+"of bytes the user specifies should be read from the vconnection in a call "
+"to ``TSVConnRead``. A common case where this occurs is when the user "
+"specifies that ``INT64_MAX`` bytes are to be read from a network connection."
msgstr ""
#: ../../sdk/io-guide.en.rst:158
@@ -209,21 +209,21 @@ msgstr ""
#: ../../sdk/io-guide.en.rst:163
msgid ""
"After using a vconnection, the user must call ``TSVConnClose`` or "
-"``TSVConnAbort``. While both calls indicate that the vconnection can destroy"
-" itself, ``TSVConnAbort`` should be used when the connection is being closed"
-" abnormally. After a call to ``TSVConnClose`` or ``TSVConnAbort``, the user "
-"will not be called back by the vconnection again."
+"``TSVConnAbort``. While both calls indicate that the vconnection can "
+"destroy itself, ``TSVConnAbort`` should be used when the connection is "
+"being closed abnormally. After a call to ``TSVConnClose`` or "
+"``TSVConnAbort``, the user will not be called back by the vconnection again."
msgstr ""
#: ../../sdk/io-guide.en.rst:170
msgid ""
"Sometimes it's desirable to simply close down the write portion of a "
-"connection while keeping the read portion open. This can be accomplished via"
-" the ``TSVConnShutdown`` function, which shuts down either the read or write"
-" portion of a vconnection. *Shutdown* means that the vconnection will no "
-"longer call back the user with events for the portion of the connection that"
-" was shut down. For example: if the user shuts down the write portion of a "
-"connection, then the ``TS_EVENT_VCONN_WRITE_READY`` or "
+"connection while keeping the read portion open. This can be accomplished "
+"via the ``TSVConnShutdown`` function, which shuts down either the read or "
+"write portion of a vconnection. *Shutdown* means that the vconnection will "
+"no longer call back the user with events for the portion of the connection "
+"that was shut down. For example: if the user shuts down the write portion "
+"of a connection, then the ``TS_EVENT_VCONN_WRITE_READY`` or "
"``TS_EVENT_VCONN_WRITE_COMPLETE`` events will not be produced. In the null "
"transform plugin, the write operation is shut down with a call to "
"``TSVConnShutdown``. To learn how vconnections are used in transformation "
@@ -237,48 +237,48 @@ msgstr ""
#: ../../sdk/io-guide.en.rst:185
msgid ""
-"```TSVConnAbort`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a08444a9b2fee637672e177ede78b6218>`__"
+"```TSVConnAbort`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#a08444a9b2fee637672e177ede78b6218>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:186
msgid ""
-"```TSVConnClose`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a69344c2c6e57ece0990a5cee73b75215>`__"
+"```TSVConnClose`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a69344c2c6e57ece0990a5cee73b75215>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:187
msgid ""
-"```TSVConnClosedGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a441d74cd77bf5d5564048682ca83b6ec>`__"
+"```TSVConnClosedGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkAPI_8cc.html#a441d74cd77bf5d5564048682ca83b6ec>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:188
msgid ""
-"```TSVConnRead`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a29674799a8deffdde3d6ae3231aba1dc>`__"
+"```TSVConnRead`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#a29674799a8deffdde3d6ae3231aba1dc>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:189
msgid ""
-"```TSVConnReadVIOGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#aa6f8788f062737f211c788ad5fcd2813>`__"
+"```TSVConnReadVIOGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkAPI_8cc.html#aa6f8788f062737f211c788ad5fcd2813>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:190
msgid ""
-"```TSVConnShutdown`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a5935b6c762b65fe87057adf94b1b00b4>`__"
+"```TSVConnShutdown`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#a5935b6c762b65fe87057adf94b1b00b4>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:191
msgid ""
-"```TSVConnWrite`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#acea65496d1fcaf01924b0210f3129e6b>`__"
+"```TSVConnWrite`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#acea65496d1fcaf01924b0210f3129e6b>`__"
msgstr ""
#: ../../sdk/io-guide.en.rst:192
msgid ""
-"```TSVConnWriteVIOGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#ae9a38dbd4866c59131a1f3b806a18aab>`__"
+"```TSVConnWriteVIOGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkAPI_8cc.html#ae9a38dbd4866c59131a1f3b806a18aab>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api.en.po
index 71a0c71..f5a1f73 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -48,16 +48,16 @@ msgstr ""
#: ../../sdk/io-guide/guide-to-cache-api.en.rst:59
msgid ""
-"``TS_EVENT_CACHE_OPEN_READ`` - indicates the lookup was successful. The data"
-" passed back along with this event is a cache vconnection that can be used "
-"to initiate a read on this keyed data."
+"``TS_EVENT_CACHE_OPEN_READ`` - indicates the lookup was successful. The "
+"data passed back along with this event is a cache vconnection that can be "
+"used to initiate a read on this keyed data."
msgstr ""
#: ../../sdk/io-guide/guide-to-cache-api.en.rst:63
msgid ""
-"``TS_EVENT_CACHE_OPEN_READ_FAILED`` - indicates the lookup was unsuccessful."
-" Reasons for this event could be that another continuation is writing to "
-"that cache location, or the cache key doesn't refer to a cached resource. "
-"Data payload for this event indicates the possible reason the read failed "
-"(``TSCacheError``)."
+"``TS_EVENT_CACHE_OPEN_READ_FAILED`` - indicates the lookup was "
+"unsuccessful. Reasons for this event could be that another continuation is "
+"writing to that cache location, or the cache key doesn't refer to a cached "
+"resource. Data payload for this event indicates the possible reason the "
+"read failed (``TSCacheError``)."
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/errors.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/errors.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/errors.en.po
index ce6ec71..c03662d 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/errors.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/errors.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/example.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/example.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/example.en.po
index ab2303b..d73c603 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/example.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/example.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -20,10 +20,10 @@ msgid ""
"In the example below, suppose there is a cache hit and the cache returns a "
"vconnection that enables you to read the document from cache. To do this, "
"you need to prepare a buffer (``cache_bufp``) to hold the document; "
-"meanwhile, use ``TSVConnCachedObjectSizeGet`` to find out the actual size of"
-" the document (``content_length``). Then, issue ``TSVConnRead`` to read the "
-"document with the total data length required as ``content_length``. Assume "
-"the following data:"
+"meanwhile, use ``TSVConnCachedObjectSizeGet`` to find out the actual size "
+"of the document (``content_length``). Then, issue ``TSVConnRead`` to read "
+"the document with the total data length required as ``content_length``. "
+"Assume the following data:"
msgstr ""
#: ../../sdk/io-guide/guide-to-cache-api/example.en.rst:38
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-remove.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-remove.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-remove.en.po
index de05652..f19d817 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-remove.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-remove.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-write.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-write.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-write.en.po
index 3ae5031..04e0eb3 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-write.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/guide-to-cache-api/how-to-do-a-cache-write.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/io-buffers.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/io-buffers.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/io-buffers.en.po
index 9ac91bf..5117678 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/io-buffers.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/io-buffers.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -23,22 +23,22 @@ msgid ""
"(``TSIOBufferBlock``) and buffer data (``TSIOBufferData``) data structures "
"are reference-counted, so they can reside in multiple buffers at the same "
"time. This makes it extremely efficient to copy data from one IO buffer to "
-"another via ``TSIOBufferCopy``, since Traffic Server must only copy pointers"
-" and adjust reference counts appropriately (and doesn't actually copy any "
-"data)."
+"another via ``TSIOBufferCopy``, since Traffic Server must only copy "
+"pointers and adjust reference counts appropriately (and doesn't actually "
+"copy any data)."
msgstr ""
#: ../../sdk/io-guide/io-buffers.en.rst:31
msgid ""
-"The IO buffer abstraction provides for a single writer and multiple readers."
-" In order for the readers to have no knowledge of each other, they "
-"manipulate IO buffers through the ``TSIOBufferReader`` data structure. Since"
-" only a single writer is allowed, there is no corresponding "
+"The IO buffer abstraction provides for a single writer and multiple "
+"readers. In order for the readers to have no knowledge of each other, they "
+"manipulate IO buffers through the ``TSIOBufferReader`` data structure. "
+"Since only a single writer is allowed, there is no corresponding "
"``TSIOBufferWriter`` data structure. The writer simply modifies the IO "
"buffer directly. To see an example that illustrates how to use IOBuffers, "
-"refer to the sample code in the description of ```TSIOBufferBlockReadStart``"
-" "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a367203e6e2cf4349e019952782deb96c>`__."
+"refer to the sample code in the description of "
+"```TSIOBufferBlockReadStart`` <http://people.apache.org/~amc/ats/doc/html/"
+"ts_8h.html#a367203e6e2cf4349e019952782deb96c>`__."
msgstr ""
#: ../../sdk/io-guide/io-buffers.en.rst:40
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/net-vconnections.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/net-vconnections.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/net-vconnections.en.po
index e91361f..44493f4 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/net-vconnections.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/net-vconnections.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -19,9 +19,9 @@ msgstr ""
msgid ""
"A **network** **vconnection** (or*\\* netvconnection*\\ \\*) is a wrapper "
"around a TCP socket that enables the socket to work within the Traffic "
-"Server vconnection framework. See `vconnections "
-"<index.en.html#Vconnections>`__ for more information about the Traffic "
-"Server abstraction for doing asynchronous IO."
+"Server vconnection framework. See `vconnections <index.en."
+"html#Vconnections>`__ for more information about the Traffic Server "
+"abstraction for doing asynchronous IO."
msgstr ""
#: ../../sdk/io-guide/net-vconnections.en.rst:27
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/transformations.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/transformations.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/transformations.en.po
index 924486a..6b8a376 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/transformations.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/transformations.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -26,12 +26,12 @@ msgid ""
"iocore. As mentioned earlier, a given vconnection can have a maximum of one "
"read operation and one write operation being performed on it. The "
"vconnection user gets information about the operation being performed by "
-"examining the VIO returned by a call to ``TSVConnRead`` or ``TSVConnWrite``."
-" The implementor, in turn, gets a handle on the VIO operation by examining "
-"the VIO returned by ``TSVConnReadVIOGet`` or ``TSVConnWriteVIOGet`` (recall "
-"that every vconnection created through the Traffic Server API has an "
-"associated read VIO and write VIO, even if it only supports reading or "
-"writing)."
+"examining the VIO returned by a call to ``TSVConnRead`` or "
+"``TSVConnWrite``. The implementor, in turn, gets a handle on the VIO "
+"operation by examining the VIO returned by ``TSVConnReadVIOGet`` or "
+"``TSVConnWriteVIOGet`` (recall that every vconnection created through the "
+"Traffic Server API has an associated read VIO and write VIO, even if it "
+"only supports reading or writing)."
msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:36
@@ -50,8 +50,8 @@ msgid ""
"is run when an event is sent to it, or more accurately, when an event that "
"was sent to it is received. It is the handler function's job to examine the "
"event, the current state of its read VIO and write VIO, and any other "
-"internal state the vconnection might have and potentially make some progress"
-" on the IO operations."
+"internal state the vconnection might have and potentially make some "
+"progress on the IO operations."
msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:53
@@ -73,17 +73,17 @@ msgid ""
"Vconnections are state machines that are animated by the events they "
"receive. An event is sent to the vconnection whenever an ``TSVConnRead``, "
"``TSVConnWrite``, ``TSVConnClose``, ``TSVConnShutdown``, or "
-"``TSVIOReenable`` call is performed. ``TSVIOReenable`` indirectly references"
-" the vconnection through a back-pointer in the VIO structure to the "
-"vconnection. The vconnection itself only knows which call was performed by "
-"examining its state and the state of its VIOs. For example, when "
+"``TSVIOReenable`` call is performed. ``TSVIOReenable`` indirectly "
+"references the vconnection through a back-pointer in the VIO structure to "
+"the vconnection. The vconnection itself only knows which call was performed "
+"by examining its state and the state of its VIOs. For example, when "
"``TSVConnClose`` is called, the vconnection is sent an immediate event "
-"(``TS_EVENT_IMMEDIATE``). For every event the vconnection receives, it needs"
-" to check its closed flag to see if it has been closed. Similarly, when "
-"``TSVIOReenable`` is called, the vconnection is sent an immediate event. For"
-" every event the vconnection receives, it must check its VIOs to see if the "
-"buffers have been modified to a state in which it can continue processing "
-"one of its operations."
+"(``TS_EVENT_IMMEDIATE``). For every event the vconnection receives, it "
+"needs to check its closed flag to see if it has been closed. Similarly, "
+"when ``TSVIOReenable`` is called, the vconnection is sent an immediate "
+"event. For every event the vconnection receives, it must check its VIOs to "
+"see if the buffers have been modified to a state in which it can continue "
+"processing one of its operations."
msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:92
@@ -105,11 +105,11 @@ msgid ""
"A `transformation <HTTPTransformationPlugins.html#Transformations>`__ is a "
"specific type of vconnection. It supports a subset of the vconnection "
"functionality that enables one or more transformations to be chained "
-"together. A transformation sits as a bottleneck between an input data source"
-" and an output data sink, which enables it to view and modify all the data "
-"passing through it. Alternatively, some transformations simply scan the data"
-" and pass it on. A common transformation is one that compresses data in some"
-" manner."
+"together. A transformation sits as a bottleneck between an input data "
+"source and an output data sink, which enables it to view and modify all the "
+"data passing through it. Alternatively, some transformations simply scan "
+"the data and pass it on. A common transformation is one that compresses "
+"data in some manner."
msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:111
@@ -141,16 +141,16 @@ msgstr ""
msgid ""
"Data is passed in to the transformation by initiating a vconnection write "
"operation on the transformation. As a consequence of this design, a "
-"transformation must support the vconnection write operation. In other words,"
-" your transformation must expect an upstream vconnection to write data to "
-"it. The transformation has to read the data, consume it, and tell the "
-"upstream vconnection it is finished by sending it an "
+"transformation must support the vconnection write operation. In other "
+"words, your transformation must expect an upstream vconnection to write "
+"data to it. The transformation has to read the data, consume it, and tell "
+"the upstream vconnection it is finished by sending it an "
"``TS_EVENT_WRITE_COMPLETE`` event. Transformations cannot send the "
"``TS_EVENT_VCONN_WRITE_COMPLETE`` event to the upstream vconnection unless "
"they are finished consuming all incoming data. If "
-"``TS_EVENT_VCONN_WRITE_COMPLETE`` is sent prematurely, then certain internal"
-" Traffic Server data structures will not be deallocated, thereby causing a "
-"memory leak."
+"``TS_EVENT_VCONN_WRITE_COMPLETE`` is sent prematurely, then certain "
+"internal Traffic Server data structures will not be deallocated, thereby "
+"causing a memory leak."
msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:139
@@ -166,10 +166,10 @@ msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:155
msgid ""
-"Before sending ``TS_EVENT_VCONN_WRITE_COMPLETE``, your transformation should"
-" check the number of bytes remaining in the upstream vconnection's write VIO"
-" (input VIO) using the function ``TSVIONTodoGet`` (``input_vio``). This "
-"value should go to zero when all of the upstream data is consumed "
+"Before sending ``TS_EVENT_VCONN_WRITE_COMPLETE``, your transformation "
+"should check the number of bytes remaining in the upstream vconnection's "
+"write VIO (input VIO) using the function ``TSVIONTodoGet`` (``input_vio``). "
+"This value should go to zero when all of the upstream data is consumed "
"(``TSVIONTodoGet = nbytes - ndone``). Do not send "
"``TS_EVENT_VCONN_WRITE_COMPLETE`` events if ``TSVIONTodoGet`` is greater "
"than zero."
@@ -177,9 +177,9 @@ msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:163
msgid ""
-"The transformation passes data out of itself by using the output vconnection"
-" retrieved by ``TSTransformOutputVConnGet``. Immediately before Traffic "
-"Server initiates the write operation (which inputs data into the "
+"The transformation passes data out of itself by using the output "
+"vconnection retrieved by ``TSTransformOutputVConnGet``. Immediately before "
+"Traffic Server initiates the write operation (which inputs data into the "
"transformation), it sets the output vconnection either to the next "
"transformation in the chain of transformations or to a special terminating "
"transformation (if it's the last transformation in the chain). Since the "
@@ -189,17 +189,19 @@ msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:172
msgid ""
-"All of the transformations in a transformation chain share the transaction's"
-" mutex. This small restriction (enforced by ``TSTransformCreate``) removes "
-"many of the locking complications of implementing general vconnections. For "
-"example, a transformation does not have to grab its write VIO mutex before "
-"accessing its write VIO because it knows it already holds the mutex."
+"All of the transformations in a transformation chain share the "
+"transaction's mutex. This small restriction (enforced by "
+"``TSTransformCreate``) removes many of the locking complications of "
+"implementing general vconnections. For example, a transformation does not "
+"have to grab its write VIO mutex before accessing its write VIO because it "
+"knows it already holds the mutex."
msgstr ""
#: ../../sdk/io-guide/transformations.en.rst:179
msgid ""
-"The transformation functions are: \\* ```TSTransformCreate`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a54c4902bb537d3d40763bd947ed753b9>`__"
-" \\* ```TSTransformOutputVConnGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#ac6832718a2d9f2658409ad231811e1e3>`__"
+"The transformation functions are: \\* ```TSTransformCreate`` <http://people."
+"apache.org/~amc/ats/doc/html/ts_8h."
+"html#a54c4902bb537d3d40763bd947ed753b9>`__ \\* "
+"```TSTransformOutputVConnGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"ts_8h.html#ac6832718a2d9f2658409ad231811e1e3>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/io-guide/vios.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/vios.en.po b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/vios.en.po
index 701e785..279b1ec 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/io-guide/vios.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/io-guide/vios.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -40,66 +40,66 @@ msgstr ""
#: ../../sdk/io-guide/vios.en.rst:48
msgid ""
-"```TSVIOBufferGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a55df75b6ba6e9152292a01e0b4e21963>`__"
+"```TSVIOBufferGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a55df75b6ba6e9152292a01e0b4e21963>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:49
msgid ""
-"```TSVIOVConnGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a32b9eaaadf2145f98ceb4d64b7c06c2f>`__"
+"```TSVIOVConnGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a32b9eaaadf2145f98ceb4d64b7c06c2f>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:50
msgid ""
-"```TSVIOContGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a071f12b307885c02aceebc41601bbdcf>`__"
+"```TSVIOContGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a071f12b307885c02aceebc41601bbdcf>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:51
msgid ""
-"```TSVIOMutexGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#ab4e8c755cf230918a14a4411af8b3e63>`__"
+"```TSVIOMutexGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#ab4e8c755cf230918a14a4411af8b3e63>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:52
msgid ""
-"```TSVIONBytesGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#af6fc57adc7308864b343b6b7fd30c5ff>`__"
+"```TSVIONBytesGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#af6fc57adc7308864b343b6b7fd30c5ff>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:53
msgid ""
-"```TSVIONBytesSet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a27594723f14891ac43da3e1368328d0e>`__"
+"```TSVIONBytesSet`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a27594723f14891ac43da3e1368328d0e>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:54
msgid ""
-"```TSVIONDoneGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#ad71156f68a119c00502ff1fd598824ab>`__"
+"```TSVIONDoneGet`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#ad71156f68a119c00502ff1fd598824ab>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:55
msgid ""
-"```TSVIONDoneSet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#af4590966899039571d874e0c090042ad>`__"
+"```TSVIONDoneSet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#af4590966899039571d874e0c090042ad>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:56
msgid ""
-"```TSVIONTodoGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a1dd145ddd60822a5f892becf7b8e8f84>`__"
+"```TSVIONTodoGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a1dd145ddd60822a5f892becf7b8e8f84>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:57
msgid ""
-"```TSVIOReaderGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a471ee1fde01fbeabce6c39944dfe9da6>`__"
+"```TSVIOReaderGet`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a471ee1fde01fbeabce6c39944dfe9da6>`__"
msgstr ""
#: ../../sdk/io-guide/vios.en.rst:58
msgid ""
-"```TSVIOReenable`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a792ef9d6962193badad2877a81d8bcff>`__"
+"```TSVIOReenable`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a792ef9d6962193badad2877a81d8bcff>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide.en.po b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide.en.po
index 87cf492..9681129 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -19,16 +19,16 @@ msgstr ""
msgid ""
"Most of the functions in the Traffic Server API provide an interface to "
"specific code modules within Traffic Server. The miscellaneous functions "
-"described in this chapter provide some useful general capabilities. They are"
-" categorized as follows:"
+"described in this chapter provide some useful general capabilities. They "
+"are categorized as follows:"
msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:34
msgid ""
-"The C library already provides functions such as ``printf``, ``malloc``, and"
-" ``fopen`` to perform these tasks. The Traffic Server API versions, however,"
-" overcome various C library limitations (such as portability to all Traffic "
-"Server-support platforms)."
+"The C library already provides functions such as ``printf``, ``malloc``, "
+"and ``fopen`` to perform these tasks. The Traffic Server API versions, "
+"however, overcome various C library limitations (such as portability to all "
+"Traffic Server-support platforms)."
msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:40
@@ -37,37 +37,36 @@ msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:42
msgid ""
-"```TSDebug`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#afccd91047cc46eb35478a751ec65c78d>`__"
-" prints out a formatted statement if you are running Traffic Server in debug"
-" mode."
+"```TSDebug`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#afccd91047cc46eb35478a751ec65c78d>`__ prints out a formatted statement "
+"if you are running Traffic Server in debug mode."
msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:46
msgid ""
-"```TSIsDebugTagSet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a2d3ceac855c1cde83eff5484bc952288>`__"
-" checks to see if a debug tag is set. If the debug tag is set, then Traffic "
-"Server prints out all debug statements associated with the tag."
+"```TSIsDebugTagSet`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a2d3ceac855c1cde83eff5484bc952288>`__ checks to see if a debug tag is "
+"set. If the debug tag is set, then Traffic Server prints out all debug "
+"statements associated with the tag."
msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:51
msgid ""
-"```TSError`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a19ff77fecfc3e331b03da6e358907787>`__"
-" prints error messages to Traffic Server's error log"
+"```TSError`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#a19ff77fecfc3e331b03da6e358907787>`__ prints error messages to Traffic "
+"Server's error log"
msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:54
msgid ""
-"```TSAssert`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#ad94eb4fb1f08082ea1634f169cc49c68>`__"
-" enables the use of assertion in a plugin."
+"```TSAssert`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#ad94eb4fb1f08082ea1634f169cc49c68>`__ enables the use of assertion in "
+"a plugin."
msgstr ""
#: ../../sdk/misc-interface-guide.en.rst:57
msgid ""
-"```TSReleaseAssert`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a5e751769785de91c52bd503bcbc28b0a>`__"
-" enables the use of assertion in a plugin."
+"```TSReleaseAssert`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a5e751769785de91c52bd503bcbc28b0a>`__ enables the use of assertion in "
+"a plugin."
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/memory-allocation.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/memory-allocation.en.po b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/memory-allocation.en.po
index dac132f..90462d4 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/memory-allocation.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/memory-allocation.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -18,19 +18,19 @@ msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:21
msgid ""
"Traffic Server provides five routines for allocating and freeing memory. "
-"These routines correspond to similar routines in the C library. For example,"
-" ``TSrealloc`` behaves like the C library routine ``realloc``."
+"These routines correspond to similar routines in the C library. For "
+"example, ``TSrealloc`` behaves like the C library routine ``realloc``."
msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:25
msgid ""
"There are two main reasons for using the routines provided by Traffic "
-"Server. The first is portability: the Traffic Server API routines behave the"
-" same on all of Traffic Server's supported platforms. For example, "
+"Server. The first is portability: the Traffic Server API routines behave "
+"the same on all of Traffic Server's supported platforms. For example, "
"``realloc`` does not accept an argument of ``NULL`` on some platforms. The "
"second reason is that the Traffic Server routines actually track the memory "
-"allocations by file and line number. This tracking is very efficient, always"
-" turned on, and quite useful when tracking down memory leaks."
+"allocations by file and line number. This tracking is very efficient, "
+"always turned on, and quite useful when tracking down memory leaks."
msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:34
@@ -39,30 +39,30 @@ msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:36
msgid ""
-"```TSfree`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#afe7f18beddf31a80436a03a5ab7e759f>`__"
+"```TSfree`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#afe7f18beddf31a80436a03a5ab7e759f>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:38
msgid ""
-"```TSmalloc`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#af030092823148cbbc5525c4fcde9bb37>`__"
+"```TSmalloc`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#af030092823148cbbc5525c4fcde9bb37>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:40
msgid ""
-"```TSrealloc`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a3abaf3d50d82377dccd1c16bc7b631ab>`__"
+"```TSrealloc`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a3abaf3d50d82377dccd1c16bc7b631ab>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:42
msgid ""
-"```TSstrdup`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a92c01584655c52e46a58986435e17c86>`__"
+"```TSstrdup`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a92c01584655c52e46a58986435e17c86>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/memory-allocation.en.rst:44
msgid ""
-"```TSstrndup`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a11072c11fa6d8470ace2963615229146>`__"
+"```TSstrndup`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a11072c11fa6d8470ace2963615229146>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/thread-functions.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/thread-functions.en.po b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/thread-functions.en.po
index 07038e3..03d8615 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/thread-functions.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/thread-functions.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -21,8 +21,8 @@ msgid ""
"identify threads within Traffic Server. Multithreading enables a single "
"program to have more than one stream of execution and to process more than "
"one transaction at a time. Threads serialize their access to shared "
-"resources and data using the ``TSMutex`` type, as described in `Mutexes "
-"<../mutex-guide/#Mutexes>`__."
+"resources and data using the ``TSMutex`` type, as described in `Mutexes <../"
+"mutex-guide/#Mutexes>`__."
msgstr ""
#: ../../sdk/misc-interface-guide/thread-functions.en.rst:28
@@ -31,24 +31,24 @@ msgstr ""
#: ../../sdk/misc-interface-guide/thread-functions.en.rst:30
msgid ""
-"```TSThreadCreate`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#ad087d67be30b68b6d608a5094fceed2a>`__"
+"```TSThreadCreate`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#ad087d67be30b68b6d608a5094fceed2a>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/thread-functions.en.rst:31
msgid ""
-"```TSThreadDestroy`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a600e8ad830081bdcf6caabc07b54c9e4>`__"
+"```TSThreadDestroy`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a600e8ad830081bdcf6caabc07b54c9e4>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/thread-functions.en.rst:32
msgid ""
-"```TSThreadInit`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a11088d9aaba362827841687864e55242>`__"
+"```TSThreadInit`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a11088d9aaba362827841687864e55242>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/thread-functions.en.rst:33
msgid ""
-"```TSThreadSelf`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a5cc33c5182755e3d62b4aa55277425d9>`__"
+"```TSThreadSelf`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a5cc33c5182755e3d62b4aa55277425d9>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/tsfopen-family.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/tsfopen-family.en.po b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/tsfopen-family.en.po
index 762b636..9df457e 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/tsfopen-family.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/misc-interface-guide/tsfopen-family.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -22,10 +22,11 @@ msgid ""
"line-by-line basis. The ``TSfopen`` family of functions aims at solving the "
"same problem of buffered IO and line at a time IO in a platform-independent "
"manner. The ``fopen`` family of C library functions can only open a file if "
-"a file descriptor less than 256 is available. Since Traffic Server often has"
-" more than 2000 file descriptors open at once, however, the likelihood of an"
-" available file descriptor less than 256 very small. To solve this problem, "
-"the ``TSfopen`` family can open files with descriptors greater than 256."
+"a file descriptor less than 256 is available. Since Traffic Server often "
+"has more than 2000 file descriptors open at once, however, the likelihood "
+"of an available file descriptor less than 256 very small. To solve this "
+"problem, the ``TSfopen`` family can open files with descriptors greater "
+"than 256."
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:32
@@ -37,42 +38,42 @@ msgid ""
"thread for doing the blocking IO. The ``TSfopen`` family is intended for "
"reading and writing configuration information when corresponding usage of "
"the ``fopen`` family of functions is inappropriate due to file descriptor "
-"and portability limitations. The ``TSfopen`` family of functions consists of"
-" the following:"
+"and portability limitations. The ``TSfopen`` family of functions consists "
+"of the following:"
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:42
msgid ""
-"```TSfclose`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a2efebe7583752668e6136de0b47bee4f>`__"
+"```TSfclose`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#a2efebe7583752668e6136de0b47bee4f>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:44
msgid ""
-"```TSfflush`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc.html#a3cb0cb348ed189a98577f84e0629ca9a>`__"
+"```TSfflush`` <http://people.apache.org/~amc/ats/doc/html/InkAPI_8cc."
+"html#a3cb0cb348ed189a98577f84e0629ca9a>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:46
msgid ""
-"```TSfgets`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a6dcc724a432a287836352b31984e0de8>`__"
+"```TSfgets`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a6dcc724a432a287836352b31984e0de8>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:48
msgid ""
-"```TSfopen`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a53b0430d5b0c042bdb3d06689cf244f3>`__"
+"```TSfopen`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a53b0430d5b0c042bdb3d06689cf244f3>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:50
msgid ""
-"```TSfread`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a29f83c50b52e4fcabfe2b829de5742e2>`__"
+"```TSfread`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a29f83c50b52e4fcabfe2b829de5742e2>`__"
msgstr ""
#: ../../sdk/misc-interface-guide/tsfopen-family.en.rst:52
msgid ""
-"```TSfwrite`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a596a5562db5180ea8818f7bb87336a15>`__"
+"```TSfwrite`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a596a5562db5180ea8818f7bb87336a15>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/mutex-guide.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/mutex-guide.en.po b/doc/locale/ja/LC_MESSAGES/sdk/mutex-guide.en.po
index 526d151..19ba46d 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/mutex-guide.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/mutex-guide.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -38,13 +38,14 @@ msgid ""
"The Traffic Server API provides two functions that attempt to access and "
"lock the data: ``InkMutexLockTry`` and ``TSMutexLock``. **``TSMutexLock``** "
"is a blocking call - if you use it, you can slow Traffic Server performance "
-"because transaction processing pauses until the mutex is unlocked. It should"
-" be used only on threads created by the plugin ``TSContThreadCreate``. Never"
-" use it on a continuation handler called back by the Cache, Net, or Event "
-"Processor. Even if the critical section is very small, do not use it. If you"
-" need to update a flag, then set a variable and/or use atomic operations. If"
-" ``TSMutexLock`` is used in any case other than the one recommended above, "
-"then the result will be a serious performance impact."
+"because transaction processing pauses until the mutex is unlocked. It "
+"should be used only on threads created by the plugin "
+"``TSContThreadCreate``. Never use it on a continuation handler called back "
+"by the Cache, Net, or Event Processor. Even if the critical section is very "
+"small, do not use it. If you need to update a flag, then set a variable and/"
+"or use atomic operations. If ``TSMutexLock`` is used in any case other than "
+"the one recommended above, then the result will be a serious performance "
+"impact."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:47
@@ -52,8 +53,8 @@ msgid ""
"**``TSMutexLockTry``**, on the other hand, attempts to lock the mutex only "
"if it is unlocked (i.e., not being used by another thread). It should be "
"used in all cases other than the above mentioned ``TSMutexLock`` case. If "
-"the ``TSMutexLockTry`` attempt fails, then you can schedule a future attempt"
-" (which must be at least 10 milliseconds later)."
+"the ``TSMutexLockTry`` attempt fails, then you can schedule a future "
+"attempt (which must be at least 10 milliseconds later)."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:54
@@ -98,12 +99,11 @@ msgid ""
"The ``blacklist-1.c`` sample plugin implements a mutex that locks global "
"data. The blacklist plugin reads its blacklisted sites from a configuration "
"file; file read operations are protected by a mutex created in "
-"``TSPluginInit``. The ``blacklist-1.c`` code uses ``TSMutexLockTry`` instead"
-" of ``InkMutexLock``. For more detailed information, see the "
+"``TSPluginInit``. The ``blacklist-1.c`` code uses ``TSMutexLockTry`` "
+"instead of ``InkMutexLock``. For more detailed information, see the "
"```blacklist-1.c`` <../sample-source-code#Sample_blacklist-1.c>`__ code; "
-"start by looking at the ```TSPluginInit`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a9a0b0ac9cbce9d6644f66bbe93098313>`__"
-" function."
+"start by looking at the ```TSPluginInit`` <http://people.apache.org/~amc/"
+"ats/doc/html/ts_8h.html#a9a0b0ac9cbce9d6644f66bbe93098313>`__ function."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:87
@@ -112,25 +112,26 @@ msgstr ""
#: ../../sdk/mutex-guide.en.rst:89
msgid ""
-"Create a mutex for the shared data with ```TSMutexCreate`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#aa4300d8888c6962a44c9e827d633e433>`__."
+"Create a mutex for the shared data with ```TSMutexCreate`` <http://people."
+"apache.org/~amc/ats/doc/html/ts_8h."
+"html#aa4300d8888c6962a44c9e827d633e433>`__."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:92
msgid ""
"Whenever you need to read or modify this data, first lock it by calling "
-"```TSMutexLockTry`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#ac9c08451aa529851b9474e3c035f44bb>`__;"
-" then read or modify the data."
+"```TSMutexLockTry`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#ac9c08451aa529851b9474e3c035f44bb>`__; then read or modify the data."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:97
msgid ""
-"When you are done with the data, unlock it with ```TSMutexUnlock`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#afbb474c217fd5b927f1f8487c45646dd>`__."
-" If you are unlocking data accessed during the processing of an HTTP "
-"transaction, then you must unlock it before calling ```TSHttpTxnReenable`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#ac367347e02709ac809994dfb21d3288a>`__."
+"When you are done with the data, unlock it with ```TSMutexUnlock`` <http://"
+"people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#afbb474c217fd5b927f1f8487c45646dd>`__. If you are unlocking data "
+"accessed during the processing of an HTTP transaction, then you must unlock "
+"it before calling ```TSHttpTxnReenable`` <http://people.apache.org/~amc/ats/"
+"doc/html/ts_8h.html#ac367347e02709ac809994dfb21d3288a>`__."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:104
@@ -176,8 +177,8 @@ msgstr ""
#: ../../sdk/mutex-guide.en.rst:143
msgid ""
-"You want to store data specific to each HTTP transaction that you might need"
-" to reuse across various hooks."
+"You want to store data specific to each HTTP transaction that you might "
+"need to reuse across various hooks."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:146
@@ -193,8 +194,8 @@ msgstr ""
#: ../../sdk/mutex-guide.en.rst:152
msgid ""
"A typical way of adding the new continuation is by registering the plugin "
-"continuation to be called back by HTTP transactions globally when they reach"
-" ``TS_HTTP_TXN_START_HOOK``. Refer to the example below, which uses a "
+"continuation to be called back by HTTP transactions globally when they "
+"reach ``TS_HTTP_TXN_START_HOOK``. Refer to the example below, which uses a "
"transaction-specific continuation called ``txn_contp``."
msgstr ""
@@ -244,14 +245,14 @@ msgstr ""
#: ../../sdk/mutex-guide.en.rst:345
msgid ""
-"You do not need to use locks when a continuation has registered itself to be"
-" called back by HTTP hooks and it only uses the HTTP APIs. In the example "
+"You do not need to use locks when a continuation has registered itself to "
+"be called back by HTTP hooks and it only uses the HTTP APIs. In the example "
"above, the continuation ``txn_contp`` has registered itself to be called "
"back at HTTP hooks and it only uses the HTTP APIs. In this case only, it's "
"safe to access data shared between ``txnp`` and ``txn_contp`` without "
"grabbing a lock. In the example above, ``txn_contp`` is created with a "
-"``NULL`` mutex. This works because the HTTP transaction ``txnp`` is the only"
-" one that will call back ``txn_contp``, and you are guaranteed that "
+"``NULL`` mutex. This works because the HTTP transaction ``txnp`` is the "
+"only one that will call back ``txn_contp``, and you are guaranteed that "
"``txn_contp`` will be called back only one hook at a time. After processing "
"is finished, ``txn_contp`` will reenable ``txnp``."
msgstr ""
@@ -263,9 +264,10 @@ msgid ""
"where ``txn_contp`` is scheduled to be called back by a processor (such as "
"the cache processor, the DNS processor, etc.). This ensures that "
"``txn_contp`` is called back sequentially and not simultaneously. In other "
-"words, you need to ensure that ``txn_contp`` will not be called back by both"
-" ``txnp`` and the cache processor at the same time, since this will result "
-"in a situation wherein you're executing two pieces of code in conflict."
+"words, you need to ensure that ``txn_contp`` will not be called back by "
+"both ``txnp`` and the cache processor at the same time, since this will "
+"result in a situation wherein you're executing two pieces of code in "
+"conflict."
msgstr ""
#: ../../sdk/mutex-guide.en.rst:368
@@ -291,18 +293,18 @@ msgstr ""
#: ../../sdk/mutex-guide.en.rst:408
msgid ""
-"```TSMutexCreate`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#aa4300d8888c6962a44c9e827d633e433>`__"
+"```TSMutexCreate`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#aa4300d8888c6962a44c9e827d633e433>`__"
msgstr ""
#: ../../sdk/mutex-guide.en.rst:409
msgid ""
-"```TSMutexLock`` "
-"<http://people.apache.org/~amc/ats/doc/html/InkIOCoreAPI_8cc.html#a306f9923bc9d3c0f417c185919531934>`__"
+"```TSMutexLock`` <http://people.apache.org/~amc/ats/doc/html/"
+"InkIOCoreAPI_8cc.html#a306f9923bc9d3c0f417c185919531934>`__"
msgstr ""
#: ../../sdk/mutex-guide.en.rst:410
msgid ""
-"```TSMutexLockTry`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#ac9c08451aa529851b9474e3c035f44bb>`__"
+"```TSMutexLockTry`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#ac9c08451aa529851b9474e3c035f44bb>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/new-protocol-plugins.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/new-protocol-plugins.en.po b/doc/locale/ja/LC_MESSAGES/sdk/new-protocol-plugins.en.po
index f3d9215..0583edb 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/new-protocol-plugins.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/new-protocol-plugins.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -19,8 +19,8 @@ msgstr ""
msgid ""
"The new protocol APIs enable you to extend Traffic Server to be a web proxy "
"for any protocol. This chapter describes new protocol APIs and the plugins "
-"that support new protocols. It also provides a detailed review of code for a"
-" sample Protocol plugin that supports a very simple artificial HTTP-like "
+"that support new protocols. It also provides a detailed review of code for "
+"a sample Protocol plugin that supports a very simple artificial HTTP-like "
"protocol."
msgstr ""
@@ -31,8 +31,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:35
msgid ""
"The sample protocol enables a client to ask a server for a file. Clients "
-"send requests to a specific Traffic Server port (specified in "
-":file:`plugin.config`); each request has the following structure::"
+"send requests to a specific Traffic Server port (specified in :file:`plugin."
+"config`); each request has the following structure::"
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:41
@@ -40,8 +40,8 @@ msgid ""
"Using the Protocol plugin, Traffic Server can accept these requests, parse "
"them, and act as a proxy cache (i.e., request the file from the origin "
"server on the client's behalf and store copies of response messages in "
-"cache). The Protocol plugin is a state machine that flows through the states"
-" illustrated in the `Sample Protocol State Diagram "
+"cache). The Protocol plugin is a state machine that flows through the "
+"states illustrated in the `Sample Protocol State Diagram "
"<#SampleProtocolStDiag>`_. This figure illustrates the steps that Traffic "
"Server and the Protocol plugin go through in order to support the sample "
"protocol."
@@ -53,8 +53,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:52
msgid ""
-"Listen for and accept client connections (on the accept port specified in "
-":file:`plugin.config`)"
+"Listen for and accept client connections (on the accept port specified in :"
+"file:`plugin.config`)"
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:55
@@ -104,10 +104,10 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:81
msgid ""
"To see how the Protocol plugin works, you need to understand some broader "
-"concepts. This section assumes you're familiar with the concepts of "
-":term:`continuation`, Traffic Server's **asynchronous event model**, and "
-"basic Traffic Server **plugin structure**. If you are not familiar with "
-"these concepts, then reference `Getting Started <../getting-"
+"concepts. This section assumes you're familiar with the concepts of :term:"
+"`continuation`, Traffic Server's **asynchronous event model**, and basic "
+"Traffic Server **plugin structure**. If you are not familiar with these "
+"concepts, then reference `Getting Started <../getting-"
"started#GettingStarted>`_ and `How to Create Traffic Server Plugins <../how-"
"to-create-trafficserver-plugins>`_"
msgstr ""
@@ -127,9 +127,9 @@ msgid ""
"transaction (where a :term:`transaction` consists of a client request and "
"Traffic Server's response). Each transaction state machine lives until the "
"transaction completes; then it is destroyed. If the client's request for "
-"content is a cache miss, then a transaction state machine might need to open"
-" a connection to the origin server. This is illustrated in the `Protocol "
-"Plugin Overview <#ProtocolPluginOverview>`__ diagram below."
+"content is a cache miss, then a transaction state machine might need to "
+"open a connection to the origin server. This is illustrated in the "
+"`Protocol Plugin Overview <#ProtocolPluginOverview>`__ diagram below."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:106
@@ -175,8 +175,8 @@ msgstr ""
msgid ""
"Implementing the rest of the Protocol plugin requires that you understand "
"the flow of events during the course of a transaction. Unlike HTTP "
-"transaction plugins, this plugin must read data from network connections and"
-" then read/write data to the Traffic Server cache. This means that its "
+"transaction plugins, this plugin must read data from network connections "
+"and then read/write data to the Traffic Server cache. This means that its "
"continuations do not receive HTTP state machine events; they receive events "
"from Traffic Server's processor subsystems. For example: the accept state "
"machine is activated by an ``TS_EVENT_NET_ACCEPT`` event from Traffic "
@@ -226,12 +226,12 @@ msgid ""
"Notice that this flow of events is independent of the Protocol plugin's "
"design (i.e., whether you build **accept** or **transaction** state "
"machines). Any plugin that supports network connections uses the net "
-"vconnection interfaces (``TSNetAccept``, ``TSNetConnect``) and thus receives"
-" events from the Net Processor. Any plugin that performs cache lookups or "
-"cache writes uses ``TSCacheRead``, ``TSCacheWrite``, ``TSVConnRead``, and "
-"``TSVConnWrite`` and thus receives events from the Cache Processor and "
-"Traffic Server event system. Similarly, any plugin that does DNS lookups "
-"receives events from the Host Database Processor."
+"vconnection interfaces (``TSNetAccept``, ``TSNetConnect``) and thus "
+"receives events from the Net Processor. Any plugin that performs cache "
+"lookups or cache writes uses ``TSCacheRead``, ``TSCacheWrite``, "
+"``TSVConnRead``, and ``TSVConnWrite`` and thus receives events from the "
+"Cache Processor and Traffic Server event system. Similarly, any plugin that "
+"does DNS lookups receives events from the Host Database Processor."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:182
@@ -240,8 +240,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:184
msgid ""
-"**Transaction state machines** (**TSMs**) in the Protocol plugin must do the"
-" following:"
+"**Transaction state machines** (**TSMs**) in the Protocol plugin must do "
+"the following:"
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:187
@@ -266,8 +266,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:197
msgid ""
-"Create a data structure for transactions that contains all of the state data"
-" you need to keep track of. In the Protocol plugin this is a struct, "
+"Create a data structure for transactions that contains all of the state "
+"data you need to keep track of. In the Protocol plugin this is a struct, "
"``Txn_SM``."
msgstr ""
@@ -289,8 +289,8 @@ msgstr ""
msgid ""
"Write the handler for the TSM. Its job is to receive events, examine the "
"current state, and execute the appropriate state handler function. In the "
-"Protocol plugin, the handler is ``main_handler``. ``main_handler`` calls the"
-" state handler functions to handle each state."
+"Protocol plugin, the handler is ``main_handler``. ``main_handler`` calls "
+"the state handler functions to handle each state."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:215
@@ -308,8 +308,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:222
msgid ""
-"**``main_handler``** examines the state of the transaction-in particular, it"
-" examines the current handler."
+"**``main_handler``** examines the state of the transaction-in particular, "
+"it examines the current handler."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:225
@@ -333,9 +333,10 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:238
msgid ""
"**``state2_handler``** arranges the next callback of the TSM. Typically, it "
-"gives Traffic Server additional work to do (such as writing a file to cache)"
-" so that it can progress to the next state. The TSM (**``main_handler``**) "
-"then waits for the next event to arrive from Traffic Server."
+"gives Traffic Server additional work to do (such as writing a file to "
+"cache) so that it can progress to the next state. The TSM "
+"(**``main_handler``**) then waits for the next event to arrive from Traffic "
+"Server."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:244
@@ -390,14 +391,14 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:274
msgid ""
"The **``init``** function creates the accept state machine using "
-"**``AcceptCreate``**. The code for **``AcceptCreate``** is in the "
-"``Accept.c`` file."
+"**``AcceptCreate``**. The code for **``AcceptCreate``** is in the ``Accept."
+"c`` file."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:278
msgid ""
-"The accept state machine, like the transaction state machine, keeps track of"
-" its state with a data structure. This data structure, **``Accept``**, is "
+"The accept state machine, like the transaction state machine, keeps track "
+"of its state with a data structure. This data structure, **``Accept``**, is "
"defined in the ``Accept.h`` file. State data in **``AcceptCreate``** is "
"associated with the new accept state machine via **``TSContDataSet``**."
msgstr ""
@@ -413,17 +414,17 @@ msgid ""
"The handler for the accept state machine is **``accept_event``** in the "
"``Accept.c`` file. When Traffic Server's Net Processor sends "
"**``TS_EVENT_NET_ACCEPT``** to the accept state machine, "
-"**``accept_event``** creates a transaction state machine (**``txn_sm``**) by"
-" calling **``TxnSMCreate``**. Notice that **``accept_event``** creates a "
+"**``accept_event``** creates a transaction state machine (**``txn_sm``**) "
+"by calling **``TxnSMCreate``**. Notice that **``accept_event``** creates a "
"mutex for the transaction state machine, since each transaction state "
"machine has its own mutex."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:296
msgid ""
-"The **``TxnSMCreate``** function is in the ``TxnSM.c`` file. The first thing"
-" it does is initialize the transaction's data, which is of type ``TxnSM`` "
-"(as defined in ``TxnSM.h``). Notice that the current handler "
+"The **``TxnSMCreate``** function is in the ``TxnSM.c`` file. The first "
+"thing it does is initialize the transaction's data, which is of type "
+"``TxnSM`` (as defined in ``TxnSM.h``). Notice that the current handler "
"(**``q_current_handler``**) is set to **``state_start``**."
msgstr ""
@@ -436,9 +437,9 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:306
msgid ""
-"When **``accept_event``** receives **``TS_EVENT_NET_ACCEPT``**, it calls the"
-" transaction state machine ( **``TSContCall (txn_sm, 0, NULL);``** ). The "
-"event passed to **``main_handler``** is ``0`` (**``TS_EVENT_NONE``**)."
+"When **``accept_event``** receives **``TS_EVENT_NET_ACCEPT``**, it calls "
+"the transaction state machine ( **``TSContCall (txn_sm, 0, NULL);``** ). "
+"The event passed to **``main_handler``** is ``0`` (**``TS_EVENT_NONE``**)."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:311
@@ -456,9 +457,9 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:319
msgid ""
-"The **``state_start``** handler function (in the ``TxnSM.c`` file) is handed"
-" an event (at this stage, the event is **``TS_EVENT_NET_ACCEPT``**) and a "
-"client vconnection. **``state_start``** checks to see if this client "
+"The **``state_start``** handler function (in the ``TxnSM.c`` file) is "
+"handed an event (at this stage, the event is **``TS_EVENT_NET_ACCEPT``**) "
+"and a client vconnection. **``state_start``** checks to see if this client "
"vconnection is closed; if it is not, then **``state_start``** attempts to "
"read data from the client vconnection into an **``TSIOBuffer``** "
"(**``state_start``** is handling the event it receives)."
@@ -473,9 +474,9 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:331
msgid ""
-"**``state_start``** initiates a read of the client vconnection (arranges for"
-" Traffic Server to send **``TS_EVENT_VCONN_READ_READY``** events to the TSM)"
-" by calling **``TSVConnRead``**."
+"**``state_start``** initiates a read of the client vconnection (arranges "
+"for Traffic Server to send **``TS_EVENT_VCONN_READ_READY``** events to the "
+"TSM) by calling **``TSVConnRead``**."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:336
@@ -504,8 +505,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:350
msgid ""
-"**``state_read_request_from_client``** updates the current state to the next"
-" state, **``state_handle_cache_lookup``** ."
+"**``state_read_request_from_client``** updates the current state to the "
+"next state, **``state_handle_cache_lookup``** ."
msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:353
@@ -517,7 +518,8 @@ msgstr ""
#: ../../sdk/new-protocol-plugins.en.rst:357
msgid ""
-"When the **``TSCacheRead``** sends the TSM either **``TS_EVENT_OPEN_READ``**"
-" (a cache hit) or **``TS_EVENT_OPEN_READ_FAILED``** (a cache miss), "
-"**``main_handler``** calls **``state_handle_cache_lookup``**."
+"When the **``TSCacheRead``** sends the TSM either "
+"**``TS_EVENT_OPEN_READ``** (a cache hit) or "
+"**``TS_EVENT_OPEN_READ_FAILED``** (a cache miss), **``main_handler``** "
+"calls **``state_handle_cache_lookup``**."
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/plugin-configurations.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/plugin-configurations.en.po b/doc/locale/ja/LC_MESSAGES/sdk/plugin-configurations.en.po
index dc6cb4a..4018566 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/plugin-configurations.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/plugin-configurations.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"
@@ -30,21 +30,20 @@ msgstr ""
msgid ""
"The functions discussed in this section do not examine or modify Traffic "
"Server configuration variables. To examine Traffic Server configuration and "
-"statistics variables, see `\"Reading Traffic Server Settings and "
-"Statistics\" <../plugin-management/reading-trafficserver-settings-and-"
-"statistics>`__"
+"statistics variables, see `\"Reading Traffic Server Settings and Statistics"
+"\" <../plugin-management/reading-trafficserver-settings-and-statistics>`__"
msgstr ""
#: ../../sdk/plugin-configurations.en.rst:37
msgid ""
"The ``TSConfig`` family of functions is designed to provide a fast and "
"efficient mechanism for accessing and changing global configuration "
-"information within a plugin. Such a mechanism is simple enough to provide in"
-" a single-threaded program, but the translation to a multi-threaded program "
-"such as Traffic Server is difficult. A common technique is to have a single "
-"mutex protect the global configuration information; however, the problem "
-"with this solution is that a single mutex becomes a performance bottleneck "
-"very quickly."
+"information within a plugin. Such a mechanism is simple enough to provide "
+"in a single-threaded program, but the translation to a multi-threaded "
+"program such as Traffic Server is difficult. A common technique is to have "
+"a single mutex protect the global configuration information; however, the "
+"problem with this solution is that a single mutex becomes a performance "
+"bottleneck very quickly."
msgstr ""
#: ../../sdk/plugin-configurations.en.rst:46
@@ -54,8 +53,8 @@ msgid ""
"reference count information about the data pointer so that a call to "
"``TSConfigSet`` will not disturb another thread using the current data "
"pointer. The philosophy is that once a user has a hold of the configuration "
-"pointer, it is okay for it to be used even if the configuration changes; all"
-" that a user typically wants is a non-changing snapshot of the "
+"pointer, it is okay for it to be used even if the configuration changes; "
+"all that a user typically wants is a non-changing snapshot of the "
"configuration. You should use ``TSConfigSet`` for all global data updates."
msgstr ""
@@ -69,24 +68,24 @@ msgstr ""
#: ../../sdk/plugin-configurations.en.rst:108
msgid ""
-"```TSConfigDataGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#aed2a6f9d350935ac890f75fdd80605db>`__"
+"```TSConfigDataGet`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#aed2a6f9d350935ac890f75fdd80605db>`__"
msgstr ""
#: ../../sdk/plugin-configurations.en.rst:110
msgid ""
-"```TSConfigGet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a478189d6ad87c6b873d8676cb51508c5>`__"
+"```TSConfigGet`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a478189d6ad87c6b873d8676cb51508c5>`__"
msgstr ""
#: ../../sdk/plugin-configurations.en.rst:112
msgid ""
-"```TSConfigRelease`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a06711d4a0e70f1ff27f9b5ca34bb649c>`__"
+"```TSConfigRelease`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a06711d4a0e70f1ff27f9b5ca34bb649c>`__"
msgstr ""
#: ../../sdk/plugin-configurations.en.rst:114
msgid ""
-"```TSConfigSet`` "
-"<http://people.apache.org/~amc/ats/doc/html/ts_8h.html#a8bba9468fdca478e68035a9776f6e9ca>`__"
+"```TSConfigSet`` <http://people.apache.org/~amc/ats/doc/html/ts_8h."
+"html#a8bba9468fdca478e68035a9776f6e9ca>`__"
msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/sdk/plugin-management.en.po
----------------------------------------------------------------------
diff --git a/doc/locale/ja/LC_MESSAGES/sdk/plugin-management.en.po b/doc/locale/ja/LC_MESSAGES/sdk/plugin-management.en.po
index b122997..592d92e 100644
--- a/doc/locale/ja/LC_MESSAGES/sdk/plugin-management.en.po
+++ b/doc/locale/ja/LC_MESSAGES/sdk/plugin-management.en.po
@@ -1,4 +1,4 @@
-#
+#
msgid ""
msgstr ""
"Project-Id-Version: Apache Traffic Server 4.1\n"