Skip to content

Commit

Permalink
chore: sync translations
Browse files Browse the repository at this point in the history
  • Loading branch information
task-bot authored Jul 20, 2023
1 parent 7e7a016 commit 15a09e4
Show file tree
Hide file tree
Showing 8 changed files with 44 additions and 44 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -937,10 +937,10 @@ tasks:

Task also adds the following functions:

- `OS`: Returns the operating system. Possible values are "windows", "linux", "darwin" (macOS) and "freebsd".
- `ARCH`: return the architecture Task was compiled to: "386", "amd64", "arm" or "s390x".
- `splitLines`: Splits Unix (\n) and Windows (\r\n) styled newlines.
- `catLines`: Replaces Unix (\n) and Windows (\r\n) styled newlines with a space.
- `OS`: Returns the operating system. Possible values are `windows`, `linux`, `darwin` (macOS) and `freebsd`.
- `ARCH`: return the architecture Task was compiled to: `386`, `amd64`, `arm` or `s390x`.
- `splitLines`: Splits Unix (`\n`) and Windows (`\r\n`) styled newlines.
- `catLines`: Replaces Unix (`\n`) and Windows (`\r\n`) styled newlines with a space.
- `toSlash`: Does nothing on Unix, but on Windows converts a string from `\` path format to `/`.
- `fromSlash`: Opposite of `toSlash`. Does nothing on Unix, but on Windows converts a string from `/` path format to `\`.
- `exeExt`: Returns the right executable extension for the current OS (`".exe"` for Windows, `""` for others).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -937,10 +937,10 @@ tasks:

Task also adds the following functions:

- `OS`: Returns the operating system. Possible values are "windows", "linux", "darwin" (macOS) and "freebsd".
- `ARCH`: return the architecture Task was compiled to: "386", "amd64", "arm" or "s390x".
- `splitLines`: Splits Unix (\n) and Windows (\r\n) styled newlines.
- `catLines`: Replaces Unix (\n) and Windows (\r\n) styled newlines with a space.
- `OS`: Returns the operating system. Possible values are `windows`, `linux`, `darwin` (macOS) and `freebsd`.
- `ARCH`: return the architecture Task was compiled to: `386`, `amd64`, `arm` or `s390x`.
- `splitLines`: Splits Unix (`\n`) and Windows (`\r\n`) styled newlines.
- `catLines`: Replaces Unix (`\n`) and Windows (`\r\n`) styled newlines with a space.
- `toSlash`: Does nothing on Unix, but on Windows converts a string from `\` path format to `/`.
- `fromSlash`: Opposite of `toSlash`. Does nothing on Unix, but on Windows converts a string from `/` path format to `\`.
- `exeExt`: Returns the right executable extension for the current OS (`".exe"` for Windows, `""` for others).
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
slug: /
sidebar_position: 1
title: Home
title: ホーム
---

# Task
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,13 +3,13 @@ slug: /translate/
sidebar_position: 12
---

# Translate
# 翻訳

Want to help us translate this documentation? In this document we explain how.
このドキュメントの翻訳を手伝ってくれませんか? このドキュメントではどのように翻訳に協力できるかを説明します。

Do NOT edit translated markdown files directly on the GitHub repository! We use [Crowdin][crowdin] to allow contributors on work on translations. The repository is periodically updated with progress from Crowdin.
※GitHubリポジトリ上にある翻訳されたマークダウンファイルを直接編集しないでください! 翻訳作業は[Crowdin][crowdin]を使っています。 リポジトリはCrowdinからの進捗状況で定期的に更新されます。

If you want to have access to the Crowdin project to be able to suggest translations, please ask for access on the [#translations channel on our Discord server][discord]. If a given language is not being shown to Crowdin yet, just ask and we can configure it.
翻訳に協力するためにCrowdinプロジェクトへのアクセスが必要な場合は、[Discordサーバーの#translationsチャンネル][discord]でCrowdinへのアクセスを依頼してください。 特定の言語がまだCrowdinに表示されていない場合は依頼してください。

<!-- prettier-ignore-start -->

Expand Down
38 changes: 19 additions & 19 deletions docs/i18n/ja-JP/docusaurus-plugin-content-docs/current/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,13 +28,13 @@ tasks:
task assets build
```

