Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Common Workflow Language Apache-2.0 0 0 0 0 0 0 0
CWL User Guide Apache-2.0 0 0 0 0 51 0 7
CWL User Guide: Sphinx Apache-2.0 0 0 0 0 0 0 0

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-2.0 Common Workflow Language CWL User Guide CWL User Guide: Sphinx
6 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 689 13,569 94,010
Translated 100% 689 100% 13,569 100% 94,010
Needs editing 0% 0 0% 0 0% 0
Read-only 97% 671 99% 13,546 99% 93,838
Failing checks 7% 51 12% 1,646 11% 10,437
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 4 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 70 changes 1,264 changes 0 changes 8 changes 1 change 2 changes 2 changes 21 changes 1 change
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

13,569
Hosted words
689
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

String added

  1. Common Workflow Language
  2. Common Workflow Language Glossary
  3. English
CWL definition
CWL definition
3 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.

a month 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.

a month 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 ?

2 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.
4 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.
4 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.
4 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.
4 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.
4 months ago
User avatar None

Source string added

  1. Common Workflow Language
  2. CWL User Guide
  3. English
The [`glob`](https://w3id.org/cwl/CommandLineTool.html#CommandOutputBinding) field consists of the pattern to match file names in the output directory. This can simply be the file's exact name. But if you don't know the name of the file in advance, you can use a wildcard pattern like `glob: '*.txt'`.
4 months ago
Browse all changes for this language