# Copyright (C) 2014 Quick Cache
# This file is distributed under the same license as the Quick Cache package.
msgid ""
msgstr ""
"Project-Id-Version: Raindrops1.253\n"
"Report-Msgid-Bugs-To: http://wordpress.org/tag/quick-cache\n"
"POT-Creation-Date: 2014-10-02 03:13:36+00:00\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2014-11-11 14:41+0900\n"
"Last-Translator: Akio Tenman <a.tenman@gmail.com>\n"
"Language-Team: raindrops-quickcache <a.tenman@gmail.com>\n"
"X-Generator: Poedit 1.5.7\n"
"X-Poedit-SourceCharset: UTF-8\n"
"Language: ja\n"

#. translators: This string is actually NOT translatable because the `__()`
#. function is not available at this point in the processing.
#: includes/advanced-cache.tpl.php:715
msgid ""
"Quick Cache fully functional :-) Cache file served for (%1$s) in %2$s "
"seconds, on: %3$s."
msgstr "%1$s　は、クイックキャッシュが完全に機能 :-)　%3$s に、%2$s 秒"

#: includes/advanced-cache.tpl.php:847
msgid "Unexpected OB phase: `%1$s`."
msgstr ""

#: includes/advanced-cache.tpl.php:909
msgid ""
"Cache directory not writable. Quick Cache needs this directory please: `"
"%1$s`. Set permissions to `755` or higher; `777` might be needed in some "
"cases."
msgstr ""
"キャッシュディレクトリが書き込み可能ではありません。クイックキャッシュは、"
"ディレクトリ： `%1$s`が書き込み可能である必要があります。パーミッションの設定"
"を`755`または、それ以上に設定してください。いくつかのケースで`777` が必要にな"
"ることがあります。"

#: includes/advanced-cache.tpl.php:917 includes/advanced-cache.tpl.php:939
msgid ""
"Unable to create symlink: `%1$s` » `%2$s`. Possible permissions issue (or "
"race condition), please check your cache directory: `%3$s`."
msgstr ""
"シンボリックリンクを作ることが出来ません： `%1$s` » `%2$s`　キャッシュディレ"
"クトリ：`%3$s`のパーミッション（または競合状態）の可能性がありますので、"
"チェックしてください。"

#: includes/advanced-cache.tpl.php:925
msgid "Quick Cache file path: %1$s"
msgstr "クイックキャッシュ　ファイルパス："

#: includes/advanced-cache.tpl.php:926
msgid "Quick Cache file built for (%1$s) in %2$s seconds, on: %3$s."
msgstr "%1$s のクイックキャッシュが、 %3$s　に作成（in %2$s seconds）"

#: includes/advanced-cache.tpl.php:928
msgid ""
"This Quick Cache file will auto-expire (and be rebuilt) on: %1$s (based on "
"your configured expiration time)."
msgstr ""
"クイックキャッシュファイルは、あなたが設定した期間　 %1$s　の満了により、自動"
"的に期限切れ（再構築）されます。"

#: includes/advanced-cache.tpl.php:949
msgid ""
"Quick Cache: failed to write cache file for: `%1$s`; possible permissions "
"issue (or race condition), please check your cache directory: `%2$s`."
msgstr ""
"Quick Cache: `%1$s`;の書き込みに失敗しました。パーミッション（または、競合状"
"態）の可能性があります。お手数ですが、キャッシュディレクトリ： `%2$s`　を"
"チェックしてください"

#: includes/advanced-cache.tpl.php:995
msgid ""
"because `PHP_SAPI` reports that you are currently running from the command "
"line."
msgstr "PHP_SAPIは、現在コマンドラインから実行されていることを報告しています"

#: includes/advanced-cache.tpl.php:999
msgid "because `$_GET['qcAC']` is set to a boolean-ish FALSE value."
msgstr "`$_GET['qcAC']` は、booleanのような、FALSE がセットされています"

#: includes/advanced-cache.tpl.php:1003
msgid ""
"because `$_SERVER['HTTP_HOST']` is missing from your server configuration."
msgstr " `$_SERVER['HTTP_HOST']`　サーバー設定が間違っています"

#: includes/advanced-cache.tpl.php:1007
msgid ""
"because `$_SERVER['REQUEST_URI']` is missing from your server configuration."
msgstr "`$_SERVER['REQUEST_URI']` サーバー設定が間違っています"

#: includes/advanced-cache.tpl.php:1011
msgid ""
"because the PHP constant `QUICK_CACHE_ALLOWED` has been set to a boolean-ish "
"`FALSE` value at runtime. Perhaps by WordPress itself, or by one of your "
"themes/plugins. This usually means that you have a theme/plugin "
"intentionally disabling the cache on this page; and it's usually for a very "
"good reason."
msgstr ""
"PHP定数`QUICK_CACHE_ALLOWED` は、おそらく、WordPress本体、または、プラグイン"
"やテーマからランタイムでbool値のような`FALSE`に設定されました。テーマやプラグ"
"インが意図的に、通常、理にかなった理由により、このページのキャッシュを無効に"
"していることを意味します。"

#: includes/advanced-cache.tpl.php:1015
msgid ""
"because the environment variable `$_SERVER['QUICK_CACHE_ALLOWED']` has been "
"set to a boolean-ish `FALSE` value at runtime. Perhaps by WordPress itself, "
"or by one of your themes/plugins. This usually means that you have a theme/"
"plugin intentionally disabling the cache on this page; and it's usually for "
"a very good reason."
msgstr ""
"環境変数 `$_SERVER['QUICK_CACHE_ALLOWED']` は、おそらくWordPress本体、また"
"は、プラグインやテーマからランタイムでbool値のような`FALSE`に設定されました。"
"テーマやプラグインが意図的に、通常、理にかなった理由により、このページの"
"キャッシュを無効にしていることを意味します。"

#: includes/advanced-cache.tpl.php:1019
msgid ""
"because the PHP constant `DONOTCACHEPAGE` has been set at runtime. Perhaps "
"by WordPress itself, or by one of your themes/plugins. This usually means "
"that you have a theme/plugin intentionally disabling the cache on this page; "
"and it's usually for a very good reason."
msgstr ""
"PHP定数 `DONOTCACHEPAGE` は、おそらくWordPress本体、または、プラグインやテー"
"マからランタイムでbool値のような`FALSE`に設定されました。テーマやプラグインが"
"意図的に、通常、理にかなった理由により、このページのキャッシュを無効にしてい"
"ることを意味します。"

#: includes/advanced-cache.tpl.php:1023
msgid ""
"because the environment variable `$_SERVER['DONOTCACHEPAGE']` has been set "
"at runtime. Perhaps by WordPress itself, or by one of your themes/plugins. "
"This usually means that you have a theme/plugin intentionally disabling the "
"cache on this page; and it's usually for a very good reason."
msgstr ""
"環境変数 `$_SERVER['DONOTCACHEPAGE']` は、おそらくWordPress本体、または、プラ"
"グインやテーマからランタイムでbool値のような`FALSE`に設定されました。テーマや"
"プラグインが意図的に、通常、理にかなった理由により、このページのキャッシュを"
"無効にしていることを意味します。"

#: includes/advanced-cache.tpl.php:1027
msgid ""
"because `$_SERVER['REQUEST_METHOD']` is `POST`, `PUT`, `DELETE`, `HEAD`, "
"`OPTIONS`, `TRACE` or `CONNECT`. These request methods should never (ever) "
"be cached in any way."
msgstr ""
"サーバー変数`$_SERVER['REQUEST_METHOD']` は `POST`, `PUT`, `DELETE`, `HEAD`, "
"`OPTIONS`, `TRACE` or `CONNECT`. これらのリクエストは、どのような方法でも"
"キャッシュされるべきではありません。"

#: includes/advanced-cache.tpl.php:1031
msgid ""
"because `$_SERVER['REMOTE_ADDR']` === `$_SERVER['SERVER_ADDR']`; i.e. a self-"
"serve request. DEVELOPER TIP: if you are testing on a localhost "
"installation, please add `define('LOCALHOST', TRUE);` to your `/wp-config."
"php` file while you run tests :-) Remove it (or set it to a `FALSE` value) "
"once you go live on the web."
msgstr ""
" `$_SERVER['REMOTE_ADDR']` === `$_SERVER['SERVER_ADDR']`;例えば、セルフサービ"
"スリクエスト　開発者へのヒント：ローカルホストにインストールしてテストしてい"
"る場合は、テストの間中、wp-config.phpに、`define('LOCALHOST', TRUE);`を追加し"
"てください。WEB上でライブにする場合は、削除するか、または、値に`FALSE`を設定"
"してください"

#: includes/advanced-cache.tpl.php:1035
msgid ""
"because `$_SERVER['REQUEST_URI']` indicates this is a `/feed`; and the "
"configuration of this site says not to cache XML-based feeds."
msgstr ""
"`$_SERVER['REQUEST_URI']`は、これが`/feed`; である事を示します。このサイトの"
"構成は、XMLベースのフィードをキャッシュしません。"

#: includes/advanced-cache.tpl.php:1039
msgid ""
"because `$_SERVER['REQUEST_URI']` indicates this is a `wp-` or `xmlrpc` "
"file; i.e. a WordPress systematic file. WordPress systematics are never "
"(ever) cached in any way."
msgstr ""

#: includes/advanced-cache.tpl.php:1043
msgid ""
"because `$_SERVER['REQUEST_URI']` or the `is_admin()` function indicates "
"this is an administrative area of the site."
msgstr ""

#: includes/advanced-cache.tpl.php:1047
msgid ""
"because `$_SERVER['REQUEST_URI']` indicates this is a Multisite Network; and "
"this was a request for `/files/*`, not a page."
msgstr ""

#: includes/advanced-cache.tpl.php:1052
msgid ""
"because the current user visiting this page (usually YOU), appears to be "
"logged-in. The current configuration says NOT to cache pages for logged-in "
"visitors. This message may also appear if you have an active PHP session on "
"this site, or if you've left (or replied to) a comment recently. If this "
"message continues, please clear your cookies and try again."
msgstr ""
"カレントユーザー（通常、あなた）が、ログイン済みでこのページを閲覧しているた"
"め、現在の設定では、ログイン訪問者にキャッシュを見せません。あなたが、最近コ"
"メント（または、返信）した場合にも、このサイト上でアクティブPHPセッションを"
"持っている場合このメッセージが表示されることがあります。このメッセージが続く"
"ようなら、あなたのクッキーをクリアして、再度お試しください。"

#: includes/advanced-cache.tpl.php:1056
msgid ""
"because `$_GET` contains query string data. The current configuration says "
"NOT to cache GET requests with a query string."
msgstr ""
"`$_GET`リクエストに、クエリストリングを含んでいるので、現在の設定では、クエリ"
"ストリングを含んだリクエストでは、キャッシュを表示しません。"

#: includes/advanced-cache.tpl.php:1060
msgid ""
"because the WordPress `is_404()` Conditional Tag says the current page is a "
"404 error. The current configuration says NOT to cache 404 errors."
msgstr ""

#: includes/advanced-cache.tpl.php:1064
msgid ""
"because a plugin running on this installation says this page is in "
"Maintenance Mode; i.e. is not available publicly at this time."
msgstr ""

#: includes/advanced-cache.tpl.php:1068
msgid ""
"because Quick Cache is unable to cache already-compressed output. Please use "
"`mod_deflate` w/ Apache; or use `zlib.output_compression` in your `php.ini` "
"file. Quick Cache is NOT compatible with `ob_gzhandler()` and others like "
"this."
msgstr ""

#: includes/advanced-cache.tpl.php:1072
msgid ""
"because the contents of this document contain `<body id=\"error-page\">`, "
"which indicates this is an auto-generated WordPress error message."
msgstr ""

#: includes/advanced-cache.tpl.php:1076
msgid ""
"because a `Content-Type:` header was set via PHP at runtime. The header "
"contains a MIME type which is NOT a variation of HTML or XML. This header "
"might have been set by your hosting company, by WordPress itself; or by one "
"of your themes/plugins."
msgstr ""

#: includes/advanced-cache.tpl.php:1080
msgid ""
"because a `Status:` header (or an `HTTP/` header) was set via PHP at "
"runtime. The header contains a non-`2xx` status code. This indicates the "
"current page was not loaded successfully. This header might have been set by "
"your hosting company, by WordPress itself; or by one of your themes/plugins."
msgstr ""

#: includes/advanced-cache.tpl.php:1084
msgid ""
"because the WordPress `is_404()` Conditional Tag says the current page is a "
"404 error; and this is the first time it's happened on this page. Your "
"current configuration says that 404 errors SHOULD be cached, so Quick Cache "
"built a cached symlink which points future requests for this location to "
"your already-cached 404 error document. If you reload this page (assuming "
"you don't clear the cache before you do so); you should get a cached version "
"of your 404 error document. This message occurs ONCE for each new/unique 404 "
"error request."
msgstr ""

