rkward - en to en_GB translation catalogue (19 entries)

note: i18n: ectx: (RKWard Add-Ons) <summary>
en: <strong>Kate add-ons</strong>: Kate is the engine behind RKWard's script editor. It comes with powerful add-on features, many of which should come pre-installed with RKWard. However, due to their sheer number, not all are activated by default. It can further be extended with custom scripts, or color-schemes.
en_GB: <strong>Kate add-ons</strong>: Kate is the engine behind RKWard's script editor. It comes with powerful add-on features, many of which should come pre-installed with RKWard. However, due to their sheer number, not all are activated by default. It can further be extended with custom scripts, or colour-schemes.

note: i18n: ectx: (RKWard Add-Ons) <summary>
en: <strong>RKWard plugins</strong>: If you are looking for a graphical dialog to help you import/convert/analyse/visualize your data, such dialogs are mostly implemented as plugin-ins in RKWard. Many such plugins are available for download, separately.
en_GB: <strong>RKWard plugins</strong>: If you are looking for a graphical dialog to help you import/convert/analyse/visualise your data, such dialogs are mostly implemented as plugin-ins in RKWard. Many such plugins are available for download, separately.

note: i18n: ectx: (RKWard Add-Ons) <section title="RKWard Plugins">
en: Not all RKWard plugins packaged this way will be visible in the R package installation dialog, as they are not hosted (yet) in the default repositories, notably, at the time of this writing, the very extensive <link href="https://github.com/rkward-community/rk.Teaching">rk.Teaching</link> set of plugins. Many of these are hosted on platforms such as github.com, and knowing the repository url, can be installed with few clicks, using <link href="rkward://runplugin/rkward::install_from_git/fullURL.text=https://github.com/rkward-community/rk.Teaching.git">this dialog</link> (pre-initialized for installation of rk.Teaching).
en_GB: Not all RKWard plugins packaged this way will be visible in the R package installation dialog, as they are not hosted (yet) in the default repositories, notably, at the time of this writing, the very extensive <link href="https://github.com/rkward-community/rk.Teaching">rk.Teaching</link> set of plugins. Many of these are hosted on platforms such as github.com, and knowing the repository URL, can be installed with few clicks, using <link href="rkward://runplugin/rkward::install_from_git/fullURL.text=https://github.com/rkward-community/rk.Teaching.git">this dialog</link> (pre-initialised for installation of rk.Teaching).

note: i18n: ectx: (Using the RKWard R Console) <section title="Configurable Settings">
en: To configure the behavior of the console, select <a href="rkward://settings/console">Settings->Configure RKWard->R Console</a> or "Configure" from the context menu. The following options are configurable:
en_GB: To configure the behaviour of the console, select <a href="rkward://settings/console">Settings->Configure RKWard->R Console</a> or "Configure" from the context menu. The following options are configurable:

note: i18n: ectx: (Using the RKWard R Console) <section title="Configurable Settings">
en: <b>Run commands from script editor through the console</b>: Commands coming from script editors may be sent through the console, i.e. the commands and their results will be shown in the console. If this option is not checked, the commands will only be visible in the Command log, but not in the console.
en_GB: <b>Run commands from script editor through the console</b>: Commands coming from script editors may be sent through the console, i.e. the commands and their results will be shown in the console. If this option is not ticked, the commands will only be visible in the Command log, but not in the console.

note: i18n: ectx: (Using the RKWard R Console) <section title="Configurable Settings">
en: <b>Also add those commands to console history</b>: If the above option is checked, this affects, whether such commands are also added to the console history. Turning off this option may help to keep the console history "clean".
en_GB: <b>Also add those commands to console history</b>: If the above option is ticked, this affects, whether such commands are also added to the console history. Turning off this option may help to keep the console history "clean".

note: i18n: ectx: (Using the RKWard R Console) <section title="Configurable Settings">
en: <b>Command history is context-sensitive by default</b>: If this is checked, the context-sensitive mode of navigating the <link href="#command_history">command history</link> is the default, i.e. available with Up/Down without Shift. Else the key binding for this is Shift+Up/Down.
en_GB: <b>Command history is context-sensitive by default</b>: If this is ticked, the context-sensitive mode of navigating the <link href="#command_history">command history</link> is the default, i.e. available with Up/Down without Shift. Else the key binding for this is Shift+Up/Down.

