easyeda2021 / easyeda-i18n Goto Github PK

Sorry, if I open so many issues 😋

During the translation, some times I see the word Attributes and some times the word Properties in the menu title.

Now I see that in the design and PCB they are used for the same thing.

Example on PCB:
Attribute:

Properties:

Is it possible to use the same word in the entire translation to be coherent? Or can we translate it using just one of them?

It doesn't look good if I click on the PCB and I see "Canvas Attributes" and if I click on the track I see "Track Properties" (you can set the same parameters).

OT:
As I feel to be a little arrogant to open so many issue, I make my other questions here 😋
Question 1:

Grid.Line Width =

Does this need a special translation? Some times there is a point between 2 words. Where is it used? Should we leave this point also in the translation?

Question 2:

Bus entry x1 =
No, Generate Gerber =

Some times all words are written with the first letter as upper case, some times all with lowercase. I was always thinking that the menu items are written with the upper case letter. But it is not always so. Normally (for example english, italian and spanish), only the first letter of a sentence is in uppercase. On menus, there is a stylesheet attribute that automatically convert the first letter (text-transform: capitalize).

Hi,

Are we supposed to translate words and numbers that are between curley braces?

For example:

Hi {username} =
[{file}] is not a valid json file =
Hi, I found a problem of your library, this library seems incorrect.\ntitle:{title}\nType:{type}\nlink:{link}\n{content}\nThank you! =

If I were translating this into Italian (for example) would they end up like this (Option 1)

Ciao {nome utente}
[{il file}] non è un file json valido
Ciao, ho riscontrato un problema della tua libreria, questa libreria sembra errata.\ntitolo:{titolo}\ncollegamento:{collegamento}\ncontenuto:{contenuto}\nGrazie!

Or should they be translated like this (Option 2)

Ciao {username}
[{file}] non è un file json valido
Ciao, ho riscontrato un problema della tua libreria, questa libreria sembra errata.\ntitolo:{title}\ncollegamento:{type}\ncontenuto:{content}\nGrazie!

Hello, I found these lines in the template that both start with # symbol and also have an = at the end.

Can you tell me which of these lines should have the # symbol removed and which ones should have the = sign removed so I can fix the template and issue a pull request?

Also, is it OK to remove the first space after any # symbol that starts a new line? Look at line numbers 2529 and 2530 for example ... would it be OK to remove the space after the # symbol and would that be universally ok to do throughout the entire template?

Line Number,Line Text
263,#Terms of Use & Privacy Policy =
271,#PCB Fabrication Capabilities =
963,#Duplicated document title =
986,#Clone it to a project =
987,#Clone it, then edit it =
1019,#It will take a while to unroute this net, do you want to continue? =
2300,#Ripup Nets =
2529,# Column Spacing =
2530,# Row Spacing =
3022,Assign LCSC Part# =
3079,# Rename Folder =

Thank you,

Mike

Hello,

I spent the last day or so writing a Java program that engages the Google Cloud API for language translation and from my initial experiments, it seems to do pretty well with your document. However, I did notice some areas that would be better to translate by breaking the line down into different parts and translating those words then re-assembling the line so that some of the non-language portions of the document can remain properly placed in the translated side of the document.

Would you look at some of these translations that I did and if you can provide me with any kind of rules or text patterns to look for so that I can guarantee that they remain properly placed in the translation side ... I think it might be possible to translate into every language in a manner of minutes once the program is properly handling the areas of the document that won't translate straight across.

Anyways, I look forward to your feedback.

Mike
Translations.zip

I had found the following lines:

Channel_A =
Channel A =

Should I preserve the underscore _? Is it relevant for EasyEDA?

Has the EasyEDA Pro translation been planned?

For your first time order, less than $20 discount on the freight!

Means that on your first order, you get less than 20$ discount.

Do you mean "For your first time order, up to $20 discount on the freight!"
Or "For your first time order, more than $20 discount on the freight!"
Or "For your first time order, less than $20 discount on the freight :'("

Live Translation, load the extension, and hit Start, but the translation doesn't change.

Hi,
I just noticed some suspicious strings in the ui_data_CLEAN.txt file.
You need to check the ui_data_CLEAN.txt file at lines 265, 273, 972, 995, 996, 1028, 2328, 2559, 2560.
These lines start with # and they end with =
If they were comments, you should delete the = character at the end of the lines.

Hi,

