doc-l10n-kit / quarkus-adoc-po-translator Goto Github PK

Kotlin 100.00%

quarkus-adoc-po-translator's Introduction

doc-l10n-kit

doc-l10n-kit is a set of utilities to translate .asciidoc files.

This project uses Quarkus, the Supersonic Subatomic Java Framework. If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .

Build

Prerequisites

JDK 11
GraalVM (If you want to build a native image directly)
Docker or Podman (If you want to build a native image in a container)

Creating an uber-jar

The application can be packaged using following command:

./gradlew quarkusBuild -Dquarkus.package.type=uber-jar

It produces the doc-l10n-kit-runner.jar file in the build directory.

Configuration

place application.yml to <doc-l10n-kit working directory>/config/application.yml

application.yml

translator:
  deepL:
    apiKey: <put your api key here>
  language:
    source: en   # default source language
    target: ja   # default target language

Execution

machine translate .po file

java -jar doc-l10n-kit-runner.jar po machine-translate --po=<po file path> --source=<source language> --target=<target language>

Apply translation memory to .po file

java -jar doc-l10n-kit-runner.jar po apply-tmx --tmx=<fmx file path> --po=<po file path>

Create a new glossary

java -jar doc-l10n-kit-runner.jar glossary create --name=<name> --source=<source language code> --target=<target language code> <glossary CSV file path>

list glossaries

java -jar doc-l10n-kit-runner.jar glossary list

Delete a glossary

java -jar doc-l10n-kit-runner.jar glossary delete --glossaryId=<glossary id>

quarkus-adoc-po-translator's People

Contributors

Stargazers

Watchers

Forkers

msfm tadayosi

quarkus-adoc-po-translator's Issues

Support Hugo template

As a memo, please support Hugo template style as follows:

# Why Camel?

{{< div "box right" >}}

{{< div "content">}}

## Based on Enterprise Integration Patterns

Camel supports most of the Enterprise Integration Patterns from the excellent book by Gregor Hohpe and Bobby Woolf, and newer integration patterns from microservice architectures to help you solve your integration problem by applying best practices out of the box.

Currently, even with --asciidoctor=false po files are generated like this:

#. type: Title #
#: upstream/content/_index.md:9
#, fuzzy, no-wrap
msgid "Why Camel?"
msgstr "なぜキャメルなのか？"

#. type: Plain text
#: upstream/content/_index.md:12 upstream/content/_index.md:53
#, fuzzy, no-wrap
msgid "{{< div \"box right\" >}}\n"
msgstr ""
"< div \"box right\" >{{}}\n"
"</div>"

#. type: Plain text
#: upstream/content/_index.md:14 upstream/content/_index.md:41
#: upstream/content/_index.md:55 upstream/content/_index.md:80
#, fuzzy, no-wrap
msgid "{{< div \"content\">}}\n"
msgstr ""
"< div \"content\">{{}}\n"
"</div>"

[Security] Workflow ci.yml is using vulnerable action actions/checkout

The workflow ci.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

quoted url is broken

When a text that contains a quoted URL is passed, translator fails to convert properly.

Input:

The site is `http://example.com`

Output:

サイトは `&lt;a href="http://example.com" class="bare"&gt;http://example.com&lt;/a&gt;`

Expected:

サイトは `http://example.com`

image handling

image:graphql-ui-screenshot01.png[alt=GraphQL UI]

should be handled properly.