aboutsummaryrefslogtreecommitdiff
path: root/source/zh-CN/nlpsolver/help
diff options
context:
space:
mode:
authorChristian Lohmaier <lohmaier+LibreOffice@googlemail.com>2018-04-25 22:51:37 +0200
committerChristian Lohmaier <lohmaier+LibreOffice@googlemail.com>2018-04-25 23:06:53 +0200
commit61991bde16235b2c9c4028466bcdc51a352e7bc5 (patch)
treeb2d7059a15a64a79ef1f2dd05566586eebdaaf1a /source/zh-CN/nlpsolver/help
parente3802bb90081c3cc63ca8ec9726772d8e42299b0 (diff)
update translatiosn for 6.1.0 alpha1
Change-Id: I0ed5d948cf89a4260c8771057d463448b76a4527
Diffstat (limited to 'source/zh-CN/nlpsolver/help')
-rw-r--r--source/zh-CN/nlpsolver/help/en/com.sun.star.comp.Calc.NLPSolver.po10
1 files changed, 5 insertions, 5 deletions
diff --git a/source/zh-CN/nlpsolver/help/en/com.sun.star.comp.Calc.NLPSolver.po b/source/zh-CN/nlpsolver/help/en/com.sun.star.comp.Calc.NLPSolver.po
index 3fa273114c0..27fcf01d56c 100644
--- a/source/zh-CN/nlpsolver/help/en/com.sun.star.comp.Calc.NLPSolver.po
+++ b/source/zh-CN/nlpsolver/help/en/com.sun.star.comp.Calc.NLPSolver.po
@@ -4,8 +4,8 @@ msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: https://bugs.libreoffice.org/enter_bug.cgi?product=LibreOffice&bug_status=UNCONFIRMED&component=UI\n"
"POT-Creation-Date: 2016-11-09 14:10+0100\n"
-"PO-Revision-Date: 2016-12-27 04:21+0000\n"
-"Last-Translator: 锁琨珑 <suokunlong@126.com>\n"
+"PO-Revision-Date: 2018-03-06 03:36+0000\n"
+"Last-Translator: Voina i Mir <shanshandehongxing@outlook.com>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: zh_CN\n"
"MIME-Version: 1.0\n"
@@ -14,7 +14,7 @@ msgstr ""
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Accelerator-Marker: ~\n"
"X-Generator: Pootle 2.8\n"
-"X-POOTLE-MTIME: 1482812474.000000\n"
+"X-POOTLE-MTIME: 1520307416.000000\n"
#: Options.xhp
msgctxt ""
@@ -374,7 +374,7 @@ msgctxt ""
"par_id0603200910430845\n"
"help.text"
msgid "Regardless whether you use DEPS or SCO, you start by going to Tools - Solver and set the Cell to be optimized, the direction to go (minimization, maximization) and the cells to be modified to reach the goal. Then you go to the Options and specify the solver to be used and if necessary adjust the according <link href=\"com.sun.star.comp.Calc.NLPSolver/Options.xhp\">parameters</link>."
-msgstr "不管您是使用DEPS还是SCO, 首先您需要到“工具 - 选项 - 求解器”,并设定需要优化的单元格、求解方向(最小还是最大),以及为了达到该目标需要更改的单元格。然后您需要在“选项”中指定需要使用的求解引擎;如果有必要您还需要调整相应的<link href=\"com.sun.star.comp.Calc.NLPSolver/Options.xhp\">参数</link>。"
+msgstr "不管您是使用 DEPS 还是 SCO,首先您需要到“工具 - 选项 - 求解器”,并设定需要优化的单元格、求解方向(最小还是最大),以及为了达到该目标需要更改的单元格。然后您需要在“选项”中指定需要使用的求解引擎;如果有必要您还需要调整相应的<link href=\"com.sun.star.comp.Calc.NLPSolver/Options.xhp\">参数</link>。"
#: Usage.xhp
msgctxt ""
@@ -382,7 +382,7 @@ msgctxt ""
"par_id0603200910430821\n"
"help.text"
msgid "There is also a list of constraints you can use to restrict the possible range of solutions or to penalize certain conditions. However, in case of the evolutionary solvers DEPS and SCO, these constraints are also used to specify bounds on the variables of the problem. Due to the random nature of the algorithms, it is <emph>highly recommended</emph> to do so and give upper (and in case \"Assume Non-Negative Variables\" is turned off also lower) bounds for all variables. They don't have to be near the actual solution (which is probably unknown) but should give a rough indication of the expected size (0 ≤ var ≤ 1 or maybe -1000000 ≤ var ≤ 1000000)."
-msgstr "<emph>强烈建议</emph>为所有变量指定上边界。不必与实际结果(可能未知)相近,但应该大致推测结果尺寸 (0 ≤ 变量 ≤ 1 也可能是 -1000000 ≤ 变量 ≤ 1000000)。"
+msgstr "<emph>强烈建议</emph>为所有变量指定上边界。不必与实际结果(可能未知)相近,但应该大致推测结果尺寸 (0 ⩽ 变量 ⩽ 1 也可能是 -1000000 ⩽ 变量 ⩽ 1000000)。"
#: Usage.xhp
msgctxt ""