CatalogWorkspaceService.
generate_localized_workspaces
generate_localized_workspaces(workspace_id: str, to_lang: str, to_locale: str, from_lang: str, translator_func: Callable | None, layout_root_path: Path | None, provision_workspace: bool | None, store_layouts: bool | None, place_in_hierarchy: bool) -> None
Generate layouts of new workspaces based on the source workspace. All texts (titles, ...) will be translated to different languages if requested. Translation YAML files are created for each language containing pairs of source and target texts. If translation is not requested, source and target texts are identical. Users must translate it manually We recommend to translate using a third party service and polish the result manually.
Parameters
| name | type | description |
|---|---|---|
| workspace_id | str | ID of source workspace which we clone and translate all texts in it |
| to_lang | str | ISO lang name (IETF BCP 47) |
| to_locale | str | ISO lang code and country code (IETF BCP 47, e.g. en-US, cs-CZ, ...). Check GoodData documentation for what codes are supported. |
| from_lang | str | from which language we are going to translate |
| translator_func | Callable | None | 3rd party service capable of translating a batch of strings to various languages |
| layout_root_path | Path | None | folder, where to store all layout YAML files (of new translated workspaces)
Also, the translation files are stored there.
if empty, they are stored to:
|
| provision_workspace | bool | None | Should new workspace for the target language be provisioned? Including setting of corresponding locales. |
| store_layouts | bool | None | Store declarative layouts of all workspaces to disk |
| place_in_hierarchy | bool | Flag if localized workspace should be placed in the hierarchy. |
Returns
| type | description |
|---|---|
| None | None |