Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] How can I use custom-dictionary-path option? #9

Open
ysekiy opened this issue Nov 5, 2023 · 0 comments
Open

[Question] How can I use custom-dictionary-path option? #9

ysekiy opened this issue Nov 5, 2023 · 0 comments

Comments

@ysekiy
Copy link

ysekiy commented Nov 5, 2023

Hello all,

Thanks for this awesome work.
How can I use custom-dictionary-path option? Could you post sample custom terminology file or usage?

Expected Behavior

I'd like to use custom terminology. but custom-dictionary-path option seem to be ignored.

e.g)

  • [original (en)] Amazon Bedrock
  • [machine translation (ja)] アマゾン 岩盤
  • [my expectation (ja)] Amazon Bedrock

Actual Behavior

"Amazon Bedrock"(en) was translated to "アマゾン 岩盤"(ja).

Steps to Reproduce the Issue

custom-word.json

{
    "Amazon Bedrock": "Amazon Bedrock"
}

index.md

# Amazon Bedrock Workshop

command

mdt --path index.md --no-hugo --custom-dictionary-path ./custom-word.json

output (index.ja.md)

# アマゾン岩盤工房
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant