Download the PHP package phil/translation-bundle without Composer

On this page you can find all versions of the php package phil/translation-bundle. 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?

Informations about the package translation-bundle

phil/translation-bundle

A translation screen for Symfony: segments that survive edits, a memory that remembers, a glossary that checks.

phil/translation-bundle brings phil/translation-memory into a Symfony application. A document written in blocks — a document in UJO (Universal JSON Output), the block document format of phil/ujo — is cut into segments kept in Doctrine, one row per segment and target language, with its state from untranslated to reviewed. When the author edits the source, the segments are brought up to date: the unchanged ones keep their translation, those that moved take it with them, those that changed become stale. Translators work on a screen that shows each segment with what the translation memory proposes, the glossary's terms and issues, the quality checks, what changed under a stale target, and its comments; they can export the document as XLIFF 2.1 for a translation tool, and import XLIFF 2.x or 1.2 back. A regional variant such as fr-CA is read through its parent: only the segments that differ in Canada are translated again. Machine translation proposes targets behind a port, off by default and marked as such, and translators are thanked with a public credit.

It is for Symfony applications that publish what people write in more than one language: articles, pages, rules, books. The memory and the glossaries are shared by every document of the application, so a sentence translated once is proposed everywhere and a term is translated the same way throughout. It translates UJO documents only: the message catalogues of an application's interface stay with Symfony's translation component and its tools.

It is a bundle built on the library; it requires Doctrine ORM, Twig and Symfony's HTTP and routing components. The application keeps the documents: it names them to the bundle through a SourceDocuments service, says who may translate and review through a TranslationPolicy, and publishes the translated document the bundle puts together. Until both services are configured, the screen answers 404.

The design follows the layers of the monorepo: Domain holds the rows — SegmentRecord, MemoryRecord, TermRecord, CommentRecord — and the ports of their stores; Application holds Translations, Glossaries, Comments, Progress and the application's ports — SourceDocuments, TranslationPolicy, Translators, MachineTranslator; Infrastructure holds the Doctrine and in-memory stores, the controllers and their routes, the Twig function of the credits, the EasyAdmin links, and the service wiring.

Status

Part State
Segments in Doctrine, prepared from a UJO document and brought up to date when the source changes Implemented and tested
Exact matches of the memory proposed to new segments Implemented and tested
Translate, propose, review, confirm and clear a segment; usable targets learnt by the memory Implemented and tested
Translation memory and glossaries in Doctrine, shared by every document Implemented and tested
XLIFF 2.1 export, XLIFF 2.x and 1.2 import with a report Implemented and tested
The translated document put together from usable segments Implemented and tested
Translation screen in Twig: segments, matches, terms, issues, changes, forms, export and import Implemented and tested
Regional variants read through their parent, fr-CA and en-CA by default; translated and raw readings Implemented and tested
Quality checks on the screen, dismissed per segment by a flag kept with its row Implemented and tested
One target per segment and comments on segments, signed by the current user Implemented and tested
Who wrote and reviewed each target; a public credit of the translators, in Twig Implemented and tested
Glossary pages through Glossaries, inflected forms, TBX export and import, EasyAdmin links Implemented and tested
Machine translation behind a port with named adapters, off by default, marked as machine output Implemented and tested

Documentation

Document What it covers
Installation Requirements, registering the bundle, the tables and the routes.
Configuration Every option of phil_translation.
Translating documents Translations: preparing, the actions on a segment, progress, XLIFF, the translated document.
The translation screen The routes, what the page shows, the forms, the application's services, the layout.
Memory and glossaries The shared memory, Glossaries, and how both reach the screen.
Regional variants The chain from fr-CA to fr to the source, the translated and raw readings.
Comments and credits One target per segment, comments, who did what, the public credit, Translators.
Glossary pages Editing glossaries on screen, TBX, EasyAdmin links, inflected forms.
Machine translation The port, the adapters, proposals marked as machine output.
Storage The three tables, their keys, and the stores in memory.
Exceptions What the bundle throws, and what the screen answers.
Extension points What an application implements, configures, replaces or relies on.
Testing The bundle's tests, and how to test an application that uses it.
Reference Every type of the bundle, with its role.

Quick start

The screen of an article is then /admin/translate/article:42/fr, and its French version is put together by:

Requirements

PHP 8.5 or later, Symfony 8.2, Doctrine ORM 3.7, Twig 3.21, phil/translation-memory and phil/ujo.

Contributing

Contributions are welcome on the PHIL monorepo: read the contribution guide and the security policy explains, never in a public issue.

License

MIT, © Philippe Gamache, doing business as Le Gnome Archiviste; a Parler Haut Interagir Librement project. See LICENSE.


All versions of translation-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=8.5
ext-mbstring Version *
doctrine/orm Version ^3.7
phil/translation-memory Version ^0.1@dev
phil/ujo Version ^0.1@dev
psr/clock Version ^1.0
symfony/config Version ^8.2
symfony/dependency-injection Version ^8.2
symfony/http-foundation Version ^8.2
symfony/http-kernel Version ^8.2
symfony/routing Version ^8.2
symfony/security-csrf Version ^8.2
twig/twig Version ^3.21
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 phil/translation-bundle contains the following files

Loading the files please wait ...