kicad/kicad-i18n

Translations for KiCad source code [moved to https://gitlab.com/kicad]

KiCad README

For specific documentation about building KiCad, policies and guidelines, and source code documentation see the Developer Documentation website.

You may also take a look into the Wiki, the contribution guide.

For general information about KiCad and information about contributing to the documentation and libraries, see our Website and our Forum.

Build state

KiCad uses a host of CI resources.

GitLab CI pipeline status can be viewed for Linux and Windows builds of the latest commits.

Release status

Files

• AUTHORS.txt - The authors, contributors, document writers and translators list
• CMakeLists.txt - Main CMAKE build tool script
• copyright.h - A very short copy of the GNU General Public License to be included in new source files
• Doxyfile - Doxygen config file for KiCad
• INSTALL.txt - The release (binary) installation instructions
• uncrustify.cfg - Uncrustify config file for uncrustify sources formatting tool
• _clang-format - clang config file for clang-format sources formatting tool

Subdirectories

• 3d-viewer - Sourcecode of the 3D viewer
• bitmap2component - Sourcecode of the bitmap to PCB artwork converter
• cmake - Modules for the CMAKE build tool
• common - Sourcecode of the common library
• cvpcb - Sourcecode of the CvPCB tool
• demos - Some demo examples
• doxygen - Configuration for generating pretty doxygen manual of the codebase
• eeschema - Sourcecode of the schematic editor
• gerbview - Sourcecode of the gerber viewer
• include - Interfaces to the common library
• kicad - Sourcecode of the project manager
• libs - Sourcecode of KiCad utilities (geometry and others)
• pagelayout_editor - Sourcecode of the pagelayout editor
• patches - Collection of patches for external dependencies
• pcbnew - Sourcecode of the printed circuit board editor
• plugins - Sourcecode for the 3D viewer plugins
• qa - Unit testing framework for KiCad
• resources - Packaging resources such as bitmaps and operating system specific files
  • bitmaps_png - Menu and program icons
  • project_template - Project template
• scripting - Python integration for KiCad
• thirdparty - Sourcecode of external libraries used in KiCad but not written by the KiCad team
• tools - Helpers for developing, testing and building
• translation - Translation data files (managed through Weblate for most languages)
• utils - Small utils for KiCad, e.g. IDF, STEP, and OGL tools and converters

kicad-i18n's Issues

Pcbnew Wrong German Menue Translation

Pcbnew shows a menu item with Place->Dimension. For German translation, there are two diffrent expressions in use for "dimension". The German translation "Einfügen->Abmessungen" should change in "Einfügen->Bemaßung". For Austria and Switzerland "Bemassung" is ok (becouse of missing "scharfes Ess" in their character set) and will be also accepted for Germans. "Abmessungen" is also ok to understand after using once, but correct menue items makes the Kicad much more intuitive for beginners who consider to change from other EDA. "Abmessung" may be accepted for e.g. length=30mm if used for associative drawing input while "Bemaßung" describes the use of arrows graphics in all styles. For examples see the lesson here:

https://www.hs-anhalt.de/fileadmin/Dateien/FB6/personen/voigt_st/Lehrunterlagen/05_CAD/04_techZeich_Masseintragungen.pdf

Even Autocad is translating well:
https://knowledge.autodesk.com/de/support/autocad/getting-started/caas/CloudHelp/cloudhelp/2019/DEU/AutoCAD-Core/files/GUID-9810D35D-E975-49E2-88EA-51FE4ACC92DB-htm.html

Application: Pcbnew
Version: (5.1.4-87-g78af1daa2)-1, release build
Libraries:
wxWidgets 3.0.4
libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.21.0 (+libidn2/2.1.1) nghttp2/1.34.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.68.0
OpenCASCADE Community Edition: 6.9.1
Curl: 7.61.1
Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_PYTHON3=OFF
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON

String should be split

Dear maintainers,

i've found confusing merge of strings to be translated:
a string ID #2132 "Circular" defines both pad shape and the type of array. Need to mention "hole" and "array" are of different genders in some languages and needs to be matched in the translation.

IMHO, these strings from pcbnew/dialogs/dialog_pad_properties_base.cpp (line 68) and pcbnew/dialogs/dialog_create_array_base.cpp (line 281) should be separated.

fr translation update

I fixed 2 errors in french translation.

diff --git a/fr/kicad.po b/fr/kicad.po
index f1118ca..fb13634 100644
--- a/fr/kicad.po
+++ b/fr/kicad.po
@@ -3667,7 +3667,7 @@ msgstr "Réinitialiser à Défaut"

#: common/widgets/widget_hotkey_list.cpp:435
msgid "Undo All Changes"
-msgstr "Unnuler tous les Changements"
+msgstr "Annuler tous les Changements"

#: common/widgets/widget_hotkey_list.cpp:436
msgid "Restore All to Default"
@@ -11856,7 +11856,7 @@ msgstr "Ouvrir schématique"

#: eeschema/tool_sch.cpp:71
msgid "Save (all sheets)"
-msgstr "Quitter (toutes les feuilles)"
+msgstr "Sauver (toutes les feuilles)"

#: eeschema/tool_sch.cpp:76
msgid "Edit Page settings"

kicad.po.gz
fr.diff.gz

Tag 5.1.5

On sunday I will tag the 5.1 branch for 5.1.5.

Please help check for untranslated or fuzzy strings before sunday (17th of november) if possible. Thank you.

I know it is a short notice, but the rc has been announced some time ago and hopefully only minimal changes are needed.

https://lists.launchpad.net/kicad-developers/msg42597.html

Tag 5.1.3

On sunday I will tag the 5.1 branch for 5.1.3.

Please help check for untranslated or fuzzy strings before sunday if possible. Thank you.

Missing 5.1 branch?

Shouldn't it have a 5.1 branch here, like the one on Kicad source?

Tag 5.1.1

I intent to dag 5.1.1 tonight in my timezone.

@ciampix Should we run the update-po-files.sh script first to make sure it matches the source code?

I18n building should follow standard conventions

After this comment: #2 (comment)
I decided to re-open this issue with another title.
I18n building process does not follow the standard rules:
cmake .. (should configure but actually it compiles)
make (should compile but actually does nothing)
make install (actually installs, this is correct)

Problem opening project files (at least with -de template)

It sounds strange, but when I use the -de template for German, opening a project does not work. When I switch back to English, it works.

This is the bug as originally reported in the KiCAD bug tracker with all the information. After getting the information that this seems to be locale related I was directed here to report it. I have personally verified that it actually is an i18n issue by trying to open a project both with the German as well as the English setting (Default is German, I had to explicitly set it to English to make it work for me).

https://bugs.launchpad.net/kicad/+bug/1740481

Italian translation fails to compile

Since commit eabd17e, msgfmt fails while processing the Italian translation.

Tag 5.0.0

It looks like we can safely tag this.

It looks like complete translations in:
de, en, es, fr, it, ja, ru
Almost complete with:
zh_CN
Trailing a little behind here is:
hu, pl

Tag 5.0.2

5.0.2 of kicad has been tagged, I will tag the translations shortly after this. It looks like there are three fuzzy strings. Please help update these ASAP.

Below languages not checked needs to be updated

• cs
• de
• en
• es
• fr
• it
• ja
• pl
• pt
• ru
• zh_CN

Work on this should of course happen on the 5.0 branch. Other changes that track kicad master should be on the master branch.

Random '&' characters in Polish translation

For example (line 14244)
msgid "Hide &Grid"
msgstr "Ukryj siatkę"

(14228)
msgid "Print Pre&view..."
msgstr "Podgląd wydruku..."

Should they be included in translated string or can be removed?

Tag 5.1.0

5.1.0-rc2 was recently tagged [1], now the time for 5.1.0 has come [2]. As the translations seem to be in good nick I will tag 5.1.0 on this sunday unless there are any objections or intentions to finish up some more languages.

The following languages are complete or almost complete:
de, en, fr, it, pt, ru, pl, zh_CN, ja, and cs

Thank you all for your contributions.

Contributions that matches up with the 5.1.0 tag of the kicad source still go on the master branch of kicad-i18n untill we have tagged 5.1.0. here.

[1] https://lists.launchpad.net/kicad-developers/msg39560.html
[2] https://lists.launchpad.net/kicad-developers/msg39627.html

Fails to compile

Hi,

since commit e98962e I get a build failure in the zh_CN translation.

4.x as master

Please, make the 4.0 branch as master. IMO, it is confusing, when the default (master) branch doesn't show current status and one need to switch the branch after clone. Or i miss something?

Missing compilation of .mo files from .po source files

In actual cmake config files is missing the automatic generation of compiled gettext message catalogs (.mo) files from their source (.po) files.
This is the first step to avoid having to use manually poedit to compile the message catalogs.

Tag 5.0.1

Soon 5.0.1 will be tagged, I will tag the translations shortly after this. There should be no string updates, but if people would like some other languages, the time is now. Hungarian (hu) and Greek (el) are the two languages that are closest to being complete, but not quite there yet.

Work on this should of course happen on the 5.0 branch. Other changes that track kicad master should be on the master branch.

Persisting and recurring quality issues in the German translation

What can we do about the extremely heterogeneous quality of German translated messages?

While roughly half of them are flawless, many are ungrammatical or use misspelled compound nouns.
(German compound nouns are never spelled with whitespace!)

Furthermore, some lexically correct translations are semantically closer to a riddle than to a translation. (I.e. "Try to guess the English phrase")
One example is "Zoomauswahl". It is a valid translation of "zoom selection", but that function will not let you select a zoom level, it will let you zoom to a selection.

Mixing English and German acronyms for the same thing does not help, either.
(In this case "VIA" and "DuKo")

The menu entries should also either all use infinitive or they should all use imperative, but not a wild mixture.
They mostly look the same in English. (e.g. "[to] edit the file" vs. "[Computer?] Edit the file[!]")
In German, however, they are different and infinitive is way more common in German GUIs.

All this leads me to the question:
How can we address this and how can we prevent these issues in the future?
Maybe one could put a glossary and translation guidelines in a document somewhere.
Let's discuss!

Indonesian Language

Administrator,
I want to contribute Indonesian GUI.
Pls open / add related folder and file(s) .
Tks.

"Choose the library table to add the library"

As you can see, the final word "to" has been left out. For newbies to KiCad like me, I found this yet another unnecessary confusing step on my way to learning KiCad. Thank you for correcting this!

Translations license

There is no license file for translations. Is it GPL-2.0+ as KiCad or KiCad documentation license?

Missing Slovak (sk) in Language menu

I don't know if this is proper place, if not then i am sorry. But recently the Slovak translation was added, however the Slovak language is missing in the Language menu.

The Slovak translation works for me when i choose the default language, but i afraid what when the system's language differs.

sk translation update

Hi,

i updated the Slovak (sk) translation (attached gziped). It has translated about 75 % of strings against kicad 4.0.4 version.

regards
kicad.po.gz

German translation typo in Eeschema DRC dialog.

I just found a small typo in the German translation.
In the DRC dialog of Eeschema, it should be "Starten" instead of "Starte".

#: eeschema/dialogs/dialog_erc_base.cpp:103 msgid "Run" msgstr "Starte"

The status tool gives the wrong status (ru, branch 4.0)

I use to translate the Poedit tool.
It show that all strings translated and no fuzzy.
But if I run the status tool it show me:

ru

4894 translated messages
12 fuzzy translations
14 untranslated messages

Tag the 4.0.6 release

If any one has things they want included in the 4.0.6 release, shout up now. If no one replies then I will tag 635bd45 as 4.0.6 early in the weekend.

GitLab Translation Migration

Hi Translators-

As part of the Great KiCad GitLab migration of 2019, I am testing the movement of open issues and PRs from GitHub to GitLab.

Here's what we know so far:

• Open Pull Requests will transfer to GitLab without moving the source of the PR. That means pull requests will become GitLab Merge Requests that are referenced to the user's GitHub repository
• Open Issues will transfer to GitLab issues
• Closed/Resolved PRs and Issues will also transfer

In order to facilitate the transfer, it will be helpful if you can do two things:

• Open a GitLab account (these can use your GitHub OAuth)
• Set your GitHub email to public
• Let me know who the responsible parties are for the Translation repository

The second point is critical because the migration script will only link users whose e-mail addresses match. If the script can't see your GitHub e-mail address, the issue will be tied to the KiCad-Bot that performs the migration.

The timeline for the actual migration will be determined by the responsible parties from bullet 3 above but it would greatly assist my testing for bugs if you could do the first two steps above as soon as possible.

Thank you-
Seth

Commit message format

Do we need a common format of commit message?
And what information may be helpful in this message?
For now every translator write messages as they wont and and to check the state of translations not so easy.
Maybe we should arrange to use common style of commit messages?
For example:
update from last sources:
[RU] update for b37969f584c900eda07748fb198daab8a261930a
fix some errors in translation without updating from sources:
[RU] fixes (... optional explanation)
or something else.

Tag 5.1.4

On sunday I will tag the 5.1 branch for 5.1.4.

Please help check for untranslated or fuzzy strings before sunday (11th of august) if possible. Thank you.

Translation file is too large!

In the kicad.po file, there are approximately 4.8k items to be translated.
Sometimes, gete keepers of the repository have to check a vast number of them.
It's almost impossible.

How about to consider to separate the translation file to each application? (e.g., eeschema.po, pcbnew.po, ...)

sv.po is encoded from 8859

This appears to create issues on some systems

Lithuanian (lt) translation request

Dear Translators and Maintainers,

i want to start translating the KiCcad package to Lithuanian and i need the PO files, in sync with the development tree. How can i help this to happen?