matrix-docker-ansible-deploy/i18n/locales/jp/LC_MESSAGES/docs/configuring-playbook-bridge-mautrix-telegram.po
Slavi Pantaleev d4f8d0918a Initial work on translations / localization
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3841

Most of the preparation for this was done by Suguru Hirahara (https://github.com/luixxiul).
I've merely reorganized/polished the scripts and instructions in the `i18n/` directory.

While translations can happen even now, more work is necessary to

- make the translation flow better (integrating Weblate), etc.

- restore the Github Actions workflows that Suguru Hirahara had already developed to
  adapt them to our new workflow
2024-12-20 09:37:38 +02:00

223 lines
7.8 KiB
Plaintext

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community
# members
# This file is distributed under the same license as the
# matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2024.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-16 12:05+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: jp\n"
"Language-Team: jp <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.16.0\n"
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:1
msgid "Setting up Mautrix Telegram bridging (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:3
msgid ""
"The playbook can install and configure [mautrix-"
"telegram](https://github.com/mautrix/telegram) for you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:5
msgid ""
"See the project's "
"[documentation](https://docs.mau.fi/bridges/python/telegram/index.html) "
"to learn what it does and why it might be useful to you."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:7
msgid "Prerequisite (optional)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:9
msgid ""
"If you want to set up [Double "
"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) "
"(hint: you most likely do) for this bridge automatically, you need to "
"have enabled [Appservice Double Puppet](configuring-playbook-appservice-"
"double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-"
"secret-auth.md) service for this playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:11
msgid ""
"For details about configuring Double Puppeting for this bridge, see the "
"section below: [Set up Double Puppeting](#-set-up-double-puppeting)"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:13
msgid "Adjusting the playbook configuration"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:15
msgid ""
"You'll need to obtain API keys from "
"[https://my.telegram.org/apps](https://my.telegram.org/apps) and then add"
" the following configuration to your "
"`inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:23
msgid "Installing"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:25
msgid ""
"After configuring the playbook, run it with [playbook tags](playbook-"
"tags.md) as below:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:32
msgid "**Notes**:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:34
msgid ""
"The `ensure-matrix-users-created` playbook tag makes the playbook "
"automatically create the bot's user account."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:36
msgid ""
"The shortcut commands with the [`just` program](just.md) are also "
"available: `just install-all` or `just setup-all`"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:38
msgid ""
"`just install-all` is useful for maintaining your setup quickly ([2x-5x "
"faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-"
"runtime) than `just setup-all`) when its components remain unchanged. If "
"you adjust your `vars.yml` to remove other components, you'd need to run "
"`just setup-all`, or these components will still remain installed."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:40
msgid "Usage"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:42
msgid ""
"To use the bridge, you need to start a chat with "
"`@telegrambot:example.com` (where `example.com` is your base domain, not "
"the `matrix.` domain)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:44
msgid ""
"If you want to use the relay-bot feature ([relay bot "
"documentation](https://docs.mau.fi/bridges/python/telegram/relay-"
"bot.html)), which allows anonymous user to chat with telegram users, add "
"the following configuration to your "
"`inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:54
msgid "You might also want to give permissions to administrate the bot:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:63
msgid ""
"More details about permissions in this example: "
"https://github.com/mautrix/telegram/blob/master/mautrix_telegram/example-"
"config.yaml#L410"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:65
msgid ""
"If you like to exclude all groups from syncing and use the Telgeram-"
"Bridge only for direct chats, you can add the following additional "
"playbook configuration:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:71
msgid "💡 Set up Double Puppeting"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:73
msgid ""
"After successfully enabling bridging, you may wish to set up [Double "
"Puppeting](https://docs.mau.fi/bridges/general/double-puppeting.html) "
"(hint: you most likely do)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:75
msgid "To set it up, you have 2 ways of going about it."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:77
msgid ""
"Method 1: automatically, by enabling Appservice Double Puppet or Shared "
"Secret Auth"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:79
msgid ""
"The bridge automatically performs Double Puppeting if [Appservice Double "
"Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared "
"Secret Auth](configuring-playbook-shared-secret-auth.md) service is "
"configured and enabled on the server for this playbook."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:81
msgid ""
"Enabling [Appservice Double Puppet](configuring-playbook-appservice-"
"double-puppet.md) is the recommended way of setting up Double Puppeting, "
"as it's easier to accomplish, works for all your users automatically, and"
" has less of a chance of breaking in the future."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:83
msgid ""
"Enabling double puppeting by enabling the [Shared Secret Auth"
"](configuring-playbook-shared-secret-auth.md) service works at the time "
"of writing, but is deprecated and will stop working in the future."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:85
msgid "Method 2: manually, by asking each user to provide a working access token"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:87
msgid ""
"**Note**: This method for enabling Double Puppeting can be configured "
"only after you've already set up bridging."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:89
msgid ""
"When using this method, **each user** that wishes to enable Double "
"Puppeting needs to follow the following steps:"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:91
msgid ""
"retrieve a Matrix access token for yourself. Refer to the documentation "
"on [how to do that](obtaining-access-tokens.md)."
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:93
msgid ""
"send `login-matrix` to the bot and follow instructions about how to send "
"the access token to it"
msgstr ""
#: ../../../docs/configuring-playbook-bridge-mautrix-telegram.md:95
msgid ""
"make sure you don't log out the `Mautrix-Telegram` device some time in "
"the future, as that would break the Double Puppeting feature"
msgstr ""