Translation files are relatively easy to create and do not need to be
compiled with the rest of the linuxCNC stack. What does need to be
compiled in is support in the source code and in some cases, compiler flags.

Qt and python for sure, and I think Glade, all have translation (locale)

Changing the locale on the fly is somewhat dependent on the desktop
environment in my experience. Some DE allow you to change the locale on
the fly from a settings application. Some require you to restart the X
server after making the change. For DEs that don't have a GUI way to
make the change you can easily change the locale from the cli. Again,
sometimes you will have to restart the X server. You can also make a
shortcut (.desktop file) that contains a different locale environment
variable for just the application that it launches.

Hope that helps some.

On 10/12/2016 06:43 AM, Marius Alksnys wrote:
> Thank you EBo for your great answer.
> I am surprised that LinuxCNC has more translations than it is declared. 
> There is Russian translation and docs miss that! I asked my Russian 
> friend, old LinuxCNC user (who reads Russian LinuxCNC forum a lot) if 
> LinuxCNC has Russian translation and he answered No! This is a serious 
> information gap.
> Translation might be incomplete, but it can help greatly.
> No surprise there is no Lithuanian translation :)
> Valuable info. Good to start with.
> I raised my question because I thought I can create at least my custom 
> panel(s) multilingual, which might be enough. Those panels display and 
> control things specific to that machine. I use GladeVCP embedded on the 
> right side of Axis most often, but sometimes QtQuickVCP or PyVCP on 
> Machinekit too.
> Therefore, I would like to know which way is better for custom panels 
> too. Going the long way for one and only machine might be uncomfortable..
> I hope to find a way to edit and install the translation file without 
> compiling whole linuxcnc.
> What is a good way to involve collaborators to the translation?
> 10/12/2016 12:56 PM, EBo rašė:
>> This is an excellent question, and I am sure there is plenty of people
>> who will support this in various ways.  Now on to some technical issues,
>> tools, and solutions.
>> A fair bit of work has already been done on 'internationalization'
>> (please see documentation and
>> for
>> specifics and examples).  That said, I am sure that some of the UI's are
>> missing any internationalization support.  One of the problems in the
>> past is that the UI's were written in any one of a number of different
>> tool chains -- including tcltk, gl, Qt, python binding, and I am not
>> sure what all.  From the linuxcnc/src/po/README file I see that they
>> give some specific examples, and how to.  There is current support for
>> 14 different languages and 3 extra regional dialects or additional
>> languages.  What I do not know is if the current tools and
>> implementation can switch languages on the fly (ie by a pull down menu,
>> and refresh in the new language).  It is possible that that
>> functionality already exists, but no one has updated it, or (which is
>> more likely) that the necessary low level functionality does not exist
>> in the tools used.  I know that I tried to do exactly what you are
>> suggesting back in 2001 using Qt -- they were just coming out with that
>> support in their professional tools, but not in their free version, and
>> I was developing open-source tools for ecologists at the university (ie
>> not paid, and could not afford to pony up the $5K IIRC)...  So to help
>> drill down into the question and how current implementations do not
>> support your needs please take a look at the URL above, play with
>> them a bit, and tell us where it is not working and what you would want
>> to change.  Once we have that information we can have a discussion about
>> if the request is something that anyone wants to take on and/or support.
>> One thing that would help us is if you tell us which UI you would like
>> to start with, and if you are looking to try to set it up on the fly or
>> just support the additional languages.
>> I like your idea of setting up a UI which is purely graphical.  There
>> is places where that will breakdown, but it could go a long way.  For
>> that look at the current UI's, like Axis, and tell use what you would
>> change and why.
>> Hope this helps,
>>     EBo --
>> On Oct 12 2016 12:21 AM, Marius Alksnys wrote:
>>> My integrated machines are used by different language speaking people
>>> quite often. Some of them speak / understand one language only. Thus
>>> there is a need to create UIs which could be understood by different
>>> spoken users. Currently there is a need for up to three languages on
>>> one UI.
>>> What is the best way to create and maintain such UIs or panels for
>>> LinuxCNC?
>>> My ideas:
>>> 1. Create UI without texts, just icons, numbers, other visual
>>> components. This includes various messages - warnings, errors, etc.
>>> Where to get suitable icons for that, how to adapt them, what
>>> practices
>>> to follow?
>>> 2. Let the user to choose the language (s)he prefers, for example, a
>>> group of radio buttons with flags / abbreviations and by using
>>> GladeVCP
>>> - create python script which changes labels and texts of controls at
>>> runtime depending on which language (or flag) button is activated.
>>> 3. Use HAL and connected mentioned radio button hal pins to every HAL
>>> "label"... Don't know how to do this yet.
>>> 4. Use some native GladeVCP locale methods and translation files (?).
>>> More ideas and suggestions how to realise this?
>>> How about the messages from NGC, from custom HAL components?
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most 
> engaging tech sites,!
> _______________________________________________
> Emc-developers mailing list

Attachment: signature.asc
Description: OpenPGP digital signature

Check out the vibrant tech community on one of the world's most 
engaging tech sites,!
Emc-developers mailing list

Reply via email to