#: includes/advanced-cache.tpl.php:1088
msgid ""
"because Quick Cache detected an early output buffer termination. This may "
"happen when a theme/plugin ends, cleans, or flushes all output buffers "
"before reaching the PHP shutdown phase. It's not always a bad thing. "
"Sometimes it is necessary for a theme/plugin to do this. However, in this "
"scenario it is NOT possible to cache the output; since Quick Cache is "
"effectively disabled at runtime when this occurs."
msgstr ""

#: includes/advanced-cache.tpl.php:1092
msgid ""
"due to an unexpected behavior in the application. Please report this as a "
"bug!"
msgstr ""

#: includes/advanced-cache.tpl.php:1095
msgid "Quick Cache is NOT caching this page, %1$s"
msgstr "クイックキャッシュは、 %1$s　ページをキャッシュしていません"

#: includes/menu-pages.php:24
msgid ""
"Wipe Cache (Start Fresh); clears the cache for all sites in this network at "
"once!"
msgstr ""
"Wipe Cache (Start Fresh);一度にこのネットワークのすべてのサイトのキャッシュを"
"クリアーします"

#: includes/menu-pages.php:26
msgid "Wipe"
msgstr "Wipe"

#: includes/menu-pages.php:28
msgid "Clear Cache (Start Fresh)"
msgstr "Clear Cache (Start Fresh)"

#: includes/menu-pages.php:28
msgid "; affects the current site only."
msgstr ";　現在のサイトに適用されます"

#: includes/menu-pages.php:30
msgid "Clear"
msgstr "キャッシュのクリア"

#: includes/menu-pages.php:33
msgid ""
"Restore default plugin options? You will lose all of your current settings! "
"Are you absolutely sure about this?"
msgstr ""
"オプションの設定をデフォルトに戻しますか？現在の設定はすべて失われます !　そ"
"れで本当にいいですか？"

#: includes/menu-pages.php:35
msgid "Restore"
msgstr "設定を、すべてデフォルトに戻す"

#: includes/menu-pages.php:37
msgid "All Panels"
msgstr "すべてのパネル"

#: includes/menu-pages.php:44
msgid "Pro Upgrade"
msgstr "プロ版　アップグレード"

#: includes/menu-pages.php:45
msgid "Newsletter (Subscribe)"
msgstr "ニュースレター（購読）"

#: includes/menu-pages.php:46
msgid "Beta Testers (Signup)"
msgstr "ベータテスター（サインアップ）"

#: includes/menu-pages.php:49
msgid "Plugin Options"
msgstr "プラグインオプション"

#: includes/menu-pages.php:56
msgid "Options updated successfully."
msgstr "オプションが正常に更新されました"

#: includes/menu-pages.php:62
msgid "Default options successfully restored."
msgstr "設定は、デフォルト値に修正されました。"

#: includes/menu-pages.php:68
msgid ""
"Cache wiped across all sites; recreation will occur automatically over time."
msgstr ""

#: includes/menu-pages.php:74
msgid ""
"Cache cleared for this site; recreation will occur automatically over time."
msgstr ""
"このサイトのキャッシュはクリアされました。キャッシュの再構築は時間と共に自動"
"的に行われます。"

#: includes/menu-pages.php:80
msgid ""
"Failed to update your <code>/wp-config.php</code> file automatically. Please "
"add the following line to your <code>/wp-config.php</code> file (right after "
"the opening <code>&lt;?php</code> tag; on it's own line). <pre class=\"code"
"\"><code>&lt;?php<br />define('WP_CACHE', TRUE);</code></pre>"
msgstr ""

#: includes/menu-pages.php:86
msgid ""
"Failed to update your <code>/wp-config.php</code> file automatically. Please "
"remove the following line from your <code>/wp-config.php</code> file, or set "
"<code>WP_CACHE</code> to a <code>FALSE</code> value. <pre class=\"code"
"\"><code>define('WP_CACHE', TRUE);</code></pre>"
msgstr ""

#: includes/menu-pages.php:93
msgid ""
"Failed to update your <code>/wp-content/advanced-cache.php</code> file. "
"Cannot write stat file: <code>%1$s/qc-advanced-cache</code>. Please be sure "
"this directory exists (and that it's writable): <code>%1$s</code>. Please "
"use directory permissions <code>755</code> or higher (perhaps <code>777</"
"code>). Once you've done this, please try again."
msgstr ""

#: includes/menu-pages.php:94
msgid ""
"Failed to update your <code>/wp-content/advanced-cache.php</code> file. Most "
"likely a permissions error. Please create an empty file here: <code>/wp-"
"content/advanced-cache.php</code> (just an empty PHP file, with nothing in "
"it); give it permissions <code>644</code> or higher (perhaps <code>666</"
"code>). Once you've done this, please try again."
msgstr ""

#: includes/menu-pages.php:100
msgid ""
"Failed to remove your <code>/wp-content/advanced-cache.php</code> file. Most "
"likely a permissions error. Please delete (or empty the contents of) this "
"file: <code>/wp-content/advanced-cache.php</code>."
msgstr ""

#: includes/menu-pages.php:106
msgid "close"
msgstr ""

#: includes/menu-pages.php:107
msgid ""
"<strong>Pro Features (Preview)</strong> ~ New option panels below. Please "
"explore before <a href=\"http://www.websharks-inc.com/product/quick-cache/\" "
"target=\"_blank\">upgrading <i class=\"fa fa-heart-o\"></i></a>.<br /"
"><small>NOTE: the free version of Quick Cache (this LITE version); is more-"
"than-adequate for most sites. Please upgrade only if you desire advanced "
"features or would like to support the developer.</small>"
msgstr ""

#: includes/menu-pages.php:113
msgid "Quick Cache is currently disabled; please review options below."
msgstr ""
"現在クイックキャッシュは、停止しています。起動と停止オプションをご確認くださ"
"い"

#: includes/menu-pages.php:121
msgid "Enable/Disable"
msgstr "起動と停止"

#: includes/menu-pages.php:126
msgid "Yes, enable Quick Cache!"
msgstr "クイックキャッシュを起動します！"

#: includes/menu-pages.php:126
msgid "No, disable."
msgstr "停止"

#: includes/menu-pages.php:128
msgid ""
"<strong>HUGE Time-Saver:</strong> Approx. 95% of all WordPress sites running "
"Quick Cache, simply enable it here; and that's it :-) <strong>No further "
"configuration is necessary (really).</strong> All of the other options (down "
"below) are already tuned for the BEST performance on a typical WordPress "
"installation. Simply enable Quick Cache here and click \"Save All Changes\". "
"If you get any warnings please follow the instructions given. Otherwise, "
"you're good <i class=\"fa fa-smile-o\"></i>. This plugin is designed to run "
"just fine like it is. Take it for a spin right away; you can always fine-"
"tune things later if you deem necessary."
msgstr ""
"<strong>莫大な時間の節約:</strong>おおよそ、クイックキャッシュを実行している"
"ワードプレスサイトの95%は、単に起動するだけです。<strong>これ以上の設定は、ほ"
"んとに必要ありません</strong>下のほかのオプションは、すでに典型的なワードプレ"
"スのインストールで最高のパフォーマンスのために調整されています。単にクイック"
"キャッシュを起動して、すべてを保存のボタンを押してください。あなたは、警告が"
"出た場合のみ、指示に従ってください。何らかの警告が出た場合のみ指示に従ってく"
"ださい。このプラグインは、うまく動作するように設計されています。そうでない場"
"合は、必要な時、後で微調整をすることが出来ます。<i class=\"fa fa-smile-o\"></"
"i>"

#: includes/menu-pages.php:131
msgid "How Can I Tell Quick Cache is Working?"
msgstr "クイックキャッシュが動作していることを知るには？"

#: includes/menu-pages.php:132
msgid ""
"First of all, please make sure that you've enabled Quick Cache here; then "
"scroll down to the bottom of this page and click \"Save All Changes\". All "
"of the other options (below) are already pre-configured for typical usage. "
"Feel free to skip them all for now. You can go back through all of these "
"later and fine-tune things the way you like them."
msgstr ""
"まずは、ここでクイックキャッシュを起動していることを確認してください。この"
"ページの一番下までスクロールし　すべての変更を保存　をクリックします。ほかの"
"オプションはすべて、一般的な使用に向けて事前に設定されています。あなたは、後"
"であなたの好きなように、微調整することが出来るので今は、スキップしましょう。"

#: includes/menu-pages.php:133
msgid ""
"Once Quick Cache has been enabled, <strong>you'll need to log out (and/or "
"clear browser cookies)</strong>. By default, cache files are NOT served to "
"visitors who are logged-in, and that includes you too ;-) Cache files are "
"NOT served to recent comment authors either. If you've commented (or replied "
"to a comment lately); please clear your browser cookies before testing."
msgstr ""
"一度クイックキャッシュが起動すると、あなたは、ログアウトする必要があります"
"（そして・または、ブラウザのクッキーを削除）デフォルトでは、キャッシュファイ"
"ルは、あなたを含むログインしているユーザーには使われません。<br />キャッシュ"
"ファイルは、最近のコメント投稿者にも使われません。もし、最近コメントや返信を"
"行っている場合は、テストをする前に、ブラウザのクッキーを削除してください"

#: includes/menu-pages.php:134
msgid ""
"<strong>To verify that Quick Cache is working</strong>, navigate your site "
"like a normal visitor would. Right-click on any page (choose View Source), "
"then scroll to the very bottom of the document. At the bottom, you'll find "
"comments that show Quick Cache stats and information. You should also notice "
"that page-to-page navigation is <i class=\"fa fa-flash\"></i> "
"<strong>lightning fast</strong> now that Quick Cache is running; and it gets "
"faster over time!"
msgstr ""
"<strong>クイックキャッシュの動作確認</strong> 通常の訪問者のように、サイトを"
"閲覧します。任意のページで右クリック ソースの表示を選択、ソースの一番下までス"
"クロールします。一番下には、クイックキャッシュの統計と情報が表示されたコメン"
"トが見つかります。また、そのページからページへのナビゲーションに気づくはずで"
"す<i class=\"fa fa-flash\"></i> <strong>超高速</strong> クイックキャッシュが"
"動作しています。時間が経つごとにより早く表示されます。"

#: includes/menu-pages.php:136
msgid ""
"Yes, enable notes in the source code so I can see it's working (recommended)."
msgstr ""
"はい、クイックキャッシュが起動していることを確認するため、ソースコード内の記"
"述を有効にします（おすすめ）"

#: includes/menu-pages.php:137
msgid ""
"Yes, enable notes in the source code AND show debugging details (not "
"recommended for production)."
msgstr ""
"はい、ソースコード内の記述を有効にして、デバッグ情報も書き出します（公開サイ"
"トでは、お勧めできません）"

#: includes/menu-pages.php:138
msgid "No, I don't want my source code to contain any of these notes."
msgstr "いいえ、私はソースコードの中の記述をしたくありません。"

#: includes/menu-pages.php:147
msgid "Plugin Deletion Safeguards"
msgstr "プラグイン削除時の保護機能"

#: includes/menu-pages.php:152
msgid "Uninstall on Plugin Deletion; or Safeguard Options?"
msgstr "プラグインのアンインストール、　保護機能オプション"

#: includes/menu-pages.php:153
msgid ""
"<strong>Tip:</strong> By default, if you delete Quick Cache using the "
"plugins menu in WordPress, nothing is lost. However, if you want to "
"completely uninstall Quick Cache you should set this to <code>Yes</code> and "
"<strong>THEN</strong> deactivate &amp; delete Quick Cache from the plugins "
"menu in WordPress. This way Quick Cache will erase your options for the "
"plugin, erase directories/files created by the plugin, remove the "
"<code>advanced-cache.php</code> file, terminate CRON jobs, etc. It erases "
"itself from existence completely."
msgstr ""
"<strong>ヒント：</strong> プラグインメニューからクイックキャッシュを削除した"
"場合、デフォルトでは何も失われません。もし、完全にアンインストールしたいとき"
"には、<code>Yes</code>にセットし、プラグインメニューから　デアクティベート"
"&amp;削除　を行ってください。プラグインのすべてのオプション、cronを終了し、"
"advanced-cache.phpを削除し、プラグインによって作成されたディレクトリやファイ"
"ルを消去します。"

#: includes/menu-pages.php:155
msgid "Safeguard my options and the cache (recommended)."
msgstr "オプションフィールドとキャッシュを保護する（ おすすめ )"

#: includes/menu-pages.php:156
msgid "Yes, uninstall (completely erase) Quick Cache on plugin deletion."
msgstr ""
"はい、プラグインディレクトリのクインキャッシュをアンインストール（完全に削"
"除）します"

#: includes/menu-pages.php:167
msgid "Clearing the Cache"
msgstr "キャッシュのクリアー"

