PeerTube LiveChat/Peertube Plugin Livechat Documentation — Japanese @ Framasoft Weblate: If you think there is a missing locale, please check …

Translation

English type: Plain text

Japanese

Needs editing

Skip

	English	Japanese	Actions
	Translate the plugin
	Translate
	You can contribute to this plugin translation. Translations are handled using the [Weblate](https://weblate.org/) software, using [Framasoft Weblate instance](https://weblate.framasoft.org/).
	Never modify directly files in the `languages` folder, this could lead to conflicts.
	How to
	Create an account: https://weblate.framasoft.org/accounts/register/
	Validate your email and follow the link sent
	Create your password and setup your account
	Go to the plugin project page: https://weblate.framasoft.org/projects/peertube-livechat/peertube-plugin-livechat/
	Choose the locale you want to translate
	Just translate missing sentences, or correct the ones that seems incorrect to you.
	There might be some «very technical» strings. If you are not 100% sure of the meaning, or of your translation, you better not translate it, so it will display in english.
	ConverseJS translations
	This plugin relies on [ConverseJS](https://conversejs.org/) for the chat front-end. ConverseJS has its own translations, on its own [weblate instance](https://hosted.weblate.org/projects/conversejs/#languages). You can also translate directly in the code repository. For more information, check [ConverseJS translations documentation](https://conversejs.org/docs/html/translations.html).
	Adding a new locale
	If you think there is a missing locale, please check first if it is handled in Peertube. If so, you can [open an issue](https://github.com/JohnXLivingston/peertube-plugin-livechat/issues) to ask for it.	新しい機能のリクエスト、バグ、プラグインのセットアップ時に問題が発生した場合は、[Github issue tracker](https://github.com/JohnXLivingston/peertube-plugin-livechat/issues)から報告してください。
	Adding new strings / use translations in the code
	If you are working on new features, and need new strings, you can create them directly in Weblate. The english version is mandatory. Start with it.
	Each string is linked to a key (for example `use_chat`). Choose an explicit key in english, lower case.
	If you have to test new strings without waiting for a Weblate merge, you can modify `languages/*.yml` files, but avoid to commit these changes (to minimize conflict risks).
	Use translations in front-end code
	Before using a string in front-end, you need to declare a new constant in `client/@types/global.d.ts`. The constant name must:
	start with the prefix "LOC_"
	use the string key, upper cased
	you just have to declare its type, not its value
	For example, to use "use_chat", you have to declare:
	declare const LOC_USE_CHAT: string
	The `build-client.js` script will read the `client/@types/global.d.ts`, search for such constants, and load their values from the languages files.
	Now, you can simply call `peertubeHelpers.translate(LOC_USE_CHAT)` in your code.
	Use translations in back-end code
	In theory, the only parts of the backend code where you need localization is the settings declaration and standardized data (ActivityPub, RSS, ...). Here we need to get english strings from the translation key.

Loading…

None

String updated in the repository

English

Japanese 142 characters edited Current translation Needs editing

a year ago

Browse all string changes

Things to check

Trailing newline

Source and translation do not both end with a newline

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English	Japanese
No related strings found in the glossary.

String information

Source string description

type: Plain text

Source string location

support/documentation/content/en/contributing/translate/_index.md

String age

a year ago

Last updated

5 days ago

Source string age

a year ago

Translation file

support/documentation/po/livechat.ja.po, string 128