Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
Glossary Common Workflow Language Apache-2.0 71% 2 4 28 2 0 0 0
CWL User Guide Apache-2.0 19% 483 10,706 74,462 463 18 497 0
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
an hour ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 608 11,933 83,118
Translated 20% 123 10% 1,223 10% 8,628
Needs editing 3% 20 1% 203 1% 1,512
Read-only 1% 1 1% 1 1% 6
Failing checks 2% 18 1% 158 1% 1,090
Strings with suggestions 81% 497 84% 10,039 82% 68,863
Untranslated strings 76% 465 88% 10,507 87% 72,978
Last 12 months Previous

Activity in last 12 months

0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 71 changes 0 changes 0 changes 0 changes 0 changes 1,219 changes 0 changes 185 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

11,929
Hosted words
606
Hosted strings
20%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+20%
—
Contributors
—
User avatar None

Changes committed

  1. Common Workflow Language
  2. Common Workflow Language Glossary
  3. Portuguese (Brazil)
Changes committed an hour ago
User avatar manabuishii

String added

  1. Common Workflow Language
  2. Common Workflow Language Glossary
  3. Portuguese (Brazil)
CWL implementation
 
5 hours ago
User avatar manabuishii

String added

  1. Common Workflow Language
  2. Common Workflow Language Glossary
  3. Portuguese (Brazil)
CWL runner
 
6 hours ago
User avatar None

Resource updated

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
The “locales/pt_BR/LC_MESSAGES/user_guide.po” file was changed. 5 months ago
User avatar None

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
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

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
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

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
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

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
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

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
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
User avatar None

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Brazil)
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'`.
 
5 months ago
Browse all changes for this language