Metadata-Version: 2.1
Name: oarepo-tools
Version: 0.2.2
Summary: OARepo tools
Author-email: Miroslav Simek <miroslav.simek@cesnet.cz>
Description-Content-Type: text/markdown
Requires-Dist: click
Requires-Dist: polib
Requires-Dist: jinja2
Requires-Dist: babel
Requires-Dist: PyYAML
Provides-Extra: dev
Requires-Dist: pytest>=7.1.2; extra == "dev"
Requires-Dist: oarepo-runtime>=1.4.44; extra == "dev"
Requires-Dist: black; extra == "dev"
Requires-Dist: autoflake; extra == "dev"
Requires-Dist: isort; extra == "dev"
Requires-Dist: pytest-docker; extra == "dev"
Requires-Dist: pytest-invenio; extra == "dev"
Provides-Extra: tests
Requires-Dist: pytest>=7.1.2; extra == "tests"
Requires-Dist: oarepo-runtime>=1.4.44; extra == "tests"
Requires-Dist: pytest-mock; extra == "tests"
Requires-Dist: pytest-invenio; extra == "tests"

# oarepo-tools

## Installation

Add `oarepo-tools` to 'dev' dependencies section of your setup.cfg

## Usage

### `make-translations`

To have unified translations across your javascript (+react) and python sources, add the following
configuration to your `setup.cfg`:

```ini
[oarepo.i18n]
# List of language codes for which translations should be managed
languages =
    cs
    en

# List of paths to scan for babel messages - python files and jinja templates are scanned
babel_source_paths =
    oarepo_oaipmh_harvester/oai_harvester
    oarepo_oaipmh_harvester/oai_run
    oarepo_oaipmh_harvester/oai_record
    oarepo_oaipmh_harvester/oai_batch
    oarepo_oaipmh_harvester/ui

# extra message catalogues - if you use oarepo-model-builder to generate models, add the generated
# translations directories here
babel_input_translations =
    oarepo_oaipmh_harvester/oai_harvester/translations
    oarepo_oaipmh_harvester/oai_run/translations
    oarepo_oaipmh_harvester/oai_record/translations
    oarepo_oaipmh_harvester/oai_batch/translations

# List of paths to scan for i18next messages - javascript and jsx files are scanned
i18next_source_paths =
    oarepo_oaipmh_harvester/ui/oai_harvester/theme/assets/semantic-ui/js
    oarepo_oaipmh_harvester/ui/oai_run/theme/assets/semantic-ui/js
    oarepo_oaipmh_harvester/ui/oai_batch/theme/assets/semantic-ui/js
    oarepo_oaipmh_harvester/ui/oai_record/theme/assets/semantic-ui/js

# List of extra i18next message catalogues that should be merged into
i18next_input_translations =
    ui/docs-app/docs_app/theme/assets/semantic-ui/translations/docs_app/messages

# this is the location where python translations are generated.
babel_output_translations =
    oarepo_oaipmh_harvester/translations

# this is the location where javascript translations are generated. Add this directory to webpack
# aliases
i18next_output_translations =
    oarepo_oaipmh_harvester/ui/theme/assets/semantic-ui/translations


[options.entry_points]
# Do not forget to add this directory to your package data and `invenio_i18n.translations` entry point
# - without the 'translations' suffix
invenio_i18n.translations =
    oarepo_oaipmh_harvester = oarepo_oaipmh_harvester

```

To extract translation keys from your sources, run `make-translations` inside your module.
This will generate `po` files inside the `babel_output_translations` directory.

Open the generated `po` files, either with `poedit` or directly, and translate the messages.

Then run `make-translations` again. This will both compile the translations for python sources
and generate the `json` files for javascript sources.
