Update CLDR to version 42

[OzancanKaratas]

Link to issue number:

Related nvda-cldr update: nvaccess/nvda-cldr#3

Summary of the issue:

Periodically CLDR update: CLDR team released version 42 of the CLDR package.

Description of user facing changes

New emojis and characters

Description of development approach

None

Testing strategy:

Use your favorite emoji provider like emojipedia.org

Known issues with pull request:

None

Change log entries:

Changes

• Update CLDR to version 42. (Update CLDR to version 42 #14273)

Code Review Checklist:

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

[LeonarddeR]

I'm getting the following error on multiple systems when updating submodules:

fatal: transport 'file' not allowed                                                                                     
fatal: Fetched in submodule path 'nvda-cldr', but it did not contain 8e98c77fc3cdb33cf6d530f27f82c972ef3d93c0. Direct fetching of that commit failed.                                                                                           

[zstanecic]

Strange, when u have updated RHVoice language support, I was able to successfully update this. From: Leonard de Ruijter ***@***.***> Sent: Friday, October 21, 2022 7:42 AM To: nvaccess/nvda ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [nvaccess/nvda] Update CLDR to version 42 (PR #14273) I'm getting the following error on multiple systems when updating submodules: fatal: transport 'file' not allowed fatal: Fetched in submodule path 'nvda-cldr', but it did not contain 8e98c77fc3cdb33cf6d530f27f82c972ef3d93c0. Direct fetching of that commit failed. — Reply to this email directly, view it on GitHub <#14273 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVCDEYEWHAO7B2U5P5TAXDWEIUJ7ANCNFSM6AAAAAARJGMYUU> . You are receiving this because you are subscribed to this thread. <https://github.com/notifications/beacon/ACVCDEZGLOIGTLPNHBH2Z5TWEIUJ7A5CNFSM6AAAAAARJGMYUWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSMVY4XS.gif> Message ID: ***@***.*** ***@***.***> >

[vielmetti]

This is almost certainly CVE-2022-39253 which prompted changes in git
due to security problems identified.

You may find this issue summary useful with an account of some workarounds
done by other projects to get around the "fatal: transport 'file' not allowed" problem.

https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html