Actually, the interface is pretty much 100% translated (English).
I'm talking about the code and some internal parmeters which are sometimes exposed (see attachments).
It also sometimes happens that non-numeric values in a material stream are shown with portugese strings (translation of non numerical number, I suppose) when in the stream specification form.
My point is that all code should be written in English for everybody 100% comprehension and usage.
I see. I already thought about it, obviously, but it is not so simple AND it would break binary serialization, that is, every single simulation saved in binary format would stop working as soon as I changed the name of a variable, for instance. Not to tell that this is a huge amount of work...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you give some examples of untranslated text, where they are?
Actually, the interface is pretty much 100% translated (English).
I'm talking about the code and some internal parmeters which are sometimes exposed (see attachments).
It also sometimes happens that non-numeric values in a material stream are shown with portugese strings (translation of non numerical number, I suppose) when in the stream specification form.
My point is that all code should be written in English for everybody 100% comprehension and usage.
I see. I already thought about it, obviously, but it is not so simple AND it would break binary serialization, that is, every single simulation saved in binary format would stop working as soon as I changed the name of a variable, for instance. Not to tell that this is a huge amount of work...
Fixed as much as possible in 4.0 Preview 1.