http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po ---------------------------------------------------------------------- diff --git a/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po b/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po index bfd904a..d1d39b8 100644 --- a/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po +++ b/doc/locale/ja/LC_MESSAGES/admin/working-log-files.en.po @@ -1,4 +1,4 @@ -# +# msgid "" msgstr "" "Project-Id-Version: Apache Traffic Server 4.1\n" @@ -50,36 +50,36 @@ msgstr "" #: ../../admin/working-log-files.en.rst:50 msgid "" -"**System log files** record system information, including messages about the" -" state of Traffic Server and errors/warnings it produces. This kind of " -"information might include a note that event log files were rolled, a warning" -" that cluster communication timed out, or an error indicating that Traffic " -"Server was restarted." +"**System log files** record system information, including messages about " +"the state of Traffic Server and errors/warnings it produces. This kind of " +"information might include a note that event log files were rolled, a " +"warning that cluster communication timed out, or an error indicating that " +"Traffic Server was restarted." msgstr "" #: ../../admin/working-log-files.en.rst:56 msgid "" "All system information messages are logged with the system-wide logging " -"facility :manpage:`syslog` under the daemon facility. The " -":manpage:`syslog.conf(5)` configuration file (stored in the ``/etc`` " -"directory) specifies where these messages are logged. A typical location is " -"``/var/log/messages`` (Linux)." +"facility :manpage:`syslog` under the daemon facility. The :manpage:`syslog." +"conf(5)` configuration file (stored in the ``/etc`` directory) specifies " +"where these messages are logged. A typical location is ``/var/log/" +"messages`` (Linux)." msgstr "" #: ../../admin/working-log-files.en.rst:62 msgid "" "The :manpage:`syslog(8)` process works on a system-wide basis, so it serves " "as the single repository for messages from all Traffic Server processes " -"(including :program:`traffic_server`, :program:`traffic_manager`, and " -":program:`traffic_cop`)." +"(including :program:`traffic_server`, :program:`traffic_manager`, and :" +"program:`traffic_cop`)." msgstr "" #: ../../admin/working-log-files.en.rst:67 msgid "" "System information logs observe a static format. Each log entry in the log " "contains information about the date and time the error was logged, the " -"hostname of the Traffic Server that reported the error, and a description of" -" the error or warning." +"hostname of the Traffic Server that reported the error, and a description " +"of the error or warning." msgstr "" #: ../../admin/working-log-files.en.rst:72 @@ -92,9 +92,9 @@ msgstr "" msgid "" "By default, Traffic Server creates both error and event log files and " "records system information in system log files. You can disable event " -"logging and/or error logging by setting the configuration variable " -":ts:cv:`proxy.config.log.logging_enabled` (in the :file:`records.config` " -"file) to one of the following values:" +"logging and/or error logging by setting the configuration variable :ts:cv:" +"`proxy.config.log.logging_enabled` (in the :file:`records.config` file) to " +"one of the following values:" msgstr "" #: ../../admin/working-log-files.en.rst:81 @@ -120,15 +120,16 @@ msgstr "" #: ../../admin/working-log-files.en.rst:89 msgid "" "Event log files record information about every request that Traffic Server " -"processes. By analyzing the log files, you can determine how many people use" -" the Traffic Server cache, how much information each person requested, what " -"pages are most popular, and so on. Traffic Server supports several standard " -"log file formats, such as Squid and Netscape, as well as user-defined custom" -" formats. You can analyze the standard format log files with off-the-shelf " -"analysis packages. To help with log file analysis, you can separate log " -"files so they contain information specific to protocol or hosts. You can " -"also configure Traffic Server to roll log files automatically at specific " -"intervals during the day or when they reach a certain size." +"processes. By analyzing the log files, you can determine how many people " +"use the Traffic Server cache, how much information each person requested, " +"what pages are most popular, and so on. Traffic Server supports several " +"standard log file formats, such as Squid and Netscape, as well as user-" +"defined custom formats. You can analyze the standard format log files with " +"off-the-shelf analysis packages. To help with log file analysis, you can " +"separate log files so they contain information specific to protocol or " +"hosts. You can also configure Traffic Server to roll log files " +"automatically at specific intervals during the day or when they reach a " +"certain size." msgstr "" #: ../../admin/working-log-files.en.rst:101 @@ -144,8 +145,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:106 msgid "" "You can choose a central location for storing log files, set how much disk " -"space to use for log files, and set how and when to roll log files. Refer to" -" `Managing Event Log Files`_." +"space to use for log files, and set how and when to roll log files. Refer " +"to `Managing Event Log Files`_." msgstr "" #: ../../admin/working-log-files.en.rst:110 @@ -192,9 +193,9 @@ msgstr "" #: ../../admin/working-log-files.en.rst:133 msgid "" "Designate one or more nodes on the network to serve as log collation " -"servers. These servers, which might be standalone or part of Traffic Server," -" enable you to keep all logged information in well-defined locations. Refer " -"to `Collating Event Log Files`_." +"servers. These servers, which might be standalone or part of Traffic " +"Server, enable you to keep all logged information in well-defined " +"locations. Refer to `Collating Event Log Files`_." msgstr "" #: ../../admin/working-log-files.en.rst:138 @@ -255,21 +256,22 @@ msgstr "" #: ../../admin/working-log-files.en.rst:172 msgid "" "If the autodelete option (discussed in `Rolling Event Log Files`_) is " -"*enabled*, then Traffic Server identifies previously-rolled log files (i.e.," -" log files with the ``.old`` extension). It starts deleting files one by " +"*enabled*, then Traffic Server identifies previously-rolled log files (i." +"e., log files with the ``.old`` extension). It starts deleting files one by " "one, beginning with the oldest file, until it emerges from the low state. " "Traffic Server logs a record of all deleted files in the system error log." msgstr "" #: ../../admin/working-log-files.en.rst:179 msgid "" -"If the autodelete option is *disabled* or there are not enough old log files" -" to delete for the system to emerge from its low space state, then Traffic " -"Server issues a warning and continues logging until space is exhausted. When" -" available space is consumed, event logging stops. Traffic Server resumes " -"event logging when enough space becomes available for it to exit the low " -"space state. To make space available, either explicitly increase the logging" -" space limit or remove files from the logging directory manually." +"If the autodelete option is *disabled* or there are not enough old log " +"files to delete for the system to emerge from its low space state, then " +"Traffic Server issues a warning and continues logging until space is " +"exhausted. When available space is consumed, event logging stops. Traffic " +"Server resumes event logging when enough space becomes available for it to " +"exit the low space state. To make space available, either explicitly " +"increase the logging space limit or remove files from the logging directory " +"manually." msgstr "" #: ../../admin/working-log-files.en.rst:188 @@ -362,8 +364,8 @@ msgstr "" msgid "" "The standard log formats include Squid, Netscape Common, Netscape extended, " "and Netscape Extended-2. The standard log file formats can be analyzed with " -"a wide variety of off-the-shelf log-analysis packages. You should use one of" -" the standard event log formats unless you need information that these " +"a wide variety of off-the-shelf log-analysis packages. You should use one " +"of the standard event log formats unless you need information that these " "formats do not provide. Refer to `Using the Custom Format`_." msgstr "" @@ -461,18 +463,19 @@ msgid "" "formats and gives you more control over the type of information recorded in " "log files. You should create a custom log format if you need data for " "analysis that's not available in the standard formats. You can decide what " -"information to record for each Traffic Server transaction and create filters" -" that specify which transactions to log." +"information to record for each Traffic Server transaction and create " +"filters that specify which transactions to log." msgstr "" #: ../../admin/working-log-files.en.rst:284 msgid "" "The heart of the XML-based custom logging feature is the XML-based logging " -"configuration file (:file:`logs_xml.config`) that enables you to create very" -" modular descriptions of logging objects. The :file:`logs_xml.config` file " -"uses three types of objects to create custom log files, as detailed below. " -"To generate a custom log format, you must specify at least one ``LogObject``" -" definition (one log file is produced for each ``LogObject`` definition)." +"configuration file (:file:`logs_xml.config`) that enables you to create " +"very modular descriptions of logging objects. The :file:`logs_xml.config` " +"file uses three types of objects to create custom log files, as detailed " +"below. To generate a custom log format, you must specify at least one " +"``LogObject`` definition (one log file is produced for each ``LogObject`` " +"definition)." msgstr "" #: ../../admin/working-log-files.en.rst:292 @@ -505,8 +508,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:302 msgid "" -"a previously-defined custom format (i.e., a previously-defined ``LogFormat``" -" object)." +"a previously-defined custom format (i.e., a previously-defined " +"``LogFormat`` object)." msgstr "" #: ../../admin/working-log-files.en.rst:304 @@ -515,9 +518,9 @@ msgid "" "``ASCII``. The ``ASCII_PIPE`` mode writes log entries to a UNIX-named pipe " "(a buffer in memory); other processes can then read the data using standard " "I/O functions. The advantage of this option is that Traffic Server does not " -"have to write to disk, which frees disk space and bandwidth for other tasks." -" When the buffer is full, Traffic Server drops log entries and issues an " -"error message indicating how many entries were dropped. Because Traffic " +"have to write to disk, which frees disk space and bandwidth for other " +"tasks. When the buffer is full, Traffic Server drops log entries and issues " +"an error message indicating how many entries were dropped. Because Traffic " "Server only writes complete log entries to the pipe, only full records are " "dropped." msgstr "" @@ -574,8 +577,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:337 msgid "" -"Add :ref:`LogFormat`, :ref:`LogFilters`, and :ref:`LogObject` specifications" -" to the configuration file." +"Add :ref:`LogFormat`, :ref:`LogFilters`, and :ref:`LogObject` " +"specifications to the configuration file." msgstr "" #: ../../admin/working-log-files.en.rst:339 @@ -596,9 +599,9 @@ msgstr "" msgid "" "Traffic Server performs several hundred operations per second; therefore, " "event log files can quickly grow to large sizes. Using SQL-like aggregate " -"operators, you can configure Traffic Server to create summary log files that" -" summarize a set of log entries over a specified period of time. This can " -"significantly reduce the size of the log files generated." +"operators, you can configure Traffic Server to create summary log files " +"that summarize a set of log entries over a specified period of time. This " +"can significantly reduce the size of the log files generated." msgstr "" #: ../../admin/working-log-files.en.rst:353 @@ -663,8 +666,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:402 msgid "" "You cannot create a format specification that contains both aggregate " -"operators and regular fields. For example, the following specification would" -" be **invalid**: ::" +"operators and regular fields. For example, the following specification " +"would be **invalid**: ::" msgstr "" #: ../../admin/working-log-files.en.rst:409 @@ -699,8 +702,8 @@ msgid "" "These files generate lower system overhead and generally occupy less space " "on the disk than ASCII files (depending on the type of information being " "logged). However, you must use a converter application before you can read " -"or analyze binary files via standard tools. By default, binary log files use" -" a ``.blog`` filename extension." +"or analyze binary files via standard tools. By default, binary log files " +"use a ``.blog`` filename extension." msgstr "" #: ../../admin/working-log-files.en.rst:432 @@ -713,31 +716,30 @@ msgstr "" msgid "" "For example: the value ``0`` (zero) requires only one byte to store in " "ASCII, but requires four bytes when stored as a binary integer. Conversely: " -"if you define a custom format that logs IP addresses, then a binary log file" -" would only require four bytes of storage per 32-bit address. However, the " -"same IP address stored in dot notation would require around 15 characters " -"(bytes) in an ASCII log file. Therefore, it's wise to consider the type of " -"data that will be logged before you select ASCII or binary for your log " -"files. For example, you might try logging for one day using ASCII and then " -"another day using binary. If the number of requests is roughly the same for " -"both days, then you can calculate a rough metric that compares the two " -"formats." +"if you define a custom format that logs IP addresses, then a binary log " +"file would only require four bytes of storage per 32-bit address. However, " +"the same IP address stored in dot notation would require around 15 " +"characters (bytes) in an ASCII log file. Therefore, it's wise to consider " +"the type of data that will be logged before you select ASCII or binary for " +"your log files. For example, you might try logging for one day using ASCII " +"and then another day using binary. If the number of requests is roughly the " +"same for both days, then you can calculate a rough metric that compares the " +"two formats." msgstr "" #: ../../admin/working-log-files.en.rst:447 msgid "" -"For standard log formats, select Binary or ASCII (refer to `Setting Standard" -" Log File Format Options`). For the custom log format, specify ASCII or " -"Binary mode in the :ref:`LogObject` (refer to :ref:`Using the Custom Format " -"<using-custom-log-formats>`). In addition to the ASCII and binary options, " -"you can also write custom log entries to a UNIX-named pipe (i.e., a buffer " -"in memory). Other processes can then read the data using standard I/O " -"functions. The advantage of using this option is that Traffic Server does " -"not have to write to disk, which frees disk space and bandwidth for other " -"tasks. In addition, writing to a pipe does not stop when logging space is " -"exhausted because the pipe does not use disk space. Refer to " -":file:`logs_xml.config` for more information about the ``ASCII_PIPE`` " -"option." +"For standard log formats, select Binary or ASCII (refer to `Setting " +"Standard Log File Format Options`). For the custom log format, specify " +"ASCII or Binary mode in the :ref:`LogObject` (refer to :ref:`Using the " +"Custom Format <using-custom-log-formats>`). In addition to the ASCII and " +"binary options, you can also write custom log entries to a UNIX-named pipe " +"(i.e., a buffer in memory). Other processes can then read the data using " +"standard I/O functions. The advantage of using this option is that Traffic " +"Server does not have to write to disk, which frees disk space and bandwidth " +"for other tasks. In addition, writing to a pipe does not stop when logging " +"space is exhausted because the pipe does not use disk space. Refer to :file:" +"`logs_xml.config` for more information about the ``ASCII_PIPE`` option." msgstr "" #: ../../admin/working-log-files.en.rst:463 @@ -781,10 +783,10 @@ msgstr "" #: ../../admin/working-log-files.en.rst:484 msgid "" -"Traffic Server provides a consistent naming scheme for rolled log files that" -" enables you to easily identify log files. When Traffic Server rolls a log " -"file, it saves and closes the old file before it starts a new file. Traffic " -"Server renames the old file to include the following information:" +"Traffic Server provides a consistent naming scheme for rolled log files " +"that enables you to easily identify log files. When Traffic Server rolls a " +"log file, it saves and closes the old file before it starts a new file. " +"Traffic Server renames the old file to include the following information:" msgstr "" #: ../../admin/working-log-files.en.rst:490 @@ -881,8 +883,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:538 msgid "" -"For example, suppose logs are rolled every three hours, and the first rolled" -" log file is: ::" +"For example, suppose logs are rolled every three hours, and the first " +"rolled log file is: ::" msgstr "" #: ../../admin/working-log-files.en.rst:543 @@ -955,11 +957,11 @@ msgstr "" #: ../../admin/working-log-files.en.rst:586 msgid "" -"You can fine-tune log file rolling settings for a custom log file in the " -":ref:`LogObject` specification in the :file:`logs_xml.config` file. The " +"You can fine-tune log file rolling settings for a custom log file in the :" +"ref:`LogObject` specification in the :file:`logs_xml.config` file. The " "custom log file uses the rolling settings in its :ref:`LogObject`, which " -"override the default settings you specify in Traffic Manager or the " -":file:`records.config` file described above." +"override the default settings you specify in Traffic Manager or the :file:" +"`records.config` file described above." msgstr "" #: ../../admin/working-log-files.en.rst:596 @@ -968,9 +970,9 @@ msgstr "" #: ../../admin/working-log-files.en.rst:598 msgid "" -"By default, Traffic Server uses standard log formats and generates log files" -" that contain HTTP & ICP transactions in the same file. However, you can " -"enable log splitting if you prefer to log transactions for different " +"By default, Traffic Server uses standard log formats and generates log " +"files that contain HTTP & ICP transactions in the same file. However, you " +"can enable log splitting if you prefer to log transactions for different " "protocols in separate log files." msgstr "" @@ -994,14 +996,14 @@ msgstr "" #: ../../admin/working-log-files.en.rst:616 msgid "" "HTTP host log splitting enables you to record HTTP transactions for " -"different origin servers in separate log files. When HTTP host log splitting" -" is enabled, Traffic Server creates a separate log file for each origin " -"server that's listed in the :file:`log_hosts.config` file. When both ICP and" -" HTTP host log splitting are enabled, Traffic Server generates separate log " -"files for HTTP transactions (based on the origin server) and places all ICP " -"transactions in their own respective log files. For example, if the " -":file:`log_hosts.config` file contains the two origin servers ``uni.edu`` " -"and ``company.com`` and Squid format is enabled, then Traffic Server " +"different origin servers in separate log files. When HTTP host log " +"splitting is enabled, Traffic Server creates a separate log file for each " +"origin server that's listed in the :file:`log_hosts.config` file. When both " +"ICP and HTTP host log splitting are enabled, Traffic Server generates " +"separate log files for HTTP transactions (based on the origin server) and " +"places all ICP transactions in their own respective log files. For example, " +"if the :file:`log_hosts.config` file contains the two origin servers ``uni." +"edu`` and ``company.com`` and Squid format is enabled, then Traffic Server " "generates the following log files:" msgstr "" @@ -1061,9 +1063,9 @@ msgstr "" #: ../../admin/working-log-files.en.rst:652 msgid "" -"Traffic Server also enables you to create XML-based :ref:`Custom Log Formats" -" <using-custom-log-formats>` that offer even greater control over log file " -"generation." +"Traffic Server also enables you to create XML-based :ref:`Custom Log " +"Formats <using-custom-log-formats>` that offer even greater control over " +"log file generation." msgstr "" #: ../../admin/working-log-files.en.rst:656 @@ -1091,10 +1093,10 @@ msgid "" "The default :file:`log_hosts.config` file is located in the Traffic Server " "``config`` directory. To record HTTP transactions for different origin " "servers in separate log files, you must specify the hostname of each origin " -"server on a separate line in the :file:`log_hosts.config` file. For example," -" if you specify the keyword sports, then Traffic Server records all HTTP " -"transactions from ``sports.yahoo.com`` and ``www.foxsports.com`` in a log " -"file called ``squid-sports.log`` (if the Squid format is enabled)." +"server on a separate line in the :file:`log_hosts.config` file. For " +"example, if you specify the keyword sports, then Traffic Server records all " +"HTTP transactions from ``sports.yahoo.com`` and ``www.foxsports.com`` in a " +"log file called ``squid-sports.log`` (if the Squid format is enabled)." msgstr "" #: ../../admin/working-log-files.en.rst:682 @@ -1124,19 +1126,20 @@ msgid "" "logged information in one place. Log collation enables you to analyze a set " "of Traffic Server clustered nodes as a whole (rather than as individual " "nodes) and to use a large disk that might only be located on one of the " -"nodes in the cluster. Traffic Server collates log files by using one or more" -" nodes as log collation servers and all remaining nodes as log collation " -"clients. When a Traffic Server node generates a buffer of event log entries," -" it first determines if it is the collation server or a collation client. " -"The collation server node writes all log buffers to its local disk, just as " -"it would if log collation was not enabled. Log collation servers can be " -"standalone or they can be part of a node running Traffic Server." +"nodes in the cluster. Traffic Server collates log files by using one or " +"more nodes as log collation servers and all remaining nodes as log " +"collation clients. When a Traffic Server node generates a buffer of event " +"log entries, it first determines if it is the collation server or a " +"collation client. The collation server node writes all log buffers to its " +"local disk, just as it would if log collation was not enabled. Log " +"collation servers can be standalone or they can be part of a node running " +"Traffic Server." msgstr "" #: ../../admin/working-log-files.en.rst:715 msgid "" -"The collation client nodes prepare their log buffers for transfer across the" -" network and send the buffers to the log collation server. When the log " +"The collation client nodes prepare their log buffers for transfer across " +"the network and send the buffers to the log collation server. When the log " "collation server receives a log buffer from a client, it writes it to its " "own log file as if it was generated locally. For a visual representation of " "this, see the figure below." @@ -1158,15 +1161,15 @@ msgid "" "Log collation can have an impact on network performance. Because all nodes " "are forwarding their log data buffers to the single collation server, a " "bottleneck can occur. In addition, collated log files contain timestamp " -"information for each entry, but entries in the files do not appear in strict" -" chronological order. You may want to sort collated log files before doing " -"analysis." +"information for each entry, but entries in the files do not appear in " +"strict chronological order. You may want to sort collated log files before " +"doing analysis." msgstr "" #: ../../admin/working-log-files.en.rst:740 msgid "" -"To configure Traffic Server to collate event log files, you must perform the" -" following tasks:" +"To configure Traffic Server to collate event log files, you must perform " +"the following tasks:" msgstr "" #: ../../admin/working-log-files.en.rst:743 @@ -1184,9 +1187,9 @@ msgstr "" #: ../../admin/working-log-files.en.rst:748 msgid "" -"Add an attribute to the :ref:`LogObject` specification in the " -":file:`logs_xml.config` file if you are using custom log file formats; refer" -" to `Collating Custom Event Log Files`_." +"Add an attribute to the :ref:`LogObject` specification in the :file:" +"`logs_xml.config` file if you are using custom log file formats; refer to " +"`Collating Custom Event Log Files`_." msgstr "" #: ../../admin/working-log-files.en.rst:756 @@ -1219,9 +1222,9 @@ msgstr "" #: ../../admin/working-log-files.en.rst:772 msgid "" -"If you modify the ``collation_port`` or ``secret`` after connections between" -" the collation server and collation clients have been established, then you " -"must restart Traffic Server." +"If you modify the ``collation_port`` or ``secret`` after connections " +"between the collation server and collation clients have been established, " +"then you must restart Traffic Server." msgstr "" #: ../../admin/working-log-files.en.rst:777 @@ -1260,8 +1263,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:793 msgid "" -"Create a directory called ``config`` in the directory that contains the " -":program:`traffic_sac` binary." +"Create a directory called ``config`` in the directory that contains the :" +"program:`traffic_sac` binary." msgstr "" #: ../../admin/working-log-files.en.rst:795 @@ -1274,11 +1277,11 @@ msgstr "" #: ../../admin/working-log-files.en.rst:798 msgid "" "Copy the :file:`records.config` file from a Traffic Server node configured " -"to be a log collation client to the ``config`` directory you created in Step" -" 4 on the standalone collator. The :file:`records.config` file contains the " -"log collation secret and the port you specified when configuring Traffic " -"Server nodes to be collation clients. The collation port and secret must be " -"the same for all collation clients and servers." +"to be a log collation client to the ``config`` directory you created in " +"Step 4 on the standalone collator. The :file:`records.config` file contains " +"the log collation secret and the port you specified when configuring " +"Traffic Server nodes to be collation clients. The collation port and secret " +"must be the same for all collation clients and servers." msgstr "" #: ../../admin/working-log-files.en.rst:805 @@ -1297,8 +1300,8 @@ msgstr "" msgid "" "To configure a Traffic Server node to be a collation client, follow the " "steps below. If you modify the ``collation_port`` or ``secret`` after " -"connections between the collation clients and the collation server have been" -" established, then you must restart Traffic Server." +"connections between the collation clients and the collation server have " +"been established, then you must restart Traffic Server." msgstr "" #: ../../admin/working-log-files.en.rst:822 @@ -1307,10 +1310,11 @@ msgstr "" #: ../../admin/working-log-files.en.rst:824 msgid "" -":ts:cv:`proxy.local.log.collation_mode`: ``2`` to configure this node as log" -" collation client and send standard formatted log entries to the collation " -"server. For XML-based formatted log entries, see :file:`logs_xml.config` " -"file; refer to :ref:`Using the Custom Format <using-custom-log-formats>`." +":ts:cv:`proxy.local.log.collation_mode`: ``2`` to configure this node as " +"log collation client and send standard formatted log entries to the " +"collation server. For XML-based formatted log entries, see :file:`logs_xml." +"config` file; refer to :ref:`Using the Custom Format <using-custom-log-" +"formats>`." msgstr "" #: ../../admin/working-log-files.en.rst:828 @@ -1331,9 +1335,9 @@ msgstr "" #: ../../admin/working-log-files.en.rst:840 msgid "" -"If you use custom event log files, then you must edit the " -":file:`logs_xml.config` file (in addition to configuring a collation server " -"and collation clients)." +"If you use custom event log files, then you must edit the :file:`logs_xml." +"config` file (in addition to configuring a collation server and collation " +"clients)." msgstr "" #: ../../admin/working-log-files.en.rst:844 @@ -1346,23 +1350,23 @@ msgstr "" #: ../../admin/working-log-files.en.rst:847 msgid "" -"Add the :ref:`CollationHost <logs-xml-logobject-collationhost>` attribute to" -" the :ref:`LogObject` specification: ::" +"Add the :ref:`CollationHost <logs-xml-logobject-collationhost>` attribute " +"to the :ref:`LogObject` specification: ::" msgstr "" #: ../../admin/working-log-files.en.rst:858 msgid "" -"where ``ipaddress`` is the hostname or IP address of the collation server to" -" which all log entries (for this object) are forwarded, and ``port`` is the " -"port number for communication between the collation server and collation " -"clients." +"where ``ipaddress`` is the hostname or IP address of the collation server " +"to which all log entries (for this object) are forwarded, and ``port`` is " +"the port number for communication between the collation server and " +"collation clients." msgstr "" #: ../../admin/working-log-files.en.rst:863 msgid "" "Run the command :option:`traffic_line -L` to restart Traffic Server on the " -"local node or :option:`traffic_line -M` to restart Traffic Server on all the" -" nodes in a cluster." +"local node or :option:`traffic_line -M` to restart Traffic Server on all " +"the nodes in a cluster." msgstr "" #: ../../admin/working-log-files.en.rst:868 @@ -1407,8 +1411,8 @@ msgstr "" #: ../../admin/working-log-files.en.rst:885 msgid "" -"You can retrieve the statistics via the Traffic Line command-line interface;" -" refer to `Monitoring Traffic <../monitoring-traffic>`_." +"You can retrieve the statistics via the Traffic Line command-line " +"interface; refer to `Monitoring Traffic <../monitoring-traffic>`_." msgstr "" #: ../../admin/working-log-files.en.rst:889 @@ -1432,7 +1436,7 @@ msgstr "" #: ../../admin/working-log-files.en.rst:901 msgid "" "If you need any assistance building your event log, you can try out our " -"`online log builder <http://trafficserver.apache.org/logbuilder/>`_. This is" -" a work in progress, so any comments, critique or suggestions are most " +"`online log builder <http://trafficserver.apache.org/logbuilder/>`_. This " +"is a work in progress, so any comments, critique or suggestions are most " "welcome." msgstr ""
http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po ---------------------------------------------------------------------- diff --git a/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po b/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po index 17a28be..78f9300 100644 --- a/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po +++ b/doc/locale/ja/LC_MESSAGES/admin/working-log-files/log-formats.en.po @@ -1,4 +1,4 @@ -# +# msgid "" msgstr "" "Project-Id-Version: Apache Traffic Server 4.1\n" @@ -136,8 +136,8 @@ msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:84 msgid "" -"``psct`` The proxy response content type; the object content type taken from" -" the Traffic Server response header." +"``psct`` The proxy response content type; the object content type taken " +"from the Traffic Server response header." msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:88 @@ -283,8 +283,8 @@ msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:195 msgid "" -"``phr`` The proxy hierarchy route; the route Traffic Server used to retrieve" -" the object." +"``phr`` The proxy hierarchy route; the route Traffic Server used to " +"retrieve the object." msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:203 @@ -303,9 +303,9 @@ msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:206 msgid "" -"``pfsc`` The proxy finish status code: ``FIN`` if the Traffic Server request" -" to the origin server completed successfully or ``INTR`` if the request was " -"interrupted." +"``pfsc`` The proxy finish status code: ``FIN`` if the Traffic Server " +"request to the origin server completed successfully or ``INTR`` if the " +"request was interrupted." msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:215 @@ -314,9 +314,9 @@ msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:212 msgid "" -"``crc`` The cache result code; how the Traffic Server cache responded to the" -" request: HIT, MISS, and so on. Cache result codes are described :ref:`here " -"<squid-netscape-result-codes>`." +"``crc`` The cache result code; how the Traffic Server cache responded to " +"the request: HIT, MISS, and so on. Cache result codes are described :ref:" +"`here <squid-netscape-result-codes>`." msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:220 @@ -487,8 +487,8 @@ msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:351 msgid "" -"The Domain Name Server (DNS) could not resolve the origin server name, or no" -" DNS could be reached." +"The Domain Name Server (DNS) could not resolve the origin server name, or " +"no DNS could be reached." msgstr "" #: ../../admin/working-log-files/log-formats.en.rst:356 http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po ---------------------------------------------------------------------- diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po index ca66d40..605146e 100644 --- a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-api.en.po @@ -1,4 +1,4 @@ -# +# msgid "" msgstr "" "Project-Id-Version: Apache Traffic Server 4.1\n" @@ -43,6 +43,6 @@ msgstr "" #: ../../arch/cache/cache-api.en.rst:42 msgid "" -"A preprocessor macro which computes the block size multiplier for a struct " -":cpp:class:`Dir` where *big* is the *big* field value." +"A preprocessor macro which computes the block size multiplier for a struct :" +"cpp:class:`Dir` where *big* is the *big* field value." msgstr "" http://git-wip-us.apache.org/repos/asf/trafficserver/blob/2f9f2fa3/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po ---------------------------------------------------------------------- diff --git a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po index 39a8207..3cd64fe 100644 --- a/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po +++ b/doc/locale/ja/LC_MESSAGES/arch/cache/cache-appendix.en.po @@ -1,4 +1,4 @@ -# +# msgid "" msgstr "" "Project-Id-Version: Apache Traffic Server 4.1\n" @@ -48,22 +48,22 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:40 msgid "" -"The cache validates that all the data for the document is available and will" -" silently mark a partial document as a \"miss\" on read. There is no " +"The cache validates that all the data for the document is available and " +"will silently mark a partial document as a \"miss\" on read. There is no " "\"gentle\" shutdown for traffic server, you just kill the process, so the " "\"recovery\" code (fsck) is run every time traffic server starts up." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:42 msgid "" -"On startup the two versions of the index are checked, and the last valid one" -" is read into memory. Then traffic server moves forward from the last " +"On startup the two versions of the index are checked, and the last valid " +"one is read into memory. Then traffic server moves forward from the last " "snapped write cursor and reads all the fragments written to disk, and " "updates the directory (as in a log-based file system). It stops reading at " "the write before the last valid write header it sees (as a write is not " -"necessarily atomic because of sector reordering). Then the new updated index" -" is written to the invalid version (in case of a crash during startup) and " -"the system starts." +"necessarily atomic because of sector reordering). Then the new updated " +"index is written to the invalid version (in case of a crash during startup) " +"and the system starts." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:47 @@ -73,14 +73,13 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:49 msgid "" "Currently cache volumes are allocated somewhat arbitrarily from storage " -"elements. `This enhancement " -"<https://issues.apache.org/jira/browse/TS-1728>`__ allows the " -":file:`storage.config` file to assign storage units to specific volumes " -"although the volumes must still be listed in :file:`volume.config` in " -"general and in particular to map domains to specific volumes. A primary use " -"case for this is to be able to map specific types of content to different " -"storage elements. This could to have different storage devices for the " -"content (SSD vs. rotational)." +"elements. `This enhancement <https://issues.apache.org/jira/browse/"; +"TS-1728>`__ allows the :file:`storage.config` file to assign storage units " +"to specific volumes although the volumes must still be listed in :file:" +"`volume.config` in general and in particular to map domains to specific " +"volumes. A primary use case for this is to be able to map specific types of " +"content to different storage elements. This could to have different storage " +"devices for the content (SSD vs. rotational)." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:53 @@ -102,8 +101,8 @@ msgstr "" msgid "" "The cache key is by default the URL of the request. There are two possible " "choices, the original (\"pristine\") URL and the remapped URL. Which of " -"these is used is determined by the configuration value " -":ts:cv:`proxy.config.url_remap.pristine_host_hdr`." +"these is used is determined by the configuration value :ts:cv:`proxy." +"config.url_remap.pristine_host_hdr`." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:65 @@ -112,8 +111,8 @@ msgid "" "is used, and if it is not ``0`` (enabled) then the original URL is used. " "This setting also controls the value of the ``HOST`` header that is placed " "in the request sent to the origin server, using hostname from the original " -"URL if non-``0`` and the host name from the remapped URL if ``0``. It has no" -" other effects." +"URL if non-``0`` and the host name from the remapped URL if ``0``. It has " +"no other effects." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:67 @@ -125,11 +124,11 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:69 msgid "" "It becomes significant if multiple original URLs are mapped to the same " -"remapped URL. If pristine headers are enabled requests to different original" -" URLs will be stored as distinct objects in the cache. If disabled the " -"remapped URL will be used and there may be collisions. This is bad if the " -"contents different but quite useful if they are the same (e.g., the original" -" URLs are just aliases for the same underlying server)." +"remapped URL. If pristine headers are enabled requests to different " +"original URLs will be stored as distinct objects in the cache. If disabled " +"the remapped URL will be used and there may be collisions. This is bad if " +"the contents different but quite useful if they are the same (e.g., the " +"original URLs are just aliases for the same underlying server)." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:71 @@ -139,8 +138,8 @@ msgid "" "different server address then the setting determines if existing cached " "objects will be served for new requests (enabled) or not (disabled). " "Similarly if the original URL mapped to a particular URL is changed then " -"cached objects from the initial original URL will be served from the updated" -" original URL if pristine headers is disabled." +"cached objects from the initial original URL will be served from the " +"updated original URL if pristine headers is disabled." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:73 @@ -158,12 +157,12 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:77 msgid "" -"A plugin that changes the cache key *must* do so consistently for both cache" -" hit and cache miss requests because two different requests that map to the " -"same cache key will be considered equivalent by the cache. Use of the URL " -"directly provides this and so must any substitute. This is entirely the " -"responsibility of the plugin, there is no way for the |TS| core to detect " -"such an occurrence." +"A plugin that changes the cache key *must* do so consistently for both " +"cache hit and cache miss requests because two different requests that map " +"to the same cache key will be considered equivalent by the cache. Use of " +"the URL directly provides this and so must any substitute. This is entirely " +"the responsibility of the plugin, there is no way for the |TS| core to " +"detect such an occurrence." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:79 @@ -177,8 +176,8 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:83 msgid "" -"The scheme ``ngeo`` was picked because it is *not* a valid URL scheme and so" -" will not collide with any valid URL." +"The scheme ``ngeo`` was picked because it is *not* a valid URL scheme and " +"so will not collide with any valid URL." msgstr "" #: ../../arch/cache/cache-appendix.en.rst:85 @@ -198,9 +197,9 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:91 msgid "" "We don't want to the same content for every possible referrer. Instead we " -"could use a plugin to convert this to the previous example and requests that" -" differed only in the referrer key would all reference the same cache entry." -" Note that we would also map ::" +"could use a plugin to convert this to the previous example and requests " +"that differed only in the referrer key would all reference the same cache " +"entry. Note that we would also map ::" msgstr "" #: ../../arch/cache/cache-appendix.en.rst:95 @@ -216,11 +215,12 @@ msgstr "" #: ../../arch/cache/cache-appendix.en.rst:97 msgid "" -"While there is explicit no requirement that the synthetic cache key be based" -" on the HTTP request header, in practice it is generally necessary due to " -"the consistency requirement. Because cache lookup happens before attempting " -"to connect to the origin server no data from the HTTP response header is " -"available, leaving only the request header. The most common case is the one " -"described above where the goal is to elide elements of the URL that do not " -"affect the content to minimize cache footprint and improve cache hit rates." +"While there is explicit no requirement that the synthetic cache key be " +"based on the HTTP request header, in practice it is generally necessary due " +"to the consistency requirement. Because cache lookup happens before " +"attempting to connect to the origin server no data from the HTTP response " +"header is available, leaving only the request header. The most common case " +"is the one described above where the goal is to elide elements of the URL " +"that do not affect the content to minimize cache footprint and improve " +"cache hit rates." msgstr ""
