Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/koreezgames/phaser3-i18n-plugin
Phaser3 i18n Plugin
https://github.com/koreezgames/phaser3-i18n-plugin
game game-development game-engine games i18n i18next internationalization internationalization-plugin localization phaser phaser-plugin phaser3
Last synced: 3 months ago
JSON representation
Phaser3 i18n Plugin
- Host: GitHub
- URL: https://github.com/koreezgames/phaser3-i18n-plugin
- Owner: koreezgames
- License: mit
- Created: 2018-03-07T07:34:06.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2020-05-28T19:12:33.000Z (over 4 years ago)
- Last Synced: 2024-09-23T06:08:13.749Z (4 months ago)
- Topics: game, game-development, game-engine, games, i18n, i18next, internationalization, internationalization-plugin, localization, phaser, phaser-plugin, phaser3
- Language: TypeScript
- Homepage:
- Size: 6.42 MB
- Stars: 22
- Watchers: 5
- Forks: 8
- Open Issues: 23
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Phaser3 i18n Plugin
[](https://github.com/koreezgames/phaser3-i18n-plugin/blob/master/LICENSE)
[](https://travis-ci.org/koreezgames/phaser3-i18n-plugin)
[](https://codebeat.co/projects/github-com-koreezgames-phaser-i18next-master)
[](https://codeclimate.com/github/koreezgames/phaser3-i18n-plugin/test_coverage)
[](https://badge.fury.io/js/%40koreez%2Fphaser3-i18n)
[](https://greenkeeper.io/)
[](https://github.com/prettier/prettier)
Phaser3 i18n is a plugin for Phaser 3 that allows you to have seamless translations in your game. It uses **[i18next](https://github.com/i18next/i18next)** as it's source for translations management, which is widely adopted by the JS community in other projects as well.
Key features:
- Support for translations namespaces
- Simple key/value JSON
- Seamless switching of languages
- No extra function calls for translating strings, directly build into Phaser's Text object
## Getting Started
### Installation
[](https://www.npmjs.com/package/@koreez/phaser3-i18n)
```shell
$ npm i -g npm
$ npm i --save @koreez/phaser3-i18n
```
## Usage
### Import the plugin
```javascript
import { I18nPlugin } from "@koreez/phaser3-i18n";
```
### Load the plugin
You need to load the plugin in your game. This is done just like any other plugin in Phaser 3.
So, to load the plugin, include it in plugins config.
```javascript
const config = {
type: Phaser.AUTO,
parent: "phaser-example",
width: 800,
height: 600,
plugins: {
scene: [
{
key: "i18nPlugin",
plugin: I18nPlugin,
mapping: "i18n"
}
]
},
scene: {
create: create
}
};
```
### Initialize the plugin
After plugin has been loaded you need to initialize it.
```javascript
create () {
this.i18n.initialize(
{
fallbackLng: 'en',
loadPath: 'assets/i18n/{{lng}}/{{ns}}.json',
debug: false,
},
function () {
console.log('I18nPlugin initialized!')
},
)
}
```
The plugin will patch _add.text, add.bitmapText and add.dynamicBitmapText / make.text, make.bitmapText and make.dynamicBitmapText_ methods with additional functionality.
### Create localized texts
```javascript
// x - any
// y - any
// font - bitmap font
// text - should be translation key
// size - font size
// interpolations - interpolation for translation (for example { 0: "value0", 1: "value1" }), note this is not required parameter
this.add.bitmapText(x, y, font, text, size, interpolations);
```
##### **_or via config_**
```javascript
var config = {
x: 100,
y: 100,
text: "translationKey",
font: "atari-classic",
size: 64,
interpolations: { 0: "value0", 1: "value1" }
};
this.make.dynamicBitmapText(config);
```
## Manage translations
When you're all done and set up for translations and have your key value file, next up is starting to translate them. For smaller games this is fairly simple and still manageable by editing your translations in a text file.
But when you start with bigger games and more translations (and translation namespaces) you want to manage your translations better, and maybe even use external translator services.
Two of those service you could use are [locize](https://locize.com/) and/or [Poeditor](https://poeditor.com). Both these services allow you to online edit key value JSON translations that are used in i18next.
The advantage of using such tools is that it's easier to allow external people work on your translations and they aggregate the statistics of your projects (translation completion, languages managed, etc.)
## Credits
Big thanks to this great repo:
https://github.com/orange-games/phaser-i18next
## License
[MIT](LICENSE)