Compile l10nUtil.exe with py2exe as one of NVDA's executables, rather than using nuitka which took way too long to compile.

[michaelDCurran]

Link to issue number:

None

Summary of the issue:

l10nUtil (which allows translators to download and upload to Crowdin, and convert xliffs to markdown and html) s currently build using nuitka. However, this takes a significant amount of time. On Appveyor this takes roughly 20 minutes, which is more than a rd of the total build time.In many cases, this pushes the buildtime past 60 minutes and the build is cancelled by appveyor.

Description of user facing changes

None.

Description of development approach

Instead of using Nuitka, compile l10nUtil.exe as one of NVDA's executables using py2exe.
Several modules and packages in lxml and markdown extensions needed to be explicitly listed in setup.py for this to work. Also, l1nutil.py, markdownTranslate.py, md2html.py and keyCommandsDoc.py were moved from user_docs to source, which made it easier to handle with py2exe.
l10nUtil.exe still works just the same, and build time is cut down by at least 19 minutes.

Testing strategy:

Tested l10nUtil downloadTranslationFile, xliff2md and xliff2html.

Known issues with pull request:

To get l10nUtil.exe you now need to download NVDA and eitherinstall or make a portable copy, as l10nUtil.exe is one of the executables inside.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary

[AppVeyorBot]

• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/4wwukoommyswbyy8/artifacts/output/nvda_snapshot_pr17712-35338,115a627d.exe
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.3,
  INSTALL_END 1.1,
  BUILD_START 0.0,
  FINISH_END 17.4

See test results for failed build of commit 115a627d2a

[hwf1324]

Can you clean up the other trailing spaces in requirements.txt by the way?

[AppVeyorBot]

• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/5jm482fdnu4ixbsi/artifacts/output/nvda_snapshot_pr17712-35343,199a1e7f.exe
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.4,
  INSTALL_END 1.1,
  BUILD_START 0.0,
  FINISH_END 18.0

See test results for failed build of commit 199a1e7f65

[AppVeyorBot]

• FAIL: Unit tests. See test results for more information.
• PASS: System tests (tags: installer NVDA).
• PASS: Lint check.
• PASS: Translation comments check.
• CI timing (mins):
  INIT 0.0,
  INSTALL_START 1.2,
  INSTALL_END 1.0,
  BUILD_START 0.0,
  BUILD_END 18.9,
  TESTSETUP_START 0.0,
  TESTSETUP_END 0.4,
  TEST_START 0.0,
  TEST_END 18.7,
  FINISH_END 0.1
• Build (for testing PR): https://ci.appveyor.com/api/buildjobs/axu36edudnoxhqq0/artifacts/output/nvda_snapshot_pr17712-35344,49174e2a.exe
• PASS: License check.

See test results for failed build of commit 49174e2afc

[wmhn1872265132]

Need to be updated.github/workflows/regenerate_english_userDocs_translation_source.yml

python user_docs/markdownTranslate.py updateXliff -x $xliff -m $file -o $tempXliff

[SaschaCowley]

@michaelDCurran

To get l10nUtil.exe you now need to download NVDA and eitherinstall or make a portable copy, as l10nUtil.exe is one of the executables inside.

Couldn't we retain the command to build l10nutil, but make it depend on dist, (or source) and then copy l10nutil from there? We could optionally delete l10nutil from dist (and thus launcher) if we wanted to, since most users won't need it

[CyrilleB79]

How big is it? If it is not too big, from a translator's point of view, it's quite nice to have it already packed in NVDA install.