Skip to content

Commit eee35a4

Browse files
dabrtmnocon
authored andcommitted
Implement reviewer comments
1 parent 9c835d9 commit eee35a4

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

docs/multisite/languages/automated_translations.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,11 @@ description: With the automated translation add-on, users can translate content
77
The automated translation add-on package allows users have content items machine-translated into multiple languages by using either Google Translate or DeepL external translation engine.
88
The package integrates with [[= product_name =]], and allows users to [request from the UI]([[= user_doc =]]/content_management/translate_content.md#add-translations) that a content item is translated.
99
However, you can also run an API command to translate a specific content item.
10-
Either way, as a result, a new version of the content item is created with [translatable fields](languages.md#translatable-and-untranslatable-fields) of the following types translated into a target language:
10+
Either way, as a result, a new version of the content item is created, with the following elements translated into a target language:
1111

12-
- in pages: [TextBlock](../../content_management/field_types/field_type_reference//textblockfield.md) and [RichText](../../content_management/field_types/field_type_reference//richtextfield.md)
13-
- in other content types: [TextLine](../../content_management/field_types/field_type_reference//textlinefield.md) and RichText
12+
13+
- for pages: blocks that have the `text` or `richtext` [block attributes](../../content_management/pages/page_block_attributes/#block-attribute-types)
14+
- for other content types: Fields of the [TextLine](../../content_management/field_types/field_type_reference//textlinefield.md) and [RichText](../../content_management/field_types/field_type_reference//richtextfield.md) type
1415

1516
!!! note "DeepL limitations"
1617

@@ -28,8 +29,8 @@ composer require ibexa/automated-translation
2829

2930
!!! caution "Modify the default configuration"
3031

31-
Flex installs and activates the package.
32-
However, you must modify the `bundles.php` file to change the template loading order:
32+
Symfony Flex installs and activates the package.
33+
However, you must modify the `config/bundles.php` file to change the template loading order:
3334

3435
```php
3536
<?php
@@ -65,7 +66,7 @@ ibexa_automated_translation:
6566
6667
The configuration is SiteAccess-aware, therefore, you can configure different engines to be used for different sites.
6768
68-
## Translate content items with API
69+
## Translate content items with CLI
6970
7071
To create a machine translation of a specific content item, run the following command:
7172
@@ -80,6 +81,6 @@ You would do it, for example, when a new service emerges on the market, or your
8081

8182
To add a custom engine to a list of available translation services, do the following:
8283

83-
- create a service that implements ` Ibexa\AutomatedTranslation\Client\ClientInterface`
84-
- implement the `translate` method
85-
- in `services.yaml` file, tag the service as `ibexa.automated_translation.client`
84+
1. Create a service that implements ` Ibexa\AutomatedTranslation\Client\ClientInterface`
85+
1. Implement the `translate` method
86+
1. In `services.yaml` file, tag the service as `ibexa.automated_translation.client`

0 commit comments

Comments
 (0)