I've been helping translate from English to Portuguese, and have found some lines at ui_data_pt.txt that don't have the equal sign to put the translation, e. g. lines from 478 to 502.
Should I put the sign and translate?

Thanks,

Is it possibile to re-run the tutorial of the UI? I would check the actual translation

The line begins with a '#'. But it seems more a translation than a comment.

But I can't find "Rename folder" anywhere in EasyEda, so I don't know what is better.

We had seen the new template ui_data_CLEAN.txt. Should we merge this file in each translation file by ourself? The readme doesn't say anything about update existing translations.

When will Korean be included in EasyEDA's Language Settings?

I found some terms without clarity, possible spelling mistakes:

Line 3172: should be Placement Tolerance rather than
Plcarment Tolerance

Line 3172:
(less then 0.15mm),
should be (less than 0.15mm)
Similarly applied to line 3133: (less then 0.08mm) >> (less than 0.08mm)

In several cases "can not less " seems to be incorrect, should be "can not be less" >> a replace all should be ok! Similarly applied for "can not" >> "cannot"
Line 2439: "charaters" should be characters
Line 2290: "must larger" >> should be "must be larger"
Line 2266: "must more" >> should be "must be more"
Line 3135: "System footprint must exist pad number" >> should be "System footprint must have pad number"
Line 2057: "thirdparty" >> should be "third-party"
Line 1314: "Found the complicated polygon object can not" >> should be "Found the complicated polygon that object cannot"
Some more I have not recalled yet!
Please check with thanks!
Dang Dinh Ngoc
PS. Minor but good to do some checks

While I cannot translate mandarin to English, for example, I can correct grammar in parts of the program where broken English is already implemented or the translation is not in the correct context. I have noticed this everywhere when using it online and was wondering if there would be an easy way for me to correct these mistakes.

What does it mean the following comment, found here?

#后端返回英文的错误信息

There are other instances:

• easyeda-i18n/editor-std/ui_data_it.txt

  Line 2025 in f59c17f

  # Upload {site} 目前仅有波兰论坛使用

• easyeda-i18n/editor-std/ui_data_it.txt

  Line 2556 in f59c17f

  # 阵列分布与阵列克隆

and many more. Translating these comments may help other translators.

I have 50% completed the translation of Korean.

Do I have to submit a Pull request to save it in the middle? Or do I only save it for my local fork?

At line 462 (italian file) and beyond, some lines don't have the = sign. Is it error? Should I add it?

I try to open it here, until there is a right section.
There are some words that are hard to translate, if there is not a real context on the translation word.
But if there are many people translating the text, many different words could be used.
It is important to use always the same word and not different words for the same English word.

Here an example:
Net, Pin and Layer

How should it be translated?
Net can be "Net", or "Rete"
Pin can be "Pin", or "Piedino"

On "Net", you can use both and you see both in the schematics documentations.
On "Pin", the right definition is "Piedino" but you rarely see this definition in the documentation. So what is better to use?

And now the most difficult one: "Layer".
Most Italian users never use the Italian language in such programs, as the translation is just too much (or too many italian words, instead of leave the original names). Some times, leaving the original language is better than have a correct but strange translated word.
In the current translation, "Layer" was translated in "Livello". This is the right definition for "Layer".
Many manuals doesn't write "Livello" as it means also level. So they write "Strato".

Before we translate it in 3 different ways, it would be better if we define/fix some words to be sure we use the right words in all translations. But there should be a section to write them.

As there are some words translated in different ways, I would like to replace them all with just one definition.
But as I am not the best one for this translation, I want to be sure the words are right. Please correct my words if they are wrong.

Words List - Italian

* In Italian, the plural of an English word is written without "s". "Many files" in Italian is "tanti file".? link

The following words will not be translated (as it create confusion and on the web we always see the English word):

* As the English word is not translated, it is more a name than a word. Word need to be capitalized: Manage net = Gestisci Net

Reference Links:
https://tekube.com/wp-content/uploads/2020/03/THE-PCB-HANDBOOK-Tekube.pdf

If there are more or there is a better word to describe something, please report it.

Hi
I've downloaded the latest version (6.4.24) of easyEDA and have found something a bit odd. Some lines (as in one of the pictures), had the suffix ".layer". I expected it to disappear when added to the software's UI but that didn't happen (as you can see in the other picture). Should I change anything or leave it as it is?

Thank you