You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
msgid"You can use this Inputs Object file now to execute the “Hello World” workflow:"
1160
-
msgstr"您现在可以使用此输入对象文件来执行“Hello World”工作流:"
1160
+
msgstr"这样就可以在执行“Hello World”工作流时使用此输入对象文件:"
1161
1161
1162
1162
#:../../src/introduction/quick-start.md:82
1163
1163
#: d4cdbe870a6f4a68b542ca719d989062
1164
1164
msgid"Passing an Inputs Object file to `cwltool`."
1165
-
msgstr"将输入对象文件传递给 `cwltool`。"
1165
+
msgstr"将输入对象文件传递给 `cwltool`."
1166
1166
1167
1167
#:../../src/introduction/quick-start.md:88
1168
1168
#: b6d59e4b9c854abab1b3f7a0fa26f504
1169
1169
msgid"We used a similar file name for the workflow and for the Inputs Object files. The *-job.json* suffix is very common in Inputs Object files, but it is not a requirement. You can choose any name for your workflows and Inputs Object files."
1170
1170
msgstr""
1171
-
"我们为工作流和输入对象文件使用了类似的文件名。*-job.json* 后缀在输入对象文件"
1172
-
"中很常见,但非必需要求,您可为工作流和输入对象文件选择任何名称。"
1171
+
"我们为工作流和输入对象文件起了类似的文件名。输入对象文件名中的 *-job.json* "
1172
+
"后缀是很常见的,但并非规定。工作流和输入对象文件的命名方式可由您任意选择。"
1173
1173
1174
1174
#:../../src/introduction/quick-start.md:96
1175
1175
#: 5535b98e8b1342f09f003ec6db2b44b1
1176
1176
msgid"Continue reading the next sections of this User Guide!"
1177
-
msgstr"继续阅读本用户指南的下一章节!"
1177
+
msgstr"请继续阅读《用户指南》后续部分!"
1178
1178
1179
1179
#:../../src/introduction/quick-start.md:97
1180
1180
#: 77e43c7117fd4c52b140f0dd52cc3963
1181
1181
msgid"[List of CWL Implementations](https://www.commonwl.org/implementations)."
"[Wikipedia 条目 Workflow Management System ](https://en.wikipedia.org/wiki/"
1217
+
"Workflow_management_system)."
1218
1218
1219
1219
#:../../src/setup.md:9
1220
1220
#: 1330bd38c4b5495f890b98c669f81a9d
1221
1221
msgid"This page is out-of-date and was kept here to preserve the links of the old User Guide. The information on this page has been migrated to the [FAQ](/faq.md) section of the new user guide."
msgid"In this example, we will wrap the Java compiler to compile a java source file to a class file. By default, \"javac\" will create the class files in the same directory as the source file. However, CWL input files (and the directories in which they appear) may be read-only, so we need to instruct \"javac\" to write the class file to the designated output directory instead."
msgid"This example references a runtime parameter. Runtime parameters provide information about the hardware or software environment when the tool is actually executed. The `$(runtime.outdir)` parameter is the path to the designated output directory. Other parameters include `$(runtime.tmpdir)`, `$(runtime.ram)`, `$(runtime.cores)`, `$(runtime.outdirSize)`, and `$(runtime.tmpdirSize)`. See the [Runtime Environment][runtime] section of the CWL specification for details."
msgid"The following are a set of recommended good practices to keep in mind when writing a Common Workflow Language description for a tool or workflow. These guidelines are presented for consideration on a scale of usefulness: although more is better, not all are required."
1290
-
msgstr""
1291
-
"以下提供了一些关于为工具或工作流编写通用语言描述的建议,请牢记在心。此处仅基"
1292
-
"于有用性量表提供部分指导原则:虽然越多越好,但并非所有原则都是必需的。"
1292
+
msgstr"本节列举一组值得留心的好习惯,推荐您在用 CWL "
1293
+
"编写工具或工作流描述时参考。您只需结合实际尽量做到,无需求全。"
1293
1294
1294
1295
#:../../src/topics/best-practices.md:8
1295
1296
#: 4bcb84707acb40a0bfe2ea0853cb10b7
1296
1297
msgid"No `type: string` parameters for names of input or reference files/directories; use `type: File` or `type: Directory` as appropriate."
msgid"A CWL document (in conjunction with any external components like `Dockerfile`s) is software code. Workflow developers should be aware that the usual rules of software licensing apply to this document. For example, if the workflow is shared publicly, licensing terms must be clear so that a future user understands under what conditions they can run the workflow, modify it and/or combine it with other workflows. For this reason, please consider including a license field in the document. The authors of this guide urge you to choose a pre-existing license rather than trying to write your own (see the link below to learn more about choosing a license), and our recommended practice is to choose a license that allows for re-use by anyone, e.g. [Apache 2.0][apache-license]."
msgid"If possible, the license should be specified with its corresponding [SPDX identifier][spdx]. Construct the metadata field for the license by providing a URL of the form `https://spdx.org/licenses/[SPDX-ID]` where `SPDX-ID` is taken from the list of identifiers linked above. See the example snippet below for guidance. For non-standard licenses without an SPDX identifier, provide a URL to the license."
0 commit comments