It would be nice having better english integration some words are still in german that would be nice to have full english integration
-
-
Hi!
For the next big version (3.0) I can tell you it is developed in english an then translated to german. So the problem is indeed known. For the 2.x-series I try to get you an answer or a solution, give us some time.
Hoc
-
i would support in modifiying the english translations - please provide me with necessary information how to deal with this.
regards,
astrakid -
There is very little in the main program that isnt in English. Most of the German actualy comes from the DDF's which are easily edited using the DDFCreator.the
The first few times, I used Google Translate to find the words that I couldnt figure out and now dont have to think about it.
Most of the translation issues in the main program are with the phraseing not the words. Occasionaly something is just translated without being re phrased properly but its easily understood. This happens in Help more than anywhere else. That makes sense as the main program is mainly single word commands and labels wereas the help is descriptive paragraphs.
Astrakid, If you have some DDF's that you want edited, let me know which ones and I'l "Anglify" them for you, I'm getting quite good at it.
--------------------------------------------------
Question to Hoc.
Does V3.0 use the same DDF's? If so, I will go through them and do the proper translations and post, if not, I wont waste my time. I would also check the definitions against the fixtures documentation while I did it, there are a few that are definatly not correct and some that need rewriting with procedures to work at their best. Probably wont fix them all on the translation pass, but at least we will have a list that we can slowly work on until they are all fixed.
I notice that, with other DMX software that has user contributed fixture definitions, there are often multiple versions done by different people for the same fixture, some are good and some are just junk (EZ View is bad for this). This causes confusion and frustration. We are early enough in DMX Control to watch this and keep it clean.
We would also need to agree on a filename convention to identfy English from German DDF files.
I would suggest, going forward that contributed DDF's go into a holding area to be checked for sanity against the fixture documentation, duplications and translation before actualy being posted publicly.
Quite often, a DDF can be written that may be ok for that persons use and show, but doesnt completely define the fixture. These could be posted into a "partial" area for use and further development by the community.
Christopher
Ambient Sound -
Astrakid, If you have some DDF's that you want edited, let me know which ones and I'l "Anglify" them for you, I'm getting quite good at it.
i don't need a translation, i was going to support here...
but thanks anyway for that offer.regards,
astrakid -
Hello,
this is a good opportunity to remember that native speaker can support us to improve the quality of string translations.
You can contribute by editing the English strings (please do not touch the German strings that are uses as key) within the wiki articles:http://www.dmxcontrol.org/wiki/Language_files
Thanks for your support.
Best regards Frank
-
Frank, would you like us to edit the English.lng.forms and English.lng.variables in the wiki directly or download localy, edit and post/email or something?
If we edit in the wiki, how do we notify you when we make changes, or, is that handled by the wiki itself?
Thanks for the link to the page, theres all sorts of things inside that wiki that I havnt found yet
What about the DDFCreator program? I've noiticed a few interesting translations in that one (the program itself, not just the DDF's). There are also the plug-ins that are sometimes not translated at all, for example, the OSC plugin.
-
Hi!
Don't worry about the DDFs for the 3.0. There won't be any DDFs in the now known stlye. More or less you just type in your DMX-tables from the device manuals. And for that reason there will be no need to translate anything there.
I hope you did not missunderstand what Frank told you about the language-files. Thats not for the wiki, thats indeed for the DMXControl program. So if a new version of DMXControl is released, Stefan (the main developer for the 2.x-series) has to take the edited pages from the wiki and compile them into the program.
Hoc
-
Thank you Hoc,
I understand, we just edit the language files using the wiki editor and Stefan compiles those so we dont download the files to our own computer, edit them there and then send to Stefan.Christopher
-
@Ambient-Sound : I will ask Stefan on how to do translations in a plugin.
When it is possible I will translate the plugin. -
Markus: Thanks,
Here are the current corrections for the DDF Creator that I know of along with suggested replacements.In DDFCreator settings:
"Raster On/Off" = "Snap To Grid On/Off" or, if that is too long, "Snap To: On/Off"
"Display raster" = "Display Snap To Grid" or "Display Snap To"
"Resolution in Pixel" = "Snap To Grid Resolution (Pixels)" or "Grid Resolution (Pixels)" or "Resolution (Pixels)"In DDF Procedures:
"initsequence" = "Init Sequence"As DDF is loading (the status box):
"DDF-Check will be started. Please be patient" = "Loading DDF"
"DDF is readed and checked. Please be patient." = "Checking DDF"Note: In reality, the computer loads these so fast that only one message is needed unless there are two for debugging so we can tell if the load fails seperatly from a syntax error in the DDF XML.
If the code is changed for only one message, then "DDF is being loaded and checked" would be proper.
You could even cheat and use the "DDF is being loaded and checked" for both, then it would look like one operation as I'm assuming that if either operation fails there would be an error message anyway.Thanks again.
Christopher -
Souko
Moved the thread from forum Development [v2] to forum Development and Features [v2]. -
Newly created posts will remain inaccessible for others until approved by a moderator.
The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.