[Plugin] Eneroth Railroad System (v 0.1.21)
-
@unknownuser said:
"Change Texts" corrected
But the French word was a synonym 
Did you even read the text when translating it? You can't refer to a menu item by another name than what it actually says in the plugin. Regarding the path I have no idea why you changed it. It was already correct so there is no reason to write something else than it already says.
I still can't see any difference between the different headers such as "rotation" and "Les pièces en mouvement". I don't know why you had to change this either because the document was already formatted. You only had to change the text. There are many many more formatting errors such as "text_Label" where "Label" should be italic to show it's a variable while "text_" is a constant. You didn't need to change this either because it was already correct.
So far I've only looked at ONE page in the whole documentation but when I looked at the Balise page I noticed there are some random spaces in "m / s". It means meter divided by second and should not have spaces in it. It didn't have it before so I don't know why you added them. Also acceleration is not measured in "m/s2". It's measured in "m/s[sup:3o2e9utn]2[/sup:3o2e9utn]". It means meter divided by second squared - how much the velocity (m/s) changes per second ((m/s)/s). It was correct so there was no reason to change that either.
-
I will see that and have a little idea why this happened!
Drawing roads need a little training but funny to make!
-
I've also noticed you randomly color color names in the text as if the user didn't know what colors look like. This is done at the Coupling Tool page and the red back lights on trains at the Create Rolling Stock page. In the real documentation colors were only used for model axes to better explain what color corresponds to what axis name. Coloring other text is just confusing since it may lead the user to think it has to do with the model axes. Also you didn't even color the text with the color it says but used cyan where it says blue on the Coupling Tool page.
-
Corrected - near the perfection!
And about the curious "double pt2" railways on the above image?
-
@unknownuser said:
Corrected - near the perfection!
No.
The path is still wrong.
There still seems to be no difference between the third and forth header level.
There is still colored text where it shouldn't be.
The colored text is now also bold which makes it even harder to read the document.
The attributes for moving parts are sometimes bold, sometimes not.
There are now missing line breaks at the balise page.
It's not near perfection.
It's not even decent.
@unknownuser said:
And about the curious "double pt2" railways on the above image?
Those are the corresponding tracks to use on a double track railroad along with those called pt 1.
-
@unknownuser said:
The path is still wrong.
So it's still wrong also on the documentation, see the image above.
I don't know what I must put!
@unknownuser said:
There still seems to be no difference between the third and forth header level.
I will see that I can make...
@unknownuser said:
There is still colored text where it shouldn't be.
I can't with my sytem make the same than the colored arounded text
@unknownuser said:
The colored text is now also bold which makes it even harder to read the document.
Easy to change
@unknownuser said:
The attributes for moving parts are sometimes bold, sometimes not.
Easy to change
@unknownuser said:
There are now missing line breaks at the balise page.
Damned!
@unknownuser said:
It's not near perfection.
Perfection is not for this world!
@unknownuser said:
It's not even decent.
I have yet seen worse!
-
@unknownuser said:
@unknownuser said:
The path is still wrong.
So it's still wrong also on the documentation, see the image above.
I don't know what I must put!It should say what it said before you changed it!
@unknownuser said:
@unknownuser said:
There still seems to be no difference between the third and forth header level.
I will see that I can make...
There was already correct headers in the document. You only had to change the text inside the existing elements.
@unknownuser said:
@unknownuser said:
There is still colored text where it shouldn't be.
I can't with my sytem[sic] make the same than the colored arounded[sic] text
Then don't use that system. It was already correct. You only had to change the text. Not recreate the document from scratch.
Also that doesn't even answer what I said. text is colored where it shouldn't be colored. You even changed it to different colors where there shouldn't be any colors in the first place.
@unknownuser said:
@unknownuser said:
It's not near perfection.
Perfection is not for this world!
You we're the one saying it was near perfection, thus bringing the term perfection into the conversation and now you say it shouldn't be perfect.
@unknownuser said:
@unknownuser said:
It's not even decent.
I have yet seen worse!
I've found so many errors it's embarrassing. And that's just about formatting, exact quotes and other things I as someone not speaking French can see. I have no idea what the grammar and spelling is like. I have no idea if the text says what it should say. It could just as well be a cupcake recipe. I don't know if you would even notice if it was a cupcake recipe since you don't seem to have understood the text in the first place when you translate text quoted from the context menu within the plugin.
-
I have created a Spanish Language File with all strings to translate. It's a .txt file that it includes the English string and the corresponding Spanish string:
"English Text"="Spanish Text"
The strings are organized by files i.e. main.rb, balise.rb, balise - index.html, ....
I hope that this file can help you to give support to translate the plugin to all languages. -
@oxer said:
I have created a Spanish Language File with all strings to translate. It's a .txt file that it includes the English string and the corresponding Spanish string:
"English Text"="Spanish Text"
The strings are organized by files i.e. main.rb, balise.rb, balise - index.html, ....
I hope that this file can help you to give support to translate the plugin to all languages.[attachment=0:kyjytomg]<!-- ia0 -->Spanish Language.txt.zip<!-- ia0 -->[/attachment:kyjytomg]
Thanks
. If I add a language system to the plugin I'll include this -
It's a pleasure, you are doing a great work with this incredible plugin.
-
My translation is perfectly understandable by French people : i have tested it!
Hundred persons on many forum
And after some corrections from your advices anybody who read it can use your terrific plugin with great pleasure!
It's a quasi copy cat!The story of color text / emulation as my system can't make exactly the same is that we say in French des "Queues de cerises" !
About perfection : that is just a touch of humor
PS I even made publicity for your plugin at the Paris Maker Faire this past week-end!
Where they where John Bacus and Omar-Pierre Soubra!
This last one said to me (in French that your plugin will be put in front on the next Sketchup exibitions everywhere on the world! -
Version 0.1.12 is now published!
The main new features are a better interface to save rolling stocks to library and support for translations (big thanks to Oxer for Spanish translation now shipped in the extension
).
The new interface for saving rolling stocks along with the improved documentation has made it easier to add rolling stocks to the library. Now rolling stocks can be saved from within any model instead of having to be alone. Images are also automatically generated now even if it's a bit buggy and a better image can be generated manually (more info in documentation). The new dialog for saving rolling stocks now suggests IDs for them so the user doesn't need to worry to much about that either.
To save a rolling stocks to library, select it (after it's initialized) and run Ene_Railroad.ss_2_rs_library to open the dialog (graphical interface to open dialog is planned for a later version).
The translation system allows for translated versions of all strings within the plugin itself. The documentation will however stay in English since it constantly changes.
You can change between available languages in Plugins > Railroad > Change Language.
To translate the plugin download the attached file, add the language name and your name at the top 2 lines. The syntax for the translation is "original string"="translated string". When adding the translation remember to look at the string in its context inside the plugin and be consistent with reoccurring terms such as track and rolling stock. Save the file as <language code>.l10n inside the folder "lang/" in the plugin's folder.
If you want to I can include the translation in the next version
.I hope to see pictures of people's own rolling stocks posted here now
.
-
Incredible work, all work fine on Mac & SU2014.
-
Cool new version!
Let see if I will make better this time!Translation of the text file multi language done!
Must be inserted on the dialog boxes for verification!
(because French text is some bigger than English )
Tomorrow will be made. -
@unknownuser said:
Cool new version!
Let see if I will make better this time!Translation of the text file multi language done!
Must be inserted on the dialog boxes for verification!
(because French text is some bigger than English )
Tomorrow will be made.german language have longer words
german language is ready
dean
-
@deaneau said:
@unknownuser said:
Cool new version!
Let see if I will make better this time!Translation of the text file multi language done!
Must be inserted on the dialog boxes for verification!
(because French text is some bigger than English )
Tomorrow will be made.german language have longer words
german language is ready
dean
It already supports Spanish which has short words but a lot of them so I think it'll work
-
Downloaded new ver. and still get empty dialogue boxes.
-
@mwm5053 said:
Downloaded new ver. and still get empty dialogue boxes.
Odd
. What OS version is it? Do you know if it's older or newer than Oxer's? -
I remember there was the
set_htmlissue (although it was reported not to happen anymore). Is that a possible cause? -
I have the last version of OSX 10.9.4 & Safari 7.0.5, updated yesterday and for me all work fine.
Advertisement