#: includes/menu-pages.php:171
msgid "Clearing the Cache (Manually)"
msgstr "キャッシュのクリアー（手動）"

#: includes/menu-pages.php:173
msgid ""
"Once Quick Cache is enabled, you will find this new option in your WordPress "
"Admin Bar (see screenshot on right). Clicking this button will clear the "
"cache and you can start fresh at anytime (e.g. you can do this manually; and "
"as often as you wish)."
msgstr ""

#: includes/menu-pages.php:174
msgid ""
"Depending on the structure of your site, there could be many reasons to "
"clear the cache. However, the most common reasons are related to Post/Page "
"edits or deletions, Category/Tag edits or deletions, and Theme changes. "
"Quick Cache handles most scenarios all by itself. However, many site owners "
"like to clear the cache manually; for a variety of reasons (just to force a "
"refresh)."
msgstr ""

#: includes/menu-pages.php:176
msgid ""
"Yes, enable the &quot;Clear Cache&quot; button in the WordPress admin bar."
msgstr ""

#: includes/menu-pages.php:177
msgid "No, I don't intend to clear the cache manually; exclude from admin bar."
msgstr ""

#: includes/menu-pages.php:179
msgid ""
"Running the <a href=\"http://www.websharks-inc.com/product/s2clean/\" target="
"\"_blank\">s2Clean Theme</a> by WebSharks?"
msgstr ""

#: includes/menu-pages.php:180
msgid ""
"If s2Clean is installed, Quick Cache can be configured to clear the Markdown "
"cache too (if you've enabled Markdown processing with s2Clean). The s2Clean "
"Markdown cache is only cleared when you manually clear the cache (with Quick "
"Cache); and only if you enable this option here. Note: s2Clean's Markdown "
"cache is extremely dynamic. Just like the rest of your site, s2Clean caches "
"do NOT need to be cleared away at all, as this happens automatically when "
"your content changes. However, some developers find this feature useful "
"while developing their site; just to force a refresh."
msgstr ""

#: includes/menu-pages.php:182
msgid ""
"Yes, if the s2Clean theme is installed; also clear s2Clean-related caches."
msgstr ""

#: includes/menu-pages.php:183
msgid ""
"No, I don't use s2Clean; or, I don't want s2Clean-related caches cleared."
msgstr ""

#: includes/menu-pages.php:185
msgid "Process Other Custom PHP Code?"
msgstr ""

#: includes/menu-pages.php:186
msgid ""
"If you have other custom routines you'd like to process when the cache is "
"cleared manually, please type your custom PHP code here. The PHP code that "
"you provide is only evaluated when you manually clear the cache (with Quick "
"Cache); and only if the field below contains PHP code. Note: if your PHP "
"code outputs a message (e.g. if you have <code>echo '&lt;p&gt;My message&lt;/"
"p&gt;';</code>); your message will be displayed along with any other notes "
"from Quick Cache itself. This could be useful to developers that need to "
"clear server caches too (such as <a href=\"http://www.php.net/manual/en/"
"function.apc-clear-cache.php\" target=\"_blank\">APC</a> or <a href=\"http://"
"www.php.net/manual/en/memcache.flush.php\" target=\"_blank\">memcache</a>)."
msgstr ""

#: includes/menu-pages.php:188
msgid ""
"<strong>Example:</strong> <code>&lt;?php apc_clear_cache(); echo '&lt;p&gt;"
"Also cleared APC cache.&lt;/p&gt;'; ?&gt;</code>"
msgstr ""

#: includes/menu-pages.php:190
msgid "Purging the Cache (Automatically)"
msgstr ""

#: includes/menu-pages.php:192
msgid ""
"This is built into the Quick Cache plugin; e.g. this functionality is "
"\"always on\". If you edit a Post/Page (or delete one), Quick Cache will "
"automatically purge the cache file(s) associated with that content. This way "
"a new updated version of the cache will be created automatically the next "
"time this content is accessed. Simple updates like this occur each time you "
"make changes in the Dashboard, and Quick Cache will notify you of these as "
"they occur. Quick Cache monitors changes to Posts (of any kind, including "
"Pages), Categories, Tags, Links, Themes (even Users); and more. "
"Notifications in the Dashboard regarding these detections can be enabled/"
"disabled below."
msgstr ""

#: includes/menu-pages.php:194
msgid ""
"Yes, enable Quick Cache notifications in the Dashboard when changes are "
"detected &amp; one or more cache files are purged automatically."
msgstr ""

#: includes/menu-pages.php:195
msgid ""
"No, I don't want to know (don't really care) what Quick Cache is doing "
"behind-the-scene."
msgstr ""

#: includes/menu-pages.php:197
msgid "Auto-Purge Designated \"Home Page\" Too?"
msgstr ""

#: includes/menu-pages.php:198
msgid ""
"On many sites, the Home Page (aka: the Front Page) offers an archive view of "
"all Posts (or even Pages). Therefore, if a single Post/Page is changed in "
"some way; and Quick Cache purges/resets the cache for a single Post/Page, "
"would you like Quick Cache to also purge any existing cache files for the "
"\"Home Page\"?"
msgstr ""

#: includes/menu-pages.php:200
msgid ""
"Yes, if any single Post/Page is purged/reset; also purge the \"Home Page\"."
msgstr ""

#: includes/menu-pages.php:201
msgid ""
"No, my Home Page does not provide a list of Posts/Pages; e.g. this is not "
"necessary."
msgstr ""

#: includes/menu-pages.php:203
msgid "Auto-Purge Designated \"Posts Page\" Too?"
msgstr ""

#: includes/menu-pages.php:204
msgid ""
"On many sites, the Posts Page (aka: the Blog Page) offers an archive view of "
"all Posts (or even Pages). Therefore, if a single Post/Page is changed in "
"some way; and Quick Cache purges/resets the cache for a single Post/Page, "
"would you like Quick Cache to also purge any existing cache files for the "
"\"Posts Page\"?"
msgstr ""

#: includes/menu-pages.php:206
msgid ""
"Yes, if any single Post/Page is purged/reset; also purge the \"Posts Page\"."
msgstr ""

#: includes/menu-pages.php:207
msgid ""
"No, I don't use a separate Posts Page; e.g. my Home Page IS my Posts Page."
msgstr ""

#: includes/menu-pages.php:209
msgid "Auto-Purge \"Author Page\" Too?"
msgstr ""

#: includes/menu-pages.php:210
msgid ""
"On many sites, each author has a related \"Author Page\" that offers an "
"archive view of all posts associated with that author. Therefore, if a "
"single Post/Page is changed in some way; and Quick Cache purges/resets the "
"cache for a single Post/Page, would you like Quick Cache to also purge any "
"existing cache files for the related \"Author Page\"?"
msgstr ""

#: includes/menu-pages.php:212
msgid ""
"Yes, if any single Post/Page is purged/reset; also purge the \"Author Page\"."
msgstr ""

#: includes/menu-pages.php:213
msgid ""
"No, my site doesn't use multiple authors and/or I don't have any \"Author "
"Page\" archive views."
msgstr ""

#: includes/menu-pages.php:215
msgid "Auto-Purge \"Category Archives\" Too?"
msgstr ""

#: includes/menu-pages.php:216
msgid ""
"On many sites, each post is associated with at least one Category. Each "
"category then has an archive view that contains all the posts within that "
"category. Therefore, if a single Post/Page is changed in some way; and Quick "
"Cache purges/resets the cache for a single Post/Page, would you like Quick "
"Cache to also purge any existing cache files for the associated Category "
"archive views?"
msgstr ""

#: includes/menu-pages.php:218
msgid ""
"Yes, if any single Post/Page is purged/reset; also purge the associated "
"Category archive views."
msgstr ""

#: includes/menu-pages.php:219
msgid ""
"No, my site doesn't use Categories and/or I don't have any Category archive "
"views."
msgstr ""

#: includes/menu-pages.php:221
msgid "Auto-Purge \"Tag Archives\" Too?"
msgstr ""

#: includes/menu-pages.php:222
msgid ""
"On many sites, each post may be associated with at least one Tag. Each tag "
"then has an archive view that contains all the posts assigned that tag. "
"Therefore, if a single Post/Page is changed in some way; and Quick Cache "
"purges/resets the cache for a single Post/Page, would you like Quick Cache "
"to also purge any existing cache files for the associated Tag archive views?"
msgstr ""

#: includes/menu-pages.php:224
msgid ""
"Yes, if any single Post/Page is purged/reset; also purge the associated Tag "
"archive views."
msgstr ""

#: includes/menu-pages.php:225
msgid "No, my site doesn't use Tags and/or I don't have any Tag archive views."
msgstr ""

#: includes/menu-pages.php:227
msgid "Auto-Purge \"Custom Term Archives\" Too?"
msgstr ""

#: includes/menu-pages.php:228
msgid ""
"Most sites do not use any custom Terms so it should be safe to leave this "
"disabled. However, if your site uses custom Terms and they have their own "
"Term archive views, you may want to clear those when the associated post is "
"cleared. Therefore, if a single Post/Page is changed in some way; and Quick "
"Cache purges/resets the cache for a single Post/Page, would you like Quick "
"Cache to also purge any existing cache files for the associated Tag archive "
"views?"
msgstr ""

#: includes/menu-pages.php:230
msgid ""
"Yes, if any single Post/Page is purged/reset; also purge any associated "
"custom Term archive views."
msgstr ""

#: includes/menu-pages.php:231
msgid ""
"No, my site doesn't use any custom Terms and/or I don't have any custom Term "
"archive views."
msgstr ""

#: includes/menu-pages.php:233
msgid "Auto-Purge \"Custom Post Type Archives\" Too?"
msgstr ""

#: includes/menu-pages.php:234
msgid ""
"Most sites do not use any Custom Post Types so it should be safe to disable "
"this option. However, if your site uses Custom Post Types and they have "
"their own Custom Post Type archive views, you may want to clear those when "
"any associated post is cleared. Therefore, if a single Post with a Custom "
"Post Type is changed in some way; and Quick Cache purges/resets the cache "
"for that post, would you like Quick Cache to also purge any existing cache "
"files for the associated Custom Post Type archive views?"
msgstr ""

#: includes/menu-pages.php:236
msgid ""
"Yes, if any single Post with a Custom Post Type is purged/reset; also purge "
"any associated Custom Post Type archive views."
msgstr ""

#: includes/menu-pages.php:237
msgid ""
"No, my site doesn't use any Custom Post Types and/or I don't have any Custom "
"Post Type archive views."
msgstr ""

#: includes/menu-pages.php:246
msgid "Directory / Expiration Time"
msgstr "キャッシュディレクトリ　キャッシュ有効期限"

#: includes/menu-pages.php:250
msgid ""
"Base Cache Directory (Must be Writable; e.g. <a href=\"http://codex."
"wordpress.org/Changing_File_Permissions\" target=\"_blank\">Permissions</a> "
"<code>755</code> or Higher)"
msgstr ""
"キャッシュディレクトリ（書き込み可能にしてください 　例. <a href=\"http://"
"codex.wordpress.org/Changing_File_Permissions\" target=\"_blank\">パーミッ"
"ション</a> <code>755</code> または、それ以上)"

#: includes/menu-pages.php:251
msgid ""
"This is where Quick Cache will store the cached version of your site. If "
"you're not sure how to deal with directory permissions, don't worry too much "
"about this. If there is a problem, Quick Cache will let you know about it. "
"By default, this directory is created by Quick Cache and the permissions are "
"setup automatically. In most cases there is nothing more you need to do."
msgstr ""
"クイックキャッシュが、サイトのキャッシュを保存する場所です。ディレクトリの"
"パーミッションの指定方法がよくわからなくても心配しないでください。問題がある"
"場合に調べてください。デフォルトでは、ディレクトリはクイックキャッシュにに"
"よって作成され、パーミッションも自動的にセットされます。ほとんどのケースで"
"は、あなたが特に必要としない限り何もしなくていいです。"

#: includes/menu-pages.php:255
msgid "Automatic Expiration Time (Max Age)"
msgstr "自動キャッシュ有効期間（最大期間）"

#: includes/menu-pages.php:256
msgid ""
"If you don't update your site much, you could set this to <code>6 months</"
"code> and optimize everything even further. The longer the Cache Expiration "
"Time is, the greater your performance gain. Alternatively, the shorter the "
"Expiration Time, the fresher everything will remain on your site. A default "
"value of <code>7 days</code> (recommended); is a good conservative middle-"
"ground."
msgstr ""
"サイトをあまり変更しない場合は、<code>6 months</code>を設定し、更にすべてを最"
"適化することが出来ます。キャッシュ有効時間が長いほど大きなパフォーマンスを得"
"られ、有効時間が短いほど、新鮮です。<code>7 days</code> (おすすめ);は、控えめ"
"な良い妥協点です。"

