Right now besides just “Spanish” in crowdin there’s also 3 more variations of spanish available:
crowdin_spanish_variations.png
what do we want these for? Why split the translation effort? Are there any meaningful differences in technical terminologies to warrant 3 latinoamerican variations? IMO at most we should have “Spanish” and “Spanish, Latinoamerica” (or however that’s usually called).
Señores no seamos absurdamente fanáticos de cada país, mejor nos ayudamos entre todos y mejoramos lo ya existente en vez de seguir creando variaciones que no van para ningun lado.
It’s not about being a fanatic, but about adjusting to the standards that each country has. When I began to translate in the supposedly official Spanish, I found that it was impossible to agree with a majority that does not know the technical drawing standards of my country.
Why deny the possibility of using FreeCAD without having to find unpleasant translations that do not conform to those standards?
Beyond that, should I give up the hours of selfless dedication to the project?
Like I said I can understand having a latinoamerican variation, but do we really need 3 variations? How much difference is there between Argentina, Venezuela and Colombia? Is it really better to have a translation that covers 25% of the app but uses your minor regional differences or one that covers 90% where a couple of words look a little odd to you?
Did you try changing the words you didn’t like on the existing translation?
btw the Argentina variant is pretty advanced by now so if we do something I would like to turn that one into a general lationamerican variation not delete it. The other two can probably be removed though.
In any case if we really have some things that can’t be reconciled between what’s used in each country (which I doubt) it would be better to start of from a common spanish base and change only what doesn’t fit. I wonder if it’s possible to make composite translations to automate something like that.
Another problem is the wiki, somehow the documentation on the wiki should be coherent with the program, so, any variance in the terms used in the program could cause confusion.
I agree, tipically localization for Spanish is either a single neutral es, or alternativelly es_ES and es_la. In the context of FreeCAD, a CAD program all the mathematics, physics, engineering it’s the same, so what’s the difference, the verb conjugations, the way in which we elaborate statements? I mean this is an engineering software not media.
What are the most disruptive changes between es_AR and es_ES?
Yeah, Venezuela has no changes in one year, and Colombia very few.
Edit:
But with no doubts the Spanish localization is quite tricky due variations of the language, look at those other languages FreeCAD is being translated, most of them are from a single country. Trivia: Natively, Arabic, English and French are spoken in more countries than Spanish is and yet we don’t see n Arabic/English/French translations (not only in FreeCAD but on any software) source
Step one
you make an effort to make a translation for the language version adopted as the main one.
Step two
you download the translation file. In the local environment, e.g. using QT Linguist, you make adjustments to convert this language version to another.
The next step
you perform an import of the prepared translations into Crowdin for the selected language version.
No special permissions are required in Crowdin for these actions. Any translator can do this. I know people who work this way and get good results with less effort.
Adriansaval, if I can say something regarding several language versions … if there is a person who wants to do it let him work. Do not torpedo these efforts. More users will benefit.
However, in this regard, you must find a common path and decide for yourselves how many dialects should be available for your nationality.
You brought up some very relevant facts. The problem is one language version with a dialect of choice for Wiki documentation.
However, I would not assume that FreeCAD is a program exclusively for engineers. I will not continue this topic …
You always e to do a survey and ask the community for their opinion.
For sure, what I meant is that the science base that makes a CAD programs is the same across countries, what changes the most is the “common” language, (ok, linguistics is more complicated than that) .
In the most basic level if someone creates a dictionary of equivalences between dialects it could be possible to automate string substitutions (nouns should match number and gender but verbs are trickier due to conjugation)
I know people who work this way and get good results with less effort.