Overview

Project website lsj.readthedocs.io
Instructions for translators

Dear translators,

welcome and thank you for your willingness to contribute to the translation of the “learning statistics with jamovi”-text book!

There are a couple of things that I would like to ask you, in order to make your and my life a bit easier (manual corrections need time, so that what you translated won't appear until I fixed it): [1] There are buttons underneath the “Translation” box. One of them is “Automatic suggestions” which provides you with a machine translation of the text to be translated. This can just be copied into the target field for the translation and adjusted. [2] There are a couple of text elements that should be treated different from the rest of the text (please check: the automatic suggestions might translate this “wrong”): - placeholders (marked by “|”) should not be translated: e.g., |placeholder| or |placeholder|_, among them is |continuous| which produces an icon denoting a continuous level of measurement - double backticks : they typically are used for variable or analysis names – the variable names shouldn't be changed, for the analysis names, it is up to your discretion whether to translate them or not (I decided to rather go with the English analysis since the feature to set the UI language in jamovi is fairly new and it is relatively simple to figure out the translated name from the English one) - be careful that :doc: does not contain spaces at the begin of the string, also ensure to leave the part enclosed by <> as it is (it points to a file; therefore, please double-check that the automatic translation did not translate it otherwise it will end up as a broken link) - figure references, e.g., :numref:fig-normAreaSD should not to be translated - (language-specific) quotation marks: there are buttons above the text field for the target translation that can be used to replace "'s by your language specific quotation marks [3] markdown-formattings for italicsor bold: please ensure that the stars are placed around the same word / meaning in the translation as in the original [4] if there doesn't exist a good translation of a particular word or technical term, either try "translation (original word / phrase)" or "original word / phrase" (this shows the original English term in italics either with a translation that you may not be completely happy with or without a translation

Finally, I would like to suggest that you install LanguageTool (browser add-on) as an additional check that your translations are correct (however, LanguageTool might not be available for every language).

Don't hesitate to contact me (@sjentsch) if you have questions or suggestions.
Project maintainers User avatar sjentsch
2 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 107,514 4,569,574 27,244,453
Source 4,315 183,516 1,094,153
Translated 36% 39,233 18% 832,727 18% 5,039,469
Needs editing 1% 1 1% 3 1% 21
Read-only 4% 4,315 4% 183,516 4% 1,094,153
Failing checks 1% 729 1% 68,191 1% 412,421
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 63% 68,280 81% 3,736,844 81% 22,204,963
Last 12 months Previous

Activity in last 12 months

20 changes 0 changes 0 changes 25 changes 152 changes 22 changes 9 changes 0 changes 0 changes 6,554 changes 0 changes 0 changes 0 changes 11 changes 10 changes 0 changes 8 changes 0 changes 4,491 changes 8,823 changes 0 changes 27 changes 88 changes 7,266 changes
AprMayJunJulAugSepOctNovDecJanFebMar

Quick numbers

0
Hosted words
0
Hosted strings
0%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Alert triggered
Broken project website URL 2 weeks ago
User avatar None

Alert triggered
Broken project website URL 2 weeks ago
User avatar None

Component unlocked
Fixing an alert automatically unlocked the component. 2 weeks ago
User avatar None

Resource updated
The “nb/LC_MESSAGES/Ch13.po” file was changed. 2 weeks ago
User avatar None

String updated in the repository
\begin{array}{rcl}
\mbox{RSS}_{b} &=& \sum_k \sum_i ( \bar{R}_k - \bar{R} )^2 \\
&=& \sum_k N_k ( \bar{R}_k - \bar{R} )^2
\end{array}
\begin{array}{rcl}
\mbox{RSS}_{b} &=& \sum_k \sum_i ( \bar{R}_k - \bar{R} )^2 \\
&=& \sum_k N_k ( \bar{R}_k - \bar{R} )^2
\end{array}
2 weeks ago
User avatar None

String updated in the repository
\mbox{RSS}_{tot} = \sum_k \sum_i ( R_{ik} - \bar{R} )^2

\mbox{RSS}_{tot} = \sum_k \sum_i ( R_{ik} - \bar{R} )^2

2 weeks ago
User avatar None

String updated in the repository
\bar{R} = \frac{1}{N} \sum_{i} \sum_{k} R_{ik}

\bar{R} = \frac{1}{N} \sum_{i} \sum_{k} R_{ik}

2 weeks ago
User avatar None

String updated in the repository
\bar{R}_k = \frac{1}{N_K} \sum_{i} R_{ik}

\bar{R}_k = \frac{1}{N_K} \sum_{i} R_{ik}

2 weeks ago
User avatar None

String updated in the repository
Okay, so how do we run the Levene test? Simple really - under the ``ANOVA`` → ``Assumption Checks`` option, just click on the ``Homogeneity tests`` checkbox. If we look at the output, shown in :numref:`fig-anova4`, we see that the test is non-significant (*F*\{2,15} = 1.45, *p* = 0.266), so it looks like the homogeneity of variance assumption is fine. However, looks can be deceptive! If your sample size is pretty big, then the Levene test could show up a significant effect (i.e., *p* < 0.05) even when the homogeneity of variance assumption is not violated to an extent which troubles the robustness of ANOVA. This was the point George Box was making in the quote above. Similarly, if your sample size is quite small, then the homogeneity of variance assumption might not be satisfied and yet a Levene test could be non-significant (i.e. *p* > 0.05). What this means is that, alongside any statistical test of the assumption being met, you should always plot the standard deviation around the means for each group / category in the analysis… just to see if they look fairly similar (i.e. homogeneity of variance) or not.
Hvordan kjører vi Levene-testen? Det er egentlig enkelt - under ``ANOVA`` → ``Assumption Checks`` klikker du bare på avmerkingsboksen ``Homogeneity tests``. Hvis vi ser på resultatet, som vises i :numref:`fig-anova4`, ser vi at testen ikke er signifikant (*F*\{2,15} = 1,45, *p* = 0,266), så det ser ut til at forutsetningen om varianshomogenitet er gitt. Utseendet kan imidlertid bedra! Hvis utvalgsstørrelsen er ganske stor, kan Levene-testen vise en signifikant effekt (dvs. *p* < 0,05) selv om forutsetningen om varianshomogenitet ikke er brutt i en grad som svekker robustheten til ANOVA. Dette var poenget George Box kom med i sitatet ovenfor. På samme måte kan det hende at forutsetningen om varianshomogenitet ikke er oppfylt hvis utvalgsstørrelsen er ganske liten, og at en Levene-test likevel kan være ikke-signifikant (dvs. *p* > 0,05). Dette betyr at du, ved siden av enhver statistisk test av om forutsetningen er oppfylt, alltid bør plotte standardavviket rundt gjennomsnittene for hver gruppe / kategori i analysen… bare for å se om de ser ganske like ut (dvs. varianshomogenitet) eller ikke.
2 weeks ago
User avatar None

String updated in the repository
Or, if we want to be sticklers for accuracy, :math:`1 + \frac{2}{df_2 - 2}`.
Eller, hvis vi skal være helt nøyaktige, :math:`1 + \frac{2}{df_2 - 2}`.
2 weeks ago
Browse all project changes
User avatar sjentsch

Announcement posted

Dear translators,

welcome and thank you for your willingness to contribute to the translation of the “learning statistics with jamovi”-text book!

There are a couple of things that I would like to ask you, in order to make your and my life a bit easier (manual corrections need time, so that what you translated won't appear until I fixed it): [1] There are buttons underneath the “Translation” box. One of them is “Automatic suggestions” which provides you with a machine translation of the text to be translated. This can just be copied into the target field for the translation and adjusted. [2] There are a couple of text elements that should be treated different from the rest of the text (please check: the automatic suggestions might translate this “wrong”): - placeholders (marked by “|”) should not be translated: e.g., |placeholder| or |placeholder|_, among them is |continuous| which produces an icon denoting a continuous level of measurement - double backticks : they typically are used for variable or analysis names – the variable names shouldn't be changed, for the analysis names, it is up to your discretion whether to translate them or not (I decided to rather go with the English analysis since the feature to set the UI language in jamovi is fairly new and it is relatively simple to figure out the translated name from the English one) - be careful that :doc: does not contain spaces at the begin of the string, also ensure to leave the part enclosed by <> as it is (it points to a file; therefore, please double-check that the automatic translation did not translate it otherwise it will end up as a broken link) - figure references, e.g., :numref:fig-normAreaSD should not to be translated - (language-specific) quotation marks: there are buttons above the text field for the target translation that can be used to replace "'s by your language specific quotation marks [3] markdown-formattings for italicsor bold: please ensure that the stars are placed around the same word / meaning in the translation as in the original [4] if there doesn't exist a good translation of a particular word or technical term, either try "translation (original word / phrase)" or "original word / phrase" (this shows the original English term in italics either with a translation that you may not be completely happy with or without a translation

Finally, I would like to suggest that you install LanguageTool (browser add-on) as an additional check that your translations are correct (however, LanguageTool might not be available for every language).

Don't hesitate to contact me (@sjentsch) if you have questions or suggestions.

2 years ago
Browse all project changes