#: includes/menu-pages.php:257
msgid ""
"Keep in mind that your Expiration Time is only one part of the big picture. "
"Quick Cache will also purge the cache automatically as changes are made to "
"the site (i.e. you edit a post, someone comments on a post, you change your "
"theme, you add a new navigation menu item, etc., etc.). Thus, your "
"Expiration Time is really just a fallback; e.g. the maximum amount of time "
"that a cache file could ever possibly live."
msgstr ""
"有効期限の時間は、全体の中の一部に過ぎない事を留意してください。サイトに対し"
"て変更が行われるようにクイックキャッシュも自動的にキャッシュをパージします。"
"（つまり、あなたが投稿を編集、誰かが、投稿にコメントしテーマを変更すると、新"
"しいナビゲーションメニューなどを追加します）このように有効期限は、単なる予備"
"です。例えば、キャッシュファイル最大生存限度"

#: includes/menu-pages.php:258
msgid ""
"All of that being said, you could set this to just <code>60 seconds</code> "
"and you would still see huge differences in speed and performance. If you're "
"just starting out with Quick Cache (perhaps a bit nervous about old cache "
"files being served to your visitors); you could set this to something like "
"<code>30 minutes</code>, and experiment with it while you build confidence "
"in Quick Cache. It's not necessary to do so, but many site owners have "
"reported this makes them feel like they're more-in-control when the cache "
"has a short expiration time. All-in-all, it's a matter of preference <i "
"class=\"fa fa-smile-o\"></i>."
msgstr ""
"<code>60 seconds</code>を設定し、スピードとパフォーマンスの大きな違いを見るこ"
"とが出来るといわれています。クイックキャッシュを使い始めると（サイトの訪問者"
"に提供される　やや不安な古いキャッシュ）また、<code>30 minutes</code>という設"
"定も行うことが出来ます。特にこうしなければならないという事はありませんが、多"
"くのサイトオーナーは、キャッシュの有効期限が短い時、制御しやすいと感じると報"
"告しています。最も大切なのは、パフォーマンスの問題です <i class=\"fa fa-"
"smile-o\"></i>"

#: includes/menu-pages.php:260
msgid ""
"<strong>Tip:</strong> the value that you specify here MUST be compatible "
"with PHP's <a href=\"http://php.net/manual/en/function.strtotime.php\" "
"target=\"_blank\" style=\"text-decoration:none;\"><code>strtotime()</code></"
"a> function. Examples: <code>30 seconds</code>, <code>2 hours</code>, "
"<code>7 days</code>, <code>6 months</code>, <code>1 year</code>."
msgstr ""
"<strong>ヒント</strong>ここに設定する値は、PHP関数<a href=\"http://php.net/"
"manual/en/function.strtotime.php\" target=\"_blank\" style=\"text-decoration:"
"none;\"><code>strtotime()</code></a> で指定可能な引数を指定しなければなりませ"
"ん。例： <code>30 seconds</code>, <code>2 hours</code>, <code>7 days</code>, "
"<code>6 months</code>, <code>1 year</code>."

#: includes/menu-pages.php:261
msgid ""
"<strong>Note:</strong> Quick Cache will never serve a cache file that is "
"older than what you specify here (even if one exists in your cache "
"directory; stale cache files are never used). In addition, a WP Cron job "
"will automatically cleanup your cache directory (once daily); purging "
"expired cache files periodically. This prevents a HUGE cache from building "
"up over time, creating a potential storage issue."
msgstr ""
"<strong>注:</strong>クイックキャッシュはここで設定した期限よりも古いものを提"
"供する事はありません（たとえキャッシュディレクトリにファイルが存在していても"
"使われません）時間経過とともに巨大化するキャッシュを防ぐため、WP　Cronで"
"キャッシュディレクトリのクリーンアップが一日一回行われます。"

#: includes/menu-pages.php:269
msgid "Client-Side Cache"
msgstr "クライアントサイド　キャッシュ"

#: includes/menu-pages.php:274
msgid "Allow Double-Caching In The Client-Side Browser?"
msgstr "クライアントサイドブラウザで　ダブルキャッシングを行いますか？"

#: includes/menu-pages.php:275
msgid ""
"Recommended setting: <code>No</code> (for membership sites, very important). "
"Otherwise, <code>Yes</code> would be better (if users do NOT log in/out of "
"your site)."
msgstr ""
"ユーザーがログインログアウトを行う会員制サイトでは、<code>いいえ</code>に設定"
"するのが特に重要です。ユーザーがログインやログアウトを行わないサイトの場合は"
"<code>はい</code>がおすすめです。"

#: includes/menu-pages.php:276
msgid ""
"Quick Cache handles content delivery through its ability to communicate with "
"a browser using PHP. If you allow a browser to (cache) the caching system "
"itself, you are momentarily losing some control; and this can have a "
"negative impact on users that see more than one version of your site; e.g. "
"one version while logged-in, and another while NOT logged-in. For instance, "
"a user may log out of your site, but upon logging out they report seeing "
"pages on the site which indicate they are STILL logged in (even though "
"they're not — that's bad). This can happen if you allow a client-side cache, "
"because their browser may cache web pages they visited while logged into "
"your site which persist even after logging out. Sending no-cache headers "
"will work to prevent this issue."
msgstr ""
"クイックキャッシュは、ブラウザへのコンテンツの配信をPHPを使って処理します。ブ"
"ラウザキャッシュを有効にしたときに、いくつかのコントロールを失います　これ"
"は、あなたのサイトの複数のバージョンを参照して、ユーザーにネガティブなインパ"
"クトを与えます。例えば、あるバージョンでは、ログイン済み、あるバージョンで"
"は、ログアウト状態、例えば、ユーザーがログアウトしても、彼らがみるページは、"
"依然としてログインしたページです。クライアント側のキャッシュを許可した場合、"
"そのブラウザがログアウトした後でもログインしている間彼らが訪問したWEBページの"
"キャッシュを持つことが出来るので発生する可能性があります。この問題を防ぐため"
"に、ノーキャッシュヘッダーを送信します。"

#: includes/menu-pages.php:277
msgid ""
"All of that being said, if all you care about is blazing fast speed and "
"users don't log in/out of your site (only you do); you can safely set this "
"to <code>Yes</code> (recommended in this case). Allowing a client-side "
"browser cache will improve speed and reduce outgoing bandwidth when this "
"option is feasible."
msgstr ""
"もし、爆速で、ユーザーがログインやログアウトをしない　あなただけが管理するサ"
"イトなら、<code>Yes</code>（この場合は、Yesがおすすめ）クライアントサイドの"
"キャッシュを許可すると速度は改善し、送信帯域幅が減少します。"

#: includes/menu-pages.php:279
msgid "No, prevent a client-side browser cache (safest option)."
msgstr ""
"いいえ、クライアントサイドブラウザキャッシュを使わない（もっとも安全な選択"
"肢）"

#: includes/menu-pages.php:280
msgid "Yes, I will allow a client-side browser cache of pages on the site."
msgstr "はい、サイトのページのクライアントサイドブラウザキャッシュを許可します"

#: includes/menu-pages.php:282
msgid ""
"<strong>Tip:</strong> Setting this to <code>No</code> is highly recommended "
"when running a membership plugin like <a href=\"http://wordpress.org/plugins/"
"s2member/\" target=\"_blank\">s2Member</a> (as one example). In fact, many "
"plugins like s2Member will send <a href=\"http://codex.wordpress.org/"
"Function_Reference/nocache_headers\" target=\"_blank\">nocache_headers()</a> "
"on their own, so your configuration here will likely be overwritten when you "
"run such plugins (which is better anyway). In short, if you run a membership "
"plugin, you should NOT allow a client-side browser cache."
msgstr ""
"<strong>ヒント：</strong> メンバーシッププラグイン<a href=\"http://wordpress."
"org/plugins/s2member/\" target=\"_blank\">s2Member</a> (一例です).実際には、"
"s2Memberのようなプラグインは、<a href=\"http://codex.wordpress.org/"
"Function_Reference/nocache_headers\" target=\"_blank\">nocache_headers()</a> "
"をそれ自身で出力しますので、この種のプラグインを使っている場合は、上書きされ"
"ます。<br />つまり、メンバーシッププラグインを使っている場合は、クライアント"
"サイドキャッシュを許可すべきではありません。"

#: includes/menu-pages.php:283
msgid ""
"<strong>Tip:</strong> Setting this to <code>No</code> will NOT impact static "
"content; e.g. CSS, JS, images, or other media. This setting pertains only to "
"dynamic PHP scripts which produce content generated by WordPress."
msgstr ""
"<strong>ヒント：</strong> <code>No</code>に設定すると静的コンテンツに影響を与"
"えません。例　CSS, JS, images, or other media. この設定は、ワードプレスにより"
"PHP動的スクリプトによって生成されるコンテンツにに関係するものです"

#: includes/menu-pages.php:284
msgid ""
"<strong>Advanced Tip:</strong> if you have this set to <code>No</code>, but "
"you DO want to allow a few special URLs to be cached by the browser; you can "
"add this parameter to your URL <code>?qcABC=1</code>. This tells Quick Cache "
"that it's OK for the browser to cache that particular URL. In other words, "
"the <code>qcABC=1</code> parameter tells Quick Cache NOT to send no-cache "
"headers to the browser."
msgstr ""
"<strong>高度なヒント:</strong>設定が<code>No</code>で、ある特定のURLSについ"
"て、クライアントサイドキャッシュを使いたいとき、URLのパラメーターに<code>?"
"qcABC=1</code>.を追加することが出来ます。これで、クイックキャッシュを呼び出し"
"特定のURLについてキャッシュします。言い換えると、<code>qcABC=1</code>パラメー"
"タは、クイックキャッシュが　no-cache headers　を送信しないことを意味します"

#: includes/menu-pages.php:294
msgid "Logged-In Users"
msgstr ""

#: includes/menu-pages.php:299
msgid "Caching Enabled for Logged-In Users &amp; Comment Authors?"
msgstr ""

#: includes/menu-pages.php:300
msgid ""
"This should almost ALWAYS be set to <code>No</code>. Most sites will NOT "
"want to cache content generated while a user is logged-in. Doing so could "
"result in a cache of dynamic content generated specifically for a particular "
"user, where the content being cached may contain details that pertain only "
"to the user that was logged-in when the cache was generated. Imagine "
"visiting a website that says you're logged-in as Billy Bob (but you're not "
"Billy Bob; NOT good). In short, do NOT turn this on unless you know what "
"you're doing."
msgstr ""

#: includes/menu-pages.php:302
msgid ""
"<strong>Exception (Membership Sites):</strong> If you run a site with many "
"users and the majority of your traffic comes from users who ARE logged-in, "
"please choose: <code>Yes (maintain separate cache)</code>. Quick Cache will "
"operate normally; but when a user is logged-in, the cache is user-specific. "
"Quick Cache will intelligently refresh the cache when/if a user submits a "
"form on your site with the GET or POST method. Or, if you make changes to "
"their account (or another plugin makes changes to their account); including "
"user <a href=\"http://codex.wordpress.org/Function_Reference/"
"update_user_option\" target=\"_blank\">option</a>|<a href=\"http://codex."
"wordpress.org/Function_Reference/update_user_meta\" target=\"_blank\">meta</"
"a> additions, updates &amp; deletions too. However, please note that "
"enabling this feature (e.g. user-specific cache entries); will eat up MUCH "
"more disk space. That being said, the benefits of this feature for most "
"sites will outweigh the disk overhead (e.g. it's NOT an issue in most "
"cases). Unless you are short on disk space (or you have MANY thousands of "
"users), the disk overhead is neglible."
msgstr ""

#: includes/menu-pages.php:304
msgid ""
"No, do NOT cache; or serve a cache file when a user is logged-in (safest "
"option)."
msgstr ""

#: includes/menu-pages.php:305
msgid ""
"Yes, and maintain a separate cache for each user (recommended for membership "
"sites)."
msgstr ""

#: includes/menu-pages.php:306
msgid ""
"Yes, but DON'T maintain a separate cache for each user (I know what I'm "
"doing)."
msgstr ""

#: includes/menu-pages.php:308
msgid ""
"<strong>Note:</strong> For most sites, the majority of their traffic (if not "
"all of their traffic) comes from visitors who are not logged in, so "
"disabling the cache for logged-in users is NOT ordinarily a performance "
"issue. When a user IS logged-in, disabling the cache is considered ideal, "
"because a logged-in user has a session open with your site; and the content "
"they view should remain very dynamic in this scenario."
msgstr ""

#: includes/menu-pages.php:309
msgid ""
"<strong>Note:</strong> This setting includes some users who AREN'T actually "
"logged into the system, but who HAVE authored comments recently. Quick Cache "
"includes comment authors as part of it's logged-in user check. This way "
"comment authors will be able to see updates to the comment thread "
"immediately; and, so that any dynamically-generated messages displayed by "
"your theme will work as intended. In short, Quick Cache thinks of a comment "
"author as a logged-in user, even though technically they are not. ~ Users "
"who gain access to password-protected Posts/Pages are also included."
msgstr ""

