|
2 | 2 |
|
3 | 3 | [id="prov-overriding-translations_{context}"] |
4 | 4 | = Overriding translations |
5 | | -//In {product-very-short} 1.8, English and French are enabled by default. You can implement translations for other languages by using a JSON file to override the existing translation strings, and by updating the `i18n` section of your `{my-app-config-file}` configuration file to include the JSON translation override file. |
6 | | - |
7 | | -//In {product-very-short} 1.8, English and French are enabled by default. You can implement translations for other languages by adding the language translation strings to a file that overrides the existing translation strings. You must also update the `i18n` section of your `{my-app-config-file}` configuration file to add the new `locale` and your translation override file. |
8 | | - |
9 | | -//In {product-very-short} 1.8, English and French are enabled by default. You can add a translation strings file to your {product-short} deployment that you can use to override the default translation strings, or to implement translations for other languages. |
10 | | - |
11 | 5 | In {product-very-short} 1.8, you can override plugin translation strings without modifying the plugin source code. |
12 | 6 |
|
13 | | - |
14 | 7 | .Prerequisites |
15 | 8 | * You have enabled localization in your {product-very-short} application. |
| 9 | +* For an Operator-installed {product-very-short} instance, you have installed the {openshift-cli}. For more information about installing `oc`, see {ocp-docs-link}/html/cli_tools/openshift-cli-oc#installing-openshift-cli[Installing the OpenShift CLI]. |
16 | 10 |
|
17 | 11 | .Procedure |
18 | 12 | // This feature is not being included in 1.8 |
@@ -58,7 +52,7 @@ oc create configmap all-translations \ |
58 | 52 |
|
59 | 53 | . Update your deployment configuration based on your installation method: |
60 | 54 |
|
61 | | -.. For an Operator-installed {product-very-short} instance, update your `{product-custom-resource-type}` custom resource (CR). For more information about configuring a CR, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html/configuring_red_hat_developer_hub/provisioning-and-using-your-custom-configuration#using-the-operator-to-run-rhdh-with-your-custom-configuration[Using the Red Hat Developer Hub Operator to run Developer Hub with your custom configuration]. |
| 55 | +.. For an Operator-installed {product-very-short} instance, update your `{product-custom-resource-type}` custom resource (CR). For more information about configuring a CR, see link::https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html/configuring_red_hat_developer_hub/provisioning-and-using-your-custom-configuration#using-the-operator-to-run-rhdh-with-your-custom-configuration[Using the Red Hat Developer Hub Operator to run Developer Hub with your custom configuration]. |
62 | 56 | ... In the `spec.application.extraFiles` section, add the translations custom app configuration as shown in the following example: |
63 | 57 | + |
64 | 58 | .{product-custom-resource-type} custom resource fragment |
|
0 commit comments