scratch-l10n 5.0.195 → 5.0.197

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.
Files changed (84) hide show
  1. package/CHANGELOG.md +14 -0
  2. package/editor/interface/ab.json +53 -0
  3. package/editor/interface/af.json +53 -0
  4. package/editor/interface/am.json +53 -0
  5. package/editor/interface/an.json +53 -0
  6. package/editor/interface/ar.json +53 -0
  7. package/editor/interface/ast.json +53 -0
  8. package/editor/interface/az.json +53 -0
  9. package/editor/interface/be.json +53 -0
  10. package/editor/interface/bg.json +53 -0
  11. package/editor/interface/bn.json +53 -0
  12. package/editor/interface/ca.json +53 -0
  13. package/editor/interface/ckb.json +53 -0
  14. package/editor/interface/cs.json +53 -0
  15. package/editor/interface/cy.json +53 -0
  16. package/editor/interface/da.json +53 -0
  17. package/editor/interface/de.json +53 -0
  18. package/editor/interface/el.json +53 -0
  19. package/editor/interface/en.json +53 -0
  20. package/editor/interface/eo.json +53 -0
  21. package/editor/interface/es-419.json +53 -0
  22. package/editor/interface/es.json +53 -0
  23. package/editor/interface/et.json +53 -0
  24. package/editor/interface/eu.json +53 -0
  25. package/editor/interface/fa.json +53 -0
  26. package/editor/interface/fi.json +53 -0
  27. package/editor/interface/fil.json +53 -0
  28. package/editor/interface/fr.json +53 -0
  29. package/editor/interface/fy.json +53 -0
  30. package/editor/interface/ga.json +53 -0
  31. package/editor/interface/gd.json +53 -0
  32. package/editor/interface/gl.json +53 -0
  33. package/editor/interface/ha.json +53 -0
  34. package/editor/interface/he.json +53 -0
  35. package/editor/interface/hi.json +53 -0
  36. package/editor/interface/hr.json +53 -0
  37. package/editor/interface/ht.json +53 -0
  38. package/editor/interface/hu.json +53 -0
  39. package/editor/interface/hy.json +53 -0
  40. package/editor/interface/id.json +53 -0
  41. package/editor/interface/is.json +53 -0
  42. package/editor/interface/it.json +53 -0
  43. package/editor/interface/ja-Hira.json +53 -0
  44. package/editor/interface/ja.json +53 -0
  45. package/editor/interface/ka.json +53 -0
  46. package/editor/interface/kk.json +53 -0
  47. package/editor/interface/km.json +53 -0
  48. package/editor/interface/ko.json +53 -0
  49. package/editor/interface/ku.json +53 -0
  50. package/editor/interface/lt.json +53 -0
  51. package/editor/interface/lv.json +53 -0
  52. package/editor/interface/mi.json +53 -0
  53. package/editor/interface/mn.json +53 -0
  54. package/editor/interface/nb.json +53 -0
  55. package/editor/interface/nl.json +53 -0
  56. package/editor/interface/nn.json +53 -0
  57. package/editor/interface/nso.json +53 -0
  58. package/editor/interface/oc.json +53 -0
  59. package/editor/interface/or.json +53 -0
  60. package/editor/interface/pl.json +53 -0
  61. package/editor/interface/pt-br.json +53 -0
  62. package/editor/interface/pt.json +53 -0
  63. package/editor/interface/qu.json +53 -0
  64. package/editor/interface/rap.json +53 -0
  65. package/editor/interface/ro.json +53 -0
  66. package/editor/interface/ru.json +53 -0
  67. package/editor/interface/sk.json +53 -0
  68. package/editor/interface/sl.json +53 -0
  69. package/editor/interface/sr.json +53 -0
  70. package/editor/interface/sv.json +53 -0
  71. package/editor/interface/sw.json +53 -0
  72. package/editor/interface/th.json +53 -0
  73. package/editor/interface/tn.json +53 -0
  74. package/editor/interface/tr.json +53 -0
  75. package/editor/interface/uk.json +53 -0
  76. package/editor/interface/uz.json +53 -0
  77. package/editor/interface/vi.json +53 -0
  78. package/editor/interface/xh.json +53 -0
  79. package/editor/interface/zh-cn.json +53 -0
  80. package/editor/interface/zh-tw.json +53 -0
  81. package/editor/interface/zu.json +53 -0
  82. package/locales/editor-msgs.js +4240 -0
  83. package/locales/interface-msgs.js +4240 -0
  84. package/package.json +2 -2
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": "Betal",
78
78
  "gui.customProcedures.ok": "Baş e",
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": "Ji kerema xwe hişyar be, guherokên ewrê tenê piştgiriya hejmaran dike, piştgiriya herf û sembolan nake. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Zêdetir bizane.",
281
332
  "gui.alerts.importing": "Têxistinî nav dibe...",
