Translations

Made for 0.4.15 SR9 version.
Works well on Linux (Mint) and Windows 10.

Made for 0.4.15 SR9 version.
Works well on Linux (Mint) and Windows 10.

Ok, thamk you very much.

Hello.
I have updated Russian translation.
New strings were translated and fixed some typos.
Also, help files were updated.

P.S This is for the trunk version

Hi, I updated Czech translation for trunk revision 1472.
I found two minor mistakes

• there is an extra space after "Gate Delay" in file logicsubc.cpp
  
• windows title for saving VCD file is "Save circuit"
  

By the way I don't know how to translate Auto step. Translation word by word sounds strange in Czech language. If something is automatic then it is not necessary to set it. What is the exact meaning of the number?

@vranik
Thanks, I will have a look at those errors.

By the way I don't know how to translate Auto step. Translation word by word sounds strange in Czech language. If something is automatic then it is not necessary to set it. What is the exact meaning of the number?

https://simulide.forumotion.com/t938-simulation-speed-reactive-components

In any case everything in development branch can change, and this "auto step" thing will change almost for sure.
Even numbered versions can change, until they reach "stable" state.

My goal is to publish 1.0.0 as "stable" as soon as posible.
So I reviewed translations recently and found some garbage left by QtDesigner files and some other minor errors.
I'm updating and cleaning ts files for 1.0.0 and hopefully upload in a few days.

Translation files for 1.0.0 has been updated for the definitive "stable" state.
If you wish you can finish the translations.

arcachofo wrote:Translation files for 1.0.0 has been updated for the definitive "stable" state.
If you wish you can finish the translations.

OT: I guess you know already that 1.0.0 is not updated for debugging AVR assembly codes (for Atmega8, for example) as you did to 1.0.1.

OT: I guess you know already that 1.0.0 is not updated for debugging AVR assembly codes (for Atmega8, for example) as you did to 1.0.1.

No, that feature was introduced after 1.0.0

I fixed the problem with incomplete or wrong translations messing with the Component List (1.0.0 Rev 1196).
I didn't update ts files to not interfere with the last files uploaded.

Is anyone working in the last files uploaded for 1.0.0?

arcachofo wrote:Is anyone working in the last files uploaded for 1.0.0?

No, I don't work on any translation.

No, I don't work on any translation.

Ok thanks.

Active Component list was getting too long so I created 3 groups: Rectifiers, Transistors and Other Active.
This adds a few new string to translate.

Also fixed Editor Find/Replace dialog not showing the message with number of coincidences and added plurals to it.

New files for 1.0.0 where uploaded (download links at the first post).

Hi, I updated Czech translation for version 1.0.0 revision 1208.
I found three minor mistakes

• there is missing letter k at the end of KY-013 Joystic in file ky023.cpp
  

• there is misspelled word Warning in file reactive.cpp
  

• I propose to change warning "Capacitor can't update fast enough" to "Capacitor is not updated fast enough" in file reactive.cpp
  

Hi, I updated Czech translation for version 1.0.0 revision 1208.
I found three minor mistakes

there is missing letter k at the end of KY-013 Joystic in file ky023.cpp

there is misspelled word Warning in file reactive.cpp

I propose to change warning "Capacitor can't update fast enough" to "Capacitor is not updated fast enough" in file reactive.cpp

Thanks, fixed at Rev 1209 and files updated in the first post.
Also fixed a misspelled word "Perifericals" should be "Peripherals".

I updated Czech translation for version 1.0.0 revision 1223.

By the way I think that the component 7 seg BCD should be in group Leds instead of Other logic.

By the way I think that the component 7 seg BCD should be in group Leds instead of Other logic.

Yes it could be there. It is in the Logic section to not be confused with the real 7 segments.

Hi, I would like to update Russian translation for version 1.0.0.
I just wanted to inform you about this in case someone else is working on this translation.

Hi mariiaalt

Maybe you should talk with Sergey, user name: Fizik_S.

I am going to upload Turkish translations of 1.0.0 in at most 2 days.

I updated German translation for version 1.0.0.

One small correction for the english text in McuMonitor:
"Byte-PC"  --> would be better as: "Adresses as Byte"
(does not only affect PC, but also representation of Flash)

There are also some buttons, where their text i not available in the linguist file, e.g. in the serial monitor "Clear" and "Value", or in the scope.

Aejwt wrote:I am going to upload Turkish translations of 1.0.0 in at most 2 days.

Thanks. We still have at least one week and maybe more, seems that there are still some error to fix.

TimFisch wrote:One small correction for the english text in McuMonitor:
"Byte-PC" --> would be better as: "Adresses as Byte"
(does not only affect PC, but also representation of Flash)

Yes you are right.
But there is not much space, so it should be as short as possible.

TimFisch wrote:There are also some buttons, where their text i not available in the linguist file, e.g. in the serial monitor "Clear" and "Value", or in the scope.

Ok, I will have a look.

I completed Turkish translation of 1.0.0. The attached file can be used as is, but some translations seem too long. I'm going to use the program for a few days to correct things that are not displayed properly.

TimFisch wrote:There are also some buttons, where their text i not available in the linguist file, e.g. in the serial monitor "Clear" and "Value", or in the scope.

Solved at Rev 1225.

Aejwt wrote:I completed Turkish translation of 1.0.0. The attached file can be used as is, but some translations seem too long. I'm going to use the program for a few days to correct things that are not displayed properly.

Thaks, translation updated.

I uploaded new files with some errors fixed.

Thanks for the fast resoponse.

I updated the German file (see attached).

I also found some "unlabelled text":
- "Open" on serial port
- Function component: the word "Output" in Set Function window
- Trigger Types in Flipflops
- Package properties: text in the dropdown for type
- "Running" Indicator: texts "Stopped", "Running", "Probably Circuit Error", etc.
- context menu in textboxes of the oscilloscope and logic analyzer such as the expanded logic analyzer
- all context menus for textboxes in component properties


Additionally:
- the turkish translation contributor (Doğu Kocatepe) is just out of the view in when opening "about SimulIDE" in WIN10 on my machine.
- The unit "Kilohertz" is given as KHz but should be kHz

That's enough german nitpicking for today  :-)

TimFisch TimFisch wrote:I also found some "unlabelled text":

- "Open" on serial port
- Function component: the word "Output" in Set Function window
- "Running" Indicator: texts "Stopped", "Running", "Probably Circuit Error", etc.
I'm solving these.


- Trigger Types in Flipflops
- Package properties: text in the dropdown for type
This is related to a problem with enums.
It was solved for next versions but never ported to 1.0.0.

The main problem is that the translated string ends in the circuit file, leading to errors if a circuit was saved in a different language.
So we need 2 sets of strings: one translated for the GUI and another untranslated for the file.


- context menu in textboxes of the oscilloscope and logic analyzer such as the expanded logic analyzer
- all context menus for textboxes in component properties
I think these context menus shouldn't be there in the first place.
So better remove them (if I find how to do it)

TimFisch wrote:That's enough german nitpicking for today  :-)

Well... sometimes the "nitpicking" show out some relevant problems like the issue with the enums.

Aejwt wrote:I completed Turkish translation of 1.0.0. The attached file can be used as is, but some translations seem too long. I'm going to use the program for a few days to correct things that are not displayed properly.

Yes, string length is often a headache, specially in cases like buttons or so.

In some cases I can't find an equivalent expression that is short enough, and sometimes I can't find an equivalent one at all
So I just leave the original English string.