Update translation files

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Co-authored-by: Hosted Weblate <[email protected]>
Translate-URL: https://hosted.weblate.org/projects/pypa/packaging-python-org/
Translation: pypa/packaging.python.org

Author: weblate

locales/ar/LC_MESSAGES/messages.po

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python Packaging User Guide\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-05-17 20:46+0000\n"
+"POT-Creation-Date: 2025-05-18 19:05+0000\n"
 "PO-Revision-Date: 2025-01-19 01:44+0000\n"
 "Last-Translator: Mohamed Brahimi <[email protected]>\n"
 "Language-Team: Arabic <https://hosted.weblate.org/projects/pypa/packaging-"
@@ -48,7 +48,7 @@ msgid "Writing new content"
 msgstr ""
 
 #: ../source/contribute.rst:14
-msgid "Translate the guide"
+msgid "Translating the guide"
 msgstr ""
 
 #: ../source/contribute.rst:16
@@ -1873,7 +1873,7 @@ msgstr ""
 
 #: ../source/discussions/pip-vs-easy-install.rst:14
 msgid ""
-":ref:`pip` came later in 2008, as alternative to :ref:`easy_install "
+":ref:`pip` came later in 2008, as an alternative to :ref:`easy_install "
 "<easy_install>`, although still largely built on top of :ref:`setuptools` "
 "components.  It was notable at the time for *not* installing packages as :"
 "term:`Eggs <Egg>` or from :term:`Eggs <Egg>` (but rather simply as 'flat' "
@@ -2714,7 +2714,7 @@ msgid ""
 "There are known exceptions for selecting the next version number. The "
 "maintainers may consciously choose to break the assumption that the last "
 "version segment only contains backwards-compatible changes. One such case is "
-"when security vulnerability needs to be addressed. Security releases often "
+"when a security vulnerability needs to be addressed. Security releases often "
 "come in patch versions but contain breaking changes inevitably."
 msgstr ""
 
@@ -2790,7 +2790,7 @@ msgstr ""
 #: ../source/discussions/versioning.rst:126
 msgid ""
 "Semantic versioning is not a suitable choice for all projects, such as those "
-"with a regular time based release cadence and a deprecation process that "
+"with a regular time-based release cadence and a deprecation process that "
 "provides warnings for a number of releases prior to removal of a feature."
 msgstr ""
 
@@ -2829,7 +2829,7 @@ msgstr ""
 #: ../source/discussions/versioning.rst:150
 msgid ""
 "Combinations of the above schemes are possible. For example, a project may "
-"combine date based versioning with serial versioning to create a *year."
+"combine date-based versioning with serial versioning to create a *year."
 "serial* numbering scheme that readily conveys the approximate age of a "
 "release, but doesn't otherwise commit to a particular release cadence within "
 "the year."
@@ -4479,8 +4479,8 @@ msgstr ""
 #: ../source/guides/creating-command-line-tools.rst:7
 msgid ""
 "This guide will walk you through creating and packaging a standalone command-"
-"line application that can be installed with :ref:`pipx`, a tool creating and "
-"managing :term:`Python Virtual Environments <Virtual Environment>` and "
+"line application that can be installed with :ref:`pipx`, a tool for creating "
+"and managing :term:`Python Virtual Environments <Virtual Environment>` and "
 "exposing the executable scripts of packages (and available manual pages) for "
 "use on the command-line."
 msgstr ""
@@ -4550,7 +4550,7 @@ msgid ""
 "The file :file:`__main__.py` marks the main entry point for the application "
 "when running it via :mod:`runpy` (i.e. ``python -m greetings``, which works "
 "immediately with flat layout, but requires installation of the package with "
-"src layout), so initizalize the command-line interface here:"
+"src layout), so initialize the command-line interface here:"
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:111
@@ -4619,7 +4619,7 @@ msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:165
 msgid ""
-"This syntax is a bit unpractical, however; as the name of the entry point we "
+"This syntax is a bit impractical, however; as the name of the entry point we "
 "defined above does not match the package name, we need to state explicitly "
 "which executable script to run (even though there is only on in existence)."
 msgstr ""
