Merge branch 'master' of https://github.com/nvaccess/nvda into Securi…

…tyandPrivacyNotes

# Conflicts:
#	user_docs/en/userGuide.md

.coderabbit.yml

@@ -0,0 +1,66 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+# https://docs.coderabbit.ai/guides/configure-coderabbit/
+
+language: "en-US"
+early_access: true
+reviews:
+  profile: "chill"
+  high_level_summary: true
+  request_changes_workflow: false
+  review_status: false
+  collapse_walkthrough: false
+  poem: false
+  auto_review:
+    enabled: false
+    auto_incremental_review: false
+    drafts: true
+    base_branches:
+      - master
+      - beta
+      - rc
+  path_instructions:
+    - path: "**/*"
+      instructions: "
+      Focus on code smells, logic errors, edge cases, missing test cases, security flaws and serious issues.
+      Avoid commenting on minor issues such as linting, formatting and style issues.
+      This project uses tabs instead of spaces, do not suggest usage of spaces over tabs.
+      Are there any 'red flags' in this code that might warrant closer investigation from a security standpoint?
+      Explain what makes them suspicious.
+      When providing code suggestions, particularly when requested, ensure GitHub's suggestion format is used, i.e.:
+      ```suggestion
+      <code changes>
+      ```
+      "
+    - path: "**/*.py"
+      instructions: "
+      _, pgettext, ngettext, and ngettext are defined globally, errors for this being undefined can be ignored.
+      "
+    - path: "**/*.md"
+      instructions: "
+      Focus on grammar, spelling, and punctuation.
+      Also consider readability and clarity of contents.
+      Ensure that changes follow the style of one sentence per line, suggest changes if this is not met.
+      "
+    - path: "user_docs/en/changes.md"
+      instructions: "
+      Ensure each change log entry references an issue or pull request number.
+      Change log entries can also include a reference to a GitHub author.
+      Examples of valid change log entries:
+      * Item with sub-items (#123, @username):
+        * sub-item
+        * bar (#342)
+      * Item with.
+      Multiple lines. (#143)
+      "
+  tools:
+    github-checks:
+      enabled: true
+    ruff:
+      enabled: true
+    markdownlint:
+      # We use custom markdown syntax such as {#Anchor} for anchors.
+      # This is not supported by markdownlint.
+      # In future we plan to introduce markdownlint directly with custom rules. (#16453)
+      enabled: false
+chat:
+  auto_reply: true

.editorconfig

@@ -0,0 +1,12 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+
+[*.{cpp,h,py}]
+charset = utf-8
+indent_style = tab
+tab_width = 4
+trim_trailing_whitespace = true
+max_line_length = 110

.git-blame-ignore-revs

@@ -1,5 +1,29 @@
-# Normalize line endings in t2t files
-e6a639bfe237ff7f98c4cbec2094a34ac4b879db
-# Migrate t2t to markdown
-884c75fe73accbc36bf81260827f4d21c7f40074
-7afafc698a0c5e6689701f024764ca525acf50af
+# Documentation: https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt
+# Usage: git config --local blame.ignoreRevsFile .git-blame-ignore-revs
+
+# #12649: Replace internal controlTypes.ROLE_* usages with controlTypes.Role.*
+defed0ef2317cf3192922692a40cc2eb92d41143
+# #12712: replace controlTypes.STATE_* with controlTypes.State.*
+17e52866e1dfc353edcc7dc9d466449e7920a155
+# #12836: Remove usages of deprecated characterProcessing.SYMLVL_ constants and controlTypes helper functions
+48f502257182356549f22a4095016b37dacdaf9f
+# Normalize line endings in t2t files
+e6a639bfe237ff7f98c4cbec2094a34ac4b879db
+# Migrate t2t to markdown
+884c75fe73accbc36bf81260827f4d21c7f40074
+7afafc698a0c5e6689701f024764ca525acf50af
+# Normalize all line endings
+8fb8ffcaba3950b1e4ca7b58e165267fc5369eb9
+# Lint the repository with Ruff
+d3ce6b8879b14464058d5eaf3f914f803e8f22ac
+8bdfbc2e8da78945e20c3b203b39b9a81227d596
+d7b29daceb98e717aeb4828eb9e71e34e9e33b5e
+55fb00ad342b0cd4b0a8913cfc75e0ea61b28100
+b31c94cf5856832f2fff2c6270e1d5e44c9cd6af
+b9ebcbf5a9ef408372b2dc3073b2bfa4226a2586
+# Fix trailing whitespaces
+f227ca64c7f4cb41f83f531436c6dd11cf3c1d58
+# Add trailing commas
+be112ed44cb68f622a770c72fd29dd10899e9d07
+# Fix E721
+73a3529d8b10eb73a45117eead906c0a9cb4c41b

.gitattributes

@@ -3,3 +3,84 @@
 # Every person expected to commit po files should change their personal config file as described here:
 # https://mail.gnome.org/archives/kupfer-list/2010-June/msg00002.html
 *.po filter=cleanpo
+
+eol=lf
+*	text=auto
+
+# Files which should not be renormalized
+*.dic   -text
+*.po    -text
+
+# Git files
+.gitignore       text
+.gitattributes   text
+CODEOWNERS       text
+
+# Documentation files
+*.md     text
+*.txt    text
+
+# Scripts
+*.ps1    text
+*.bat    text
+*.nsi    text
+
+# Config files
+*.ini    text
+*.yml    text
+*.robot  text
+*.subst  text
+Doxyfile     text
+Makefile     text
+
+# Other files
+*.def text
+*.css text
+*.svg text
+
+# Source files
+# ============
+# Python Sources
+*.py     text diff=python
+*.pyw    text diff=python
+*_sconscript  text diff=python
+sconscript    text diff=python
+sconstruct    text diff=python
+# C++ Sources
+*.c     text diff=c
+*.cpp   text diff=cpp
+*.h     text diff=c
+*.idl   text diff=c
+*.acf   text diff=c
+
+# Binary files
+# ============
+# Python binary files
+# *.db     binary
+# *.p      binary
+# *.pkl    binary
+# *.pickle binary
+# *.pyc    binary
+# *.pyd    binary
+# *.pyo    binary
+# # Compiled C++ Object files
+# *.slo   binary
+# *.lo    binary
+# *.o     binary
+# *.obj   binary
+# # Precompiled C++ Headers
+# *.gch   binary
+# *.pch   binary
+# # Compiled C++ Dynamic libraries
+# *.so    binary
+# *.dylib binary
+# *.dll   binary
+# # Compiled C++ Static libraries
+# *.lai   binary
+# *.la    binary
+# *.a     binary
+# *.lib   binary
+# # C++ Executables
+# *.exe   binary
+# *.out   binary
+# *.app   binary

.github/CODEOWNERS

@@ -1,55 +1,56 @@
-# This is a comment.
-# Each line is a file pattern followed by one or more owners.
-
-# These owners will be the default owners for everything in
-# the repo. Unless a later match takes precedence,
-# @global-owner1 and @global-owner2 will be requested for
-# review when someone opens a pull request.
-# *       @global-owner1 @global-owner2
-
-# Order is important; the last matching pattern takes the most
-# precedence. When someone opens a pull request that only
-# modifies JS files, only @js-owner and not the global
-# owner(s) will be requested for a review.
-# *.js    @js-owner
-
-# You can also use email addresses if you prefer. They'll be
-# used to look up users just like we do for commit author
-# emails.
-# *.go [email protected]
-
-# In this example, @doctocat owns any files in the build/logs
-# directory at the root of the repository and any of its
-# subdirectories.
-# /build/logs/ @doctocat
-
-# The `docs/*` pattern will match files like
-# `docs/getting-started.md` but not further nested files like
-# `docs/build-app/troubleshooting.md`.
-# docs/*  [email protected]
-
-# In this example, @octocat owns any file in an apps directory
-# anywhere in your repository.
-# apps/ @octocat
-
-# In this example, @doctocat owns any file in the `/docs`
-# directory in the root of your repository and any of its
-# subdirectories.
-# /docs/ @doctocat
-
-# Start of NVDA config
-
-# By default auto request review from NV Access developer team.
-* @nvaccess/developers
-
-# For changes to the userGuide auto request review from userDocs team
-/user_docs/en/userGuide.md @nvaccess/userDocs
-
-# For various project documentation, require appropriate teams
-/projectDocs/community/ @nvaccess/userDocs
-/projectDocs/testing/ @nvaccess/userDocs @nvaccess/developers
-/projectDocs/issues/ @nvaccess/userDocs @nvaccess/developers
-/readme.md @nvaccess/userDocs @nvaccess/developers
-security.md @nvaccess/userDocs @nvaccess/developers
-CODE_OF_CONDUCT.md @nvaccess/userDocs @nvaccess/developers
-.github/CONTRIBUTING.md @nvaccess/userDocs @nvaccess/developers
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+
+# These owners will be the default owners for everything in
+# the repo. Unless a later match takes precedence,
+# @global-owner1 and @global-owner2 will be requested for
+# review when someone opens a pull request.
+# *       @global-owner1 @global-owner2
+
+# Order is important; the last matching pattern takes the most
+# precedence. When someone opens a pull request that only
+# modifies JS files, only @js-owner and not the global
+# owner(s) will be requested for a review.
+# *.js    @js-owner
+
+# You can also use email addresses if you prefer. They'll be
+# used to look up users just like we do for commit author
+# emails.
+# *.go [email protected]
+
+# In this example, @doctocat owns any files in the build/logs
+# directory at the root of the repository and any of its
+# subdirectories.
+# /build/logs/ @doctocat
+
+# The `docs/*` pattern will match files like
+# `docs/getting-started.md` but not further nested files like
+# `docs/build-app/troubleshooting.md`.
+# docs/*  [email protected]
+
+# In this example, @octocat owns any file in an apps directory
+# anywhere in your repository.
+# apps/ @octocat
+
+# In this example, @doctocat owns any file in the `/docs`
+# directory in the root of your repository and any of its
+# subdirectories.
+# /docs/ @doctocat
+
+# Start of NVDA config
+
+# By default auto request review from NV Access developer team.
+* @nvaccess/developers
+
+# For changes to the userGuide auto request review from userDocs team
+/user_docs/en/userGuide.md @nvaccess/userDocs
+/projectDocs/dev/userGuideStandards.md @nvaccess/userDocs
+
+# For various project documentation, require appropriate teams
+/projectDocs/community/ @nvaccess/userDocs
+/projectDocs/testing/ @nvaccess/userDocs @nvaccess/developers
+/projectDocs/issues/ @nvaccess/userDocs @nvaccess/developers
+/readme.md @nvaccess/userDocs @nvaccess/developers
+security.md @nvaccess/userDocs @nvaccess/developers
+CODE_OF_CONDUCT.md @nvaccess/userDocs @nvaccess/developers
+.github/CONTRIBUTING.md @nvaccess/userDocs @nvaccess/developers

.github/CONTRIBUTING.md

@@ -1,15 +1,15 @@
-# Contributing to NVDA
-
-Please note: the NVDA project has a [Citizen and Contributor Code of Conduct](../CODE_OF_CONDUCT.md).
-NV Access expects that all contributors and other community members will read and abide by the rules set out in this document while participating or contributing to this project.
-
-The NVDA project is guided by a [product vision statement and set of principles](../projectDocs/product_vision.md).
-The vision and principles should be always considered when planning features and prioritizing work.
-
-There are several ways in which you can contribute to the NVDA project:
-- [Reporting issues](../projectDocs/issues/readme.md)
-- [Issue triage and investigation](../projectDocs/issues/triage.md)
-- [Testing](../projectDocs/testing/contributing.md)
-- [Translating NVDA](https://github.com/nvaccess/nvda/wiki/Translating)
-- [Code or documentation contributions](../projectDocs/dev/contributing.md)
-- [Creating add-ons](../projectDocs/dev/addons.md)
+# Contributing to NVDA
+
+Please note: the NVDA project has a [Citizen and Contributor Code of Conduct](../CODE_OF_CONDUCT.md).
+NV Access expects that all contributors and other community members will read and abide by the rules set out in this document while participating or contributing to this project.
+
+The NVDA project is guided by a [product vision statement and set of principles](../projectDocs/product_vision.md).
+The vision and principles should be always considered when planning features and prioritizing work.
+
+There are several ways in which you can contribute to the NVDA project:
+- [Reporting issues](../projectDocs/issues/readme.md)
+- [Issue triage and investigation](../projectDocs/issues/triage.md)
+- [Testing](../projectDocs/testing/contributing.md)
+- [Translating NVDA](../projectDocs/translating/readme.md)
+- [Code or documentation contributions](../projectDocs/dev/contributing.md)
+- [Creating add-ons](../projectDocs/dev/addons.md)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,7 +8,7 @@ about: Create a report to help us improve
 Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
 Issues may be closed if the required information is not present.
 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/githubIssueTemplateExplanationAndExamples.md
-Please also note that the NVDA project has a Citizen and Contributor Code of Conduct which can be found at https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV Access expects that all contributors and other community members read and abide by the rules set out in this document while participating or contributing to this project. This includes creating or commenting on issues and pull requests. 
+Please also note that the NVDA project has a Citizen and Contributor Code of Conduct which can be found at https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV Access expects that all contributors and other community members read and abide by the rules set out in this document while participating or contributing to this project. This includes creating or commenting on issues and pull requests.
 
 Each of the questions and sections below start with multiple hash symbols (#). Place your answers and information on the blank line below each question.
 -->
@@ -17,14 +17,14 @@ Each of the questions and sections below start with multiple hash symbols (#). P
 
 ### Actual behavior:
 <!--
-Use "Speak command keys" (NVDA+4) and speech viewer to copy and paste here. 
+Use "Speak command keys" (NVDA+4) and speech viewer to copy and paste here.
 Use braille viewer to copy and paste here.
 You may additionally include an explanation.
 -->
 
 ### Expected behavior:
 <!--
-Use "Speak command keys" (NVDA+4) and speech viewer to copy and paste here. 
+Use "Speak command keys" (NVDA+4) and speech viewer to copy and paste here.
 Use braille viewer to copy and paste here.
 You may additionally include an explanation.
 -->

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +1 @@
-blank_issues_enabled: false
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,7 +8,7 @@ about: Suggest an idea for this project
 Please thoroughly read NVDA's wiki article on how to fill in this template, including how to provide the required files.
 Issues may be closed if the required information is not present.
 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/githubIssueTemplateExplanationAndExamples.md
-Please also note that the NVDA project has a Citizen and Contributor Code of Conduct which can be found at https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV Access expects that all contributors and other community members read and abide by the rules set out in this document while participating or contributing to this project. This includes creating or commenting on issues and pull requests. 
+Please also note that the NVDA project has a Citizen and Contributor Code of Conduct which can be found at https://github.com/nvaccess/nvda/blob/master/CODE_OF_CONDUCT.md. NV Access expects that all contributors and other community members read and abide by the rules set out in this document while participating or contributing to this project. This includes creating or commenting on issues and pull requests.
 
 Each of the questions and sections below start with multiple hash symbols (#). Place your answers and information on the blank line below each question.
 -->