note: i18n: ectx: (RKWard for new Users) <section title="Basic Analyses">
en: In order to familiarize yourself with RKWard (or with your data), one of the first things to do might be to choose Analysis->Descriptive Statistics from the Menu. You will be presented with a dialog that allows you to select one or more variables to analyse. This looks similar to the workspace browser introduced above. On the additional tabs you can choose which types of descriptive statistics should be calculated.
en_GB: In order to familiarise yourself with RKWard (or with your data), one of the first things to do might be to choose Analysis->Descriptive Statistics from the Menu. You will be presented with a dialogue that allows you to select one or more variables to analyse. This looks similar to the workspace browser introduced above. On the additional tabs you can choose which types of descriptive statistics should be calculated.

note: i18n: ectx: (RKWard for new Users) <section title="Basic Analyses">
en: At the lower right of the dialog, there is a button labelled "Code". Using this, you can show/hide a text area. If you look at the contents of this text area (you may have to resize the window to view it more comfortably), you can see the text changing according to the settings you choose in the dialog. This text is actually R syntax. It is the code that is needed to perform these calculations in R. Most of RKWard is based on generating this code for you, and then running it inside R. Later, when you feel more comfortable, have specific needs not covered by RKWard, or you want to automate repetitive tasks, you can use this syntax to literally program your analyses. Note that the code is divided into up to three sections: "Preprocess" for loading required libraries or defining helper functions, "Calculate" to perform the actual calculations, and "Printout" to generate output in RKWard's output window.
en_GB: At the lower right of the dialogue, there is a button labelled "Code". Using this, you can show/hide a text area. If you look at the contents of this text area (you may have to resize the window to view it more comfortably), you can see the text changing according to the settings you choose in the dialogue. This text is actually R syntax. It is the code that is needed to perform these calculations in R. Most of RKWard is based on generating this code for you, and then running it inside R. Later, when you feel more comfortable, have specific needs not covered by RKWard, or you want to automate repetitive tasks, you can use this syntax to literally program your analyses. Note that the code is divided into up to three sections: "Preprocess" for loading required libraries or defining helper functions, "Calculate" to perform the actual calculations, and "Printout" to generate output in RKWard's output window.