@@ -6484,7 +6484,7 @@ msgstr ""
 
 #: ../source/guides/installing-using-pip-and-virtual-environments.rst:203
 msgid ""
-"For example,let's install the `Requests`_ library from the :term:`Python "
+"For example, let's install the `Requests`_ library from the :term:`Python "
 "Package Index (PyPI)`:"
 msgstr ""
 
@@ -10260,7 +10260,7 @@ msgstr ""
 
 #: ../source/index.rst:82
 msgid ""
-"The :doc:`discussions/index` section for in-depth explanations and "
+"The :doc:`discussions/index` section provides in-depth explanations and "
 "discussion about topics, such as:"
 msgstr ""
 
@@ -22728,10 +22728,10 @@ msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:8
 msgid ""
-"The current standard format of source distribution format is identified by "
-"the presence of a :file:`pyproject.toml` file in the distribution archive.  "
-"The layout of such a distribution was originally specified in :pep:`517` and "
-"is formally documented here."
+"The current standard source distribution format is identified by the "
+"presence of a :file:`pyproject.toml` file in the distribution archive.  The "
+"layout of such a distribution was originally specified in :pep:`517` and is "
+"formally documented here."
 msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:13
@@ -22757,7 +22757,7 @@ msgstr ""
 msgid ""
 "A *source tree* is a collection of files and directories -- like a version "
 "control system checkout -- which contains a :file:`pyproject.toml` file that "
-"can be use to build a source distribution from the contained files and "
+"can be used to build a source distribution from the contained files and "
 "directories. :pep:`517` and :pep:`518` specify what is required to meet the "
 "definition of what :file:`pyproject.toml` must contain for something to be "
 "deemed a source tree."
@@ -23323,7 +23323,7 @@ msgstr ""
 
 #: ../source/specifications/version-specifiers.rst:229
 msgid ""
-"Date based release segments are also permitted. An example of a date based "
+"Date-based release segments are also permitted. An example of a date-based "
 "release scheme using the year and month of the release::"
 msgstr ""
 

locales/ars/LC_MESSAGES/messages.po

@@ -6,7 +6,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python Packaging User Guide\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-05-17 20:46+0000\n"
+"POT-Creation-Date: 2025-05-18 19:05+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: Automatically generated\n"
 "Language-Team: none\n"
@@ -42,7 +42,7 @@ msgid "Writing new content"
 msgstr ""
 
 #: ../source/contribute.rst:14
-msgid "Translate the guide"
+msgid "Translating the guide"
 msgstr ""
 
 #: ../source/contribute.rst:16
@@ -1867,7 +1867,7 @@ msgstr ""
 
 #: ../source/discussions/pip-vs-easy-install.rst:14
 msgid ""
-":ref:`pip` came later in 2008, as alternative to :ref:`easy_install "
+":ref:`pip` came later in 2008, as an alternative to :ref:`easy_install "
 "<easy_install>`, although still largely built on top of :ref:`setuptools` "
 "components.  It was notable at the time for *not* installing packages as :"
 "term:`Eggs <Egg>` or from :term:`Eggs <Egg>` (but rather simply as 'flat' "
@@ -2708,7 +2708,7 @@ msgid ""
 "There are known exceptions for selecting the next version number. The "
 "maintainers may consciously choose to break the assumption that the last "
 "version segment only contains backwards-compatible changes. One such case is "
-"when security vulnerability needs to be addressed. Security releases often "
+"when a security vulnerability needs to be addressed. Security releases often "
 "come in patch versions but contain breaking changes inevitably."
 msgstr ""
 
@@ -2784,7 +2784,7 @@ msgstr ""
 #: ../source/discussions/versioning.rst:126
 msgid ""
 "Semantic versioning is not a suitable choice for all projects, such as those "
-"with a regular time based release cadence and a deprecation process that "
+"with a regular time-based release cadence and a deprecation process that "
 "provides warnings for a number of releases prior to removal of a feature."
 msgstr ""
 
