Download the PHP package hyperdigital/hd_translator without Composer

On this page you can find all versions of the php package hyperdigital/hd_translator. 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 hyperdigital/hd_translator

Informations about the package hd_translator

Translator

TYPO3 extension for handling translations. It allows editors to edit static strings from XLF files (usually placed in EXT:/Resources/Private/Languages) or to export database entries, edit them over translation tool/agency in the xlf format and then import it again back to TYPO3.

Changelog

2.0.0

Initialization

Upon installation, a new submodule will be added under the WEB module. Before utilizing the extension's features, it is essential to specify the location where new translations should be stored. Follow these steps:

  1. Navigate to the Extension Configuration section.
  2. Look for the "Storage path (from the root of the project)" option within the HD Translator settings. When inserting a relative path in this field, consider that starting point is the project root, where your project's composer.json is stored.

Static Strings Translations

Previews

All locallang files categories

All locallangs for category

Example of german translation for one locallang

Specific locallang files

A key feature of this extension lies in its ability to work seamlessly with locallang.xlf files. To enable the handling of specific locallang.xlf files, follow these steps:

  1. Open the ext_localconf.php file in your TYPO3 extension.

  2. Add the following configuration to register the desired locallang.xlf file (the unique_key must be always unique):

    • label: Provide a descriptive label for the set of translations.
    • path: Specify the path to the target locallang.xlf file within your extension.
    • category: Categorize the translations under a specific category.
    • languages: Define the supported languages for the translations.

Ensure that the provided path is correct and corresponds to the actual location of your locallang.xlf file. You can extend the 'languages' array to include additional language codes as required.

Synchronizing All locallang.xlf Files

The system has the capability to retrieve all accessible locallang.xlf files across all extensions, making translation management more efficient. Follow these steps to synchronize the files:

  1. In the extension configuration, locate and check the checkbox labeled "All locallang.xlf files."

  2. Navigate to the Translator module within the TYPO3 backend.

  3. Find the "Synchronize all files" button and click on it.

This action generates settings for all the locallang.xlf files, ensuring that the system is aware of and can handle translations from every extension. If you add a new translation file or introduce a new extension, it's essential to click the "Synchronize all files" button again. This process updates the system settings accordingly.

By utilizing this feature, you streamline the management of translations across your TYPO3 project, ensuring that the Translator module is aware of all relevant translation files and extensions.

Correct Language Configuration

To define the correct language for your TYPO3 site, you can specify it within the site configuration file located at config/sites/xxx/config.yaml. Here's an example configuration:

Enable New Language not Supported by TYPO3

To enable a new language not supported by TYPO3, add the following code to either LocalConfiguration.php or AdditionalConfiguration.php. Ensure that this code appears before all extensions are loaded:

Important Components:

Translation Removal and Backup

When you remove a translation, the system automatically creates a backup of the deleted translation. If you attempt to create the same translation again, you will be prompted with an option to either restore the backup or generate a new translation from scratch.

Database Export

The extension provides a flexible mechanism for exporting fields from the database, allowing you to tailor the exported data based on your needs.

Default Export Settings

The default list of exported fields from the database is located in the same section as the "Show Fields" configuration. It follows the same "type" logic. If this setting is empty, all accessible non-TYPO3 core fields will be included in the export.

Different Settings for Different Table Types

In many cases, you may find it necessary to have distinct settings for various content elements. For instance, you might want specific export configurations for a Content Element of type 'Header' as opposed to a 'Text' element. To achieve this level of granularity, utilize the type-specific settings. Here's an example for 'Header' and 'Text' elements within the tt_content table:

Header Content Element
Text Content Element

Exporting Flexform Fields

When the Flexform is included in the export, it retrieves all fields by default. However, you can limit the exported fields similar to the entire table. Use the following configuration:

Displaying Export Buttons

Export buttons will appear next to the save or edit buttons when editing a table entry or within the Page module. It's also a part of context menues.

Customize the export settings according to your specific requirements to ensure that only the necessary data is included in the exported file.

All versions of hd_translator with dependencies

PHP Build Version
Package Version
Requires typo3/cms-core Version >=13.0 <13.99
phpoffice/phpspreadsheet Version 1.*
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 hyperdigital/hd_translator contains the following files

Loading the files please wait ....