Skip to content
This repository was archived by the owner on Jan 16, 2024. It is now read-only.

Commit 97790d9

Browse files
authored
New Crowdin updates (#442)
* New translations installation.md (Spanish) * New translations installation.md (Greek) * New translations installation.md (Russian) * New translations installation.md (Turkish) * New translations installation.md (Ukrainian) * New translations installation.md (Chinese Simplified)
1 parent a39284b commit 97790d9

File tree

6 files changed

+12
-12
lines changed

6 files changed

+12
-12
lines changed

Diff for: el-gr/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -76,15 +76,15 @@ The PHAR isn't available before 0.11.4, so if you need an older version, you can
7676
#### Global Composer Application
7777

7878
```bash
79-
composer global require zephir-lang/zephir
79+
composer global require phalcon/zephir
8080
```
8181

8282
There are two approaches to running Zephir at this point. The first is to ensure that `${COMPOSER_HOME}/vendor/bin` is in your `$PATH`, then Zephir should be available as `zephir` on the command line. The second is to simply use `composer global exec zephir` instead.
8383

8484
#### Project Dependency
8585

8686
```bash
87-
composer require zephir-lang/zephir
87+
composer require phalcon/zephir
8888
```
8989

9090
Use `composer exec zephir` within the project you installed Zephir in, above, to run it. (Alternately, you can still run `vendor/bin/zephir`.)

Diff for: es-es/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -76,15 +76,15 @@ The PHAR isn't available before 0.11.4, so if you need an older version, you can
7676
#### Global Composer Application
7777

7878
```bash
79-
composer global require zephir-lang/zephir
79+
composer global require phalcon/zephir
8080
```
8181

8282
There are two approaches to running Zephir at this point. The first is to ensure that `${COMPOSER_HOME}/vendor/bin` is in your `$PATH`, then Zephir should be available as `zephir` on the command line. The second is to simply use `composer global exec zephir` instead.
8383

8484
#### Project Dependency
8585

8686
```bash
87-
composer require zephir-lang/zephir
87+
composer require phalcon/zephir
8888
```
8989

9090
Use `composer exec zephir` within the project you installed Zephir in, above, to run it. (Alternately, you can still run `vendor/bin/zephir`.)

Diff for: ru-ru/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -76,15 +76,15 @@ The PHAR isn't available before 0.11.4, so if you need an older version, you can
7676
#### Global Composer Application
7777

7878
```bash
79-
composer global require zephir-lang/zephir
79+
composer global require phalcon/zephir
8080
```
8181

8282
There are two approaches to running Zephir at this point. The first is to ensure that `${COMPOSER_HOME}/vendor/bin` is in your `$PATH`, then Zephir should be available as `zephir` on the command line. The second is to simply use `composer global exec zephir` instead.
8383

8484
#### Project Dependency
8585

8686
```bash
87-
composer require zephir-lang/zephir
87+
composer require phalcon/zephir
8888
```
8989

9090
Для запуска Zephir используйте команду `composer exec zephir` в проекте с установленым Zephir как показано выше. (Alternately, you can still run `vendor/bin/zephir`.)

Diff for: tr-tr/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -76,15 +76,15 @@ The PHAR isn't available before 0.11.4, so if you need an older version, you can
7676
#### Global Composer Application
7777

7878
```bash
79-
composer global require zephir-lang/zephir
79+
composer global require phalcon/zephir
8080
```
8181

8282
There are two approaches to running Zephir at this point. The first is to ensure that `${COMPOSER_HOME}/vendor/bin` is in your `$PATH`, then Zephir should be available as `zephir` on the command line. The second is to simply use `composer global exec zephir` instead.
8383

8484
#### Project Dependency
8585

8686
```bash
87-
composer require zephir-lang/zephir
87+
composer require phalcon/zephir
8888
```
8989

9090
Use `composer exec zephir` within the project you installed Zephir in, above, to run it. (Alternately, you can still run `vendor/bin/zephir`.)

Diff for: uk-ua/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -76,15 +76,15 @@ PHAR не доступний до версії 0.11.4, тому якщо вам
7676
#### Composer як глобальна програма
7777

7878
```bash
79-
composer global require zephir-lang/zephir
79+
composer global require phalcon/zephir
8080
```
8181

8282
На даний момент існує два підходи до запуску Zephir. Перший, переконайтеся, що `${COMPOSER_HOME}/vendor/bin` знаходиться у вашому `$PATH`, Zephir повинен бути доступний в командному рядку за допомогою команди `zephir`. Другий, замість цього можна використовувати команду `composer global exec zephir`.
8383

8484
#### Залежність проекту
8585

8686
```bash
87-
composer require zephir-lang/zephir
87+
composer require phalcon/zephir
8888
```
8989

9090
Для запуску Zephir використовуйте команду `composer exec zephir` в проекті з встановленим Zephir як показано вище. (Крім того, як альтернативу ви можете запустити `vendor/bin/zephir`

Diff for: zh-cn/installation.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -80,15 +80,15 @@ version: '0.12'
8080
#### Global Composer Application
8181

8282
```bash
83-
composer global require zephir-lang/zephir
83+
composer global require phalcon/zephir
8484
```
8585

8686
There are two approaches to running Zephir at this point. The first is to ensure that `${COMPOSER_HOME}/vendor/bin` is in your `$PATH`, then Zephir should be available as `zephir` on the command line. The second is to simply use `composer global exec zephir` instead.
8787

8888
#### Project Dependency
8989

9090
```bash
91-
composer require zephir-lang/zephir
91+
composer require phalcon/zephir
9292
```
9393

9494
Use `composer exec zephir` within the project you installed Zephir in, above, to run it. (Alternately, you can still run `vendor/bin/zephir`.)

0 commit comments

Comments
 (0)