#: includes/menu-pages.php:317
msgid "GET Requests"
msgstr "GET リクエスト"

#: includes/menu-pages.php:322
msgid "Caching Enabled for GET (Query String) Requests?"
msgstr "GETリクエスト（クエリ文字列のついた）リクエストをキャッシュしますか？"

#: includes/menu-pages.php:323
msgid ""
"This should almost ALWAYS be set to <code>No</code>. UNLESS, you're using "
"unfriendly Permalinks. In other words, if all of your URLs contain a query "
"string (e.g. <code>/?key=value</code>); you're using unfriendly Permalinks. "
"Ideally, you would refrain from doing this; and instead, update your "
"Permalink options immediately; which also optimizes your site for search "
"engines. That being said, if you really want to use unfriendly Permalinks, "
"and ONLY if you're using unfriendly Permalinks, you should set this to "
"<code>Yes</code>; and don't worry too much, the sky won't fall on your "
"head :-)"
msgstr ""
"デフォルトのパーマリンクを使用していない限り、ほぼ、すべての場合いつでも、"
"<code>いいえ</code>に設定すべきです。言い換えれば、あなたの（サイト）すべての"
"URLにクエリ文字が含まれている(例えばこんな形で. <code>/?key=value</code>);な"
"ら、あなたはデフォルトパーマリンクを使用しています。　理想的には、これを控え"
"て、パーマリンクの設定を更新して検索エンジンのために最適なURLに変更する事で"
"す。もし、あなたが、デフォルトのパーマリンク設定を使用したいと考え、デフォル"
"トパーマリンクしか使わないなら、天罰が下るわけでもないので　:-)　あまり心配し"
"ないで<code>はい</code>; を設定しましょう"

#: includes/menu-pages.php:325
msgid ""
"No, do NOT cache (or serve a cache file) when a query string is present."
msgstr ""
"いいえ、クエリ文字列が存在する場合、キャッシュしない（キャッシュを提供しな"
"い）"

#: includes/menu-pages.php:326
msgid "Yes, I would like to cache URLs that contain a query string."
msgstr "はい、クエリ文字列を含むURLをキャッシュする"

#: includes/menu-pages.php:328
msgid ""
"<strong>Note:</strong> POST requests (i.e. forms with <code>method=&quot;"
"post&quot;</code>) are always excluded from the cache, which is the way it "
"should be. Any <a href=\"http://www.w3.org/Protocols/rfc2616/rfc2616-sec9."
"html\" target=\"_blank\">POST/PUT/DELETE</a> request should NEVER (ever) be "
"cached. CLI (and self-serve) requests are also excluded from the cache "
"(always). A CLI request is one that comes from the command line; commonly "
"used by CRON jobs and other automated routines. A self-serve request is an "
"HTTP connection established from your site -› to your site. For instance, a "
"WP Cron job, or any other HTTP request that is spawned not by a user, but by "
"the server itself."
msgstr ""
"<strong>注：</strong>POST　リクエスト(i.e. forms with <code>method=&quot;"
"post&quot;</code>)は、常にキャッシュから除外されます。<a href=\"http://www."
"w3.org/Protocols/rfc2616/rfc2616-sec9.html\" target=\"_blank\">POST/PUT/"
"DELETE</a> リクエストは、キャッシュされるべきではありません。CLI (and self-"
"serve) は、常にキャッシュから除外されます。CLIリクエストは、コマンドラインか"
"らくるものです。一般的に、cronジョブやほかの自動化ルーティンが使用。セルフ"
"サービスリクエストは、あなたのサイトからあなたのサイトへHTTP接続です。例えば"
"WP Cronジョブやユーザーによるものではない、サーバー自身が行うリクエストです。"

#: includes/menu-pages.php:329
msgid ""
"<strong>Advanced Tip:</strong> If you are NOT caching GET requests "
"(recommended), but you DO want to allow some special URLs that include query "
"string parameters to be cached; you can add this special parameter to any "
"URL <code>?qcAC=1</code>. This tells Quick Cache that it's OK to cache that "
"particular URL, even though it contains query string arguments. If you ARE "
"caching GET requests and you want to force Quick Cache to NOT cache a "
"specific request, you can add this special parameter to any URL <code>?"
"qcAC=0</code>."
msgstr ""
"<strong>高度なヒント：</strong>あなたが、お勧めの　GETリクエストをキャッシュ"
"しない設定をしており、しかしあなたが、特定のクエリストリングを含むURLのキャッ"
"シュを望む場合には、<code>?qcAC=1</code>という特別なパラメータを追加すること"
"が出来ます。これは、特定のURLがクエリストリングを持っていても、クイックキャッ"
"シュがキャッシュしてよい事を伝えます。もし、GETリクエストをキャッシュしてい"
"て、特定のURLに対してキャッシュをしたくない場合は、それらそれぞれに、<code>?"
"qcAC=0</code>という特別なパラメータを追加することが出来ます。"

#: includes/menu-pages.php:337
msgid "404 Requests"
msgstr "404　リクエスト"

#: includes/menu-pages.php:342
msgid "Caching Enabled for 404 Requests?"
msgstr "HTTP404リクエストをキャッシュしますか？"

#: includes/menu-pages.php:343
msgid ""
"When this is set to <code>No</code>, Quick Cache will ignore all 404 "
"requests and no cache file will be served. While this is fine for most site "
"owners, caching the 404 page on a high-traffic site may further reduce "
"server load. When this is set to <code>Yes</code>, Quick Cache will cache "
"the 404 page (see <a href=\"https://codex.wordpress.org/"
"Creating_an_Error_404_Page\" target=\"_blank\">Creating an Error 404 Page</"
"a>) and then serve that single cache file to all future 404 requests."
msgstr ""
"<code>いいえ</code>に設定されている場合は、クイックキャッシュは、すべての404"
"リクエストを無視しキャッシュファイルは作られません。これはほとんどのサイト"
"オーナーには良い事ですが、高トラフィックサイトの場合<code>はい</code>にセット"
"して、404ページをキャッシュすることで (see <a href=\"https://codex.wordpress."
"org/Creating_an_Error_404_Page\" target=\"_blank\">Creating an Error 404 "
"Page</a>) すべての404リクエストに単一のキャッシュファイルを提供し、更にサー"
"バーの負荷を軽減できることがあります。"

#: includes/menu-pages.php:345
msgid "No, do NOT cache (or serve a cache file) for 404 requests."
msgstr "いいえ、404リクエストはキャッシュしない"

#: includes/menu-pages.php:346
msgid ""
"Yes, I would like to cache the 404 page and serve the cached file for 404 "
"requests."
msgstr "はい、404リクエストをキャッシュし、キャッシュを提供する"

#: includes/menu-pages.php:348
msgid ""
"<strong>How does Quick Cache cache 404 requests?</strong> Quick Cache will "
"create a special cache file (<code>----404----.html</code>, see Advanced Tip "
"below) for the first 404 request and then <a href=\"http://www.php.net/"
"manual/en/function.symlink.php\" target=\"_blank\">symlink</a> future 404 "
"requests to this special cache file. That way you don't end up with lots of "
"404 cache files that all contain the same thing (the contents of the 404 "
"page). Instead, you'll have one 404 cache file and then several symlinks (i."
"e., references) to that 404 cache file."
msgstr ""
"<strong>クイックキャッシュは、404リクエストをどのようにキャッシュするのです"
"か？</strong> クイックキャッシュは、最初の404リクエストで、特別なキャッシュ"
"ファイル（<code>----404----.html</code>, 下の特別なヒントをご覧ください）を作"
"成し、それから<a href=\"http://www.php.net/manual/en/function.symlink.php\" "
"target=\"_blank\">シンボリックリンク</a> この特殊なキャッシュファイルにそれ以"
"降の404リクエストに使われます。このやり方は、同じ内容の多数の404キャッシュ"
"ファイルを生成しません"

#: includes/menu-pages.php:349
msgid ""
"<strong>Advanced Tip:</strong> The default 404 cache filename "
"(<code>----404----.html</code>) is designed to minimize the chance of a "
"collision with a cache file for a real page with the same name. However, if "
"you want to override this default and define your own 404 cache filename, "
"you can do so by adding <code>define('QUICK_CACHE_404_CACHE_FILENAME', "
"'your-404-cache-filename');</code> to your <code>wp-config.php</code> file "
"(note that the <code>.html</code> extension should be excluded when defining "
"a new filename)."
msgstr ""
"<strong>高度なヒント</strong>デフォルトの404のファイル名 (<code>----404----."
"html</code>) は、同じ名前の実ページ用のキャッシュファイルとの衝突の可能性を最"
"小限に抑えるように設計されています。しかし、デフォルトの設定を上書きして、独"
"自の404ファイル名を定義するする場合<code>define"
"('QUICK_CACHE_404_CACHE_FILENAME', 'your-404-cache-filename');</code>を"
"<code>wp-config.php</code>に定義することが出来ます。（新しいファイル名を定義"
"する際には<code>.html</code>拡張子は、除外すべきであることに注意してくださ"
"い。）"

#: includes/menu-pages.php:357
msgid "RSS, RDF, and Atom Feeds"
msgstr "RSS, RDF, and Atom フィード"

#: includes/menu-pages.php:362
msgid "Caching Enabled for RSS, RDF, Atom Feeds?"
msgstr "RSS,RDF,Atomフィードをキャッシュしますか？"

#: includes/menu-pages.php:363
msgid ""
"This should almost ALWAYS be set to <code>No</code>. UNLESS, you're sure "
"that you want to cache your feeds. If you use a web feed management provider "
"like Google® Feedburner and you set this option to <code>Yes</code>, you may "
"experience delays in the detection of new posts. <strong>NOTE:</strong> If "
"you do enable this, it is highly recommended that you also enable automatic "
"Feed Purging too. Please see the section above: \"Clearing the Cache\". Find "
"the sub-section titled: \"Auto-Purge RSS/RDF/ATOM Feeds\" (available only in "
"the pro version)."
msgstr ""
"これは、大抵どんな時も <code>いいえ</code>にすべきです。　あなたが、フィード"
"をキャッシュしてもよいと思ってない限り、もし、Google® Feedburner のような"
"フィードマネージメントプロバイダを使っていて、<code>はい</code>に設定している"
"場合、新しい投稿を検知する時間にずれが生じるでしょう　<strong>注意:</strong>"
"　もし有効にするなら、高度なおすすめですが、enable automatic Feed Purging　も"
"有効にしておくといいです。Clearing the Cache　セクションのサブセクションAuto-"
"Purge RSS/RDF/ATOM Feedsを読んでみてください（Proバージョン専用）"

#: includes/menu-pages.php:365
msgid "No, do NOT cache (or serve a cache file) when displaying a feed."
msgstr ""
"いいえ、フィードを表示する時に、キャッシュしない（キャッシュを提供しない）"

#: includes/menu-pages.php:366
msgid "Yes, I would like to cache feed URLs."
msgstr "はい、フィードURLをキャッシュします"

#: includes/menu-pages.php:368
msgid ""
"<strong>Note:</strong> This option affects all feeds served by WordPress, "
"including the site feed, the site comment feed, post-specific comment feeds, "
"author feeds, search feeds, and category and tag feeds. See also: <a href="
"\"http://codex.wordpress.org/WordPress_Feeds\" target=\"_blank\">WordPress "
"Feeds</a>."
msgstr ""

#: includes/menu-pages.php:378
msgid "URI Exclusion Patterns"
msgstr ""

#: includes/menu-pages.php:382
msgid "Don't Cache These Special URI Exclusion Patterns?"
msgstr ""

#: includes/menu-pages.php:383
msgid ""
"Sometimes there are certain cases where a particular file, or a particular "
"group of files, should never be cached. This is where you will enter those "
"if you need to (one per line). Searches are performed against the <a href="
"\"https://gist.github.com/jaswsinc/338b6eb03a36c048c26f\" target=\"_blank\" "
"style=\"text-decoration:none;\"><code>REQUEST_URI</code></a>; i.e. <code>/"
"path/?query</code> (case sensitive). So, don't put in full URLs here, just "
"word fragments found in the file path (or query string) is all you need, "
"excluding the http:// and domain name. A wildcard <code>*</code> character "
"can also be used when necessary; e.g. <code>/category/abc-followed-by-*</"
"code>; (where <code>*</code> = anything, 0 or more characters in length)."
msgstr ""

#: includes/menu-pages.php:385
msgid ""
"<strong>Tip:</strong> let's use this example URL: <code>http://www.example."
"com/post/example-post-123</code>. To exclude this URL, you would put this "
"line into the field above: <code>/post/example-post-123</code>. Or, you "
"could also just put in a small fragment, like: <code>example</code> or "
"<code>example-*-123</code> and that would exclude any URI containing that "
"word fragment."
msgstr ""

