scratch-l10n 5.0.194 → 5.0.196
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +14 -0
- package/editor/interface/ab.json +53 -0
- package/editor/interface/af.json +53 -0
- package/editor/interface/am.json +53 -0
- package/editor/interface/an.json +53 -0
- package/editor/interface/ar.json +53 -0
- package/editor/interface/ast.json +53 -0
- package/editor/interface/az.json +53 -0
- package/editor/interface/be.json +53 -0
- package/editor/interface/bg.json +53 -0
- package/editor/interface/bn.json +53 -0
- package/editor/interface/ca.json +53 -0
- package/editor/interface/ckb.json +53 -0
- package/editor/interface/cs.json +53 -0
- package/editor/interface/cy.json +53 -0
- package/editor/interface/da.json +53 -0
- package/editor/interface/de.json +53 -0
- package/editor/interface/el.json +53 -0
- package/editor/interface/en.json +53 -0
- package/editor/interface/eo.json +53 -0
- package/editor/interface/es-419.json +53 -0
- package/editor/interface/es.json +53 -0
- package/editor/interface/et.json +53 -0
- package/editor/interface/eu.json +53 -0
- package/editor/interface/fa.json +53 -0
- package/editor/interface/fi.json +53 -0
- package/editor/interface/fil.json +53 -0
- package/editor/interface/fr.json +53 -0
- package/editor/interface/fy.json +53 -0
- package/editor/interface/ga.json +53 -0
- package/editor/interface/gd.json +53 -0
- package/editor/interface/gl.json +53 -0
- package/editor/interface/ha.json +53 -0
- package/editor/interface/he.json +53 -0
- package/editor/interface/hi.json +53 -0
- package/editor/interface/hr.json +53 -0
- package/editor/interface/ht.json +53 -0
- package/editor/interface/hu.json +53 -0
- package/editor/interface/hy.json +53 -0
- package/editor/interface/id.json +53 -0
- package/editor/interface/is.json +53 -0
- package/editor/interface/it.json +53 -0
- package/editor/interface/ja-Hira.json +53 -0
- package/editor/interface/ja.json +53 -0
- package/editor/interface/ka.json +53 -0
- package/editor/interface/kk.json +53 -0
- package/editor/interface/km.json +53 -0
- package/editor/interface/ko.json +53 -0
- package/editor/interface/ku.json +53 -0
- package/editor/interface/lt.json +53 -0
- package/editor/interface/lv.json +53 -0
- package/editor/interface/mi.json +53 -0
- package/editor/interface/mn.json +53 -0
- package/editor/interface/nb.json +53 -0
- package/editor/interface/nl.json +53 -0
- package/editor/interface/nn.json +53 -0
- package/editor/interface/nso.json +53 -0
- package/editor/interface/oc.json +53 -0
- package/editor/interface/or.json +53 -0
- package/editor/interface/pl.json +53 -0
- package/editor/interface/pt-br.json +53 -0
- package/editor/interface/pt.json +53 -0
- package/editor/interface/qu.json +53 -0
- package/editor/interface/rap.json +53 -0
- package/editor/interface/ro.json +53 -0
- package/editor/interface/ru.json +53 -0
- package/editor/interface/sk.json +53 -0
- package/editor/interface/sl.json +53 -0
- package/editor/interface/sr.json +53 -0
- package/editor/interface/sv.json +53 -0
- package/editor/interface/sw.json +53 -0
- package/editor/interface/th.json +53 -0
- package/editor/interface/tn.json +53 -0
- package/editor/interface/tr.json +53 -0
- package/editor/interface/uk.json +53 -0
- package/editor/interface/uz.json +53 -0
- package/editor/interface/vi.json +53 -0
- package/editor/interface/xh.json +53 -0
- package/editor/interface/zh-cn.json +53 -0
- package/editor/interface/zh-tw.json +53 -0
- package/editor/interface/zu.json +53 -0
- package/locales/editor-msgs.js +4240 -0
- package/locales/interface-msgs.js +4240 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
@@ -3,6 +3,20 @@
|
|
3
3
|
All notable changes to this project will be documented in this file. See
|
4
4
|
[Conventional Commits](https://conventionalcommits.org) for commit guidelines.
|
5
5
|
|
6
|
+
## [5.0.196](https://github.com/scratchfoundation/scratch-l10n/compare/v5.0.195...v5.0.196) (2025-04-08)
|
7
|
+
|
8
|
+
|
9
|
+
### Bug Fixes
|
10
|
+
|
11
|
+
* pull new editor translations from Transifex ([3cadc37](https://github.com/scratchfoundation/scratch-l10n/commit/3cadc37521a4bd8fd06e11c0dcb90df0006ef2b7))
|
12
|
+
|
13
|
+
## [5.0.195](https://github.com/scratchfoundation/scratch-l10n/compare/v5.0.194...v5.0.195) (2025-04-06)
|
14
|
+
|
15
|
+
|
16
|
+
### Bug Fixes
|
17
|
+
|
18
|
+
* **deps:** lock file maintenance ([72f4906](https://github.com/scratchfoundation/scratch-l10n/commit/72f490613ef7340f9bbf49d155993471a0566cc8))
|
19
|
+
|
6
20
|
## [5.0.194](https://github.com/scratchfoundation/scratch-l10n/compare/v5.0.193...v5.0.194) (2025-04-06)
|
7
21
|
|
8
22
|
|
package/editor/interface/ab.json
CHANGED
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "Иаҟәыхтәуп",
|
78
78
|
"gui.customProcedures.ok": "OK",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "Ишәхашәмыршҭын, аԥсҭҳәатә ҽеиҭакқәа цифрақәа мацараз ауп, инбанзар ма исимволзар ауам. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "Еиҳаны аилкаара.",
|
281
332
|
"gui.alerts.importing": "Аимпорт...",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "Излалагатәу",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "Иацышәҵа аиҭаҵратә блок",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "Иацҵатәуп аблок \"иҳәатәуп\"",
|
package/editor/interface/af.json
CHANGED
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "Kanselleer",
|
78
78
|
"gui.customProcedures.ok": "OK",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "Neem asseblief kennis, wolk veranderlikes ondersteun slegs nommers, nie letters of simbole nie. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "Leer meer.",
|
281
332
|
"gui.alerts.importing": "Besig om in te voer...",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "Kom aan die gang",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "Voeg 'n beweegblok by",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "Voeg spraakblok by",
|
package/editor/interface/am.json
CHANGED
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "ይቁም",
|
78
78
|
"gui.customProcedures.ok": "እሺ",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "Please note, cloud variables only support numbers, not letters or symbols. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "Learn more.",
|
281
332
|
"gui.alerts.importing": "Importing…",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "መጀመር",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "የእንቅስቃሴ ብሎኬታ ይጨመር",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "Add a say block",
|
package/editor/interface/an.json
CHANGED
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "Cancelar",
|
78
78
|
"gui.customProcedures.ok": "Acceptar",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "Faga-se cuenta que las variables en a boira nomás admiten numeros, no letras ni simbolos. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "Mas información.",
|
281
332
|
"gui.alerts.importing": "Importando…",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "Pa empecipiar",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "Anyade un bloque de movimiento",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "Anyade un bloque de decir",
|
package/editor/interface/ar.json
CHANGED
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "إلغاء الأمر",
|
78
78
|
"gui.customProcedures.ok": "موافق",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "يرجى ملاحظة أن المتغيرات السحابية تدعم الأرقام فقط، ولا تدعم الحروف أو الرموز. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "اعرف المزيد.",
|
281
332
|
"gui.alerts.importing": "جارٍ الاستيراد...",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "الشروع في العمل",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "أضف لبنةً للحركة",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "أضف لبنة قل",
|
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "Encaboxar",
|
78
78
|
"gui.customProcedures.ok": "OK",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "Atención, les variables na ñube namás soporten númberos, nin lletres nin símbolos. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "Aprendi más.",
|
281
332
|
"gui.alerts.importing": "Importando...",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "Entamando",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "Amestar un bloque de movimientu",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "Amestar un bloque de diálogu",
|
package/editor/interface/az.json
CHANGED
@@ -77,6 +77,57 @@
|
|
77
77
|
"gui.customProcedures.cancel": "Ləğv et",
|
78
78
|
"gui.customProcedures.ok": "Oldu",
|
79
79
|
"gui.debugModal.title": "Debugging | Getting Unstuck",
|
80
|
+
"gui.debugModal.readAloud.title": "Read Aloud",
|
81
|
+
"gui.debugModal.readAloud.description1": "As you read your code aloud, think from the computer’s perspective.",
|
82
|
+
"gui.debugModal.readAloud.description2": "Are you including steps that aren’t there?",
|
83
|
+
"gui.debugModal.readAloud.description3": "Are your instructions clear?",
|
84
|
+
"gui.debugModal.readAloud.description4": "If something needs to be reset each time the program has run, are those instructions included?",
|
85
|
+
"gui.debugModal.breakItDown.title": "Break It Down",
|
86
|
+
"gui.debugModal.breakItDown.description1": "Separate the blocks into smaller chunks (or sequences), and click to see what each sequence does.",
|
87
|
+
"gui.debugModal.breakItDown.description2": "Once the smaller sequences work as you expect, add them back into the main program.",
|
88
|
+
"gui.debugModal.breakItDown.description3": "The process is called decomposition.",
|
89
|
+
"gui.debugModal.slowItDown.title": "Slow It Down",
|
90
|
+
"gui.debugModal.slowItDown.description1": "The computer runs your program so quickly it can be hard to follow with your eyes.",
|
91
|
+
"gui.debugModal.slowItDown.description2": "Add temporary “wait” or “wait until” blocks to slow down the sequence. This gives you time to process if a piece worked or not.",
|
92
|
+
"gui.debugModal.slowItDown.description3": "Remove these wait blocks once your code works.",
|
93
|
+
"gui.debugModal.addSoundCheckpoints.title": "Add Sound Checkpoints",
|
94
|
+
"gui.debugModal.addSoundCheckpoints.description1": "Similar to the Slow It Down strategy, you can add different sounds with the “play until done” block at key points to test your sequence.",
|
95
|
+
"gui.debugModal.addSoundCheckpoints.description2": "If a sound doesn’t play, your bug may be before this block. If the sound plays, the bug is probably after this block.",
|
96
|
+
"gui.debugModal.addSoundCheckpoints.description3": "Remove the sounds once your code works.",
|
97
|
+
"gui.debugModal.tinkerWithBlockOrder.title": "Tinker with Block Order",
|
98
|
+
"gui.debugModal.tinkerWithBlockOrder.description1": "Try adjusting the order/sequence of the blocks.",
|
99
|
+
"gui.debugModal.tinkerWithBlockOrder.description2": "What needs to happen first?",
|
100
|
+
"gui.debugModal.tinkerWithBlockOrder.description3": "What happens second?",
|
101
|
+
"gui.debugModal.tinkerWithBlockOrder.description4": "Do values or sprites need to reset before the next piece of code runs?",
|
102
|
+
"gui.debugModal.tinkerWithBlockOrder.description5": "Try using blocks inside a loop or conditional statement, versus outside a loop or conditional statement.",
|
103
|
+
"gui.debugModal.toLoopOrNot.title": "To Loop or Not to Loop",
|
104
|
+
"gui.debugModal.toLoopOrNot.description1": "If using Control blocks like \"forever\" and \"repeat\", check that all blocks inside a loop should be there, or if a block (like “wait”) is missing to reset the action or adjust the timing. Do you want your loop to run forever or for a certain number of times? Should something stop the looping?",
|
105
|
+
"gui.debugModal.toLoopOrNot.description2": "Perhaps you aren't using a loop when you should be? For instance, if you are using a conditional statement block like \"if then,\" does the program only need to check if it is true or false once? Or does it need to check continuously, in which case, you would want to place your conditional statement inside a forever loop?",
|
106
|
+
"gui.debugModal.timingAndParallelism.title": "Think About Timing & Parallelism",
|
107
|
+
"gui.debugModal.timingAndParallelism.sectionTitle": "Timing & Parallelism",
|
108
|
+
"gui.debugModal.timingAndParallelism.description1": "Do you have multiple events trying to run at the same time? If two sequences are programmed to start at the same time, you can get unpredictable behavior.",
|
109
|
+
"gui.debugModal.timingAndParallelism.description2": "Add small waits, broadcasts, or user interaction (like clicking or pressing a key) to see if this affects the result.",
|
110
|
+
"gui.debugModal.thinkAboutBlockOptions.title": "Think About Block Options",
|
111
|
+
"gui.debugModal.thinkAboutBlockOptions.description1": "Is there a similar but different block you can use?",
|
112
|
+
"gui.debugModal.thinkAboutBlockOptions.description2": "Some blocks look similar but can behave differently, such as “set” vs “change” or “play until done” vs “start.”",
|
113
|
+
"gui.debugModal.thinkAboutBlockOptions.description3": "Try using a similar block in place of what you have, and see if this affects the result.",
|
114
|
+
"gui.debugModal.checkTheValues.title": "Check the Values",
|
115
|
+
"gui.debugModal.checkTheValues.description1": "If you are using variables or reporter blocks, check the value at the moment the code sequence is run.",
|
116
|
+
"gui.debugModal.checkTheValues.description2": "Do/should all the sprites control a variable, or should only one sprite have control?",
|
117
|
+
"gui.debugModal.checkTheValues.description3": "Where is the value reset? Where is it changed?",
|
118
|
+
"gui.debugModal.checkCodeSequence.title": "Check Code Sequence",
|
119
|
+
"gui.debugModal.checkCodeSequence.description1": "Check that your code sequence is attached to the correct sprite or the backdrop, if appropriate.",
|
120
|
+
"gui.debugModal.checkCodeSequence.description2": "If you need to move your code to another sprite, click and drag it until you are hovering over the correct sprite. Release it once the sprite wiggles.",
|
121
|
+
"gui.debugModal.checkCodeSequence.description3": "You can also use your Backpack (bottom of screen) to store and move your code or assets.",
|
122
|
+
"gui.debugModal.commentYourCode.title": "Comment Your Code",
|
123
|
+
"gui.debugModal.commentYourCode.description1": "Adding comments to your code can help others looking at your code to understand it. It can also help you remember how your code works when you come back to it later.",
|
124
|
+
"gui.debugModal.commentYourCode.description2": "Right click on script area to “Add Comment.” Use everyday language to explain what a block, or small sequence of blocks, does.",
|
125
|
+
"gui.debugModal.takeABreak.title": "Take a Break, Step Away",
|
126
|
+
"gui.debugModal.takeABreak.description1": "Sometimes, spending too much time focused on an issue can be counterproductive and frustrating.",
|
127
|
+
"gui.debugModal.takeABreak.description2": "Take a break and step away from the screen to clear your mind. After some rest, focusing on something else, or getting some water, you can approach the problem with fresh eyes.",
|
128
|
+
"gui.debugModal.askForHelp.title": "Ask for Help",
|
129
|
+
"gui.debugModal.askForHelp.description1": "If you are still stuck, you can ask for help from a peer. Try finding a debugging/help studio and share your project, asking for help in a comment or the project notes.",
|
130
|
+
"gui.debugModal.askForHelp.description2": "Ask one to three people to try your code, as different people may have different perspectives or solutions!",
|
80
131
|
"gui.gui.shouldDeleteSprite": "Are you sure you want to delete this sprite?",
|
81
132
|
"gui.gui.shouldDeleteCostume": "Are you sure you want to delete this costume?",
|
82
133
|
"gui.gui.shouldDeleteSound": "Are you sure you want to delete this sound?",
|
@@ -279,6 +330,8 @@
|
|
279
330
|
"gui.alerts.cloudInfo": "Please note, cloud variables only support numbers, not letters or symbols. {learnMoreLink}",
|
280
331
|
"gui.alerts.cloudInfoLearnMore": "Learn more.",
|
281
332
|
"gui.alerts.importing": "Importing…",
|
333
|
+
"gui.defaultProject.meow": "Meow",
|
334
|
+
"gui.defaultProject.variable": "my variable",
|
282
335
|
"gui.howtos.intro-move-sayhello-hat.name": "Yeni başlayanlar",
|
283
336
|
"gui.howtos.intro-move.step_stepMove": "Hərəkət bloku əlavə et",
|
284
337
|
"gui.howtos.add-a-move-block.step_stepSay": "Add a say block",
|