Translate markdown files using OpenAI ChatGPT, and generate localized copies of each file.
pip install mdgpt
Set environment variable OPENAI_API_KEY
or create it in a .env
file
export OPENAI_API_KEY=YOUR_API_KEY
Download example prompts:
curl -o example.yaml https://raw.githubusercontent.com/Djarnis/mdGPT/main/prompts.yaml
Use the example WEBSITE_BUILDER
option from the prompts to build some example files;
mdgpt build example
Translate these newly created markdown files into Finish (fi) versions:
mdgpt translate example --target fi
or Danish (da):
mdgpt translate example --target da
or German (de):
mdgpt translate example --target de
Or whatever. Just make sure it is an ISO 639-1 two-letter language code, and all should be fine.
Adjust the example.yaml
prompts to suit your needs.
You can change the MODEL
to any engine supported by OpenAI, change the default temperature, and adjust max tokens.
Default values are:
MODEL:
temperature: 0.2
engine: gpt-3.5-turbo
max_tokens: 2048
This option is used for building mark down documents, given the example instructions below:
WEBSITE_BUILDER:
variables:
title: the fictive product "AI Markdown Translator"
tone: sarcastic passive aggressive
year_founded: 2019
major_milestones: 3
system_prompt: |
Only reply in valid markdown with frontmatter.
No explanations. No notes.
Language: {lang[name]}
Markdown Document:
---
# Frontmatter attributes:
title: Title of webpage
description: Short meta description
---
<!-- markdown content -->
# This will be appended as a last line to all step prompts
user_suffix: |
Respond in valid markdown format including all provided frontmatter attributes.
It should be in a {tone} tone.
steps:
- prompt: |
Write the homepage content for {title} in {lang_name} ({lang_code}).
destination: index.md
- prompt: |
Write the "About Us" page content for a fictive team behind {title} in {lang_name} ({lang_code}).
destination: about.md
- prompt: |
Write the history for {title} in {lang_name} ({lang_code}), starting in {year_founded} with {major_milestones} major milestones.
destination: history.md
- prompt: |
Write a contact page for {title} in {lang_name} ({lang_code}). Make the headquarter be at some fancy addres in Silicon Valley.
destination: contact.md
This prompt is used when translating file paths.
URL_PROMPT:
- role: system
prompt: |
Only reply in valid json.
No explanations. No notes.
Language: {lang_name}
JSON document:
{content}
- role: user
prompt: |
Translate all keys in the JSON document.
The keys are in {lang_name} ({lang_code}).
They are url paths for a website in {lang_name}.
I need you to fill out the missing values with a translated {target_lang[name]} ({target_lang_code}) version.
Should contain no special characters (hyphens and slashes are ok, as are dots in file extensions (like .md) if any).
Respond in the same format as the JSON input given, with the `key` as the json key and the (translated) `value` as the value.
Example translating from English to Danish:
"about-us.md": "om-os.md"
This prompt is used when translating markdown files.
MARKDOWN_PROMPT:
- role: system
prompt: |
Only reply in valid markdown with frontmatter.
No explanations. No notes.
Language: {lang_name}
Markdown Document:
---
# Frontmatter can be anything or nothing, but always make sure to include the frontmatter dashes.
{frontmatter}
---
{content}
- role: user
prompt: |
Translate all given values from {lang_name} ({lang_code}) to {target_lang[name]} ({target_lang_code}).
Respond in valid markdown format.
Optional boolean value, if you only want index.md
files translated when translating URL's.
ONLY_INDEXES: True
Optional list of frontmatter keys you want to translate.
Per default, all keys will be translated, but you can define selected ones here.
FIELD_KEYS:
- title
- description
- keywords
- heading
- teaser
List of languages you want to target.
TARGET_LANGUAGES:
- da
- de
- fr
- es
- it
- zh
You can run translations on all target languages by not specifying --target
.
mdgpt translate example
On Unix-based systems like Linux and MacOS, you can install Poetry by using the following command in your terminal:
curl -sSL https://install.python-poetry.org | python -
On Windows, you can use PowerShell to install Poetry with the following command:
(Invoke-WebRequest -Uri https://install.python-poetry.org -UseBasicParsing).Content | python -
You can check if Poetry was installed correctly by running:
poetry --version
In your project directory, you have a file named .env.tpl which serves as a template for environment variables. To use this file, you should rename it to .env.
On Unix-based systems, use the following command:
mv .env.tpl .env
On Windows, use the following command:
rename .env.tpl .env
Open your .env file in a text editor. You should see a line that looks something like this:
OPENAI_API_KEY=
After the equal sign, add your OpenAI API key in quotes. It should look something like this:
OPENAI_API_KEY="your-api-key-goes-here"
Save the .env file and close it.
Please note:
- Make sure to replace "your-api-key-goes-here" with your actual OpenAI API key.
- Do not share your .env file or post it online, as it contains sensitive information.
From the project directory, build and install mdGPT and its dependencies:
poetry build
poetry install
This installs mdGPT and all its dependencies, and you can now follow the example below.
The example website (./example/en) was created using the WEBSITE_BUILDER
option included in the prompts.yaml file.
poetry run mdgpt build example
Which will create these files in the ./example/en directory:
- index.md
- about.md
- contact.md
- history.md
To translate the markdown files into Finish (fi) versions, run this command:
poetry run mdgpt translate example --target fi
And you should get a /fi
subdirectory ./example/fi/ containing these files, translated from their original English (en) source:
- index.md
- tietoja.md
- yhteystiedot.md
- historia.md