#: includes/menu-pages.php:386 includes/menu-pages.php:404
#: includes/menu-pages.php:422 includes/menu-pages.php:524
#: includes/menu-pages.php:528
msgid ""
"<strong>Note:</strong> please remember that your entries here should be "
"formatted as a line-delimited list; e.g. one exclusion pattern per line."
msgstr ""

#: includes/menu-pages.php:396
msgid "HTTP Referrer Exclusion Patterns"
msgstr ""

#: includes/menu-pages.php:400
msgid "Don't Cache These Special HTTP Referrer Exclusion Patterns?"
msgstr ""

#: includes/menu-pages.php:401
msgid ""
"Sometimes there are special cases where a particular referring URL (or "
"referring domain) that sends you traffic; or even a particular group of "
"referring URLs or domains that send you traffic; should result in a page "
"being loaded on your site that is NOT from the cache (and that resulting "
"page should never be cached). This is where you will enter those if you need "
"to (one per line). Searches are performed against the <a href=\"http://www."
"php.net//manual/en/reserved.variables.server.php\" target=\"_blank\" style="
"\"text-decoration:none;\"><code>HTTP_REFERER</code></a> (case sensitive). A "
"wildcard <code>*</code> character can also be used when necessary; e.g. "
"<code>*.domain.com</code>; (where <code>*</code> = anything, 0 or more "
"characters in length)."
msgstr ""

#: includes/menu-pages.php:403
msgid ""
"<strong>Tip:</strong> let's use this example URL: <code>http://www.referring-"
"domain.com/search/?q=search+terms</code>. To exclude this referring URL, you "
"could put this line into the field above: <code>www.referring-domain.com</"
"code>. Or, you could also just put in a small fragment, like: <code>/search/"
"</code> or <code>q=*</code>; and that would exclude any referrer containing "
"that word fragment."
msgstr ""

#: includes/menu-pages.php:414
msgid "User-Agent Exclusion Patterns"
msgstr ""

#: includes/menu-pages.php:418
msgid "Don't Cache These Special User-Agent Exclusion Patterns?"
msgstr ""

#: includes/menu-pages.php:419
msgid ""
"Sometimes there are special cases when a particular user-agent (e.g. a "
"specific browser or a specific type of device); should be shown a page on "
"your site that is NOT from the cache (and that resulting page should never "
"be cached). This is where you will enter those if you need to (one per "
"line). Searches are performed against the <a href=\"http://www.php.net//"
"manual/en/reserved.variables.server.php\" target=\"_blank\" style=\"text-"
"decoration:none;\"><code>HTTP_USER_AGENT</code></a> (case insensitive). A "
"wildcard <code>*</code> character can also be used when necessary; e.g. "
"<code>Android *; Chrome/* Mobile</code>; (where <code>*</code> = anything, 0 "
"or more characters in length)."
msgstr ""

#: includes/menu-pages.php:421
msgid ""
"<strong>Tip:</strong> if you wanted to exclude iPhones put this line into "
"the field above: <code>iPhone;*AppleWebKit</code>. Or, you could also just "
"put in a small fragment, like: <code>iphone</code>; and that would exclude "
"any user-agent containing that word fragment. Note, this is just an example. "
"With a default installation of Quick Cache, there is no compelling reason to "
"exclude iOS devices (or any mobile device for that matter)."
msgstr ""

#: includes/menu-pages.php:432
msgid "Auto-Cache Engine"
msgstr ""

#: includes/menu-pages.php:437
msgid "Enable the Auto-Cache Engine?"
msgstr ""

#: includes/menu-pages.php:438
msgid ""
"After using Quick Cache for awhile (or any other page caching plugin, for "
"that matter); it becomes obvious that at some point (based on your "
"configured Expiration Time) Quick Cache has to refresh itself. It does this "
"by ditching its cached version of a page, reloading the database-driven "
"content, and then recreating the cache with the latest data. This is a never "
"ending regeneration cycle that is based entirely on your configured "
"Expiration Time."
msgstr ""

#: includes/menu-pages.php:439
msgid ""
"Understanding this, you can see that 99% of your visitors are going to "
"receive a lightning fast response from your server. However, there will "
"always be around 1% of your visitors that land on a page for the very first "
"time (before it's been cached), or land on a page that needs to have its "
"cache regenerated, because the existing cache has become outdated. We refer "
"to this as a <em>First-Come Slow-Load Issue</em>. Not a huge problem, but if "
"you're optimizing your site for every ounce of speed possible, the Auto-"
"Cache Engine can help with this. The Auto-Cache Engine has been designed to "
"combat this issue by taking on the responsibility of being that first "
"visitor to a page that has not yet been cached, or has an expired cache. The "
"Auto-Cache Engine is powered, in part, by <a href=\"http://codex.wordpress."
"org/Category:WP-Cron_Functions\" target=\"_blank\">WP-Cron</a> (already "
"built into WordPress). The Auto-Cache Engine runs at 15-minute intervals via "
"WP-Cron. It also uses the <a href=\"http://core.trac.wordpress.org/browser/"
"trunk/wp-includes/http.php\" target=\"_blank\">WP_Http</a> class, which is "
"also built into WordPress already."
msgstr ""

#: includes/menu-pages.php:440
msgid ""
"The Auto-Cache Engine obtains its list of URLs to auto-cache, from two "
"different sources. It can read an <a href=\"http://wordpress.org/extend/"
"plugins/google-sitemap-generator/\" target=\"_blank\">XML Sitemap</a> and/or "
"a list of specific URLs that you supply. If you supply both sources, it will "
"use both sources collectively. The Auto-Cache Engine takes ALL of your other "
"configuration options into consideration too, including your Expiration "
"Time, as well as any cache exclusion rules."
msgstr ""

#: includes/menu-pages.php:442
msgid "No, leave the Auto-Cache Engine disabled please."
msgstr ""

#: includes/menu-pages.php:443
msgid "Yes, I want the Auto-Cache Engine to keep pages cached automatically."
msgstr ""

#: includes/menu-pages.php:447
msgid "XML Sitemap URL (or an XML Sitemap Index)"
msgstr ""

#: includes/menu-pages.php:450
msgid "A List of URLs to Auto-Cache (One Per Line)"
msgstr ""

#: includes/menu-pages.php:453
msgid "Auto-Cache Delay Timer (in Milliseconds)"
msgstr ""

#: includes/menu-pages.php:454
msgid ""
"As the Auto-Cache Engine runs through each URL, you can tell it to wait X "
"number of milliseconds between each connection that it makes. It is strongly "
"suggested that you DO have some small delay here. Otherwise, you run the "
"risk of hammering your own web server with multiple repeated connections "
"whenever the Auto-Cache Engine is running. This is especially true on very "
"large sites; where there is the potential for hundreds of repeated "
"connections as the Auto-Cache Engine goes through a long list of URLs. "
"Adding a delay between each connection will prevent the Auto-Cache Engine "
"from placing a heavy load on the processor that powers your web server. A "
"value of <code>500</code> milliseconds is suggested here (half a second). If "
"you experience problems, you can bump this up a little at a time, in "
"increments of <code>500</code> milliseconds; until you find a happy place "
"for your server. <em>Please note that <code>1000</code> milliseconds = "
"<code>1</code> full second.</em>"
msgstr ""

#: includes/menu-pages.php:457
msgid "Auto-Cache User-Agent String"
msgstr ""

#: includes/menu-pages.php:459
msgid ""
"This is how the Auto-Cache Engine identifies itself when connecting to URLs. "
"See <a href=\"http://en.wikipedia.org/wiki/User_agent\" target=\"_blank"
"\">User Agent</a> in the Wikipedia."
msgstr ""

#: includes/menu-pages.php:470
msgid "HTML Compression (Experimental)"
msgstr ""

#: includes/menu-pages.php:475
msgid "Enable WebSharks™ HTML Compression?"
msgstr ""

#: includes/menu-pages.php:476
msgid ""
"This is an experimental feature, however it offers a potentially HUGE speed "
"boost. You can <a href=\"https://github.com/WebSharks/HTML-Compressor\" "
"target=\"_blank\">learn more here</a>. Please use with caution."
msgstr ""

#: includes/menu-pages.php:478
msgid ""
"<strong>WARNING:</strong> The HTML Compressor requires the <a href=\"http://"
"www.php.net/manual/en/book.curl.php\" target=\"_blank\" rel=\"external"
"\">cURL extension for PHP</a>. cURL must also be compiled together with <a "
"href=\"http://www.php.net/manual/en/book.openssl.php\" target=\"_blank\" rel="
"\"external\">OpenSSL</a>. Quick Cache has detected that one or both of these "
"are currently missing. Please check with your hosting company to resolve "
"this message."
msgstr ""

#: includes/menu-pages.php:480
msgid "No, do NOT compress HTML/CSS/JS code at runtime."
msgstr ""

#: includes/menu-pages.php:481
msgid "Yes, I want to compress HTML/CSS/JS for blazing fast speeds."
msgstr ""

#: includes/menu-pages.php:483
msgid ""
"<strong>Note:</strong> This is experimental. Please <a href=\"https://github."
"com/WebSharks/HTML-Compressor/issues\" target=\"_blank\">report issues here</"
"a>."
msgstr ""

#: includes/menu-pages.php:486
msgid "HTML Compression Options"
msgstr ""

#: includes/menu-pages.php:487
msgid ""
"You can <a href=\"https://github.com/WebSharks/HTML-Compressor\" target="
"\"_blank\">learn more about all of these options here</a>."
msgstr ""

#: includes/menu-pages.php:489
msgid "Yes, combine CSS from &lt;head&gt; and &lt;body&gt; into fewer files."
msgstr ""

#: includes/menu-pages.php:490
msgid ""
"No, do not combine CSS from &lt;head&gt; and &lt;body&gt; into fewer files."
msgstr ""

#: includes/menu-pages.php:493
msgid "Yes, compress the code in any unified CSS files."
msgstr ""

#: includes/menu-pages.php:494
msgid "No, do not compress the code in any unified CSS files."
msgstr ""

#: includes/menu-pages.php:497
msgid "Yes, combine JS from &lt;head&gt; into fewer files."
msgstr ""

#: includes/menu-pages.php:498
msgid "No, do not combine JS from &lt;head&gt; into fewer files."
msgstr ""

#: includes/menu-pages.php:501
msgid "Yes, combine JS footer scripts into fewer files."
msgstr ""

#: includes/menu-pages.php:502
msgid "No, do not combine JS footer scripts into fewer files."
msgstr ""

#: includes/menu-pages.php:505
msgid "Yes, combine CSS/JS from remote resources too."
msgstr ""

#: includes/menu-pages.php:506
msgid "No, do not combine CSS/JS from remote resources."
msgstr ""

#: includes/menu-pages.php:509
msgid "Yes, compress the code in any unified JS files."
msgstr ""

#: includes/menu-pages.php:510
msgid "No, do not compress the code in any unified JS files."
msgstr ""

#: includes/menu-pages.php:513
msgid "Yes, compress inline JavaScript snippets."
msgstr ""

#: includes/menu-pages.php:514
msgid "No, do not compress inline JavaScript snippets."
msgstr ""

#: includes/menu-pages.php:517
msgid "Yes, compress (remove extra whitespace) in the final HTML code too."
msgstr ""

#: includes/menu-pages.php:518
msgid "No, do not compress the final HTML code."
msgstr ""

#: includes/menu-pages.php:521
msgid "CSS Exclusion Patterns?"
msgstr ""

#: includes/menu-pages.php:522
msgid ""
"Sometimes there are special cases when a particular CSS file should NOT be "
"consolidated or compressed in any way. This is where you will enter those if "
"you need to (one per line). Searches are performed against the <code>&lt;"
"link href=&quot;&quot;&gt;</code> value, and also against the contents of "
"any inline <code>&lt;style&gt;</code> tags (case insensitive). A wildcard "
"<code>*</code> character can also be used when necessary; e.g. <code>xy*-"
"framework</code>; (where <code>*</code> = anything, 0 or more characters in "
"length)."
msgstr ""

#: includes/menu-pages.php:525
msgid "JavaScript Exclusion Patterns?"
msgstr ""

#: includes/menu-pages.php:526
msgid ""
"Sometimes there are special cases when a particular JS file should NOT be "
"consolidated or compressed in any way. This is where you will enter those if "
"you need to (one per line). Searches are performed against the <code>&lt;"
"script src=&quot;&quot;&gt;</code> value, and also against the contents of "
"any inline <code>&lt;script&gt;</code> tags (case insensitive). A wildcard "
"<code>*</code> character can also be used when necessary; e.g. <code>xy*-"
"framework</code>; (where <code>*</code> = anything, 0 or more characters in "
"length)."
msgstr ""

