Localization/translation

[terjeio]

Initial support for localization/translation support has been added to the latest version. The default locale is en-US (US english), and a partial translation to zh-CN (simplified chinese) has been added by me.

I will not make any translations myself but rather rely on the community to provide them. See the Wiki for how this can be done.

I suggest that those who want to translate add to this discussion before starting so that duplicate work can be avoided.

Tips: If you want to run ioSender with a specific language then create a shortcut to the executable and add the locale specification to the command line. E.g. -locale en-US will select the default locale independent of what the OS default is.

[einencool]

Sounds Great.
As discussed last year, I would like to help with the German Translation

[terjeio]

Thanks, I have uploaded a new version with your changes and with some new strings to translate.

The missing tooltips above are due to prorgam logic changing them at run time - to be fixed later.
The Status: IDLE has the IDLE text (and the other statuses) coming from the controller as plaintext. I'll have to figure out how to translate those, perhaps via a translatable lookup table...

From here it will take a little longer before I will be able to deliver any updates.

[einencool]

Alright, I think you've done an amazing job 👍, for the "normal" operation it seems to work really good, and there are only a few things to do...
I did some minor Fixes and the few new translations.
Your new 36.4 Version was still named as 36.3 ;-), but that's just cosmetic ;-)
translation 36.4.txt

Here are the Screenshots, so that you can see the points that have to be a little bit improved :-)
Outline Menu:

3D View from Mainwindow is correct, But from the 3D-View TAB there is this Box not in the correct size:

Tool Tips for Signals in Main Window:

Size for translation in Center Finder:

Area to Probe in height map:

different Hints in Probing tabs:

Complete GRBL Settings Tab:

Settings Program Tab:

Thank you, greets Chris

Oh, one thing, is there a way to start the Software without a connected Board, so that all tabs are visible and clickable?
Because without the Board everything is grey and sadly not clickable :-(

[terjeio]

New version uploaded. I have cracked moving strings from code to UI definition files - 2 strings moved this far, a lot more to go...
Until I get this done you do not need to mark any screen dumps for me.

Oh, one thing, is there a way to start the Software without a connected Board, so that all tabs are visible and clickable?

Currently not, and I am not sure it ever will be possible due to the tight integration between the controller and the sender I want to have. The closest will be to have a "soft" controller for the basic parts. The simulator driver fits the bill but I have only managed to compile it for Linux for now.

[phil-barrett]

Oh, one thing, is there a way to start the Software without a connected Board, so that all tabs are visible and clickable?

Currently not, and I am not sure it ever will be possible due to the tight integration between the controller and the sender I want to have. The closest will be to have a "soft" controller for the basic parts. The simulator driver fits the bill but I have only managed to compile it for Linux for now.

Kind of a kludge but you can put grbl on a cheap arduino and hook it up. You could also put grblHAL on a teensy (or any other supported micro) and use that - not quite as cheap. You don't need a full cnc machine.

[terjeio]

...or a cheap(er) Pi Pico? We could provida a binary for that as it can be programmed by drag & drop, no need to install anything.

[terjeio]

New upload with what I believe is a near 100% extract of translatable strings (exept Lathe tabs/settings - I'll add these later).

Note that many of the new strings has placeholders that is used for inserting run-time data. These are {0} ,{1} etc and must be kept in the translated strings.

Some special characters are encoded as html character entities, eg < and >, commmon for these is that they starts with an ampersand and ends with a semicolon. Again these should be kept.

Finally, some strings contain line breaks, these are represented by '\n'.

Initial translation to russian has been provided by @calabr in issue #145, this is incorporated in the new upload.

[einencool]

Here's the new Version, I made some minor bugfixes.
It seems, that these Tooltips are not in the translation List:

The rest seems to be fine, and I hope my translations make sense in the most points :-:
translation 36.7.txt

[terjeio]

Sorry about those, I have added them now.
I have also added support for parameters and expressions in macros - hopefully that does not break any existing macros.

[calabr]

It's will be good to know the maximum character count available, especially for buttons.
Direct Russian translation I made in most cases longer than English.
Also some labels need to enable line wrapping

[terjeio]

It's will be good to know the maximum character count available, especially for buttons.

There is no character limit, widths are defined in pixels - and the size of any given string is not possible to know without measuring it with the correct font settings. I have made changes to better accommodate some of them (dynamic width adjustments within limits).

Also some labels need to enable line wrapping

Wrapping is not available for labels, I can add a line break in the original source - but when translated those are lost.
I had to change the label you have marked above to at TextBlock to allow wrapping.

[terjeio]

New version has been uploaded.

Translation of alarms, error messages and settings is now possible - I will add details about how in a Wiki, likely the one for the grblHAL core.

[einencool]

Sounds good, here are the translations for 36.8
translation 36.8.txt