Skip to content

Commit

Permalink
chore(i18n,learn): processed translations (#104)
Browse files Browse the repository at this point in the history
  • Loading branch information
camperbot authored Nov 25, 2024
1 parent 2e9d4bd commit 215644f
Show file tree
Hide file tree
Showing 4,746 changed files with 494,724 additions and 7,207 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ Por ejemplo, `calculate([0,1,2,3,4,5,6,7,8])` debe regresar:

## Dessarrollo

Write your code in `mean_var_std.py`. Para el desarrollo, puedes utilizar `main.py` para probar tu código.
Write your code in `mean_var_std.py`. Para el desarrollo, puedes utilizar `main.py` para probar tu código. In order to run your code, type `python3 main.py` into the GitPod terminal and hit enter. This will cause the included CPython interpreter to run the `main.py` file.

## Pruebas

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ dashedName: step-12

# --description--

Add the words `See more` before the anchor element and `in our gallery` after the anchor element
Add the words `See more` before the anchor element and `in our gallery` after the anchor element.

# --hints--

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,9 @@ dashedName: step-2

# --description--

The <dfn>Fetch API</dfn> is a built-in JavaScript interface to make network requests to a server. It has a `fetch()` method you can use to make `GET`, `POST`, `PUT`, or `PATCH` requests. In this project, you'll make a `GET` request to a URL for a JSON file with information about authors on freeCodeCamp News.
In this project we want data about the authors on freeCodeCamp News. If you want data from an online source, you need use an `API` (Application Programming Interface). An `API` lets people from outside of an organization retrieve its internal data.

There is a method called `fetch` that allows code to receive data from an `API` by sending a `GET` request.

Here is how you can make a `GET` request with the `fetch()` method:

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ function printName() {
button.addEventListener('click', printName);
```

El método `addEventListener` toma dos argumentos. El primero es el evento al que escuchará. (Ej. `'click'`) El segundo es la función de callback, o la función que se ejecuta cuando se activa el evento.
El método `addEventListener` toma dos argumentos. El primero es el evento al que escuchará. (Ex. `'click'`) The second is the callback function, or the function that runs when the event is triggered.

Llama al método `.addEventListener()` en el botón `addEntryButton`. Pass in the string `"click"` for the first argument and the `addEntry` function for the second argument.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Inside the body of the `else if` statement, you will need to call the `showCheck

# --hints--

You should add an `else if` clause to check is the player's `x` position is greater than or equal to the checkpoint's `x` position and less than or equal to the checkpoint's `x` position plus `40`.
You should add an `else if` clause to check if the player's `x` position is greater than or equal to the checkpoint's `x` position and less than or equal to the checkpoint's `x` position plus `40`.

```js
assert.match(code, /if\s*\(\s*index\s*===\s*checkpoints\.length\s*-\s*1\s*\)\s*\{\s*isCheckpointCollisionDetectionActive\s*=\s*false\s*;?\s*showCheckpointScreen\(\s*("|'|`)You reached the final checkpoint!\1\s*\)\s*;?\s*movePlayer\(\s*("|'|`)ArrowRight\2\s*,\s*0\s*,\s*false\s*\)\s*;?\s*\}\s*else\s+if\s*\(\s*player\.position\.x\s*>=\s*checkpoint\.position\.x\s*&&\s*player\.position\.x\s*<=\s*checkpoint\.position\.x\s\+\s*40\s*\)\s*\{\s*/)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ How many composite integers, $n &lt; {10}^8$, have precisely two, not necessaril
`semiPrimes()` should return `17427258`.

```js
assert.strictEqual(euler187(), 17427258);
assert.strictEqual(semiPrimes(), 17427258);
```

# --seed--
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
---
id: 65a3dafe5c945761cef35199
videoId: nLDychdBwUg
title: "Dialogue 4: Chatting About Gadgets"
challengeType: 21
dashedName: dialogue-4-chatting-about-gadgets
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,98 @@
---
id: 671274ffc6d0b8654e13affe
title: Task 1
challengeType: 22
dashedName: task-1
---

<!-- (Audio) Tom: Hey Sophie, have you been working on the screen reader updates recently? -->

# --instructions--

Listen to the audio to complete the sentence below.

# --fillInTheBlank--

## --sentence--

`Hey Sophie, BLANK you BLANK BLANK on the screen reader updates recently?`

## --blanks--

`have`

### --feedback--

This word is used at the beginning of a question in the `Present Perfect Continuous` tense when asking about `you`.

---

`been`

### --feedback--

This word always follows `have` or `has` to form the `Present Perfect Continuous` tense.

---

`working`

### --feedback--

This is the main verb in its `-ing` form, which means actively putting effort or time into completing a task or project.

# --explanation--

The `Present Perfect Continuous` tense is used to describe actions that started in the past and are still happening. It focuses on the duration or continuation of the action. The structure of this tense is `have/has + been + verb(-ing)`. For example:

- `We have been developing a new app for accessibility.` - This means the development started in the past and is still ongoing.

- `He has been fixing bugs in the software for several hours.` - This means he started fixing the bugs earlier and is still working on it.

# --scene--

```json
{
"setup": {
"background": "company2-center.png",
"characters": [
{
"character": "Tom",
"position": {
"x": 50,
"y": 15,
"z": 1.2
},
"opacity": 0
}
],
"audio": {
"filename": "B1_4-1.mp3",
"startTime": 1,
"startTimestamp": 0,
"finishTimestamp": 4.16
}
},
"commands": [
{
"character": "Tom",
"opacity": 1,
"startTime": 0
},
{
"character": "Tom",
"startTime": 1,
"finishTime": 5.16,
"dialogue": {
"text": "Hey, Sophie, have you been working on the screen reader updates recently?",
"align": "center"
}
},
{
"character": "Tom",
"opacity": 0,
"startTime": 5.66
}
]
}
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,142 @@
---
id: 67128f6a3550cf4f98e55f8b
title: "Dialogue 1: Improving Screen Reader Compatibility"
challengeType: 21
dashedName: dialogue-1-improving-screen-reader-compatibility
---

# --description--

Watch the video below to understand the context of the upcoming lessons.

# --assignment--

Watch the video.

# --scene--

```json
{
"setup": {
"background": "company2-center.png",
"characters": [
{
"character": "Tom",
"position": { "x": -25, "y": 0, "z": 1 }
},
{
"character": "Sophie",
"position": { "x": 125, "y": 0, "z": 1 }
}
],
"audio": {
"filename": "B1_4-1.mp3",
"startTime": 1
},
"alwaysShowDialogue": true
},
"commands": [
{
"character": "Tom",
"position": { "x": 25, "y": 0, "z": 1 },
"startTime": 0
},
{
"character": "Sophie",
"position": { "x": 70, "y": 0, "z": 1 },
"startTime": 0.5
},
{
"character": "Tom",
"startTime": 1,
"finishTime": 5.16,
"dialogue": {
"text": "Hey, Sophie, have you been working on the screen reader updates recently?",
"align": "left"
}
},
{
"character": "Sophie",
"startTime": 5.72,
"finishTime": 9.92,
"dialogue": {
"text": "Yes, I started a few months ago. We've been addressing the feedback from our last user survey.",
"align": "right"
}
},
{
"character": "Sophie",
"startTime": 10.14,
"finishTime": 11.56,
"dialogue": {
"text": "How's the design side coming along?",
"align": "right"
}
},
{
"character": "Tom",
"startTime": 11.88,
"finishTime": 15.82,
"dialogue": {
"text": "Pretty well, actually. I've been tweaking the layouts based on the guidelines you shared.",
"align": "left"
}
},
{
"character": "Sophie",
"startTime": 16.36,
"finishTime": 19.08,
"dialogue": {
"text": "That's good to hear. Do you think the users have noticed the improvements?",
"align": "right"
}
},
{
"character": "Tom",
"startTime": 19.5,
"finishTime": 22.36,
"dialogue": {
"text": "I think so. We haven't been receiving as many negative comments.",
"align": "left"
}
},
{
"character": "Sophie",
"startTime": 22.74,
"finishTime": 25.72,
"dialogue": {
"text": "That's a relief. How long do you think we'll need to keep making adjustments?",
"align": "right"
}
},
{
"character": "Tom",
"startTime": 25.72,
"finishTime": 32,
"dialogue": {
"text": "Probably a few more weeks. We've been making steady progress, and I believe we're close to finalizing the major changes.",
"align": "left"
}
},
{
"character": "Sophie",
"startTime": 32.42,
"finishTime": 35.04,
"dialogue": {
"text": "That's good news. It feels great to make our app more accessible.",
"align": "right"
}
},
{
"character": "Sophie",
"position": { "x": 125, "y": 0, "z": 1 },
"startTime": 35.54
},
{
"character": "Tom",
"position": { "x": -25, "y": 0, "z": 1 },
"startTime": 36.04
}
]
}
```
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
---
id: 67164bc464cdc045edaccc5f
title: Task 2
challengeType: 19
dashedName: task-2
---

# --instructions--

This task doesn't have audio. Read the question below and select the correct answer.

# --questions--

## --text--

Which sentence uses the `Present Perfect Continuous` tense correctly?

## --answers--

`Sophie works on the screen reader updates recently.`

### --feedback--

This sentence is in the `Present Simple` tense, not the `Present Perfect Continuous`.

---

`Sophie has been working on the screen reader updates.`

---

`Sophie is working on the screen reader updates.`

### --feedback--

This sentence is in the `Present Continuous`, which describes an action happening right now, not over time.

---

`Sophie worked on the screen reader updates last week.`

### --feedback--

This sentence is in the `Past Simple`, which describes a completed action, not an ongoing one.

## --video-solution--

2

# --explanation--

The `Present Perfect Continuous` tense is used to describe actions that began in the past and are still happening. It is formed using `has/have been + verb(-ing)`.
Loading

0 comments on commit 215644f

Please sign in to comment.