#: includes/menu-pages.php:530
msgid "HTML Compression Cache Expiration"
msgstr ""

#: includes/menu-pages.php:532
msgid ""
"<strong>Tip:</strong> the value that you specify here MUST be compatible "
"with PHP's <a href=\"http://php.net/manual/en/function.strtotime.php\" "
"target=\"_blank\" style=\"text-decoration:none;\"><code>strtotime()</code></"
"a> function. Examples: <code>2 hours</code>, <code>7 days</code>, <code>6 "
"months</code>, <code>1 year</code>."
msgstr ""
"<strong>ヒント：</strong> 設定する値は PHP関数<a href=\"http://php.net/"
"manual/en/function.strtotime.php\" target=\"_blank\" style=\"text-decoration:"
"none;\"><code>strtotime()</code></a>で利用できる値でなければなりません。例："
"<code>2 hours</code>, <code>7 days</code>, <code>6 months</code>, <code>1 "
"year</code>"

#: includes/menu-pages.php:533
msgid ""
"<strong>Note:</strong> This does NOT impact the overall cache expiration "
"time that you configure with Quick Cache. It only impacts the sub-routines "
"provided by the HTML Compressor. In fact, this expiration time is mostly "
"irrelevant. The HTML Compressor uses an internal checksum, and it also "
"checks <code>filemtime()</code> before using an existing cache file. The "
"HTML Compressor class also handles the automatic cleanup of your cache "
"directories to keep it from growing too large over time. Therefore, unless "
"you have VERY little disk space there is no reason to set this to a lower "
"value (even if your site changes dynamically quite often). If anything, you "
"might like to increase this value which could help to further reduce server "
"load. You can <a href=\"https://github.com/WebSharks/HTML-Compressor\" "
"target=\"_blank\">learn more here</a>. We recommend setting this value to at "
"least double that of your overall Quick Cache expiration time."
msgstr ""

#: includes/menu-pages.php:542
msgid "GZIP Compression"
msgstr "GZIP　圧縮"

#: includes/menu-pages.php:547
msgid ""
"<a href=\"https://developers.google.com/speed/articles/gzip\" target=\"_blank"
"\">GZIP Compression</a> (Optional; Highly Recommended)"
msgstr ""
"<a href=\"https://developers.google.com/speed/articles/gzip\" target=\"_blank"
"\">GZIP Compression</a>(オプション：高度なおすすめ)"

#: includes/menu-pages.php:548
msgid ""
"You don't have to use an <code>.htaccess</code> file to enjoy the "
"performance enhancements provided by this plugin; caching is handled "
"automatically by WordPress/PHP alone. That being said, if you want to take "
"advantage of the additional speed enhancements associated w/ GZIP "
"compression (and we do recommend this), then you WILL need an <code>."
"htaccess</code> file to accomplish that part."
msgstr ""
"このプラグインで、パフォーマンスの効果を楽しむ場合、<code>.htaccess</code>を"
"使用する必要はありません。キャッシングは、WordPress/PHPが自動的に処理します。"
"もし、あなたが、w/ GZIP 圧縮による追加的なスピード強化をしたい場合は、（私た"
"ちは、これをお勧めします）<code>.htaccess</code>が必要になります。"

#: includes/menu-pages.php:549
msgid ""
"Quick Cache fully supports GZIP compression on its output. However, it does "
"not handle GZIP compression directly. We purposely left GZIP compression out "
"of this plugin, because GZIP compression is something that should really be "
"enabled at the Apache level or inside your <code>php.ini</code> file. GZIP "
"compression can be used for things like JavaScript and CSS files as well, so "
"why bother turning it on for only WordPress-generated pages when you can "
"enable GZIP at the server level and cover all the bases!"
msgstr ""
"クイックキャッシュは、GZIP圧縮をフルサポートします。しかし、それは、直接GZIP"
"圧縮されるわけではなく、Apacheのレベルで<code>php.ini</code>から有効にする必"
"要があります。あなたは、サーバーレベルでGZIPを有効にできる場合、WordPressの"
"ページ生成だけでなく、GZIP圧縮は、javascriptやCSSにも使うことが出来ます"

#: includes/menu-pages.php:550
msgid ""
"If you want to enable GZIP, create an <code>.htaccess</code> file in your "
"WordPress® installation directory, and put the following few lines in it. "
"Alternatively, if you already have an <code>.htaccess</code> file, just add "
"these lines to it, and that is all there is to it. GZIP is now enabled in "
"the recommended way! See also: <a href=\"https://developers.google.com/speed/"
"articles/gzip\" target=\"_blank\"><i class=\"fa fa-youtube-play\"></i> video "
"about GZIP Compression</a>."
msgstr ""
"GZIPを有効にしたい場合、ワードプレスのインストールディレクトリに<code>."
"htaccess</code>を作成し、以下のコードを含めてください。もし、すでに、<code>."
"htaccess</code>を使っている場合には、以下の行を追加してください。GZIPが推奨さ"
"れる方法で有効化どうかは、 <a href=\"https://developers.google.com/speed/"
"articles/gzip\" target=\"_blank\"><i class=\"fa fa-youtube-play\"></i> GZIP "
"圧縮のビデオ</a>を参照してください。"

#: includes/menu-pages.php:563
msgid "Dynamic Version Salt"
msgstr ""

#: includes/menu-pages.php:568
msgid ""
"<i class=\"fa fa-flask\"></i> <span style=\"display:inline-block; "
"padding:5px; border-radius:3px; background:#FFFFFF; color:#354913;\"><span "
"style=\"font-weight:bold; font-size:80%;\">GEEK ALERT</span></span> This is "
"for VERY advanced users only..."
msgstr ""

#: includes/menu-pages.php:569
msgid ""
"<em>Note: Understanding the Quick Cache <a href=\"http://www.websharks-inc."
"com/r/quick-cache-branched-cache-structure-wiki/\" target=\"_blank"
"\">Branched Cache Structure</a> is a prerequisite to understanding how "
"Dynamic Version Salts are added to the mix.</em>"
msgstr ""

#: includes/menu-pages.php:570
msgid ""
"A Version Salt gives you the ability to dynamically create multiple "
"variations of the cache, and those dynamic variations will be served on "
"subsequent visits; e.g. if a visitor has a specific cookie (of a certain "
"value) they will see pages which were cached with that version (i.e. w/ that "
"Version Salt: the value of the cookie). A Version Salt can really be "
"anything."
msgstr ""

#: includes/menu-pages.php:571
msgid ""
"A Version Salt can be a single variable like <code>$_COOKIE['my_cookie']</"
"code>, or it can be a combination of multiple variables, like <code>$_COOKIE"
"['my_cookie'].$_COOKIE['my_other_cookie']</code>. (When using multiple "
"variables, please separate them with a dot, as shown in the example.)"
msgstr ""

#: includes/menu-pages.php:572
msgid ""
"Experts could even use PHP ternary expressions that evaluate into something. "
"For example: <code>((preg_match('/iPhone/i', $_SERVER['HTTP_USER_AGENT'])) ? "
"'iPhones' : '')</code>. This would force a separate version of the cache to "
"be created for iPhones (e.g., <code>/cache/PROTOCOL/HOST/REQUEST-URI.v/"
"iPhones.html</code>)."
msgstr ""

#: includes/menu-pages.php:573
msgid ""
"For more documentation, please see <a href=\"http://www.websharks-inc.com/r/"
"quick-cache-dynamic-version-salts-wiki/\" target=\"_blank\">Dynamic Version "
"Salts</a>."
msgstr ""

#: includes/menu-pages.php:575
msgid ""
"Create a Dynamic Version Salt For Quick Cache? &nbsp;&nbsp;&nbsp;&nbsp;"
"&nbsp; <span style=\"font-size:90%; opacity:0.5;\">150% OPTIONAL</span>"
msgstr ""

#: includes/menu-pages.php:577
msgid ""
"<a href=\"http://php.net/manual/en/language.variables.superglobals.php\" "
"target=\"_blank\">Super Globals</a> work here; <a href=\"http://codex."
"wordpress.org/Editing_wp-config.php#table_prefix\" target=\"_blank\"><code>"
"$GLOBALS['table_prefix']</code></a> is a popular one. Or, perhaps a PHP "
"Constant defined in <code>/wp-config.php</code>; such as <code>WPLANG</code> "
"or <code>DB_HOST</code>."
msgstr ""

#: includes/menu-pages.php:578
msgid ""
"<strong>Important:</strong> your Version Salt is scanned for PHP syntax "
"errors via <a href=\"http://phpcodechecker.com/\" target=\"_blank"
"\"><code>phpCodeChecker.com</code></a>. If errors are found, you'll receive "
"a notice in the Dashboard."
msgstr ""

#: includes/menu-pages.php:579
msgid ""
"If you've enabled a separate cache for each user (optional) that's perfectly "
"OK. A Version Salt works with user caching too."
msgstr ""

#: includes/menu-pages.php:587
msgid "Theme/Plugin Developers"
msgstr "テーマ　プラグイン開発者向け"

#: includes/menu-pages.php:592
msgid "Developing a Theme or Plugin for WordPress?"
msgstr "WordPressのテーマやプラグインをカスタマイズしますか？"

#: includes/menu-pages.php:593
msgid ""
"<strong>Tip:</strong> Quick Cache can be disabled temporarily. If you're a "
"theme/plugin developer, you can set a flag within your PHP code to disable "
"the cache engine at runtime. Perhaps on a specific page, or in a specific "
"scenario. In your PHP script, set: <code>$_SERVER['QUICK_CACHE_ALLOWED'] = "
"FALSE;</code> or <code>define('QUICK_CACHE_ALLOWED', FALSE)</code>. Quick "
"Cache is also compatible with: <code>define('DONOTCACHEPAGE', TRUE)</code>. "
"It does't matter where or when you define one of these, because Quick Cache "
"is the last thing to run before script execution ends."
msgstr ""
"<strong>ヒント：</strong>クイックキャッシュは、一時的に無効にすることが出来ま"
"す。あなたが、テーマやプラグイン開発者なら、PHPコード内でフラグを設定し　実行"
"時にキャッシュエンジンを無効にすることが出来ます。たぶん、特定のページや特定"
"のシナリオのPHPで、<code>$_SERVER['QUICK_CACHE_ALLOWED'] = FALSE;</code>や"
"<code>define('QUICK_CACHE_ALLOWED', FALSE)</code>を設定します。クイックキャッ"
"シュは、<code>define('DONOTCACHEPAGE', TRUE)</code>にも対応しています。クイッ"
"クキャッシュは、これらのスクリプトが終了する直前に実行するので、いつでも、ど"
"こにでもこれらを定義することが出来ます。"

#: includes/menu-pages.php:595
msgid "Writing \"Advanced Cache\" Plugins Specifically for Quick Cache"
msgstr "クイックキャッシュ用の\"Advanced Cache\"をプラグインに書き込む"

#: includes/menu-pages.php:596
msgid ""
"Theme/plugin developers can take advantage of the Quick Cache plugin "
"architecture by creating PHP files inside this special directory: <code>/wp-"
"content/ac-plugins/</code>. There is an <a href=\"https://github.com/"
"WebSharks/Quick-Cache/blob/000000-dev/quick-cache/includes/ac-plugin.example."
"php\" target=\"_blank\">example plugin file @ GitHub</a> (please review it "
"carefully and ask questions). If you develop a plugin for Quick Cache, "
"please share it with the community by publishing it in the plugins "
"respository at WordPress.org."
msgstr ""
"テーマやプラグイン開発者は、特別なディレクトリ<code>/wp-content/ac-plugins/</"
"code>.にPHPファイルを作成し、クイックキャッシュプラグインアーキテクチャーを活"
"用することが出来ます。ここに <a href=\"https://github.com/WebSharks/Quick-"
"Cache/blob/000000-dev/quick-cache/includes/ac-plugin.example.php\" target="
"\"_blank\">プラグインのサンプル例 @ GitHub</a>があります。（慎重に検討し、質"
"問してください）クイックキャッシュ用のプラグインを開発する場合は、プラグイン"
"をWordPress.orgのプラグインリポジトリでコミュニティと共有してください。"

#: includes/menu-pages.php:597
msgid ""
"<strong>Why does Quick Cache have it's own plugin architecture?</strong> "
"WordPress loads the <code>advanced-cache.php</code> drop-in file (for "
"caching purposes) very early-on; before any other plugins or a theme. For "
"this reason, Quick Cache implements it's own watered-down version of "
"functions like <code>add_action()</code>, <code>do_action()</code>, "
"<code>add_filter()</code>, <code>apply_filters()</code>."
msgstr ""
"<strong>なぜクイックキャッシュには、プラグイン独自のアーキテクチャーがあるの"
"ですか？</strong>ワードプレスは、非常に早い段階で、プラグインやテーマより先"
"に、<code>advanced-cache.php</code> drop-in file (キャッシュ用に をロードしま"
"す。このためクイックキャッシュは、<code>add_action()</code>, <code>do_action"
"()</code>, <code>add_filter()</code>, <code>apply_filters()</code>のような、"
"加減した独自関数を実装しています"

