No strings found!

Source strings

666 Strings 100%
Browse Translate
13,538 Words 100%
93,773 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
666 13,538 93,773
All strings Browse Translate Zen
666 13,538 93,773
Read-only strings Browse Translate Zen
23 238 1,770
Strings with any failing checks Browse Translate Zen
2 31 354
Failing check: Unpluralised Browse Translate Zen
21 207 1,416
Failing check: Multiple failing checks Browse Translate Zen
9 286 2,124
Strings with comments Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
CWL User Guide: Sphinx Apache-2.0 0 0 0 0 0 0 0
Browse all components

Overview

Project website www.commonwl.org
Instructions for translators

For context, see the latest rendered CWL User Guide website.
Project maintainers User avatar mrc
Translation license Apache License 2.0
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/common-workflow-language/user_guide.git
Repository branch main
Last remote commit Merge pull request #480 from weblate/weblate-commonwl-user-guide 7f19ad8
Michael R. Crusoe authored 12 days ago
Last commit in Weblate Translated using Weblate (Japanese) 9496477
User avatar manabuishii authored 10 hours ago
Weblate repository https://hosted.weblate.org/git/commonwl/user-guide/
File mask locales/*/LC_MESSAGES/user_guide.po
Translation file Download locales/user_guide.pot
Last change May 17, 2024, 10:56 a.m.
Last author Manabu ISHII
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 666 13,538 93,773
Translated 100% 666 100% 13,538 100% 93,773
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 666 100% 13,538 100% 93,773
Failing checks 3% 23 1% 238 1% 1,770
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 69 changes 648 changes 0 changes 0 changes 1 change 0 changes 2 changes 4 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

13,538
Hosted words
666
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
+100%
User avatar manabuishii

Comment added

  1. Common Workflow Language
  2. CWL User Guide
  3. English

How about add that alexis vscode plugin related work

CWL Schema is now available on JSON Schema Store - Announcements - Common Workflow Language Discourse https://cwl.discourse.group/t/cwl-schema-is-now-available-on-json-schema-store/872

13 days ago
User avatar manabuishii

Comment added

  1. Common Workflow Language
  2. CWL User Guide
  3. English

From original https://creativecommons.org/licenses/by/4.0/deed.en This sentence end with "."(period) not ":"(colon)

2 weeks ago
User avatar ZoeCMa

Comment added

  1. Common Workflow Language
  2. CWL User Guide
  3. English

What does "using source" mean here? This looks like interpolated text intruding into the sentence.

2 months ago
User avatar ZoeCMa

Comment added

  1. Common Workflow Language
  2. CWL User Guide
  3. English

Note: the translatable text is in the alt-text of the img tag in the output.

2 months ago
User avatar manabuishii

Comment added

  1. Common Workflow Language
  2. CWL User Guide
  3. English

job parameter file and input file is using almost same meaning ? how about these terms into one term ?

3 months ago
User avatar None

Source string added

  1. Common Workflow Language
  2. CWL User Guide
  3. English
Before we run this, let's just break it down and see what some bits do. Most of this has been explained in previous sections, the only part that is really new is the [`dockerRequirement`](https://w3id.org/cwl/CommandLineTool.html#DockerRequirement) section.
5 months ago
User avatar None

Source string added

  1. Common Workflow Language
  2. CWL User Guide
  3. English
Normally, input files are located in a read-only directory separate from the output directory. This causes problems if the underlying tool expects to write its output files alongside the input file in the same directory. You use [`InitialWorkDirRequirement`](https://w3id.org/cwl/CommandLineTool.html#InitialWorkDirRequirement) to stage input files into the output directory. In this example, we use a JavaScript expression to extract the base name of the input file from its leading directory path.
5 months ago
User avatar None

Source string added

  1. Common Workflow Language
  2. CWL User Guide
  3. English
As well as a version number, a unique resource identifier (URI) for the tool is given in the form of an [RRID][rrid]. Resources with RRIDs can be looked up in the [SciCrunch][scicrunch] registry, which provides a portal for finding, tracking, and referring to scientific resources consistently. If you want to specify a tool as a [`SoftwareRequirement`](https://w3id.org/cwl/CommandLineTool.html#SoftwareRequirement), search for the tool on SciCrunch and use the RRID that it has been assigned in the registry. (Follow this [Adding a Resource Tutorial][scicrunch-add-tool] to add a tool to SciCrunch). You can use this RRID to refer to the tool (via [identifiers.org][identifiers]) in the `specs` field of your requirement description. Other good choices, in order of preference, are to include the DOI for the main tool citation and the URL to the tool.
5 months ago
User avatar None

Source string added

  1. Common Workflow Language
  2. CWL User Guide
  3. English
Often, tool descriptions will be written for a specific version of a software. To make it easier for others to use your descriptions, you can include a [`SoftwareRequirement`](https://w3id.org/cwl/CommandLineTool.html#SoftwareRequirement) field in the `hints` section. This may also help to avoid confusion about which version of a tool the description was written for.
5 months ago
User avatar None

Source string added

  1. Common Workflow Language
  2. CWL User Guide
  3. English
To capture a tool's standard output stream, add the [`stdout`](https://w3id.org/cwl/CommandLineTool.html#stdout) field with the name of the file where the output stream should go. Then add `type: stdout` on the corresponding output parameter.
5 months ago
Browse all translation changes