Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@holidays/locale/kn/LC_MESSAGES/NP.po`:
- Around line 1-29: The NP.po file's headers/msgids may be out of sync with
source; re-generate and validate the Kannada Nepal localization rather than
manually editing the .po: run the project's localization build (e.g., make l10n)
and then run msgfmt --check on holidays/locale/kn/LC_MESSAGES/NP.po to catch
msgid mismatches (verify the empty msgid/msgstr header block and
X-Source-Language: ne match source), and if translator comments (#.) are wrong,
update the original Python source strings (not the .po) and re-run the generator
so the comments and msgids are produced correctly.
- Around line 155-158: The PO entry's msgid "भाईटीका" does not exactly match the
string used in the code (tr("भाइटीका")), so update the msgid to "भाइटीका" to
match the code's tr(...) call exactly; locate the msgid in the NP.po file and
replace the current msgid value with the single-आई form "भाइटीका" so the
translation is found at runtime.
- Around line 63-66: The PO file msgid for Duwadashi is misspelled and won't
match the source lookup; update the msgid in
holidays/locale/kn/LC_MESSAGES/NP.po from "द्वादशी (दशैं)" to exactly match the
source call tr("दुवादशी (दशैं)"), and optionally adjust the Kannada translation
msgstr ("ದ್ವಾದಶಿ (ದಸರಾ)") to a more accurate transliteration of "दुवादशी" if
desired so the msgid and tr(...) string in countries/nepal.py match exactly.

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="holidays/locale/kn/LC_MESSAGES/NP.po">

<violation number="1" location="holidays/locale/kn/LC_MESSAGES/NP.po:64">
P2: This `msgid` does not match the project’s NP source string, so the translation key won’t be resolved at runtime.

(Based on your team's feedback about keeping the correct generated string set in `.po` files.) [FEEDBACK_USED]</violation>

<violation number="2" location="holidays/locale/kn/LC_MESSAGES/NP.po:156">
P2: This `msgid` key is misspelled relative to the source catalog, so this translation entry won’t be used.</violation>
</file>

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@holidays/countries/nepal.py`:
- Line 57: Update the supported_languages tuple in nepal.py so entries are
alphabetically ordered and properly spaced: swap "kn" and "ne" to make the tuple
("en_US", "kn", "ne") and ensure there's a space after the comma separating
entries; edit the supported_languages definition to reflect this change.

In `@README.md`:
- Line 1245: The language list in the table cell containing "en_US,
<strong>ne</strong>, kn" is out of alphabetical order; update that TD so the
languages are alphabetized with the bold default kept in place (i.e., change the
order to "en_US, kn, <strong>ne</strong>" or equivalent), ensuring the <strong>
tag remains on the default language token and only the sequence of tokens is
reordered.

In `@tests/countries/test_nepal.py`:
- Line 690: Remove the four trailing spaces on the blank line immediately
following the closing parenthesis in the test (i.e., delete the stray whitespace
on the blank line after the previous line's “)”), save the file so the blank
line contains no trailing whitespace, and run ruff/formatting to confirm the
trailing-whitespace lint is fixed.

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@README.md`:
- Line 1245: The table row containing the token "en_US, ne, kn" is out of
alphabetical order; edit the HTML table cell (<td>...) that currently reads
"en_US, ne, kn" and reorder the language codes to "en_US, kn, ne" while keeping
the existing emphasis markup (e.g., the <strong> wrapper around ne) intact so
the row reads "en_US, kn, <strong>ne</strong>".

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="tests/countries/test_nepal.py">

<violation number="1" location="tests/countries/test_nepal.py:652">
P2: Remove the whitespace-only line at the end of the test block; it violates the repo’s trailing-whitespace linting checks.</violation>
</file>