PHPfox v4 & Language Packs

With v4 having support for Unity, one of the hurdles we had to face was how to create language packages when developers would create and host custom Apps.

Before I continue, I should mention that v4 still supports the old method to create phrases. Nothing has changed in that area, we are simply adding support in Unity for a new method to create and maintain language packages.

Our goal with Unity is to, like the name itself states, unify Apps developed in different languages across multiple platforms, but all supported by one core product. This same concept is being developed for language packages. We will hold the repository of language packages. Translators can create a language package on Unity. They can release it for free, charge a one time fee or monthly fee. Translators can easily manage their language packages from one location. Clients simply need to update their language package core to get new translated phrases. These updated phrases are for our core product.

When it comes to 3rd party Apps, these phrases will automatically be translated. All developers have to use is our M:Markup. An example of M:Markup in action…

{m:phrase Hello World!}

In this example, the phrase is Hello World!. If no phrase is found in Unity for the selected language for a user it displays the default phrase provided by the developer.When a developer creates a new phrase using M:Markup, this updates Unity’s repository as soon as someone visits the App. Translators can then add translations to these new phrases at anytime.

For translators that wish to create a language package that is free, they will be able to accept collaborators on the language package. This new system will open the door to a lot more language packages, delivery will be much faster and developers will not have to worry about having their product translated.