333
+ "gui.defaultProject.meow": "Meow",
334
+ "gui.defaultProject.variable": "my variable",
282
335
  "gui.howtos.intro-move-sayhello-hat.name": "Dest pê bike",
283
336
  "gui.howtos.intro-move.step_stepMove": "Blokeke tevgerê tevlî bike",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Add a say block",
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": "Atšaukti",
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": "Atminkite, kad debesų kintamieji palaiko tik skaičius, o ne raides ar simbolius. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Sužinok daugiau.",
281
332
  "gui.alerts.importing": "Importuoti",
333
+ "gui.defaultProject.meow": "Meow",
334
+ "gui.defaultProject.variable": "my variable",
282
335
  "gui.howtos.intro-move-sayhello-hat.name": "Kaip pradėti",
283
336
  "gui.howtos.intro-move.step_stepMove": "Pridėk judėjimo bloką",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Add a say block",
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": "Atcelt",
78
78
  "gui.customProcedures.ok": "Labi",
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": "Lūdzu ievērojiet, ka mākoņmainīgie atbalsta tikai ciparus, nevis burtus vai simbolus. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Uzzināt vairāk.",
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": "Getting Started",
283
336
  "gui.howtos.intro-move.step_stepMove": "Pievieno pārvietošanas bloku",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Add a say block",
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": "Whakakore",
78
78
  "gui.customProcedures.ok": "Ka pai",
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": "Kia mārama koe, ka taea ngā nama anake i ngā taurangi ā-ipurangi, kāore e tautokona ngā pūreta, ngā pūāhua rānei. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Kia ako kōrero anō.",
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": "Hei Tīmatanga",
283
336
  "gui.howtos.intro-move.step_stepMove": "Tāpirihia tetahi Paraka Neke me tētahi Paraka Kī",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Add a say block",
@@ -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": "Add a say block",
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": "Avbryt",
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": "Merk at nettvariabler kan bare lagre tall, ikke bokstaver eller symboler. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Les mer.",
281
332
  "gui.alerts.importing": "Importerer …",
333
+ "gui.defaultProject.meow": "Meow",
334
+ "gui.defaultProject.variable": "my variable",
282
335
  "gui.howtos.intro-move-sayhello-hat.name": "Kom i gang",
283
336
  "gui.howtos.intro-move.step_stepMove": "Legg til en gå-kloss",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Legg til en \"si\"-kloss",
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": " Annuleren",
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": "Let op, cloud variabelen kunnen alleen worden gebruikt voor getallen, niet voor tekst of symbolen. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Meer weten.",
281
332
  "gui.alerts.importing": "Bezig met importeren ...",
333
+ "gui.defaultProject.meow": "Meow",
334
+ "gui.defaultProject.variable": "my variable",
282
335
  "gui.howtos.intro-move-sayhello-hat.name": "Aan de slag",
283
336
  "gui.howtos.intro-move.step_stepMove": "Voeg een bewegingsblok toe",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Voeg een \"zeg\" blok toe",
@@ -77,6 +77,57 @@
77
77
  "gui.customProcedures.cancel": "Avbryt",
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": "Merk at nettvariablar berre støttar tal, ikkje bokstavar eller symbol. {learnMoreLink}",
280
331
  "gui.alerts.cloudInfoLearnMore": "Lær meir.",
281
332
  "gui.alerts.importing": "Importerer …",
333
+ "gui.defaultProject.meow": "Meow",
334
+ "gui.defaultProject.variable": "my variable",
282
335
  "gui.howtos.intro-move-sayhello-hat.name": "Kom i gang",
283
336
  "gui.howtos.intro-move.step_stepMove": "Legg til ein gå-kloss",
284
337
  "gui.howtos.add-a-move-block.step_stepSay": "Legg til ein sei-kloss",