Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Contributing a Korean translation

Open
#2,764 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
52/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp
Domain
localization

Research direction

This is an unanswered question thread, not a work item yet: no maintainer has replied on whether a Korean translation is wanted or what conventions apply, so confirm that first before writing strings. Start by locating the existing translation catalogs in the repo (the .ts/.ts-style language files the issue refers to) and see how a recently added language was wired in — registration in the build/resource files and language selection in settings. Done looks like: a Korean catalog exists, compiles with Qt Linguist/lrelease, and shows up selectable in the running application's settings.

Written by the indexing model from the issue text.

Description

Hi, I’d like to contribute a Korean translation of VNote’s interface.

I checked the current translation files and couldn’t find a Korean catalog. Before starting, I’d like to ask:

  1. Is anyone already working on a Korean translation?
  2. Would you accept an initial PR covering the main menus and settings, followed by additional translations?
  3. Are there any preferred conventions or requirements for adding a new language?

I’m planning to use Qt Linguist and check the translations in the running application. Please let me know if there’s a preferred way to proceed.

Thank you.

Dominant language
C++
Stars
13k
Forks
1.3k
Avg merge
1d 22h
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vnotex/vnote

All issues in vnotex/vnote

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.