[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-commits
Subject: l10n-support/templates/summit/docmessages/playground-edu
From: Chusslove Illich <caslav.ilic () gmx ! net>
Date: 2017-01-31 8:22:25
Message-ID: E1cYThp-0007yi-Cc () code ! kde ! org
[Download RAW message or body]
SVN commit 1481335 by ilic:
Summit gather.
M +8 -8 rkwardplugins.pot
--- trunk/l10n-support/templates/summit/docmessages/playground-edu/rkwardplugins.pot \
#1481334:1481335 @@ -6,7 +6,7 @@
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2017-01-30 09:26+0100\n"
+"POT-Creation-Date: 2017-01-31 09:22+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
@@ -3024,7 +3024,7 @@
#. +> trunk
#: index.docbook:956
#, no-c-format
-msgid "In some cases, you may want to fetch further information from R, to be \
presented in your plugin's UI. For instance, you may want to offer a selection of the \
levels of a factor that the user has selected for analysis. Since version 0.6.2 of \
&rkward; it is possible to do so. Before we start, it is important that you are aware \
of some caveats:" +msgid "In some cases, you may want to fetch further information \
from &r;, to be presented in your plugin's UI. For instance, you may want to offer a \
selection of the levels of a factor that the user has selected for analysis. Since \
version 0.6.2 of &rkward; it is possible to do so. Before we start, it is important \
that you are aware of some caveats:" msgstr ""
#. Tag: para
@@ -3108,7 +3108,7 @@
#. +> trunk
#: index.docbook:972
#, no-c-format
-msgid "When the command is done, the specified callback is called \
(<parameter>commandFinished</parameter>, in this case) with two parameters: The \
result itself, and the id of the corresponding command. The result will be of a type \
resembling the representation in R, &ie; a numeric Array, if the result is numeric, \
&etc; It can even be an &r; <command>list()</command>, but in this case it will be \
represented as a JS <command>Array()</command> without names." +msgid "When the \
command is done, the specified callback is called \
(<parameter>commandFinished</parameter>, in this case) with two parameters: The \
result itself, and the id of the corresponding command. The result will be of a type \
resembling the representation in &r;, &ie; a numeric Array, if the result is numeric, \
&etc; It can even be an &r; <command>list()</command>, but in this case it will be \
represented as a JS <command>Array()</command> without names." msgstr ""
#. Tag: para
@@ -3232,7 +3232,7 @@
#. +> trunk
#: index.docbook:1016
#, no-c-format
-msgid "Of course you can also use <link linkend=\"logic\">UI logic</link> inside an \
optionset. There are two options for doing this: You can do so by making connection \
(or scripting) in the main <command><logic></command> section of your plugin, \
as usual. However, you will access the UI elements in the contents region as (⪚) \
\"set.contents.firstname.XYZ\". Note the prefix \"set\" (the \
<parameter>id</parameter> you have assigned to the set and \"contents\". \
Alternatively, you can add a separate <command><logic></command> section as a \
child element of your <command><optionset></command>. In this case, \
<parameter>id</parameter>s will be addressed relative to the contents region, ⪚ \
\"firstname.XYZ\". Only the <command><script></command>-element is not allowed \
in the logic section of an optionset. If you want to use scripting, you will have to \
utilize the plugin's main <command><logic></command> section." +msgid "Of \
course you can also use <link linkend=\"logic\">UI logic</link> inside an optionset. \
There are two options for doing this: You can do so by making connection (or \
scripting) in the main <command><logic></command> section of your plugin, as \
usual. However, you will access the UI elements in the contents region as (⪚) \
\"set.contents.firstname.XYZ\". Note the prefix \"set\" (the \
<parameter>id</parameter> you have assigned to the set and \"contents\"). \
Alternatively, you can add a separate <command><logic></command> section as a \
child element of your <command><optionset></command>. In this case, \
<parameter>id</parameter>s will be addressed relative to the contents region, ⪚ \
\"firstname.XYZ\". Only the <command><script></command>-element is not allowed \
in the logic section of an optionset. If you want to use scripting, you will have to \
utilize the plugin's main <command><logic></command> section." msgstr ""
#. Tag: para
@@ -3891,7 +3891,7 @@
#. +> trunk
#: index.docbook:1228
#, no-c-format
-msgid "That said, it is generally not a good idea to make bits like function names \
or variable names translatable. For one thing, R, the programming language, is \
inherently in English, and there is no internationalization of the language itself. \
Code comments are a different beast, but you should use the \
<command>comment()</command>-function for those. Secondly, making syntactically \
relevant parts of the generated code translatable means that translations could \
actually break your plugin. E.g. if an unsuspecting translator translates a string \
meant as a variable name in two distinct words with a space in between." +msgid "That \
said, it is generally not a good idea to make bits like function names or variable \
names translatable. For one thing, &r;, the programming language, is inherently in \
English, and there is no internationalization of the language itself. Code comments \
are a different beast, but you should use the <command>comment()</command>-function \
for those. Secondly, making syntactically relevant parts of the generated code \
translatable means that translations could actually break your plugin. E.g. if an \
unsuspecting translator translates a string meant as a variable name in two distinct \
words with a space in between." msgstr ""
#. Tag: title
@@ -4767,7 +4767,7 @@
#. +> trunk
#: index.docbook:1456
#, no-c-format
-msgid "The package has some functions for JS code constructs that are commonly used \
in &rkward; plugins, like the <function>echo()</function> function or <function>if() \
{...} else {...}</function> conditions. There are some differences between JS and R, \
⪚, for <function>paste()</function> in &r; you use the comma to concatenate \
character strings, whereas for <function>echo()</function> in JS you use \
<quote>+</quote>, and lines must end with a semicolon. By using the &r; functions, \
you can almost forget about these differences and keep writing &r; code." +msgid "The \
package has some functions for JS code constructs that are commonly used in &rkward; \
plugins, like the <function>echo()</function> function or <function>if() {...} else \
{...}</function> conditions. There are some differences between JS and &r;, ⪚, for \
<function>paste()</function> in &r; you use the comma to concatenate character \
strings, whereas for <function>echo()</function> in JS you use <quote>+</quote>, and \
lines must end with a semicolon. By using the &r; functions, you can almost forget \
about these differences and keep writing &r; code." msgstr ""
#. Tag: para
@@ -8114,7 +8114,7 @@
#. +> trunk
#: index.docbook:2689
#, no-c-format
-msgid "Data in a format suitable for pasting to R, wrapped in a cbind statement \
(string; read-only)." +msgid "Data in a format suitable for pasting to &r;, wrapped \
in a cbind statement (string; read-only)." msgstr ""
#. Tag: para
@@ -9273,7 +9273,7 @@
#. +> trunk
#: index.docbook:3163
#, no-c-format
-msgid "To include a &pluginmap; file from a different package (or an &rkward; \
&pluginmap; from your external &pluginmap;, you can refer to it by its \
<replaceable>namespacename::id</replaceable>, as specified in the required \
&pluginmap;s <document> element. Inclusion will fail, if no &pluginmap; by that \
id is known (⪚ not installed on the user's system). You should use this method for \
including &pluginmap;s outside your package, only. For maps inside your package, \
specifying a relative path (<parameter>file</parameter> attribute) is faster, and \
more reliable." +msgid "To include a &pluginmap; file from a different package (or an \
&rkward; &pluginmap; from your external &pluginmap;), you can refer to it by its \
<replaceable>namespacename::id</replaceable>, as specified in the required \
&pluginmap;s <document> element. Inclusion will fail, if no &pluginmap; by that \
id is known (⪚ not installed on the user's system). You should use this method for \
including &pluginmap;s outside your package, only. For maps inside your package, \
specifying a relative path (<parameter>file</parameter> attribute) is faster, and \
more reliable." msgstr ""
#. Tag: title
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic