10/12/2016 03:32 PM, andy pugh wrote: > On 12 October 2016 at 12:43, Marius Alksnys <mar...@robotise.lt> wrote: >> 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! > > He is at least partially incorrect. > > If you look at Nick's Youtube videos ...
Yes, I agree. My point is that information about locales is missing in the main docs. People like me (and other non-English speakers, probably) set OS locale to English because: - there is no translation to their language - or it is too bad to use (smaller number of users = not enough effort; English words are shorter usually; language core differences makes translations harder, etc.) - English is preffered (it is more universal to get used to; good way to learn English and stay with it every day; it is far easier to search for strings on internet, based on English, etc.) - it is not obvious / easy to turn other language on Linux everywhere - English is preferred over partially translated system, where English texts pop out here and there; commands and reserved words are English too - people do not know it is possible - English or some locale settings make some software just work, or have issues while localised. For example, boxes in status bar of axis interface are too narrow. - working with people of different languages - ... While only a specific program, like in this case, LinuxCNC + tools, can be specifically used by CNC operators, they might have other interface language needs than me, an integrator. And, especially, these days (people are migrating or working remotely), different multiple languages for users looking at the screen is more and more actual. I am using and installing Linux OS'es with English interface language (except some special efforts for non-EN friendly persons). Thus I don't even get to know about other language possibilities or quality, completeness of other translations. > I think that, for a standalone UI, the instructions here should be sufficient: > http://faq.pygtk.org/index.py?req=show&file=faq22.002.htp > Oh, and where you say: >> No surprise there is no Lithuanian translation :) > > You could create one with a few hours of typing. I don't believe few hours would result in usable high quality translation. The reasons: - high number of text strings - no clues how to translate some words, which somehow matured and settled in English language. For example, word Offset. And I found it left untranslated in Russian LinuxCNC G-code documentation - it is not clear where original phrase came from. Not knowing it might lead to wrong translation, different context may translate same word differently - no fast way to translate and test / no WYSIWYG translation tool - I would like to consult at least several people knowing the context about right / best translation of some phrases or words. Any good collaboration / sharing tools? I tested Google Translator Toolkit and it messed up the file to unusable. It automatically translated a lot of "5:" and alike to long random phrases from internet. There where several other drawbacks too. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
