Translation status

599 Strings 18%
Browse Translate
11,918 Words 9%
82,996 Characters 9%

Strings status

Strings Words Characters
599 11,918 82,996
All strings Browse Translate Zen
111 1,145 8,074
Translated strings Browse Translate Zen
488 10,773 74,922
Unfinished strings Browse Translate Zen
470 10,574 73,549
Untranslated strings Browse Translate Zen
18 199 1,373
Strings marked for edit Browse Translate Zen
504 10,064 69,076
Strings with suggestions Browse Translate Zen
68 1,816 13,337
Unfinished strings without suggestions Browse Translate Zen
16 155 1,028
Strings with any failing checks Browse Translate Zen
1 11 67
Failing check: Mismatched full stop Browse Translate Zen
2 17 280
Failing check: Mismatched colon Browse Translate Zen
13 127 681
Failing check: Mismatched question mark Browse Translate Zen
1 7 221
Failing check: Markdown syntax Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
CWL User Guide: Sphinx Apache-2.0 0% 2 4 33 2 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 3 weeks ago
Last commit in Weblate Translated using Weblate (Japanese) 9496477
User avatar manabuishii authored 11 days ago
Weblate repository https://hosted.weblate.org/git/commonwl/user-guide/
File mask locales/*/LC_MESSAGES/user_guide.po
Translation file Download locales/pt_PT/LC_MESSAGES/user_guide.po
Last change Dec. 16, 2023, 11:54 a.m.
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 599 11,918 82,996
Translated 18% 111 9% 1,145 9% 8,074
Needs editing 3% 18 1% 199 1% 1,373
Read-only 0% 0 0% 0 0% 0
Failing checks 2% 16 1% 155 1% 1,028
Strings with suggestions 84% 504 84% 10,064 83% 69,076
Untranslated strings 78% 470 88% 10,574 88% 73,549
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 70 changes 0 changes 0 changes 0 changes 0 changes 1,199 changes 0 changes 166 changes 0 changes 0 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

11,918
Hosted words
599
Hosted strings
18%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Resource updated

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Portugal)
The “locales/pt_PT/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 (Portugal)
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 (Portugal)
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 (Portugal)
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 (Portugal)
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 (Portugal)
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 (Portugal)
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
User avatar None

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Portugal)
The field [`outputBinding`](https://w3id.org/cwl/CommandLineTool.html#CommandOutputBinding) describes how to set the value of each output parameter.
 
5 months ago
User avatar None

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Portugal)
In previous examples, the `baseCommand` was just a string, with any arguments passed as CWL inputs. Instead of a single string, we can use an _array of strings_ as the value of `baseCommand`. The first element of the array is the command to run, and any subsequent elements are mandatory command line arguments
 
5 months ago
User avatar None

String updated in the repository

  1. Common Workflow Language
  2. CWL User Guide
  3. Portuguese (Portugal)
When a tool runs under CWL, the starting working directory is the designated output directory. The underlying tool or script must record its results in the form of files created in the output directory. The output parameters returned by the CWL tool are either the output files themselves, or the result of examining the content of those files.
 
5 months ago
Browse all translation changes