Translated using Weblate (Hindi)

[kritikarag]

Currently translated at 100.0% (359 of 359 strings)

Translation: Fortran programming language/Fortran package manager
Translate-URL: https://hosted.weblate.org/projects/fortran-lang/fpm/pt/

[arteevraina]

I have requested some changes on this PR @kritikarag.
Can you point me to the hosted url that has these changes ?

[kritikarag]

Hi @arteevraina can you please review this again?

[arteevraina]

Code looks good to me. But, when I locally built it, it only showed tranlations for some specific strings. Not for the paragraphs containing the real documentation like the explantation of FPM and others.

[arteevraina]

For example this:

[kritikarag]

Code looks good to me. But, when I locally built it, it only showed tranlations for some specific strings. Not for the paragraphs containing the real documentation like the explantation of FPM and others.

@arteevraina Hi thank you so much for approving my PR and providing the feedback. Can you tell me what might be the issue here? I tried to figure it out but unfortunately haven't been able to figure out anything.

[arteevraina]

Code looks good to me. But, when I locally built it, it only showed tranlations for some specific strings. Not for the paragraphs containing the real documentation like the explantation of FPM and others.

@arteevraina Hi thank you so much for approving my PR and providing the feedback. Can you tell me what might be the issue here? I tried to figure it out but unfortunately haven't been able to figure out anything.

I don't think you will have to reinvent the wheel here. I would suggest you to first verify if other languages also have the same issue. If not, then just follow the same procedure that has been followed for other languages and it should get solved.

[certik]

Thanks @kritikarag!

Did you translate this by hand, or using some tools like Google Translate?

I noticed FPM is translated as एफपीएम, is that how it should be done, or should rather foreign names like that be just translated as "FPM"?

[certik]

I think this is problematic. The actual text that you have to put into fpm.toml has to be in English, module-naming=true. So I would not translate those technical terms into Hindi, but keep them in English.

[certik]

chatGPT suggests the following instead:

`module-naming=true` के साथ मानक प्रिफ़िक्स सक्षम करें, `module-naming=\"prefixname\"` के साथ कस्टम प्रिफ़िक्स सक्षम करें।

I don't know if it is a better translation, but it recognizes the lines of code and does not translate them, which I think is better.

[kritikarag]

@certik Actually that's a better translation. Apparently different translation tools do give different outputs but no worries since you have pointed this out, I'l go through the whole code once again and make sure that any technical terms stays in the English language only

[kritikarag]

Thanks @kritikarag!

Did you translate this by hand, or using some tools like Google Translate?

I noticed FPM is translated as एफपीएम, is that how it should be done, or should rather foreign names like that be just translated as "FPM"?

@certik Hi actually I used both and for those terms I too had confusion that whether it should be kept in english or should to translated to Hindi as well. That's why you must have observed that at some places that word is in hindi and at some in Englist. Basically I was using translation tools (typing in hindi with an english keyboard is kind of too much pain) and after that was manually correcting the semantics in those machine translated sentences.

But no worries I'll look into the issues and terms you have pointed out and will correct them.

Please do let me know if there is any other changes that I need to make.

Thank you so much for the review.

[certik]

I would not translate the term DateTime here.

[HaoZeke]

As has been noted, much of this PR is auto-translated and I am strongly agaist merging this as is without a full rewrite. Translation tools can only to be a starting point. Also, we needn't maintain this in our codebase since we can get this kind of translation directly from google translate (or even ChatGPT). Unfortunately we don't (yet) have a policy against this, but I would be in favor of closing this out and making smaller PRs. This is too unweildy to translate in one shot. What we should do is:

• Pick a section, translate it (maybe open a draft with different language translation tools)
• Discuss with at-least two or more community members as to what would be semantically good
• Try it out on a native speaker without any introduction

Once this is done, then that section can be merged.

Maintaining a copy of auto-translation is definitely not a good idea. None of the text currently makes any sense from a native speaker perspective.

