Download the PHP package sagittariusx/beluga.translation without Composer
On this page you can find all versions of the php package sagittariusx/beluga.translation. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sagittariusx/beluga.translation
More information about sagittariusx/beluga.translation
Files in sagittariusx/beluga.translation
Package beluga.translation
Short Description A PHP translation/localization library
License LGPLv3
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package beluga.translation
Beluga.Translation
A PHP translation/localization library
Installation
Install it via
or inside the composer.json:
Usage
If you want to use this package inside you're application include the depending composer autoload.php
First step, the Locale
Create a new Locale instance
This creates the new Locale by checking the following places to get the required information
- First The current URL part is checked, if it contains an valid locale string, it is used (you can disable it by setting the 2nd Create parameter to FALSE.
- Next it checks if one of the defined request parameters (3rd parameter) is defined by $_POST, $_GET or $_SESSION
- After that it is checked if the browser sends some information about the preferred locale/language.
- Finally it is checked if the system gives usable locale information.
If all this methods fail, the declared fall back locale is returned. You can also call it main locale.
Last but not least the created locale is registered as global available Locale instance. It can be accessed from other places by:
Inside you app or lib
For example if you have an class that requires Localization
