DaoKakao Posted August 14, 2017 Share Posted August 14, 2017 Hi, folks! I'd like to ask the managing team - whether translation approvements planned? Or whether you plan to extend the translators/proofreaders team in order to speedup translation/l10n process? Best regards Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 And what exactly is your problem? Why don't you just approve the Russian translation. ;) Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 Sorry, my mistake. Now i can... Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 Another question: should the FIELDNAMES be translated from english? Could anyone clarify this question? Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 Actually ... yes! You find these items displayed in the admin section Localization --> Countries --> --->Address display -->Required fields for the address Helpful for foreign users with no or poor English skills to understand the fields' meanings in the left Address format. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 @occam Thank you for clarificatoin! Another issue i've found yet in PrestaShop: In Russian language "FROM" and "TO" could be translated two diffferent ways, depending on context. For instance, when we talk about "Start date" in the report - it has one translation, and when we talk about "source" when copying translation or file, then it should be different translation. Is it possible to take in account that and make distinction for such cases? Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 In German we have the same problem. Another example would be the item title. To avoid gross errors in translation we decided for PrestaShop some years ago to create a distinct item named social title. This is the PrestaShop ... pardon ... thirty bees' Stairway to heaven: :musicalnote: *"'Cause you know sometimes words have two meanings ...* :musicalnote: :) Actually, depending on the context there may even be more than two different meanings for e.g. title. Sometimes it is not possible to make distinctions, so you need to translate carefully and always mind the context. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 Exactly, agree for 146%! It was a headache with that 'title', i was wondered, why not 2 use the 'gender' or 'sex' for some cases? Another such bright-shining sentence is plural and single parts of phrases. Everything is Ok in English 'coz strictly one form for plural, but in Russian there's 3 forms of plural. :) Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 Thanks for this gender hint. In blocknewsletter there is an item gender that has the meaning of social title, whereas the gender in AdminGenders (Hashcode: AdminGenders019ec3132cdf8ee0f2e2a75cf5d3e459) really means gender. Not to mention the menu item Ttitles in Admin --> Customers --> Titles. This should be corrected to the real meaning Social Titles. It's no automatism, changing the name to thirty bees alone does not guarantee a correct source code for the translations. ;) And btw, in the German translation I often ignored the use of plural and single and prefered a consistent translation. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 Again agree! During the PS translation i was confused with exactly same sentences you've mentioned. I really wondered, why such ugly/overcomplicated mixture of (almost)same terms appeared. Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 You really ask why? Just because many of the programmers had to look up their source code in the absence of English language skills. Therefor these sometimes unbelievable mistakes. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 No, i did not. I wonder something slightly different - an absence of any kind of co-ordination / orchestration of such different-skilled devs. IMHO, exactly that is an obstacle for PS(and its clones) to turn into industrial-class player. Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 @daokakao said in Translation: I wonder something slightly different - an absence of any kind of co-ordination / orchestration of such different-skilled devs. Oh, they did, but far too late. Alexandra does a very good job since, and her English skills in conversation and writing are excellent. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 16, 2017 Author Share Posted August 16, 2017 Alexandra was the only who had a lot of energy to push the project forward (i talking about l10n part). But latest time i didn't saw her activity in the crowdin and/or PS forums. Pity... Link to comment Share on other sites More sharing options...
Occam Posted August 16, 2017 Share Posted August 16, 2017 Looks like she's still active (last time this evening). Link to comment Share on other sites More sharing options...
Traumflug Posted August 17, 2017 Share Posted August 17, 2017 @DaoKakao I really wondered, why such ugly/overcomplicated mixture of (almost)same terms appeared. Because there's more than one person involved in writing code. Each person has its own preferences on how to write code, this applies not only to translatable strings. And then ... well, when writing code, using elegant language in texts isn't exactly top priority. Code writers watch out much more for the code doing what it should do. That said, if you find such mismatching use of human language, don't hesitate to report them as code bugs (on Github). Changing such wording doesn't change how the code works, so it's easily replaceable. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 17, 2017 Author Share Posted August 17, 2017 I just tried to hint one simple thing, such as metrology. When i studied in the university, yet from the very beginning all teachers just hammered this subject in student's heads. Link to comment Share on other sites More sharing options...
Occam Posted August 17, 2017 Share Posted August 17, 2017 @traumflug said in Translation: @DaoKakao I really wondered, why such ugly/overcomplicated mixture of (almost)same terms appeared. Because there's more than one person involved in writing code. Each person has its own preferences on how to write code, this applies not only to translatable strings. And then ... well, when writing code, using elegant language in texts isn't exactly top priority. Code writers watch out much more for the code doing what it should do. That said, if you find such mismatching use of human language, don't hesitate to report them as code bugs (on Github). Changing such wording doesn't change how the code works, so it's easily replaceable. Nice try, but we're talking about translation items imported fom PrestaShop which have been messed up since years. And already in 2013 Francois and I had prepared a handout for the developers in order to harmonize the wording or at least the spelling. But things changed not until PrestaShop engaged a person reponsible for this with the authority to decide how the translatable strings had to look like. What we are dealing with here is to large extend a burden of the past! Link to comment Share on other sites More sharing options...
Traumflug Posted August 18, 2017 Share Posted August 18, 2017 @Occam Nice try, but we’re talking about translation items imported fom PrestaShop which have been messed up since years. Because PS failed to improve the situation thirty bees is doomed? Come on, I've heard better excuses. Link to comment Share on other sites More sharing options...
Occam Posted August 18, 2017 Share Posted August 18, 2017 @Traumflug My advice for you: Read carefully ... reflect ... then answer. ? You're barking up the wrong tree. Link to comment Share on other sites More sharing options...
DaoKakao Posted August 18, 2017 Author Share Posted August 18, 2017 It's a pity that admins approved all unapproved sentences in one fell swoop... I hoped to go thru translation thorougly, because it has some stylistic, semantic and syntax mistakes. Will it be a great insolence to ask @mdekker to revert this? Link to comment Share on other sites More sharing options...
DaoKakao Posted August 18, 2017 Author Share Posted August 18, 2017 Russian Link to comment Share on other sites More sharing options...
DaoKakao Posted August 18, 2017 Author Share Posted August 18, 2017 Want to start from position at the morning, i've already made near 40% of checks/approves Link to comment Share on other sites More sharing options...
DaoKakao Posted August 18, 2017 Author Share Posted August 18, 2017 Strange... Well, nevermind. I'll go thru approved and check again Link to comment Share on other sites More sharing options...
DaoKakao Posted August 18, 2017 Author Share Posted August 18, 2017 Pl, don't worry. Most of sentences are ok. I've been worrying more about some sentences which are same in english, but has different translations in Russian, depending on context. Fortunately, there's very few of such issues. What should i do in that cases? Open an issue in github? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now