note: i18n: ectx: (RKWard for R Users) <section title="Workspace View">
en: RKWard comes with a "workspace view" or "object browser". By default this is available by clicking on "Workspace" on the left side of the application window. This allows you to examine and manipulate all objects in the R workspace. By default, only the ".GlobalEnv" environment is shown (where you'll typically do your work; see <link href="rkward://rhelp/.GlobalEnv"/>). But, checking "Show All Environments", you can easily explore data and functions in loaded R libraries (and even in package namespaces).
en_GB: RKWard comes with a "workspace view" or "object browser". By default this is available by clicking on "Workspace" on the left side of the application window. This allows you to examine and manipulate all objects in the R workspace. By default, only the ".GlobalEnv" environment is shown (where you'll typically do your work; see <link href="rkward://rhelp/.GlobalEnv"/>). But, ticking "Show All Environments", you can easily explore data and functions in loaded R libraries (and even in package namespaces).

note: i18n: ectx: (RKWard for R Users) <section title="Managing installed and loaded Libraries">
en: RKWard provides an advanced dialog to have installation, updating, and loading of packages. This is available from Settings->Manage R Packages.
en_GB: RKWard provides an advanced dialogue to have installation, updating, and loading of packages. This is available from Settings->Manage R Packages.

note: i18n: ectx: (RKWard for R Users) <section title="Everything else">
en: You will notice that RKWard provides a lot of further menu options. These provide access to functionality in R. In fact, they do so by generating R syntax from settings made in a graphical dialog. For instance, select Analysis->Descriptive Statistics. You will notice a small window at the bottom (can be toggled on or off using the "Code" button) that contains the R code needed to generate these statistics. This way, even if you prefer to script your code by hand, you can use dialogs to gain usage examples or snippets of code for functions you are less familiar with in R.
en_GB: You will notice that RKWard provides a lot of further menu options. These provide access to functionality in R. In fact, they do so by generating R syntax from settings made in a graphical dialogue. For instance, select Analysis->Descriptive Statistics. You will notice a small window at the bottom (can be toggled on or off using the "Code" button) that contains the R code needed to generate these statistics. This way, even if you prefer to script your code by hand, you can use dialogues to gain usage examples or snippets of code for functions you are less familiar with in R.

note: i18n: ectx: (Version incompatibilities) <section title="Graphics Engine Version Mismatch">
en: This is the most common kind of version incompatibility. The same advice applies as above, i.e. please install an updated version of RKWard. However, if no update appears to be immediately available, and you are desparate to continue working, set <link href="rkward://settings/graphics">Settings->Onscreen Graphics</link>->"Integration of R standard device" to "No integration". Then you can use the vanille onscreen devices (X11() or Windows() or Quartz()), for plotting.
en_GB: This is the most common kind of version incompatibility. The same advice applies as above, i.e. please install an updated version of RKWard. However, if no update appears to be immediately available, and you are desperate to continue working, set <link href="rkward://settings/graphics">Settings->Onscreen Graphics</link>->"Integration of R standard device" to "No integration". Then you can use the vanilla onscreen devices (X11() or Windows() or Quartz()), for plotting.

note: i18n: ectx: (RKWard Output) <section title="Using the output in an office suite">
en: Internally, RKWard output files are currently simply based on HTML. If you need access to the raw HTML and image files, a .rko-file is just a zip'ed folder. You can unzip it using standard tools, or open it in RKWard, and retrieve the files from the ".rkward" of your home directory (location configurable in Settings->Configure RKWard->General).
en_GB: Internally, RKWard output files are currently simply based on HTML. If you need access to the raw HTML and image files, a .rko-file is just a zip'ed folder. You can unzip it using standard tools, or open it in RKWard, and retrieve the files from the ".rkward" of your home folder (location configurable in Settings->Configure RKWard->General).

note: i18n: ectx: (Screen device history) <section title="Configurable Settings">
en: <b>Screen device history</b>: Enables / disables the recording of plots globally. You can toggle this from within a running RKWard session, which will affect all currently open and future screen devices. When unchecked, RKWard will not store any further plots in the history; although, the ones already stored are not lost! You can access the stored plots by re-enabling this. When toggling this, RKWard tries to save any unsaved plots, but be careful especially when the maximum history length is small (see below). You may want to disable this when the implemented history behavior seems non-intuitive or when dealing with large plots.
en_GB: <b>Screen device history</b>: Enables / disables the recording of plots globally. You can toggle this from within a running RKWard session, which will affect all currently open and future screen devices. When unticked, RKWard will not store any further plots in the history; although, the ones already stored are not lost! You can access the stored plots by re-enabling this. When toggling this, RKWard tries to save any unsaved plots, but be careful especially when the maximum history length is small (see below). You may want to disable this when the implemented history behaviour seems non-intuitive or when dealing with large plots.

note: i18n: ectx: (Screen device history) <section title="Configurable Settings">
en: <b>Maximum number of recorded plots</b>: Controls the maximum number of plots that can be stored in the history. When this limit is reached, plots from the beginning of the history will get removed one by one, much like a push-pop stack. A warning dialog is shown when this happens. Be careful when setting this below the number of already stored plots. In that case an appropriate number of plots from the beginning of the history stack will get removed, which may not be desirable.
en_GB: <b>Maximum number of recorded plots</b>: Controls the maximum number of plots that can be stored in the history. When this limit is reached, plots from the beginning of the history will get removed one by one, much like a push-pop stack. A warning dialogue is shown when this happens. Be careful when setting this below the number of already stored plots. In that case an appropriate number of plots from the beginning of the history stack will get removed, which may not be desirable.

note: i18n: ectx: (Screen device history) <section title="Configurable Settings">
en: <b>Maximum size of a single recorded plot</b>: Controls the maximum allowed size (in KB) of a single plot that can be stored in the history. For a plot larger than this specified size, a dialog box, to save or to ignore the plot, will be presented. Unlike the above length restriction, this setting will affect only the future plots (that is, will not remove any already stored, yet large, plots).
en_GB: <b>Maximum size of a single recorded plot</b>: Controls the maximum allowed size (in KB) of a single plot that can be stored in the history. For a plot larger than this specified size, a dialogue box, to save or to ignore the plot, will be presented. Unlike the above length restriction, this setting will affect only the future plots (that is, will not remove any already stored, yet large, plots).

note: i18n: ectx: (Split views) <section title="Splitting views">
en: Splitting views is currently supported for the main window, only. Use Window->Split Vertical or Window->Split Horizontal to split the current view area vertically, or horizontally. For windows that support it (e.g. scripts, help pages), the newly created view area will contain a copy of the current window. When splitting other windows (such as onscreen graphics devices), the new view area will be initialized to show this help page.
en_GB: Splitting views is currently supported for the main window, only. Use Window->Split Vertical or Window->Split Horizontal to split the current view area vertically, or horizontally. For windows that support it (e.g. scripts, help pages), the newly created view area will contain a copy of the current window. When splitting other windows (such as onscreen graphics devices), the new view area will be initialised to show this help page.

note: i18n: ectx: (Workspace Browser) <section title="What is shown">
en: Note that objects are organized in a hierarchy, i.e. some types of objects contain further "child" objects. This is indicated by a "+" symbol to the left of the object name. Clicking on this will expand the view to show all the children of the object.
en_GB: Note that objects are organised in a hierarchy, i.e. some types of objects contain further "child" objects. This is indicated by a "+" symbol to the left of the object name. Clicking on this will expand the view to show all the children of the object.
