NAME
xlate - translate CLI front-end for App::Greple::xlate module
SYNOPSIS
xlate [ options ] -t lang file [ greple options ]
-h help
-v show version
-d debug
-n dry-run
-a use API
-c just check translation area
-r refresh cache
-u force update cache
-s silent mode
-e # translation engine (*deepl, gpt3, gpt4, gpt4o)
-p # pattern to determine translation area
-x # file containing mask patterns
-w # wrap line by # width
-o # output format (*xtxt, cm, ifdef, space, space+, colon)
-f # from lang (ignored)
-t # to lang (required, no default)
-m # max length per API call
-l # show library files (XLATE.mk, xlate.el)
-- terminate option parsing
N.B. default is marked as *
Make options
-M run make
-n dry-run
Docker options
-G mount git top-level directory
-R mount read-only
-U do not mount
-B run in non-interactive (batch) mode
-E # specify environment variable to be inherited
-I # docker image or version (default: tecolicom/xlate:version)
# -V # specify directory to be mounted (default: current directory)
-D * run xlate on the container with the rest parameters
-C * run following command on the container, or run shell
N.B. -D/-C terminates option parsing
Control Files:
*.LANG translation languates
*.FORMAT translation foramt (xtxt, cm, ifdef, colon, space)
*.ENGINE translation engine (deepl, gpt3, gpt4, gpt4o)
# marked as # options are experimental
VERSION
Version 0.42
DESCRIPTION
XLATE is a versatile command-line tool designed as a user-friendly frontend for the greple -Mxlate
module, simplifying the process of multilingual automatic translation using various API services. It streamlines the interaction with the underlying module, making it easier for users to handle diverse translation needs across multiple file formats and languages.
A key feature of xlate is its seamless integration with Docker environments, allowing users to quickly set up and use the tool without complex environment configurations. This Docker support ensures consistency across different systems and simplifies deployment, benefiting both individual users and teams working on translation projects.
xlate supports various document formats, including .docx
, .pptx
, and .md
files, and offers multiple output formats to suit different requirements. By combining Docker capabilities with built-in make functionality, xlate enables powerful automation of translation workflows. This combination facilitates efficient batch processing of multiple files, streamlined project management, and easy integration into continuous integration/continuous deployment (CI/CD) pipelines, significantly enhancing productivity in large-scale localization efforts.
Basic Usage
To translate a file, use the following command:
xlate -t <target_language> <file>
For example, to translate a file from English to Japanese:
xlate -t JA example.txt
Translation Engines
xlate supports multiple translation engines. Use the -e option to specify the engine:
xlate -e deepl -t JA example.txt
Available engines: deepl, gpt3, gpt4, gpt4o
Output Formats
Various output formats are supported. Use the -o option to specify the format:
xlate -o cm -t JA example.txt
Available formats: xtxt, cm, ifdef, space, space+, colon
Docker Support
xlate offers seamless integration with Docker, providing a powerful and flexible environment for translation tasks. This approach combines the strengths of xlate's translation capabilities with Docker's containerization benefits.
Key Concepts
- Containerized Environment
-
By running xlate in a Docker container, you ensure a consistent and isolated environment for all translation tasks. This eliminates issues related to system dependencies or conflicting software versions.
- Integration with Make
-
The Docker functionality can be combined with xlate's make feature, allowing for complex, multi-file translation projects to be managed efficiently within a containerized environment. For example:
xlate -DM -t 'EN FR DE' project_files/*.docx
This command runs xlate in a Docker container, utilizing make to process multiple files with specified target languages.
- Flexible Mount Options
-
xlate provides options to mount different directories, including Git repositories (
-G
) and read-only mounts (-R
). This allows for flexible workflow integration while maintaining data security. - Environment Variable Handling
-
With the ability to pass specific environment variables into the container (
-E
), you can easily manage API keys and other configuration settings without modifying the container itself. - Interactive and Batch Modes
-
xlate supports both interactive (
-C
) and non-interactive (-B
) modes when running in Docker, catering to different use cases from development to automated processing.
Make Support
xlate utilizes GNU Make for automating and managing translation tasks. This feature is particularly useful for handling translations of multiple files or to different languages.
To use the make feature:
xlate -M [options] [target]
xlate provides a specialized Makefile (XLATE.mk) that defines translation tasks and rules. This file is located in the xlate library directory and is automatically used when the -M option is specified.
Example usage:
xlate -M -t 'EN FR DE' document.docx
This command will use make to translate document.docx to English, French, and German, following the rules defined in XLATE.mk.
The -n
option can be used with -M
for a dry-run, showing what actions would be taken without actually performing the translations:
xlate -M -n -t 'EN FR DE' document.docx
Users can customize the translation process using parameter files:
- *.LANG:
-
Specifies target languages for a specific file
- *.FORMAT:
-
Defines output formats for a specific file
- *.ENGINE:
-
Selects the translation engine for a specific file
For more detailed information on the make functionality and available rules, refer to the XLATE.mk file in the xlate library directory.
OPTIONS
- -h
-
Show help message.
- -v
-
Show version information.
- -d
-
Enable debug mode.
- -n
-
Perform a dry-run without making any changes.
- -a
-
Use API for translation.
- -c
-
Check translation area without performing translation.
- -r
-
Refresh the translation cache.
- -u
-
Force update of the translation cache.
- -s
-
Run in silent mode.
- -e engine
-
Specify the translation engine to use.
- -p pattern
-
Specify a pattern to determine the translation area.
- -x file
-
Specify a file containing mask patterns.
- -w width
-
Wrap lines at the specified width.
- -o format
-
Specify the output format.
- -f lang
-
Specify the source language (currently ignored).
- -t lang
-
Specify the target language (required).
- -m length
-
Specify the maximum length per API call.
- -l file
-
Show library files (XLATE.mk, xlate.el).
MAKE OPTIONS
DOCKER OPTIONS
Docker feature is invoked by the -D or -C option. These are exclusive, so only one of them can be used. Also, once these two options appear, subsequent options are not interpreted, so they should always be specified last.
- -G
-
Mount git(1) top-level directory when running in Docker.
- -R
-
Mount directory as read-only in Docker.
- -U
-
Do not mount any directory.
- -B
-
Run in non-interactive (batch) mode in Docker.
- -E var
-
Specify environment variable to be inherited in Docker.
- -I image
-
Specify Docker image or version.
- -D
-
Run xlate on the Docker container with the rest of the parameters.
- -C
-
Run the following command on the Docker container, or run a shell if no command is provided.
ENVIRONMENT
- DEEPL_AUTH_KEY
-
Authentication key for DeepL API.
- OPENAI_API_KEY
-
API key for OpenAI (used for GPT-based engines).
FILES
- *.LANG
-
Specifies translation languages.
- *.FORMAT
-
Specifies translation format.
- *.ENGINE
-
Specifies translation engine.
EXAMPLES
1. Translate a Word document to English:
xlate -DMa -t EN-US example.docx
2. Translate to multiple languages and formats:
xlate -M -o 'xtxt ifdef' -t 'EN-US KO ZH' example.docx
3. Run a command in Docker container:
xlate -C sdif -V --nocdif example.EN-US.cm | less
4. Translate without using API (via clipboard):
xlate -t JA README.md
SEE ALSO
AUTHOR
Kazumasa Utashiro
LICENSE
Copyright © 2023-2024 Kazumasa Utashiro.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.