Download the PHP package vinou/translations without Composer

On this page you can find all versions of the php package vinou/translations. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Example code of vinou/translations

Informations about the package translations

Vinou - Translations library

The Vinou platform itself depends on this library and therefore it is continuously integrated and right under development. Regarding this the translation files contains work on every period of our platform work.

The following README documents the current status quo of translation definition rules. Regarding the huge amount of language keys and other webprojects that are depending on older coding guidelines the translation files looks sometimes really confusing.

Table of contents

1. Contribution

If you want to contribute, feel free to join and create pull request. We want to be sure that most of depending web projects could easily be updated, therefore it could take some time that your work is added. Feel free to contact us via PN, mail to [email protected] or phone call to +49 61316245390.

2. Coding Guidelines

  1. If A key is used for an array of keys it is always plural, for example countries or wineRegions
  2. If A key identifies an Object or only a String it is always singular, for example wine, product, bundle
  3. All identifiers have to be lowerCamelCase. Hyphens, underscores or other separators are not allowed. In special cases ids may be used when translation represents static database objects like grapeTypes.
  4. If an object is used in more than two other objects, it may be defined under the general object
  5. If an object containes multiple static options the values should be defined in the parent object as array, for example: the product object has a field type with 3 static options, the options should be defined as "types" in object "product".
  6. All keys should be in alpha numerical order, except properties of base objects (see below).

3. Standard object keys

Each object may define certain standard keys shown below in preferred definition order.

key description
name Singular and plural names of an entity
actions Special actions available for this object. Actions may be defined as single string or object of the following form:
actions.[ACTION].main First line of action button in application
actions.[ACTION].sub Second line of action button in application
fields Field indentifiers normally a string directly used as label
fields.[FIELD].label Label for form field if more than a label is defined for a field
fields.[FIELD].placeholder Placeholder for form field
fields.[FIELD].hint Special hint for a form field
fieldSets Form areas to devide fields into seperate sections
views Special defined views like pages, tabs, ...
filters Filter properties used in view, tab oder fieldSet
dialogs Dialog texts regarding this object
toasts Toasts regarding this object. Toast keys shall be defined in past tense for standard toasts or present tense followed by "Error" for error toasts
hints Hints for this object in views, tabs, fieldsets
[xyzTypes] Object related types or categories

4. Object example

5. Twig Extension

This library also contains a Twig extension. To implement this extension you can use this code.

Afterwards you can use the translate filter in your template like this:

Provider

This Library is developed by the Vinou GmbH.

Vinou GmbH
Mombacher Straße 68
55122 Mainz
E-Mail: [email protected]
Phone: +49 6131 6245390

All versions of translations with dependencies

PHP Build Version
Package Version
No informations.
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package vinou/translations contains the following files

Loading the files please wait ....