diff --git a/zenmap/share/zenmap/locale/ja.po b/zenmap/share/zenmap/locale/ja.po index 165809e17..d40bea723 100644 --- a/zenmap/share/zenmap/locale/ja.po +++ b/zenmap/share/zenmap/locale/ja.po @@ -1,11 +1,11 @@ msgid "" msgstr "" "Project-Id-Version: \n" -"Report-Msgid-Bugs-To: nmap-dev () insecure org\n" +"Report-Msgid-Bugs-To: nmap-dev@insecure.org\n" "POT-Creation-Date: 2012-05-22 12:52-0700\n" "PO-Revision-Date: \n" "Last-Translator: Yuji Tounai \n" -"Language-Team: bogus.jp \n" +"Language-Team: bogus.jp \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -102,12 +102,12 @@ msgstr "クラッシュを報告" #: zenmapGUI/CrashReport.py:130 #, python-format -msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the nmap-dev () insecure org mailing list. (More about the list.) The developers will see your report and try to fix the problem." -msgstr "予期しないエラーが発生しました。%(app_name)s. スタックトレースをコピーして以下の宛先のメーリングリストに送信してください。nmap-dev () insecure org (このメーリングリストについて) 開発者たちはレポートを見て問題解決に取り組みます。" +msgid "An unexpected error has crashed %(app_name)s. Please copy the stack trace below and send it to the nmap-dev@insecure.org mailing list. (More about the list.) The developers will see your report and try to fix the problem." +msgstr "予期しないエラーが発生しました。%(app_name)s. スタックトレースをコピーして以下の宛先のメーリングリストに送信してください。nmap-dev@insecure.org (このメーリングリストについて) 開発者たちはレポートを見て問題解決に取り組みます。" #: zenmapGUI/CrashReport.py:138 -msgid "Copy and email to nmap-dev () insecure org:" -msgstr "コピーして、nmap-dev () insecure org:にメールを送ってください。" +msgid "Copy and email to nmap-dev@insecure.org:" +msgstr "コピーして、nmap-dev@insecure.org:にメールを送ってください。" #: zenmapGUI/OptionBuilder.py:258 msgid "Choose file" @@ -790,13 +790,13 @@ msgstr "バグレポート方法" msgid "" "How to report a bug\n" "\n" -"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from %(nmap_web)s. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <nmap-dev () insecure org>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev () insecure org are far more likely to be answered than those sent to Fyodor directly.\n" +"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from %(nmap_web)s. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <nmap-dev@insecure.org>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are far more likely to be answered than those sent to Fyodor directly.\n" "\n" "Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n" msgstr "" "バグレポートの送り方\n" "\n" -"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from %(nmap_web)s. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <nmap-dev () insecure org>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev () insecure org are far more likely to be answered than those sent to Fyodor directly.\n" +"Like their author, %(nmap)s and %(app)s aren't perfect. But you can help make it better by sending bug reports or even writing patches. If %(nmap)s doesn't behave the way you expect, first upgrade to the latest version available from %(nmap_web)s. If the problem persists, do some research to determine whether it has already been discovered and addressed. Try Googling the error message or browsing the nmap-dev archives at http://seclists.org/. Read the full manual page as well. If nothing comes of this, mail a bug report to <nmap-dev@insecure.org>. Please include everything you have learned about the problem, as well as what version of Nmap you are running and what operating system version it is running on. Problem reports and %(nmap)s usage questions sent to nmap-dev@insecure.org are far more likely to be answered than those sent to Fyodor directly.\n" "\n" "Code patches to fix bugs are even better than bug reports. Basic instructions for creating patch files with your changes are available at http://nmap.org/data/HACKING. Patches may be sent to nmap-dev (recommended) or to Fyodor directly.\n" diff --git a/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo b/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo index aceecd0b0..1013d1881 100644 Binary files a/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo and b/zenmap/share/zenmap/locale/ja/LC_MESSAGES/zenmap.mo differ