Taskは[mvdan.cc/sh](https://mvdan.cc/sh/)というネイティブなGo shインタプリタを使用しています。 So you can write sh/bash commands, and it will work even on Windows, where `sh` or `bash` are usually not available. Just remember any executable called must be available by the OS or in PATH.
Taskは[mvdan.cc/sh](https://mvdan.cc/sh/)というネイティブなGo shインタプリタを使用しています。 なのでsh/bashコマンドを書いても、Windowsのような`sh``bash`が無いような環境でも動かすことが可能です。 実行可能なファイルはOSからアクセスできる場所、もしくはPATH内にある必要があることを覚えておいてください。

If you omit a task name, "default" will be assumed.
タスク名を省略すると、"default"が実行されます。

## サポートされているファイル名

Task will look for the following file names, in order of priority:
Taskは以下のような優先順位でファイルを探します:

- Taskfile.yml
- taskfile.yml
Expand All @@ -45,13 +45,13 @@ Task will look for the following file names, in order of priority:
- Taskfile.dist.yaml
- taskfile.dist.yaml

The intention of having the `.dist` variants is to allow projects to have one committed version (`.dist`) while still allowing individual users to override the Taskfile by adding an additional `Taskfile.yml` (which would be on `.gitignore`).
`.dist`が存在する意図は、プロジェクトが1つの固定されたバージョン(`.dist`)を持つ一方で、個々のユーザーが`Taskfile.yml`を追加することでTaskfileを上書きできるようにすることです(個々が追加したTaskfileは`.gitignore`に追加されている)

### Running a Taskfile from a subdirectory
### サブディレクトリからTaskfileを実行する

If a Taskfile cannot be found in the current working directory, it will walk up the file tree until it finds one (similar to how `git` works). When running Task from a subdirectory like this, it will behave as if you ran it from the directory containing the Taskfile.
カレントワーキングディレクトリからTaskfileが見つからなかったときは、見つかるまでファイルツリーを走査します(`git`の動きに似ています)。 このようにタスクをサブディレクトリで実行すると、Taskfileがあるディレクトリから実行したかのように動きます。

You can use this functionality along with the special `{{.USER_WORKING_DIR}}` variable to create some very useful reusable tasks. For example, if you have a monorepo with directories for each microservice, you can `cd` into a microservice directory and run a task command to bring it up without having to create multiple tasks or Taskfiles with identical content. For example:
このような機能を特別な`{{.USER_WORKING_DIR}}`変数を使うことで、非常に便利で再利用可能なタスクを作成できます。 例えば、各マイクロサービスごとのディレクトリがあるモノリポがある場合、同じ内容の複数のタスクやTaskfileを作らずに、マイクロサービスのディレクトリに`cd`で移動し、タスクコマンドを実行することができます。 例:

```yaml
version: '3'
Expand All @@ -65,11 +65,11 @@ tasks:
- docker-compose up -d
```
In this example, we can run `cd <service>` and `task up` and as long as the `<service>` directory contains a `docker-compose.yml`, the Docker composition will be brought up.
上記の例では、`cd <service>``task up`を実行すると、`<service>`ディレクトリに`docker-copmose.yml`があれば、Docker compositionが立ち上がります。

### Running a global Taskfile
### グローバルなTaskfileを実行する

If you call Task with the `--global` (alias `-g`) flag, it will look for your home directory instead of your working directory. In short, Task will look for a Taskfile that matches `$HOME/{T,t}askfile.{yml,yaml}` .
`--global` (エイリアス `-g`) フラグと一緒にTaskを実行すると、ワーキングディレクトリの代わりにホームディレクトリからTaskfileを探します。 つまり、Taskは`$HOME/{T,t}askfile.{yml,yaml}`にマッチするファイルを探します。

This is useful to have automation that you can run from anywhere in your system!

Expand All @@ -95,11 +95,11 @@ tasks:

:::

## Environment variables
## 環境変数

### Task
### タスク

You can use `env` to set custom environment variables for a specific task:
`env`を使用して特定のタスクにカスタム環境変数を設定できます:

```yaml
version: '3'
Expand All @@ -112,7 +112,7 @@ tasks:
GREETING: Hey, there!
```

Additionally, you can set global environment variables that will be available to all tasks:
また、すべてのタスクに適用できるグローバルな環境変数を設定することもできます:

```yaml
version: '3'
Expand All @@ -132,7 +132,7 @@ tasks:

:::

### .env files
### .envファイル

You can also ask Task to include `.env` like files by using the `dotenv:` setting:

Expand Down Expand Up @@ -937,10 +937,10 @@ tasks:

Task also adds the following functions:

- `OS`: Returns the operating system. Possible values are "windows", "linux", "darwin" (macOS) and "freebsd".
- `ARCH`: return the architecture Task was compiled to: "386", "amd64", "arm" or "s390x".
- `splitLines`: Splits Unix (\n) and Windows (\r\n) styled newlines.
- `catLines`: Replaces Unix (\n) and Windows (\r\n) styled newlines with a space.
- `OS`: Returns the operating system. Possible values are `windows`, `linux`, `darwin` (macOS) and `freebsd`.
- `ARCH`: return the architecture Task was compiled to: `386`, `amd64`, `arm` or `s390x`.
- `splitLines`: Splits Unix (`\n`) and Windows (`\r\n`) styled newlines.
- `catLines`: Replaces Unix (`\n`) and Windows (`\r\n`) styled newlines with a space.
- `toSlash`: Does nothing on Unix, but on Windows converts a string from `\` path format to `/`.
- `fromSlash`: Opposite of `toSlash`. Does nothing on Unix, but on Windows converts a string from `/` path format to `\`.
- `exeExt`: Returns the right executable extension for the current OS (`".exe"` for Windows, `""` for others).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -937,10 +937,10 @@ tasks:

Task also adds the following functions:

- `OS`: Returns the operating system. Possible values are "windows", "linux", "darwin" (macOS) and "freebsd".
- `ARCH`: return the architecture Task was compiled to: "386", "amd64", "arm" or "s390x".
- `splitLines`: Splits Unix (\n) and Windows (\r\n) styled newlines.
- `catLines`: Replaces Unix (\n) and Windows (\r\n) styled newlines with a space.
- `OS`: Returns the operating system. Possible values are `windows`, `linux`, `darwin` (macOS) and `freebsd`.
- `ARCH`: return the architecture Task was compiled to: `386`, `amd64`, `arm` or `s390x`.
- `splitLines`: Splits Unix (`\n`) and Windows (`\r\n`) styled newlines.
- `catLines`: Replaces Unix (`\n`) and Windows (`\r\n`) styled newlines with a space.
- `toSlash`: Does nothing on Unix, but on Windows converts a string from `\` path format to `/`.
- `fromSlash`: Opposite of `toSlash`. Does nothing on Unix, but on Windows converts a string from `/` path format to `\`.
- `exeExt`: Returns the right executable extension for the current OS (`".exe"` for Windows, `""` for others).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -937,10 +937,10 @@ tasks:

Task also adds the following functions:

- `OS`: Returns the operating system. Possible values are "windows", "linux", "darwin" (macOS) and "freebsd".
- `ARCH`: return the architecture Task was compiled to: "386", "amd64", "arm" or "s390x".
- `splitLines`: Splits Unix (\n) and Windows (\r\n) styled newlines.
- `catLines`: Replaces Unix (\n) and Windows (\r\n) styled newlines with a space.
- `OS`: Returns the operating system. Possible values are `windows`, `linux`, `darwin` (macOS) and `freebsd`.
- `ARCH`: return the architecture Task was compiled to: `386`, `amd64`, `arm` or `s390x`.
- `splitLines`: Splits Unix (`\n`) and Windows (`\r\n`) styled newlines.
- `catLines`: Replaces Unix (`\n`) and Windows (`\r\n`) styled newlines with a space.
- `toSlash`: Does nothing on Unix, but on Windows converts a string from `\` path format to `/`.
- `fromSlash`: Opposite of `toSlash`. Does nothing on Unix, but on Windows converts a string from `/` path format to `\`.
- `exeExt`: Returns the right executable extension for the current OS (`".exe"` for Windows, `""` for others).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -937,10 +937,10 @@ tasks:

Task 还增加了以下功能:

- `OS`:返回操作系统。 可能的值为“windows”、“linux”、“darwin(macOS) 和“freebsd”。
- `ARCH`:返回 Task 的编译架构为:“386”、“amd64”、“arm”或“s390x”。
- `splitLines`:拆分 Unix (\n) 和 Windows (\r\n) 样式的换行符。
- `catLines`:用空格替换 Unix (\n) 和 Windows (\r\n) 样式的换行符。
- `OS`:返回操作系统。 Possible values are `windows`, `linux`, `darwin` (macOS) and `freebsd`.
- `ARCH`: return the architecture Task was compiled to: `386`, `amd64`, `arm` or `s390x`.
- `splitLines`: Splits Unix (`\n`) and Windows (`\r\n`) styled newlines.
- `catLines`: Replaces Unix (`\n`) and Windows (`\r\n`) styled newlines with a space.
- `toSlash`:在 Unix 上不执行任何操作,但在 Windows 上将字符串从 `\` 路径格式转换为 `/`。
- `fromSlash`:与 `toSlash` 相反。 在 Unix 上不执行任何操作,但在 Windows 上将字符串从 `/` 路径格式转换为 `\`。
- `exeExt`:返回当前操作系统的正确可执行文件扩展名(Windows 为`“.exe”`,其他操作系统为`“”`)。
Expand Down

0 comments on commit 15a09e4

Please sign in to comment.