What the Hindi translation needs to be is inclusive (which in this case means simpler in a lot of situations) and concise. I think much of this can be simplified, and made a lot more streamlined.

For this PR, I would suggest focusing on a single section, and moving forward with that. Don't strive for 100%, it would be good to have the logic and format and workflow of the translation worked out here instead of aiming for 100%.

[HaoZeke]

Phonetic conversion of programming terms?

[kritikarag]

@HaoZeke Okay I did said that I used translation tools because it's really hard to type hindi letters using an english keyboard, but I'm really sorry to say that your claim that the whole document was auto-translated in one go is simply incorrect. The whole translation took me 13 days to finish, I literally had been reviewing each and every word of this translation and had been working on the semantics (I was trying on chagpt, google translate and microsoft translate but hardly any of them were giving a proper translation with proper semantics, I myself had to make changes in the words in each line). For the phonetic conversion of programming terms I had already stated wasn't sure that whether I should write them in English or in Hindi (I've seen both on different sites) so I just left it as it was and had been waiting since days for someone to review it (I got a review from another native community member like 2 weeks ago with a green signal) and now also I'm ready to do as per suggested but again I would apologize the translation that I've made is not just totally auto translated and something that was just done in one shot. But fine if the only solution is to rewrite it(full code or just some sections of it) then I'll do it (again I'm not sure how am I gonna do it simply without not using auto-translation but I'll figure something out), just I don't think I'll able to work on this up until next week because my final semester exams are going on.

[certik]

@kritikarag we appreciate your work! 13 days is a lot of time, thank you for putting so much effort into it. I am sorry if @HaoZeke or my feedback felt critical. All we want is a high quality translation that makes sense to maintain. Let's keep this PR open and let's simply break it up into smaller chunks and several PRs that several native speakers can review and if they all agree that the translation is good and natural, then we merge it one by one. You can start with my suggestion below, that is just one paragraph and that can be done, and then once we get into the workflow it will go fast. Take your time, there is no rush. If you have any questions or doubts, or want to discuss it more, I am always available.

[kritikarag]

@certik No that's totally fine infact I'm really grateful for your suggestions and will start working on that paragraph keeping your suggestions in my mind ASAP.

[HaoZeke]

Suggested change

	msgstr "फोरट्रान पैकेज प्रबंधक (एफपीएम) के प्रलेखन में आपका स्वागत है"
	msgstr "फोरट्रान पैकेज प्रबंधक (एफपीएम) के प्रलेखन में आपका स्वागत है"

I'm not sure this usage is common in technical documentation.

[certik]

Thanks @HaoZeke, I agree, the translation must be high quality and feel natural to native speakers.

@kritikarag let's do the following: let's start small, and get just one paragraph translated to Hindi, but let's do it properly. So let's take this one:

#: ../../pages/design/index.md:9
msgid ""
"Fortran Package Manager (fpm) is a package manager and build system for "
"Fortran. Its key goal is to improve the user experience of Fortran "
"programmers. It does so by making it easier to build your Fortran program or "
"library, run the executables, tests, and examples, and distribute it as a "
"dependency to other Fortran projects. Fpm's user interface is modeled after "
"[Rust's Cargo](https://doc.rust-lang.org/cargo/). Its long term vision is to "
"nurture and grow the ecosystem of modern Fortran applications and libraries."
msgstr ""
""

And let's translate it by hand. You can use tools if you don't know how to translate some English term, but the translation must feel natural, as @HaoZeke mentioned, I recommend following his bullet points.

Translation in general is a lot of work, and as @HaoZeke said, unless we can have a high quality native translation, it's better to not have it and people can just use these automatic translation tools like Google Translate to get a very decent idea and rough translation into almost any language.

@kritikarag I fully understand if you don't have time for this. As you can see, I have not provided a Czech translation either yet, as I didn't have time yet that it would take. But if you want to give it a shot and do one paragraph, I think that would be great.

We need to also create a document with guidance how to do these translations, but until we have it, the above is how we should approach it.

[kritikarag]

@certik Thank you so much I would pick this up soon.