#: includes/menu-pages.php:607
msgid "Import/Export Options"
msgstr "インポート　エクスポート　オプション"

#: includes/menu-pages.php:612
msgid "Import Options from Another Quick Cache Installation?"
msgstr "他のクイックキャッシュから設定をインポートしますか？"

#: includes/menu-pages.php:613
msgid ""
"Upload your <code>%1$s-options.json</code> file and click \"Save All Changes"
"\" below. The options provided by your import file will override any that "
"exist currently."
msgstr ""
" <code>%1$s-options.json</code>をアップロードし、「すべての変更を保存」をク"
"リックしてください。オプションの設定をインポートして、現在の設定を上書きしま"
"す。"

#: includes/menu-pages.php:616
msgid "Export Existing Options from this Quick Cache Installation?"
msgstr "クイックキャッシュの既存の設定をエクスポートしますか？"

#: includes/menu-pages.php:618
msgid "%1$s-options.json"
msgstr "%1$s-options.json"

#: includes/menu-pages.php:619
msgid ""
"Download your existing options and import them all into another Quick Cache "
"installation; saves time on future installs."
msgstr ""
"オプションの設定をダウンロードして別のクイックキャッシュのインストールにすべ"
"てをインストールします。将来インストールする時に、時間を節約できます。"

#: includes/menu-pages.php:626
msgid "Save All Changes"
msgstr "すべての変更を保存"

#: includes/share.php:219
msgid "Unable to determine cache directory location."
msgstr "キャッシュディレクトリの場所を判別できません"

#: includes/share.php:1093
msgid "Unable to delete file: `%1$s`."
msgstr "ファイル： `%1$s`を削除できません"

#: includes/share.php:1133
msgid "Invalid hook."
msgstr "無効なフック"

#: includes/version-specific-upgrade.php:66
msgid ""
"<strong>Quick Cache:</strong> this version is a <strong>complete rewrite</"
"strong> :-) Please review your Quick Cache options carefully!"
msgstr ""
"<strong>クイックキャッシュ:</strong>このバージョンは、<strong>完全に書き直さ"
"れました</strong> :-)クイックキャッシュのオプションを慎重に確認してください。"

#: includes/version-specific-upgrade.php:76
msgid ""
"<strong>Quick Cache Feature Notice:</strong> This version of Quick Cache "
"adds new options for Feed caching. Feed caching is now disabled by default. "
"If you wish to enable feed caching, please visit the Quick Cache options "
"panel."
msgstr ""
"<strong>お知らせ:クイックキャッシュの機能</strong>クイックキャッシュ（この"
"バージョン）は、フィードキャッシングのための新しいオプションが追加されます。"
"フィードキャッシングは、デフォルトで無効になっています。フィードキャッシュを"
"有効にしたい場合は、クイックキャッシュのオプションパネルをご覧ください"

#: includes/version-specific-upgrade.php:106
msgid ""
"<strong>Quick Cache Feature Notice:</strong> This version of Quick Cache "
"introduces a new <a href=\"http://www.websharks-inc.com/r/quick-cache-"
"branched-cache-structure-wiki/\" target=\"_blank\">Branched Cache Structure</"
"a> and several other <a href=\"http://www.websharks-inc.com/post/quick-cache-"
"v140605-now-available/\" target=\"_blank\">new features</a>."
msgstr ""
"<strong>お知らせ　クイックキャッシュの機能:</strong>クイックキャッシュ（この"
"バージョン）は <a href=\"http://www.websharks-inc.com/r/quick-cache-branched-"
"cache-structure-wiki/\" target=\"_blank\">新しいキャッシュ分岐構成</a>といく"
"つかの他の <a href=\"http://www.websharks-inc.com/post/quick-cache-v140605-"
"now-available/\" target=\"_blank\">新機能s</a>を発表します"

#: includes/version-specific-upgrade.php:128
msgid ""
"<strong>Quick Cache Notice:</strong> This version of Quick Cache changes the "
"default base directory that it uses, from <code>ABSPATH</code> to "
"<code>WP_CONTENT_DIR</code>. This is for improved compatibility with "
"installations that choose to use a custom <code>WP_CONTENT_DIR</code> "
"location."
msgstr ""
"<strong>クイックキャッシュ　お知らせ:</strong> このバージョンのクイックキャッ"
"シュは、使用するデフォルトベースディレクトリが、 <code>ABSPATH</code>から"
"<code>WP_CONTENT_DIR</code>に、変更になりました。インストールの互換性の改善の"
"ため<code>WP_CONTENT_DIR</code> が選択されました。"

#: includes/version-specific-upgrade.php:129
msgid ""
"Quick Cache has detected that your previously configured cache directory may "
"have been in conflict with this change. As a result, your Quick Cache "
"configuration has been updated to the new default value; just to keep things "
"running smoothly for you :-). If you would like to review this change, "
"please see: <code>Dashboard ⥱ Quick Cache ⥱ Directory &amp; Expiration Time</"
"code>; where you may customize it further if necessary."
msgstr ""

#: includes/wp-php53.php:31
msgid ""
"<strong>%1$s is NOT active; %1$s requires PHP v5.3 (or higher).</strong>"
msgstr ""
"<strong>%1$s は、非アクティブです %1$s は PHP v5.3 (または、それ以上が必要で"
"す).</strong>"

#: includes/wp-php53.php:32
msgid "You're currently running <code>PHP v%1$s</code>."
msgstr "<code>PHP v%1$s</code>を実行しています"

#: includes/wp-php53.php:33
msgid ""
"A simple update is necessary. Please ask your web hosting company to do this "
"for you."
msgstr ""
"アップデートは、基本的に必要です。アップデートを行う方法をホスティング会社に"
"訊ねてください"

#: includes/wp-php53.php:34
msgid "To remove this message, please deactivate %1$s."
msgstr "このメッセージを削除するには、 %1$sをデアクティベートしてください"

#: quick-cache.inc.php:348
msgid ""
"<strong>Quick Cache:</strong> detected a new version of itself. Recompiling "
"w/ latest version... wiping the cache... all done :-)"
msgstr ""
"<strong>Quick Cache:</strong>クイックキャッシュの新しいバージョンを検出しまし"
"た。リコンパイリング w/ 最新バージョン...キャッシュwiping...すべて完了:-)"

#. #-#-#-#-#  quick-cache.pot (Quick Cache 141001)  #-#-#-#-#
#. Plugin Name of the plugin/theme
#: quick-cache.inc.php:501 quick-cache.inc.php:517
msgid "Quick Cache"
msgstr "クイックキャッシュ"

#: quick-cache.inc.php:535
msgid "Settings"
msgstr "設定"

#: quick-cache.inc.php:536
msgid "Preview Pro Features"
msgstr ""

#: quick-cache.inc.php:537
msgid "Upgrade"
msgstr "アップグレード"

#: quick-cache.inc.php:583 quick-cache.inc.php:654
msgid "dismiss &times;"
msgstr ""

#: quick-cache.inc.php:712
msgid "Every 15 Minutes"
msgstr "15分毎"

#: quick-cache.inc.php:748
msgid "Unable to wipe file: `%1$s`."
msgstr "ファイル：`%1$s`もまた、wipeできません"

#: quick-cache.inc.php:753
msgid "Unable to wipe dir: `%1$s`."
msgstr "ディレクトリ `%1$s`もまた、wipeできません"

#: quick-cache.inc.php:762
msgid "Unable to also wipe file: `%1$s`."
msgstr "ファイル： `%1$s`もまたwipeできません"

#: quick-cache.inc.php:767
msgid "Unable to also wipe dir: `%1$s`."
msgstr "ディレクトリ：`%1$s`もまたwipeできません"

#: quick-cache.inc.php:809
msgid "Unable to clear file: `%1$s`."
msgstr "ファイル： `%1$s` clearできません"

#: quick-cache.inc.php:814
msgid "Unable to clear dir: `%1$s`."
msgstr "ディレクトリ：`%1$s`　clearできません"

#: quick-cache.inc.php:849
msgid "Unable to purge file: `%1$s`."
msgstr "ファイル：`%1$s` purge できません"

#: quick-cache.inc.php:882
msgid ""
"<strong>Quick Cache:</strong> detected significant changes. Found cache "
"files (auto-wiping)."
msgstr ""
"<strong>クイックキャッシュ：</strong>キャッシュファイルの大幅な変更を検出しま"
"した (auto-wiping)."

#: quick-cache.inc.php:925
msgid ""
"<strong>Quick Cache:</strong> detected important site changes. Found cache "
"files for this site (auto-clearing)."
msgstr ""
"<strong>クイックキャッシュ：</strong>このサイトのキャッシュファイルの重要な変"
"更を検出しました (auto-clearing)"

#: quick-cache.inc.php:1002
msgid "Post"
msgstr "投稿"

#: quick-cache.inc.php:1017 quick-cache.inc.php:1472 quick-cache.inc.php:1547
#: quick-cache.inc.php:1619 quick-cache.inc.php:1725 quick-cache.inc.php:1882
msgid "Unable to auto-purge file: `%1$s`."
msgstr "ファイル： `%1$s`　auto-purge　できません"

#: quick-cache.inc.php:1024
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found cache file(s) for %1$s "
"ID: <code>%2$s</code> (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong>cache file(s) for %1$s ID: <code>%2$s</"
"code> の変更を検出しました。(auto-purging)."

#: quick-cache.inc.php:1357
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found XML feeds of type "
"<code>%1$s</code> (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong>変更を検出しました Found XML feeds of "
"type <code>%1$s</code> (auto-purging)."

#: quick-cache.inc.php:1413
msgid "Unable to auto-purge XML sitemap file: `%1$s`."
msgstr "XML sitemap file: `%1$s`　オートパージできません"

#: quick-cache.inc.php:1419
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found XML sitemaps (auto-"
"purging)."
msgstr ""
"<strong>クイックキャッシュ</strong> Found XML sitemaps の変更を検出しまし"
"た。 (auto-purging)"

#: quick-cache.inc.php:1479
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found cache file(s) for the "
"designated \"Home Page\" (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong> \"Home Page\" のキャッシュの変更を検出"
"しました(auto-purging)"

#: quick-cache.inc.php:1554
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found cache file(s) for the "
"designated \"Posts Page\" (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong> \"Posts Page\"のキャッシュの変更を検出"
"しました (auto-purging)."

#: quick-cache.inc.php:1626
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found cache file(s) for "
"Custom Post Type <code>%1$s</code> (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong> カスタム投稿タイプ<code>%1$s</code>の"
"キャッシュの変更を検出しました。"

#: quick-cache.inc.php:1731
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found cache files for Author "
"Page: <code>%1$s</code> (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong> Author Page: <code>%1$s</code>のキャッ"
"シュの変更を検出しました"

#: quick-cache.inc.php:1889
msgid ""
"<strong>Quick Cache:</strong> detected changes. Found cache files for %1$s: "
"<code>%2$s</code> (auto-purging)."
msgstr ""
"<strong>クイックキャッシュ：</strong>%1$s: <code>%2$s</code> のキャッシュの変"
"更を検知しました(auto-purging)"

#: quick-cache.inc.php:2174 quick-cache.inc.php:2200
msgid ""
"Doing it wrong! Missing `base_dir` option value. MUST call this method after "
"`setup()`."
msgstr ""
"`base_dir` オプション値が間違っています。`setup()`の後で呼び出す必要がありま"
"す。"

#: quick-cache.inc.php:2603
msgid "Unable to remove file: `%1$s`."
msgstr "ファイル： `%1$s`を削除できません"

#: quick-cache.inc.php:2608
msgid "Unable to remove dir: `%1$s`."
msgstr "ディレクトリ： `%1$s`を削除できません"

#: quick-cache.inc.php:2613
msgid "Unable to remove base dir: `%1$s`."
msgstr "ベースディレクトリ： `%1$s`を削除できません"

#: quick-cache.inc.php:2648
msgid ""
"Please disable the LITE version of Quick Cache before you activate the PRO "
"version."
msgstr ""
"Please disable the LITE version of Quick Cache before you activate the PRO "
"version."

#. Plugin URI of the plugin/theme
msgid "http://www.websharks-inc.com/product/quick-cache/"
msgstr "http://www.websharks-inc.com/product/quick-cache/"

#. Description of the plugin/theme
msgid "WordPress advanced cache plugin; speed without compromise!"
msgstr "WordPress advanced cache plugin; speed without compromise!"

#. Author of the plugin/theme
msgid "s2Member® / WebSharks, Inc."
msgstr "s2Member® / WebSharks, Inc."

#. Author URI of the plugin/theme
msgid "http://www.s2member.com"
msgstr "http://www.s2member.com"
