aitzol/Plume
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
8696185d1e
Plume/po/ja.po

768 lines
17 KiB
Plaintext
Raw Normal View History

i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid ""
msgstr ""
"Project-Id-Version: plume\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-06-15 16:33-0700\n"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
"PO-Revision-Date: 2018-12-08 22:31+0900\n"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
"Last-Translator: Ryo Nakano <ryonakaknock3@gmail.com>\n"
"Language-Team: \n"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Poedit 2.2\n"
msgid "Latest articles"
msgstr "最新記事"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "No articles to see here yet."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ここにはまだ表示できる投稿がありません。"
msgid "New article"
msgstr "新しい記事"
msgid "New blog"
msgstr "新しいブログ"
msgid "Create a blog"
msgstr "ブログを作成"
msgid "Title"
msgstr "タイトル"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Create the blog"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ブログを作成"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Comment \"{0}\""
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "\"{0}\" にコメント"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Content"
msgstr "コメント"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Submit your comment"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "コメントを保存"
msgid "Something broke on our side."
msgstr "サーバー側で何らかの問題が発生しました。"
msgid "Sorry about that. If you think this is a bug, please report it."
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgstr ""
"申し訳ありません。これがバグだと思われる場合は、問題を報告してください。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Configuration"
msgstr "設定"
msgid "Configure your instance"
msgstr "インスタンスを設定"
msgid "Name"
msgstr "名前"
msgid "Let&#x27;s go!"
msgstr "開始しましょう！"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Welcome to {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} へようこそ"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Notifications"
msgstr "通知"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Written by {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんが作成"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "This article is published under the {0} license."
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "この記事は {0} ライセンスの元で公開されています。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "One like"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid_plural "{0} likes"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr[0] "{0} いいね"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "I don&#x27;t like this anymore"
msgstr "もうこれにいいねしません"
msgid "Add yours"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "いいね"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "One boost"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid_plural "{0} Boosts"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr[0] "{0} ブースト"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "I don&#x27;t want this boosted anymore"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "もうこれをブーストしたくありません"
msgid "Boost"
msgstr "ブースト"
msgid "Comments"
msgstr "コメント"
msgid "Respond"
msgstr "返信"
msgid "Comment"
msgstr "コメント"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Create an article"
msgstr "アカウントを作成"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Publish"
msgstr "公開"
msgid "Login"
msgstr "ログイン"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Username, or email"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ユーザー名またはメールアドレス"
msgid "Password"
msgstr "パスワード"
msgid "Dashboard"
msgstr "ダッシュボード"
msgid "Your Dashboard"
msgstr "自分のダッシュボード"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Your blogs"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "自分のブログ"
msgid "You don&#x27;t have any blog yet. Create your own, or ask to join one."
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgstr ""
"まだブログを開設していません。ご自身のブログを開設するか、他のブログに参加す"
"るようにお願いしてください。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Start a new blog"
msgstr "新しいブログを開始"
msgid "Admin"
msgstr "管理者"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "That's you"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "自分"
msgid "Edit your profile"
msgstr "自分のプロフィールを編集"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Open on {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} で開く"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Follow"
msgstr "フォロー"
msgid "Unfollow"
msgstr "フォロー解除"
msgid "Recently boosted"
msgstr "最近ブーストしたもの"
msgid "One follower"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid_plural "{0} followers"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr[0] "{0} フォロワー"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Edit your account"
msgstr "自分のアカウントを編集"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Your profile"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "自分のプロフィール"
msgid "Display Name"
msgstr "表示名"
msgid "Email"
msgstr "メールアドレス"
msgid "Summary"
msgstr "要約"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Update your account"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "アカウントをアップデート"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "{0}'s followers"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんのフォロワー"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Followers"
msgstr "フォロワー"
msgid "New Account"
msgstr "新しいアカウント"
msgid "Create an account"
msgstr "アカウントを作成"
msgid "Username"
msgstr "ユーザー名"
msgid "Password confirmation"
msgstr "パスワードの確認"
msgid "Create account"
msgstr "アカウントを作成"
msgid "Plume"
msgstr "Plume"
msgid "Menu"
msgstr "メニュー"
msgid "My account"
msgstr "自分のアカウント"
msgid "Log Out"
msgstr "ログアウト"
msgid "Log In"
msgstr "ログイン"
msgid "Register"
msgstr "登録"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be signed in, for you to create a new blog"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "新しいブログを作成するにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be signed in, so that you can post a comment"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "コメントを投稿するにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "You need to be signed in, to be able to like a post"
msgstr "新しい記事を書くにはログインする必要があります"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "You need to be logged in, so that you can see your notifications"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "通知を表示するにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be logged in, to be able to write a new post"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "新しい記事を書くにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be logged in, for you to be able to boost a post"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "投稿をブーストするにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Invalid username, or password"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ユーザー名またはパスワードが間違っています"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be logged in, to be able to access your dashboard"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ダッシュボードにアクセスするにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be logged in, to be able to follow someone"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "他の人をフォローするにはログインする必要があります"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You need to be logged in, to be able to edit your profile"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "自分のプロフィールを編集するにはログインする必要があります"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "By {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんが作成"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "{0} gave a boost to your article"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんがあなたの記事をブーストしました"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "{0} started following you"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんがあなたのフォローを開始しました"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "{0} liked your post"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんがあなたの記事をいいねしました"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "{0} commented on your post"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんがあなたの記事にコメントしました"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "We couldn&#x27;t find this page."
msgstr "このページを見つけられませんでした。"
msgid "The link that led you here may be broken."
msgstr "このリンクは切れている可能性があります。"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "You are not authorized to access this page."
msgstr "あなたはこのブログの作者ではありません。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You are not an author on this blog."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "あなたはこのブログの作者ではありません。"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "{0} mentioned you."
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんがあなたをメンションしました。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Your comment"
msgstr "あなたのコメント"
msgid "Unknown error"
msgstr "不明なエラー"
msgid "Invalid name"
msgstr "無効な名前"
msgid "A blog with the same name already exists."
msgstr "同じ名前のブログがすでに存在します。"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "The comment field can't be left empty"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "コメントは空にできません"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "An article with the same title already exists."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "同じタイトルの投稿がすでに存在します。"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "We need an email, or a username to identify you"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "あなたを識別するために、メールアドレスかユーザー名が必要です"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Your password field can't be left empty"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "パスワードは空にできません"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
msgid "The two passwords must be a match!"
msgstr ""
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "The 'username' field can't be left empty"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ユーザー名は空にできません"
msgid "Invalid email"
msgstr "無効なメールアドレス"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "The password should be at least 8 characters long"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "パスワードは最低 8 文字にするべきです"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
msgid "This blog has one author: "
msgid_plural "This blog has {0} authors: "
msgstr[0] ""
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid ""
"Log in, or use your other account within the Fediverse, to interact with "
"this article"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgstr ""
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
"この記事と関わるには、ログインするか Fediverse アカウントを使用してください"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Optional"
msgstr "省略可"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
msgid "This blog has one article"
msgid_plural "This blog has {0} articles"
msgstr[0] ""
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Previous page"
msgstr "前のページ"
msgid "Next page"
msgstr "次のページ"
msgid "Source code"
msgstr "ソースコード"
msgid "Matrix room"
msgstr "Matrix　ルーム"
msgid "Administration"
msgstr "管理"
msgid "Instance settings"
msgstr "インスタンスの設定"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Allow anyone to register here"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "不特定多数に登録を許可"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Short description - byline"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "短い説明"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Markdown syntax is supported"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "Markdown がサポートされています"
msgid "Long description"
msgstr "長い説明"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Default article license"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "デフォルトのライセンス"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Save these settings"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "設定を保存"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "There are no comments here yet. Be the first to react!"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "コメントがまだありません。最初のコメントを書きましょう！"
msgid "About this instance"
msgstr "このインスタンスについて"
msgid "What is Plume?"
msgstr "Plume とは？"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Plume is a decentralized blogging engine and a member of the Fediverse."
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "Plume は、分散型のブログエンジンです。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Authors can manage various blogs, each from a separate, unique website."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "作成者は、ある固有の Web サイトから、さまざまなブログを管理できます。"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid ""
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
"Articles are also visible on other Plume websites, called instances, and you "
"can interact with them directly from other platforms like Mastodon, or "
"WriteFreely."
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgstr ""
"記事は他の Plume Web サイトからも閲覧可能であり、Mastdon のように他のプラット"
"フォームから直接記事と関わることができます。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Create your account"
msgstr "アカウントを作成"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "About {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} について"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Home to <em>{0}</em> users"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "登録者数 <em>{0}</em> 人"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Who wrote <em>{0}</em> articles"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "投稿記事数 <em>{0}</em> 件"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "And are connected to <em>{0}</em> other instances"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "他のインスタンスからの接続数 <em>{0}</em> 件"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Read the detailed rules"
msgstr "詳細な規則を読む"
msgid "Delete this article"
msgstr "この記事を削除"
msgid "Delete this blog"
msgstr "このブログを削除"
msgid "Administred by"
msgstr "管理者"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Runs Plume {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "Plume {0} を実行中"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Your media"
msgstr "メディア"
msgid "Go to your gallery"
msgstr "ギャラリーを参照"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "{0}'s avatar'"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} さんのアバター"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Media details"
msgstr "メディアの詳細"
msgid "Go back to the gallery"
msgstr "ライブラリに戻る"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Markdown syntax"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "Markdown コード"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Copy it into your articles, to insert this media."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "このメディアを記事に挿入するには、自分の記事にコピーしてください。"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Use as an avatar"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "アバターとして使う"
msgid "Delete"
msgstr "削除"
msgid "Upload"
msgstr "アップロード"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "You don't have any media uploaded yet."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "メディアがまだありません。"
msgid "Media upload"
msgstr "メディアのアップロード"
msgid "Description"
msgstr "説明"
msgid "Content warning"
msgstr "コンテンツの警告"
msgid "File"
msgstr "ファイル"
msgid "Send"
msgstr "送信"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid ""
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
"Apologies, but registrations are closed on this particular instance. You "
"can, however, find a different one."
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgstr ""
"申し訳ありませんが、このインスタンスでは登録者は限定されています。別のインス"
"タンスをお探しください"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Subtitle"
msgstr "サブタイトル"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Log In to like"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "いいねするにはログインしてください"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Log In to boost"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "ブーストするにはログインしてください"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Personal feed"
msgstr "このインスタンスのフィード"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Federated feed"
msgstr "全インスタンスのフィード"
msgid "Local feed"
msgstr "このインスタンスのフィード"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Nothing to see here yet. Try to follow some people."
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgstr ""
"ここにはまだ表示できるものがありません。他の人をもっとフォローしてみてくださ"
"い。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Articles"
msgstr "記事"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "All of the articles within the Fediverse"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "Fediverse のすべての記事"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Articles from {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} の記事"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "View all"
msgstr "すべて表示"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Articles tagged under \"{0}\""
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "\"{0}\" タグの記事"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Edit"
msgstr "編集"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Edit {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} を編集"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Update"
msgstr "アップデート"
msgid "We couldn't find this page."
msgstr "このページは見つかりませんでした。"
msgid "Invalid CSRF token."
msgstr "無効な CSRF トークンです。"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid ""
"Something is wrong with your CSRF token. Make sure cookies are enabled in "
"you browser, and try reloading this page. If you continue to see this error "
"message, please report it."
msgstr ""
"ご自身の CSRF トークンにおいて問題が発生しました。お使いのブラウザーで "
"Cookie　が有効になっていることを確認して、このページを再読み込みしてみてくだ"
"さい。このエラーメッセージが表示され続けた場合、問題を報告してください。"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
msgid "Administration of {0}"
Update Japanese translation (#339)
2018-12-08 15:39:47 +01:00
msgstr "{0} の管理"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgid "Instances"
msgstr "インスタンス"
msgid "Unblock"
msgstr "ブロック解除"
msgid "Block"
msgstr "ブロック"
msgid "Ban"
msgstr "禁止"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Useful for visually impaired people and information about licenses"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "視覚的に障害のある方や認可の際に便利です"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Leave it empty, if none is meeded"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "不要な場合は空にしてください"
msgid "Draft"
msgstr "下書き"
msgid "This is a draft, don't publish it yet."
msgstr "これは下書きなので、まだ公開しないでください。"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Update, or publish"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "更新または公開"
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Your drafts"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "下書き"
msgid "Danger zone"
msgstr "危険"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Be very careful, any action taken here cannot be reversed."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "十分ご注意ください。ここで行ったすべての操作は取り消しできません。"
msgid "Delete your account"
msgstr "アカウントを削除"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "Sorry, but as an admin, you can't leave your own instance."
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "申し訳ありませんが、管理者として、自分のインスタンスを離脱できません。"
msgid "Users"
msgstr "ユーザー"
msgid "This post isn't published yet."
msgstr "この投稿はまだ公開されていません。"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
#, fuzzy
msgid "There are currently no articles with such a tag"
i18n: Add Japanese translation (#333) Browsing the Demo instance, I sometimes found Japanese articles. So I decided to translate Plume into Japanese.
2018-12-03 19:06:10 +01:00
msgstr "そのタグのある記事は現在ありません"
msgid "Illustration"
msgstr "図"
msgid "None"
msgstr "なし"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
License federation (#343) * Federate license * Make it possible to use no license
2018-12-09 18:43:34 +01:00
#, fuzzy
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
msgid "Leave empty to reserve all rights"
License federation (#343) * Federate license * Make it possible to use no license
2018-12-09 18:43:34 +01:00
msgstr "不要な場合は空にしてください"
msgid "All rights reserved."
msgstr ""
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Search"
msgstr ""
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Your query"
msgstr "自分のフィード"
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Advanced search"
msgstr ""
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Article title matching these words"
msgstr ""
Use Rust for the front-end too (#374) Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cargo web deploy -p plume-front ```
2018-12-25 11:51:40 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Subtitle matching these words"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Content matching these words"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "From this date"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "To this date"
msgstr ""
msgid "Containing these tags"
msgstr ""
msgid "Posted on one of these instances"
msgstr ""
msgid "Posted by one of these authors"
msgstr ""
msgid "Posted on one of these blogs"
msgstr ""
#, fuzzy
msgid "Written in this language"
msgstr "このページは見つかりませんでした。"
#, fuzzy
msgid "Published under this license"
msgstr "この記事は {0} ライセンスの元で公開されています。"
msgid "Search result for \"{0}\""
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Search result"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "No result for your query"
msgstr "ギャラリーを参照"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "No more result for your query"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Subtitle — byline"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Body content"
msgstr "コメント"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Tags"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Instance domain"
msgstr "インスタンスの設定"
msgid "Authors"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Blog title"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
msgid "Language"
msgstr ""
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
msgid "Article license"
msgstr "デフォルトのライセンス"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#~ msgid "Create blog"
#~ msgstr "ブログを作成"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#~ msgid "New post"
#~ msgstr "新しい記事"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#~ msgid "Create a post"
#~ msgstr "記事を作成"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#, fuzzy
#~ msgid "You need to be signed in, in order for you to like a post"
#~ msgstr "投稿をいいねするにはログインする必要があります"
Use Ructe (#327) All the template are now compiled at compile-time with the `ructe` crate. I preferred to use it instead of askama because it allows more complex Rust expressions, where askama only supports a small subset of expressions and doesn't allow them everywhere (for instance, `{{ macro!() | filter }}` would result in a parsing error). The diff is quite huge, but there is normally no changes in functionality. Fixes #161 and unblocks #110 and #273
2018-12-06 18:54:16 +01:00
Improve search UI (#375)
2019-01-28 13:12:56 +01:00
#~ msgid "You are not authorized."
#~ msgstr "認証されていません。"
Reference in New Issue Copy Permalink