@@ -2823,7 +2823,7 @@ msgstr ""
 #: ../source/discussions/versioning.rst:150
 msgid ""
 "Combinations of the above schemes are possible. For example, a project may "
-"combine date based versioning with serial versioning to create a *year."
+"combine date-based versioning with serial versioning to create a *year."
 "serial* numbering scheme that readily conveys the approximate age of a "
 "release, but doesn't otherwise commit to a particular release cadence within "
 "the year."
@@ -4473,8 +4473,8 @@ msgstr ""
 #: ../source/guides/creating-command-line-tools.rst:7
 msgid ""
 "This guide will walk you through creating and packaging a standalone command-"
-"line application that can be installed with :ref:`pipx`, a tool creating and "
-"managing :term:`Python Virtual Environments <Virtual Environment>` and "
+"line application that can be installed with :ref:`pipx`, a tool for creating "
+"and managing :term:`Python Virtual Environments <Virtual Environment>` and "
 "exposing the executable scripts of packages (and available manual pages) for "
 "use on the command-line."
 msgstr ""
@@ -4544,7 +4544,7 @@ msgid ""
 "The file :file:`__main__.py` marks the main entry point for the application "
 "when running it via :mod:`runpy` (i.e. ``python -m greetings``, which works "
 "immediately with flat layout, but requires installation of the package with "
-"src layout), so initizalize the command-line interface here:"
+"src layout), so initialize the command-line interface here:"
 msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:111
@@ -4613,7 +4613,7 @@ msgstr ""
 
 #: ../source/guides/creating-command-line-tools.rst:165
 msgid ""
-"This syntax is a bit unpractical, however; as the name of the entry point we "
+"This syntax is a bit impractical, however; as the name of the entry point we "
 "defined above does not match the package name, we need to state explicitly "
 "which executable script to run (even though there is only on in existence)."
 msgstr ""
@@ -6478,7 +6478,7 @@ msgstr ""
 
 #: ../source/guides/installing-using-pip-and-virtual-environments.rst:203
 msgid ""
-"For example,let's install the `Requests`_ library from the :term:`Python "
+"For example, let's install the `Requests`_ library from the :term:`Python "
 "Package Index (PyPI)`:"
 msgstr ""
 
@@ -10254,7 +10254,7 @@ msgstr ""
 
 #: ../source/index.rst:82
 msgid ""
-"The :doc:`discussions/index` section for in-depth explanations and "
+"The :doc:`discussions/index` section provides in-depth explanations and "
 "discussion about topics, such as:"
 msgstr ""
 
@@ -22722,10 +22722,10 @@ msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:8
 msgid ""
-"The current standard format of source distribution format is identified by "
-"the presence of a :file:`pyproject.toml` file in the distribution archive.  "
-"The layout of such a distribution was originally specified in :pep:`517` and "
-"is formally documented here."
+"The current standard source distribution format is identified by the "
+"presence of a :file:`pyproject.toml` file in the distribution archive.  The "
+"layout of such a distribution was originally specified in :pep:`517` and is "
+"formally documented here."
 msgstr ""
 
 #: ../source/specifications/source-distribution-format.rst:13
@@ -22751,7 +22751,7 @@ msgstr ""
 msgid ""
 "A *source tree* is a collection of files and directories -- like a version "
 "control system checkout -- which contains a :file:`pyproject.toml` file that "
-"can be use to build a source distribution from the contained files and "
+"can be used to build a source distribution from the contained files and "
 "directories. :pep:`517` and :pep:`518` specify what is required to meet the "
 "definition of what :file:`pyproject.toml` must contain for something to be "
 "deemed a source tree."
@@ -23317,7 +23317,7 @@ msgstr ""
 
 #: ../source/specifications/version-specifiers.rst:229
 msgid ""
-"Date based release segments are also permitted. An example of a date based "
+"Date-based release segments are also permitted. An example of a date-based "
 "release scheme using the year and month of the release::"
 msgstr ""