airflow icon indicating copy to clipboard operation
airflow copied to clipboard

feat(i18n): add Hindi (hi) translation support to UI

Open anandkaranubc opened this issue 5 months ago • 6 comments

Add Hindi translations for Airflow UI

This PR adds support for Hindi (hi) translations in the Airflow UI. It includes the initial common.json and other relevant files in airflow-core/src/airflow/ui/src/i18n/locales/hi.

related: #51280 & #9864


^ Add meaningful description above Read the Pull Request Guidelines for more information. In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed. In case of a new dependency, check compliance with the ASF 3rd Party License Policy. In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

anandkaranubc avatar Jun 02 '25 02:06 anandkaranubc

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst) Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits. Apache Airflow is a community-driven project and together we are making it better 🚀. In case of doubts contact the developers at: Mailing List: [email protected] Slack: https://s.apache.org/airflow-slack

boring-cyborg[bot] avatar Jun 02 '25 02:06 boring-cyborg[bot]

Thanks @rawwar, @vatsrahul1001 and @sunank200 for the review!

anandkaranubc avatar Jun 02 '25 14:06 anandkaranubc

Thanks for the contribution! As we are discussing the new i18n challnges and alongside a required policy in https://lists.apache.org/thread/d8grrtqg2p1mpcccqqozg9ld9pnn8zf2 I assume we should at least consider the points which have not finally being votes but which might be required.

Would there be anybody raising his handfor taking the lead as committer to be the CODEOWNER for future maintenance? I assume we have a couple of native speakers here. Additional people (non-commiter) who volunteer as native advocate are also welcome. Not limited to one, preferrably two? More also possible but assuming a regular check and contribution in future will be needed to maintain language over time.

FYI @shubhamraj-git also as UI codeowner would you be a candidate as well?

jscheffl avatar Jun 02 '25 20:06 jscheffl

Let's rebase and try to include more translations now that the english files are complete.

bbovenzi avatar Jun 12 '25 16:06 bbovenzi

@bbovenzi The rebase is done! Thanks for the feedback!

anandkaranubc avatar Jun 12 '25 16:06 anandkaranubc

Oops sorry. I didn't realize there were amendments to the english files. Turning it into draft and will get back with the new changes.

anandkaranubc avatar Jun 12 '25 17:06 anandkaranubc

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Aug 05 '25 00:08 github-actions[bot]

Can we rebase this and get Hindi in for 3.1.0?

bbovenzi avatar Aug 18 '25 20:08 bbovenzi

Thanks for the contribution! As we are discussing the new i18n challnges and alongside a required policy in https://lists.apache.org/thread/d8grrtqg2p1mpcccqqozg9ld9pnn8zf2 I assume we should at least consider the points which have not finally being votes but which might be required.

Would there be anybody raising his handfor taking the lead as committer to be the CODEOWNER for future maintenance? I assume we have a couple of native speakers here. Additional people (non-commiter) who volunteer as native advocate are also welcome. Not limited to one, preferrably two? More also possible but assuming a regular check and contribution in future will be needed to maintain language over time.

FYI @shubhamraj-git also as UI codeowner would you be a candidate as well?

@vatsrahul1001 is interested to be the CODEOWNER for Hindi translation 🎉 He can take this PR forward

phanikumv avatar Aug 20 '25 06:08 phanikumv

@vatsrahul1001 is interested to be the CODEOWNER for Hindi translation 🎉 He can take this PR forward

NICE!

potiuk avatar Aug 20 '25 12:08 potiuk

Closing in favor of https://github.com/apache/airflow/pull/54788

pierrejeambrun avatar Aug 22 '25 09:08 pierrejeambrun