Update translations from L10n #17232
Conversation
From translation svn revision: 83282 Authors: Diogo Costa <[email protected]> Rui Batista <[email protected]> Rui Fontes <[email protected]> Ângelo Abrantes <[email protected]> Stats: 10 8 user_docs/pt_PT/changes.md 1 file changed, 10 insertions(+), 8 deletions(-)
From translation svn revision: 83282
From translation svn revision: 83368 Authors: Zahari Yurukov <[email protected]> Kostadin Kolev <[email protected]> Stats: 2 2 source/locale/bg/symbols.dic 1 file changed, 2 insertions(+), 2 deletions(-)
From translation svn revision: 83368 Authors: Jani Kinnunen <[email protected]> Isak Sand <[email protected]> Stats: 1064 216 user_docs/fi/changes.md 1 file changed, 1064 insertions(+), 216 deletions(-)
From translation svn revision: 83368 Authors: Hrvoje Katic <[email protected]> Zvonimir Stanecic <[email protected]> Milo Ivir <[email protected]> Dejana Rakic <[email protected]> Stats: 3572 1155 user_docs/hr/changes.md 1 file changed, 3572 insertions(+), 1155 deletions(-)
From translation svn revision: 83368 Authors: Takuya Nishimoto <[email protected]> Minako Nonogaki <[email protected]> Stats: 89 5 user_docs/ja/changes.md 1 file changed, 89 insertions(+), 5 deletions(-)
From translation svn revision: 83368 Authors: Patryk Faliszewski <[email protected]> Zvonimir Stanecic <[email protected]> Dorota Krac <[email protected]> Piotr Rakowski <[email protected]> Hubert Meyer <[email protected]> Arkadiusz Swietnicki <[email protected]> Stats: 3594 1981 user_docs/pl/changes.md 1 file changed, 3594 insertions(+), 1981 deletions(-)
From translation svn revision: 83368
From translation svn revision: 83427 Authors: Bram Duvigneau <[email protected]> Bart Simons <[email protected]> A Campen <[email protected]> Leonard de Ruijter <[email protected]> Stats: 2 0 user_docs/nl/changes.md 1 file changed, 2 insertions(+)
From translation svn revision: 83427 Authors: Zvonimir Stanecic <[email protected]> Aleksandr Lin'kov <[email protected]> Stats: 1 1 source/locale/ru/symbols.dic 1 file changed, 1 insertion(+), 1 deletion(-)
From translation svn revision: 83427
From translation svn revision: 83469 Authors: Bram Duvigneau <[email protected]> Bart Simons <[email protected]> A Campen <[email protected]> Leonard de Ruijter <[email protected]> Stats: 2827 95 user_docs/nl/changes.md 1 file changed, 2827 insertions(+), 95 deletions(-)
From translation svn revision: 83469 Authors: Dinakar T.D. <[email protected]> Stats: 3 3 user_docs/ta/userGuide.md 1 file changed, 3 insertions(+), 3 deletions(-)
From translation svn revision: 83469
From translation svn revision: 83507 Authors: Bram Duvigneau <[email protected]> Bart Simons <[email protected]> A Campen <[email protected]> Leonard de Ruijter <[email protected]> Stats: 52 18 user_docs/nl/changes.md 1 file changed, 52 insertions(+), 18 deletions(-)
From translation svn revision: 83507 Authors: Dinakar T.D. <[email protected]> Stats: 30 219 user_docs/ta/userGuide.md 1 file changed, 30 insertions(+), 219 deletions(-)
From translation svn revision: 83507
From translation svn revision: 83640 Authors: Fatma Mehanna <[email protected]> Shaimaa Ibrahim <[email protected]> Abdelkrim Bensaid <[email protected]> Omar Alojaimi <[email protected]> Stats: 218 10 user_docs/ar/changes.md 1 file changed, 218 insertions(+), 10 deletions(-)
From translation svn revision: 83640 Authors: Zahari Yurukov <[email protected]> Kostadin Kolev <[email protected]> Stats: 310 290 user_docs/bg/changes.md 1 file changed, 310 insertions(+), 290 deletions(-)
From translation svn revision: 83640 Authors: Simone Dal Maso <[email protected]> Alberto Buffolino <[email protected]> Stats: 181 72 user_docs/it/changes.md 1 file changed, 181 insertions(+), 72 deletions(-)
From translation svn revision: 83640 Authors: Diogo Costa <[email protected]> Rui Batista <[email protected]> Rui Fontes <[email protected]> Ângelo Abrantes <[email protected]> Stats: 35 178 user_docs/pt_PT/changes.md 1 file changed, 35 insertions(+), 178 deletions(-)
From translation svn revision: 83640 Authors: Zvonimir Stanecic <[email protected]> Aleksandr Lin'kov <[email protected]> Stats: 34 34 user_docs/ru/userGuide.md 1 file changed, 34 insertions(+), 34 deletions(-)
From translation svn revision: 83640
From translation svn revision: 83649 Authors: Zahari Yurukov <[email protected]> Kostadin Kolev <[email protected]> Stats: 31 26 user_docs/bg/changes.md 1 file changed, 31 insertions(+), 26 deletions(-)
From translation svn revision: 83649
From translation svn revision: 83690 Authors: Fatma Mehanna <[email protected]> Shaimaa Ibrahim <[email protected]> Abdelkrim Bensaid <[email protected]> Omar Alojaimi <[email protected]> Stats: 951 345 user_docs/ar/changes.md 1 file changed, 951 insertions(+), 345 deletions(-)
From translation svn revision: 83690 Authors: Daniel K. Gartmann <[email protected]> Nicolai Svendsen <[email protected]> [email protected] Stats: 1476 3 user_docs/da/changes.md 1 file changed, 1476 insertions(+), 3 deletions(-)
From translation svn revision: 83690 Authors: Bernd Dorer <[email protected]> David Parduhn <[email protected]> Rene Linke <[email protected]> Adriani Botez <[email protected]> Karl Eick <[email protected]> Robert Hänggi <[email protected]> Astrid Waldschmetterling <[email protected]> Stats: 2 14 source/locale/de/gestures.ini 1 file changed, 2 insertions(+), 14 deletions(-)
From translation svn revision: 83690 Authors: Dinakar T.D. <[email protected]> Stats: 112 112 user_docs/ta/userGuide.md 1 file changed, 112 insertions(+), 112 deletions(-)
From translation svn revision: 83690
From translation svn revision: 83862 Authors: Zahari Yurukov <[email protected]> Kostadin Kolev <[email protected]> Stats: 3 3 source/locale/bg/symbols.dic 1 file changed, 3 insertions(+), 3 deletions(-)
From translation svn revision: 83862 Authors: Daniel K. Gartmann <[email protected]> Nicolai Svendsen <[email protected]> [email protected] Stats: 62 45 user_docs/da/changes.md 1 file changed, 62 insertions(+), 45 deletions(-)
From translation svn revision: 83862
From translation svn revision: 83877 Authors: Daniel K. Gartmann <[email protected]> Nicolai Svendsen <[email protected]> [email protected] Stats: 1007 153 user_docs/da/changes.md 1 file changed, 1007 insertions(+), 153 deletions(-)
From translation svn revision: 83877
From translation svn revision: 83896 Authors: Bram Duvigneau <[email protected]> Bart Simons <[email protected]> A Campen <[email protected]> Leonard de Ruijter <[email protected]> Stats: 103 106 user_docs/nl/userGuide.md 1 file changed, 103 insertions(+), 106 deletions(-)
From translation svn revision: 83896 Authors: [email protected] [email protected] Aaron Wu <[email protected]> Victor Cai <[email protected]> [email protected] Stats: 1422 1235 source/locale/zh_TW/characterDescriptions.dic 75 3 source/locale/zh_TW/symbols.dic 2 files changed, 1497 insertions(+), 1238 deletions(-)
From translation svn revision: 83896
From translation svn revision: 83924 Authors: Ali Aslani <[email protected]> Mohammadreza Rashad <[email protected]> Stats: 2455 275 user_docs/fa/changes.md 1 file changed, 2455 insertions(+), 275 deletions(-)
From translation svn revision: 83924 Authors: Bram Duvigneau <[email protected]> Bart Simons <[email protected]> A Campen <[email protected]> Leonard de Ruijter <[email protected]> Stats: 4 4 user_docs/nl/userGuide.md 1 file changed, 4 insertions(+), 4 deletions(-)
From translation svn revision: 83924 Authors: Cleverson Casarin Uliana <[email protected]> Marlin Rodrigues <[email protected]> Tiago Melo Casal <[email protected]> Lucas Antonio <[email protected]> Stats: 8 49 user_docs/pt_BR/changes.md 1 1 user_docs/pt_BR/userGuide.md 2 files changed, 9 insertions(+), 50 deletions(-)
From translation svn revision: 83924 Authors: Zvonimir Stanecic <[email protected]> Aleksandr Lin'kov <[email protected]> Stats: 49 49 user_docs/ru/userGuide.md 1 file changed, 49 insertions(+), 49 deletions(-)
From translation svn revision: 83924 Authors: Ondrej Rosik <[email protected]> Peter Vagner <[email protected]> Jan Kulik <[email protected]> Stats: 1200 131 user_docs/sk/changes.md 1 file changed, 1200 insertions(+), 131 deletions(-)
From translation svn revision: 83924 Authors: [email protected] [email protected] Aaron Wu <[email protected]> Victor Cai <[email protected]> [email protected] Stats: 561 532 source/locale/zh_TW/characterDescriptions.dic 1 file changed, 561 insertions(+), 532 deletions(-)
From translation svn revision: 83924
From translation svn revision: 83929 Authors: Ali Aslani <[email protected]> Mohammadreza Rashad <[email protected]> Stats: 83 83 user_docs/fa/changes.md 1 file changed, 83 insertions(+), 83 deletions(-)
From translation svn revision: 83929 Authors: [email protected] [email protected] Aaron Wu <[email protected]> Victor Cai <[email protected]> [email protected] Stats: 73 67 source/locale/zh_TW/symbols.dic 1 file changed, 73 insertions(+), 67 deletions(-)
From translation svn revision: 83929
WalkthroughThis pull request includes extensive updates across multiple language locales for the NonVisual Desktop Access (NVDA) software. Key changes involve enhancements to symbol definitions and translations in various languages, modifications to keyboard shortcut mappings, and updates to user guides reflecting new features and system requirements. The updates aim to improve localization, accessibility, and user experience for NVDA across different platforms and languages. Changes
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Outside diff range and nitpick comments (17)
source/locale/zh_TW/symbols.dic (2)
825-920: LGTM: New entries in "化學用字" section are appropriate, with a minor suggestion.The numerous new entries for chemical-related characters have been correctly added, mapping complex characters to their simpler equivalents. This is consistent with the existing entries and improves accessibility for users working with chemical terminology.
Consider adding a brief explanation of why these mappings are important, especially for screen reader users or those unfamiliar with chemical notation. This could be added as a comment just below the "化學用字" section header.
825-920: LGTM: Removals from "特殊化學用字" section are appropriate, with a suggestion for clarity.The entries removed from the "特殊化學用字" section have been correctly moved to the more general "化學用字" section. This improves the overall organization and consistency of the chemical character mappings.
To improve clarity, consider adding a comment explaining that the "特殊化學用字" section has been merged into the "化學用字" section. This will help future maintainers understand the reason for these changes.
user_docs/ar/userGuide.md (3)
41-46: LGTM: System requirements are clear and well-formatted.The system requirements are presented clearly, with each requirement on a separate line. The grammar and punctuation appear to be correct, and the content is easy to read.
Consider adding a brief explanation of what ARM64 means for users who may not be familiar with the term.
1909-1917: LGTM: Unicode normalization explanation is clear and well-formatted.The explanation of Unicode normalization is well-structured and informative. Each point is presented on a separate line, following the one-sentence-per-line style. The examples provided are clear and helpful.
Consider adding a brief explanation of what NFKC stands for in parentheses after its first mention, to help users understand the abbreviation.
4091-4092: LGTM: Supported Braille displays information is clear and well-formatted.The information about supported Braille displays is presented clearly, with each device on a separate line. The note about Zoomax is helpful for users.
Consider adding a brief explanation or link to more information about "external definitions" for users who might be unfamiliar with the term.
user_docs/ru/userGuide.md (2)
4052-4058: LGTM with a minor suggestion for clarity.The added content about the Hedo MobilLine USB braille display is well-translated and provides useful information. The text follows the one sentence per line style and appears accurate.
To improve clarity, consider adding a blank line between the following sentences:
Сначала установите USB драйвера предоставленные производителем. + Автоопределение для этого брайлевского дисплея не поддерживается.This small change would enhance readability by separating the installation instruction from the auto-detection information.
4091-4093: LGTM with a minor suggestion for consistency.The added content about supported braille displays and keyboard shortcuts is well-translated and informative. The text follows the one sentence per line style and appears accurate.
To maintain consistency, consider capitalizing "Brailliant" in the following line:
-В NVDA используются следующие комбинации клавиш для брайлевских дисплеев Brailliant BI/B и BrailleNote touch. +В NVDA используются следующие комбинации клавиш для брайлевских дисплеев Brailliant BI/B и BrailleNote Touch.This small change would ensure consistent capitalization of product names throughout the document.
user_docs/pt_BR/userGuide.md (4)
Line range hint
8-20: Consider adding a text description for the YouTube videoThe link to the YouTube video "What is NVDA?" is helpful, but it would be beneficial to include a brief text description of the video's content. This would provide the information to users who may not be able to access YouTube or prefer text-based information.
Line range hint
22-37: Consider explaining performance implications of minimum requirementsThe system requirements are clearly listed, which is helpful. However, it might be beneficial to add a brief explanation of how NVDA's performance might be affected if a user's system only meets the minimum requirements. This could help users make informed decisions about using NVDA on older or less powerful systems.
Line range hint
39-45: Consider adding a brief explanation of speech synthesizersFor users who may be new to screen readers, it might be helpful to include a brief explanation of what a speech synthesizer is and its role in NVDA. This could help users better understand this crucial component of the software.
Line range hint
47-53: Consider explaining LibLouis brieflyThe mention of LibLouis is helpful, but some users might not be familiar with this tool. Consider adding a brief explanation of what LibLouis is and its role in braille translation. This could help users better understand how NVDA handles braille output.
user_docs/pt_BR/changes.md (3)
402-403: Reformat for improved readability and clarityPlease consider reformatting the text to follow the one-sentence-per-line style for better readability. Additionally, consider providing brief explanations for technical terms to improve clarity for users.
Here's a suggested reformatting with added clarifications:
-* `braille.BrailleHandler.handlePendingCaretUpdate` foi removido sem substituição pública. (#15163, @LeonarddeR) -* `bdDetect.addUsbDevices e bdDetect.addBluetoothDevices` foram removidos. -Os drivers de linhas Braille devem implementar o método de classe `registerAutomaticDetection`. -Esse método recebe um objeto `DriverRegistrar` no qual os métodos `addUsbDevices` e `addBluetoothDevices` podem ser usados. (#15200, @LeonarddeR) +* `braille.BrailleHandler.handlePendingCaretUpdate` foi removido sem substituição pública. (#15163, @LeonarddeR) +* `bdDetect.addUsbDevices` e `bdDetect.addBluetoothDevices` foram removidos. +Os drivers de linhas Braille devem implementar o método de classe `registerAutomaticDetection`. +Esse método recebe um objeto `DriverRegistrar`. +No objeto `DriverRegistrar`, os métodos `addUsbDevices` e `addBluetoothDevices` podem ser usados para registrar dispositivos USB e Bluetooth, respectivamente. (#15200, @LeonarddeR) +* A implementação padrão do método de verificação (check) em `BrailleDisplayDriver` agora requer que os atributos `threadSafe` e `supportsAutomaticDetection` sejam definidos como `True`. (#15200, @LeonarddeR) +Isso garante que o driver seja seguro para uso em múltiplas threads e suporte detecção automática de dispositivos.
656-656: Reformat for improved readability and add context for Unicode symbolsPlease consider reformatting the text to follow the one-sentence-per-line style for better readability. Additionally, consider providing brief explanations or context for the Unicode symbols to improve clarity for users.
Here's a suggested reformatting with added clarifications:
- * símbolos braille como `⠣⠄⠃⠗⠇⠠⠜`. (#14548) - * Símbolo da tecla Option do Mac `⌥`. (#14682) -* Comandos — Gestos — adicionados para linhas braille Tivomatic Caiku Albatross. (#14844, #15002) - * mostrar a caixa de diálogo de configurações braille +* Adicionada pronúncia de símbolos Unicode: + * Símbolos braille como `⠣⠄⠃⠗⠇⠠⠜` (que representa a palavra "braille" em Braille). (#14548) + * Símbolo da tecla Option do Mac `⌥` (também conhecido como tecla Alt em outros sistemas). (#14682) +* Comandos (Gestos) adicionados para linhas braille Tivomatic Caiku Albatross. (#14844, #15002) +* Adicionado comando para mostrar a caixa de diálogo de configurações braille.
1559-1559: Reformat for improved readability and clarityPlease consider reformatting the text to follow the one-sentence-per-line style for better readability. Additionally, consider providing brief explanations for technical terms to improve clarity for users.
Here's a suggested reformatting with added clarifications:
-Há atualizações para eSpeak-NG e LibLouis, incluindo novas tabelas em Russo e Venda. -Os sons de erro podem ser habilitados em compilações estáveis do NVDA por meio de uma nova opção de configurações avançadas. -Leitura contínua em Word agora rola a tela para manter a posição atual visível. -Existem muitas melhorias ao usar o Office com UIA. -Uma correção UIA é que o Outlook agora ignora mais tipos de tabelas de leiaute nas mensagens. +Há atualizações para eSpeak-NG (sintetizador de voz) e LibLouis (tradutor e back-translator braille). +Estas atualizações incluem novas tabelas em Russo e Venda. +Os sons de erro podem ser habilitados em compilações estáveis do NVDA por meio de uma nova opção de configurações avançadas. +Leitura contínua em Word agora rola a tela para manter a posição atual visível. +Existem muitas melhorias ao usar o Office com UIA (UI Automation, uma API de acessibilidade da Microsoft). +Uma correção UIA é que o Outlook agora ignora mais tipos de tabelas de leiaute nas mensagens, melhorando a leitura de e-mails. Notas importantes:user_docs/it/changes.md (3)
Line range hint
801-805: Contenuto chiaro, ma formattazione migliorabile.Le informazioni sul supporto per nuovi display Braille e i miglioramenti per le versioni di Windows sono chiare. Tuttavia, la formattazione potrebbe essere migliorata per mantenere la coerenza di una frase per riga.
Suggerisco di riformattare il testo come segue:
Introdotto il supporto per i display braille Tivomatic Caiku Albatross 46/80. Migliorato anche il supporto per le versioni ARM64 e AMD64 di Windows. -Sono stati risolti anche molti bug soprattutto inerenti a windows11.. +Sono stati risolti anche molti bug soprattutto inerenti a Windows 11. Come sempre, eSpeak, LibLouis, Sonic rate boost e Unicode CLDR sono stati aggiornati.
1281-1295: Contenuto chiaro, ma formattazione migliorabile.Le informazioni sui vari miglioramenti e correzioni di bug sono chiare e dettagliate. Tuttavia, la formattazione potrebbe essere migliorata per mantenere la coerenza di una frase per riga.
Suggerisco di riformattare il testo come segue:
NVDA annuncerà i risultati quando vengono premuti più comandi, come i comandi dalla modalità scientifica. (#13383) -* In Windows 11, è nuovamente possibile navigare e interagire con gli elementi dell'interfaccia utente, -come la barra delle applicazioni e la visualizzazione attività utilizzando il mouse o l'interazione a tocco. (#13508) +* In Windows 11, è nuovamente possibile navigare e interagire con gli elementi dell'interfaccia utente, come la barra delle applicazioni e la visualizzazione attività utilizzando il mouse o l'interazione a tocco. (#13508) * NVDA annuncerà il contenuto della barra di stato nel Blocco note di Windows 11. (#13688) * L'evidenziazione del navigatore ad oggetti ora si attiverà istantaneamente subito dopo l'attivazione della funzione.. (#13641) * Sistemata la lettura della prima colonna nella visualizzazione ad elenco degli elementi. (#13659, #13735) * Sistemato il cambio lingua automatico in eSpeak per Inglese e Francese che selezioneranno British English and French (France). (#13727) * Risolto il problema con il cambio automatico della lingua di OneCore quando si tenta di passare a una lingua precedentemente installata. (#13732) ### Changes for Developers * Compiling NVDA dependencies with Visual Studio 2022 (17.0) is now supported. For development and release builds, Visual Studio 2019 is still used. (#13033) * When retrieving the count of selected children via accSelection, the case where a negative child ID or an IDispatch is returned by `IAccessible::get_accSelection` is now handled properly. (#13277)
2343-2350: Correzioni di bug e miglioramenti ben descritti, ma presenza di testo in inglese.Le informazioni sulle varie correzioni di bug e miglioramenti sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle correzioni in Excel, Google Chrome e altre applicazioni sono ben spiegati.
Si noti che c'è del testo in inglese in questo segmento di un documento italiano. Potrebbe essere necessario tradurre la sezione "Changes for Developers" in italiano per mantenere la coerenza linguistica del documento.
📜 Review details
Configuration used: .coderabbit.yml
Review profile: CHILL
📒 Files selected for processing (13)
- source/locale/bg/symbols.dic (1 hunks)
- source/locale/de/gestures.ini (1 hunks)
- source/locale/es/symbols.dic (1 hunks)
- source/locale/nl/symbols.dic (6 hunks)
- source/locale/ru/symbols.dic (1 hunks)
- source/locale/zh_TW/symbols.dic (3 hunks)
- user_docs/ar/userGuide.md (7 hunks)
- user_docs/it/changes.md (64 hunks)
- user_docs/ja/changes.md (15 hunks)
- user_docs/nl/userGuide.md (64 hunks)
- user_docs/pt_BR/changes.md (4 hunks)
- user_docs/pt_BR/userGuide.md (1 hunks)
- user_docs/ru/userGuide.md (7 hunks)
🧰 Additional context used
📓 Path-based instructions (13)
source/locale/bg/symbols.dic (1)
Pattern
**/*: 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.source/locale/de/gestures.ini (1)
Pattern
**/*: 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.source/locale/es/symbols.dic (1)
Pattern
**/*: 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.source/locale/nl/symbols.dic (1)
Pattern
**/*: 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.source/locale/ru/symbols.dic (1)
Pattern
**/*: 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.source/locale/zh_TW/symbols.dic (1)
Pattern
**/*: 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.user_docs/ar/userGuide.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.user_docs/it/changes.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.user_docs/ja/changes.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.user_docs/nl/userGuide.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.user_docs/pt_BR/changes.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.user_docs/pt_BR/userGuide.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.user_docs/ru/userGuide.md (2)
Pattern
**/*: 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.
Pattern
**/*.md: 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.
🔇 Additional comments (69)
source/locale/de/gestures.ini (2)
11-11: Approved: Consistent formatting of keyboard shortcutsThe removal of quotation marks from keyboard shortcuts in lines 11 and 17 improves consistency in the file format. This change aligns with best practices for configuration files.
Also applies to: 17-17
Line range hint
1-19: Summary of changes and request for clarificationThe visible changes in this file are minimal and primarily related to formatting improvements, specifically the removal of quotation marks from keyboard shortcuts. These changes enhance consistency and are approved.
However, there are significant inconsistencies between the AI-generated summary and the visible changes:
- The summary mentions changes to left and right mouse button actions for laptops, which are not visible in the provided code.
- The summary states that the LibreOffice section has been removed, but this is not evident in the visible changes.
To ensure an accurate and comprehensive review, please clarify these discrepancies. Are there additional changes that were not included in the provided diff? If so, please provide the complete set of changes for a thorough review.
source/locale/zh_TW/symbols.dic (3)
4-4: LGTM: Metadata update is correct.The edit date has been appropriately updated to September 25, 2024, which is consistent with the changes made in this pull request.
819-823: LGTM: New entries in "中日韓統一表意文字" section are appropriate.The four new entries (敻, 㚬, 䧟, 𪹚) have been correctly added, mapping complex characters to their simpler equivalents. This is consistent with the existing entries and improves accessibility for users.
Line range hint
1-1492: Overall LGTM: Excellent improvements to Traditional Chinese (Taiwan) localization.This update significantly enhances the
symbols.dicfile for Traditional Chinese (Taiwan) localization. The changes include:
- Updated metadata with the correct edit date.
- New entries in the "中日韓統一表意文字" section, improving accessibility for complex characters.
- Extensive additions to the "化學用字" section, greatly improving support for chemical terminology.
- Reorganization of chemical character mappings by merging "特殊化學用字" into "化學用字".
These changes will notably improve the experience for screen reader users, particularly those working with scientific or chemical content. The consistency and organization of the file have also been enhanced.
Great work on this update! The changes align well with the PR objectives and will significantly benefit NVDA users in Taiwan.
user_docs/ar/userGuide.md (3)
25-28: LGTM: Feature list is well-formatted and clear.The list of NVDA features is presented clearly, with each feature on a separate line. The grammar and punctuation appear to be correct, and the content is easy to read.
1931-1934: LGTM: Instructions for Unicode normalization settings are clear and concise.The instructions for toggling Unicode normalization and reporting normalized characters are well-presented. Each point is on a separate line, following the one-sentence-per-line style. The content is informative and easy to understand.
2176-2179: LGTM: Braille Unicode normalization section is correctly formatted.The table header for Braille Unicode normalization settings is correctly formatted. However, the section seems incomplete. Consider adding more context or explanation about Braille Unicode normalization to improve user understanding.
Could you provide more information about the Braille Unicode normalization settings? This would help ensure the documentation is comprehensive.
user_docs/ru/userGuide.md (4)
1403-1403: LGTM: Clear and consistent translation.The added row in the table is well-formatted, follows the one sentence per line style, and provides clear information about the screen dimming feature. The translation appears accurate and consistent with the rest of the document.
4019-4019: LGTM: Well-formatted and consistent translations.The added rows in the table are properly formatted and provide clear translations for various keyboard shortcuts. The content follows the established style and appears accurate.
4075-4075: Duplicate content, no additional review needed.This hunk contains content identical to what was reviewed in hunk 2. No further review is necessary.
4121-4121: LGTM: Consistent and clear translations.The added rows in the table are well-formatted and provide clear translations for various keyboard shortcuts. The content follows the established style and appears accurate.
user_docs/ja/changes.md (15)
1791-1793: LGTM: Clear documentation of API changesThe changes to the
NVDAObjectclass and itsisCurrentproperty are well-documented. The information is presented clearly, with one sentence per line, which adheres to the project's style guidelines.
2682-2684: LGTM: Well-documented bug fixesThe bug fixes for Windows 7 and NVDA startup issues are clearly documented. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
2965-2967: LGTM: Clear documentation of new features and improvementsThe new support for braille displays, initial support for Microsoft Edge, and improvements to the Windows 10 Mail app are well-documented. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
3239-3243: LGTM: Well-documented bug fixes and improvementsThe bug fixes and improvements for Skype for Desktop, context menu issues, color reporting in Windows 7, and Microsoft PowerPoint are clearly documented. Each item is presented concisely, with one sentence per line, adhering to the project's style guidelines.
3259-3261: LGTM: Clear documentation of new features and improvementsThe new braille translation tables, support for QWERTY keyboard on a specific braille display, and experimental support for Microsoft Edge and Windows 10 browser engine are well-documented. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
3324-3326: LGTM: Well-documented accessibility improvementThe improvement in image navigation for Internet Explorer and MSHTML controls, specifically the correct processing of ARIA role img markup, is clearly documented. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
3431-3434: LGTM: Clear documentation of hardware-specific fixThe bug fix for Papenmeier BRAILLEX braille displays with BrxCom is well-documented. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
3664-3666: LGTM: Well-documented bug fixesThe bug fixes for NVDA screen review switching, Freedom Scientific braille display driver issues, and key detection problems are clearly documented. Each fix is presented concisely, with one sentence per line, adhering to the project's style guidelines.
3736-3739: LGTM: Clear documentation of application-specific bug fixesThe bug fixes for Microsoft PowerPoint (duplicate announcements and thumbnail view handling) and Adobe Reader (crash prevention for improperly formatted PDFs) are well-documented. Each fix is presented concisely, with one sentence per line, adhering to the project's style guidelines.
Line range hint
3878-3883: LGTM: Comprehensive documentation of new features and improvementsThis segment clearly documents a wide range of new features and improvements, including enhancements to Microsoft Outlook, Adobe Reader, eSpeak voices, NVDA settings management, and braille display support. Each item is presented concisely, with one sentence per line, adhering to the project's style guidelines.
4090-4102: LGTM: Comprehensive documentation of developer-focused changesThis segment provides a clear and detailed overview of changes relevant to developers. It covers a wide range of topics including debugging tools, logging improvements, new methods and mix-ins, constant reorganization, and enhancements to specific drivers. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
4163-4168: LGTM: Clear documentation of new language switching feature for developersThis segment provides a concise yet comprehensive explanation of the new language switching feature for speech synthesizers. It includes implementation details for drivers and information about language handling in VoiceInfo objects. The information is presented clearly, with one sentence per line, adhering to the project's style guidelines.
4186-4189: LGTM: Well-documented user-facing improvementsThis segment clearly outlines several user-facing improvements, including customizable pronunciation settings, enhanced Microsoft Excel and Word functionality, and new configuration options for table navigation. Each improvement is presented concisely, with one sentence per line, adhering to the project's style guidelines.
4284-4301: LGTM: Comprehensive documentation of developer-focused changesThis segment provides a detailed overview of various changes relevant to developers. It covers a wide range of topics including documentation generation, localization enhancements, debugging options, synth driver improvements, GUI-related changes, and build process updates. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines.
4390-4424: LGTM: Extensive and clear documentation of major developer-focused changesThis segment provides a comprehensive and well-structured overview of significant changes relevant to developers. It covers a wide range of topics including build processes, input handling, scripting, localization, new behaviors and plugins, and changes to various drivers and modules. The information is presented concisely, with one sentence per line, adhering to the project's style guidelines. This documentation will be invaluable for developers working on or with NVDA.
user_docs/nl/userGuide.md (20)
34-35: Goedgekeurde toevoeging van compatibiliteitsinformatie.Deze toevoeging biedt duidelijke informatie over de ondersteuning van NVDA voor oudere Windows-versies. Dit is waardevolle informatie voor gebruikers die mogelijk nog werken met Windows 8.1 of oudere Server-versies.
52-53: Goedgekeurde toevoeging van systeemvereisten.Deze toevoeging verduidelijkt dat 32-bit besturingssystemen niet langer actief worden ondersteund. Dit is belangrijke informatie voor gebruikers met oudere systemen en helpt bij het bepalen van compatibiliteit.
272-273: Goedgekeurde toevoeging van web-navigatietabel.De nieuwe tabel met web-navigatiecommando's verbetert de documentatie aanzienlijk. Het biedt gebruikers een duidelijk overzicht van belangrijke sneltoetsen voor het navigeren van webinhoud, wat de bruikbaarheid van de handleiding vergroot.
333-335: Goedgekeurde verduidelijking van add-on installatie-instructies.De wijzigingen in deze sectie bieden meer gedetailleerde en precieze instructies voor het installeren van add-ons. De toevoeging van informatie over het "Acties" menu en specifieke toetscombinaties maakt het proces duidelijker voor gebruikers, wat de gebruiksvriendelijkheid van de handleiding verbetert.
355-356: Goedgekeurde toevoeging van Escape-toets functionaliteit.De nieuwe informatie over het gebruik van de Escape-toets in het Add-on Store venster is een waardevolle toevoeging. Het biedt gebruikers een handige sneltoets voor navigatie die voorheen niet gedocumenteerd was, wat de gebruiksvriendelijkheid van de interface verbetert.
365-366: Goedgekeurde toevoeging van informatie over automatische update-meldingen.Deze nieuwe informatie over automatische meldingen voor add-on updates is een waardevolle toevoeging aan de handleiding. Het maakt gebruikers bewust van een handige functie en verwijst correct naar een meer gedetailleerde sectie voor verdere informatie. Dit verbetert de algehele bruikbaarheid van NVDA voor gebruikers.
1407-1409: Goedgekeurde toevoeging van Screen Curtain beperkingen.Deze nieuwe informatie over de beperkingen van de Screen Curtain functie is een belangrijke toevoeging. Het helpt gebruikers te begrijpen welke taken niet mogelijk zijn wanneer Screen Curtain is ingeschakeld, zoals OCR of het maken van schermafbeeldingen. Dit voorkomt potentiële verwarring en verbetert de gebruikservaring.
2315-2316: Goedgekeurde update van sneltoets voor Audio Ducking Mode.De wijziging van de sneltoets voor Audio Ducking Mode van NVDA+shift+a naar NVDA+shift+d is een belangrijke update. Het is essentieel dat gebruikers op de hoogte zijn van deze verandering om verwarring te voorkomen. Deze update zorgt ervoor dat de documentatie accuraat blijft en helpt gebruikers bij het efficiënt gebruik van NVDA.
2546-2547: Goedgekeurde toevoeging van aanpassingsmogelijkheid voor tekstresolutie bij muisvolgen.Deze nieuwe informatie over het aanpassen van de tekstresolutie bij het volgen van de muis is een waardevolle toevoeging voor gevorderde gebruikers. Het biedt meer controle over de functionaliteit en verwijst correct naar het gebruik van het Invoerhandelingen dialoogvenster voor het toewijzen van een aangepaste handeling. Dit vergroot de flexibiliteit en aanpasbaarheid van NVDA voor gebruikers met specifieke behoeften.
2637-2638: Goedgekeurde verduidelijking van objectdetailrapportage.De wijziging in deze sectie biedt een belangrijke verduidelijking over hoe objectdetails worden gerapporteerd. Door te vermelden dat bepaalde details afhankelijk kunnen zijn van instellingen in de categorieën Objectweergave of Documentopmaak, krijgen gebruikers een beter begrip van hoe verschillende NVDA-instellingen met elkaar samenhangen. Dit helpt gebruikers bij het effectiever configureren van NVDA naar hun behoeften.
2653-2654: Goedgekeurde toevoeging van informatie over geschatte objectpositie.De nieuwe informatie over het schatten van objectpositie-informatie is een waardevolle toevoeging aan de handleiding. Het legt uit hoe NVDA bij benadering de positie van bepaalde objecten kan bepalen wanneer deze informatie niet direct beschikbaar is. Dit helpt gebruikers te begrijpen hoe NVDA werkt en wat ze kunnen verwachten in termen van positie-informatie voor verschillende objecten. De vermelding dat deze informatie mogelijk niet volledig nauwkeurig is, is een belangrijke kanttekening die gebruikers helpt realistische verwachtingen te hebben.
3663-3665: Goedgekeurde toevoeging van COM-registratie reparatietool sectie.De nieuwe sectie over de COM-registratie reparatietool is een belangrijke toevoeging aan de handleiding. Het biedt gebruikers en systeembeheerders waardevolle informatie over hoe ze problemen kunnen oplossen die voortkomen uit onjuiste COM DLL-registraties. Deze informatie kan cruciaal zijn voor het behouden van de optimale functionaliteit van NVDA, vooral na installatie of verwijdering van bepaalde software. De uitleg over de potentiële problemen en hoe de tool deze kan oplossen, is helder en informatief.
3681-3683: Goedgekeurde verduidelijking van plugin herlaadfunctie.De wijzigingen in deze sectie bieden een duidelijkere uitleg van de plugin herlaadfunctie. Door expliciet te vermelden dat zowel app modules als globale plugins opnieuw worden geladen, en kort uit te leggen wat deze componenten doen, krijgen gebruikers een beter begrip van deze functie. Dit is vooral nuttig voor gevorderde gebruikers en ontwikkelaars die met NVDA-extensies werken. De verbeterde uitleg draagt bij aan een beter begrip van NVDA's architectuur en functionaliteit.
3691-3691: Goedgekeurde toevoeging van sneltoets voor app module en executable informatie.De nieuwe sneltoets voor het melden van de geladen app module en executable is een waardevolle toevoeging voor gevorderde gebruikers en ontwikkelaars. Deze functie kan zeer nuttig zijn bij het debuggen van NVDA-extensies of het onderzoeken van de interactie tussen NVDA en specifieke applicaties. Het biedt een snelle manier om belangrijke technische informatie te verkrijgen zonder de normale workflow te onderbreken.
3703-3703: Goedgekeurde update van standaard synthesizer informatie.De wijziging die specificeert dat eSpeak NG de standaard synthesizer is in Windows 8.1 is een belangrijke verduidelijking. Deze informatie helpt gebruikers te begrijpen wat ze kunnen verwachten bij het gebruik van NVDA op verschillende Windows-versies. Het draagt bij aan een duidelijker beeld van de out-of-the-box ervaring met NVDA op specifieke Windows-versies, wat vooral nuttig kan zijn voor nieuwe gebruikers of systeembeheerders die NVDA op verschillende systemen installeren.
3709-3709: Goedgekeurde update van eSpeak NG stemvarianten informatie.De wijziging die vermeldt dat er veel varianten beschikbaar zijn om aan te passen hoe stemmen klinken, is een waardevolle toevoeging. Deze informatie benadrukt de flexibiliteit en aanpasbaarheid van de eSpeak NG synthesizer. Het moedigt gebruikers aan om te experimenteren met verschillende stemvarianten om een stem te vinden die het beste bij hun voorkeuren past, wat kan leiden tot een verbeterde gebruikerservaring met NVDA.
3734-3736: Goedgekeurde verduidelijking van Microsoft Speech Platform installatie-instructies.De wijzigingen in deze sectie bieden een duidelijkere uitleg van het proces voor het selecteren en installeren van specifieke taalcomponenten voor de Microsoft Speech Platform. De toegevoegde details, zoals het voorbeeld van het MSSpeech_TTS_en-US_ZiraPro.msi bestand, maken het voor gebruikers gemakkelijker om de juiste componenten te identificeren en te installeren. Deze verbeterde instructies zullen gebruikers helpen bij het effectief uitbreiden van de beschikbare stemmen in NVDA, wat leidt tot een meer gepersonaliseerde ervaring.
3744-3744: Goedgekeurde update van instructies voor het toevoegen van Windows OneCore stemmen.De wijziging die gebruikers naar de "Spraakinstellingen" in de Windows systeeminstellingen verwijst voor het toevoegen van nieuwe stemmen is een belangrijke update. Deze informatie weerspiegelt de huidige interface van Windows en zorgt ervoor dat gebruikers de juiste locatie kunnen vinden om nieuwe stemmen toe te voegen. Door de handleiding up-to-date te houden met veranderingen in Windows, blijft deze relevant en bruikbaar voor gebruikers van verschillende Windows-versies.
Line range hint
3079-3080: Goedgekeurde toevoeging van informatie over het uitschakelen van add-ons.De wijziging die vermeldt dat het uitschakelen van add-ons vanaf elke locatie kan worden gedaan door een aangepaste handeling toe te wijzen, is een waardevolle toevoeging. Deze informatie biedt gebruikers meer flexibiliteit en controle over hun NVDA-configuratie. Het is vooral nuttig voor gevorderde gebruikers die snel toegang willen tot deze functie, bijvoorbeeld voor het oplossen van problemen of het testen van NVDA-gedrag zonder bepaalde add-ons. Deze toevoeging verbetert de aanpasbaarheid van NVDA en kan de efficiëntie van gebruikers verhogen.
5053-5054: Goedgekeurde uitbreiding van commandoregel-opties informatie.De wijzigingen en toevoegingen in deze sectie bieden een meer uitgebreide en gedetailleerde uitleg van de commandoregel-opties voor NVDA. De toegevoegde voorbeelden en verduidelijkingen over het gebruik van verschillende opties zijn bijzonder waardevol voor gevorderde gebruikers en systeembeheerders. Deze informatie stelt gebruikers in staat om NVDA nauwkeuriger te configureren bij het opstarten, wat nuttig kan zijn voor geautomatiseerde installaties, probleemoplossing, en geavanceerd gebruik. De verbeterde documentatie van deze opties draagt bij aan de flexibiliteit en kracht van NVDA als hulpmiddel voor toegankelijkheid.
Also applies to: 5057-5057, 5061-5063, 5070-5070, 5079-5080, 5085-5086
user_docs/it/changes.md (19)
129-131: Contenuto chiaro e ben formattato.Il testo è ben strutturato, con una frase per riga, e fornisce informazioni chiare sui nuovi comandi di navigazione.
175-177: Mappatura dei tasti ben descritta.Le nuove mappature dei tasti alt+freccia sono chiaramente spiegate, mantenendo il formato di una frase per riga.
325-327: Correzioni di bug ben descritte.Le correzioni di bug e i miglioramenti sono chiaramente spiegati, mantenendo il formato di una frase per riga.
Line range hint
645-657: Nuove funzionalità Braille ben descritte.Le nuove funzionalità relative al Braille sono chiaramente spiegate, mantenendo il formato di una frase per riga. Le informazioni sui tasti di scelta rapida e le nuove opzioni sono presentate in modo chiaro.
656-657: Ulteriori funzionalità Braille e pronuncia dei simboli ben descritte.Le informazioni aggiuntive sulle funzionalità Braille e la pronuncia dei simboli sono presentate chiaramente, mantenendo il formato di una frase per riga.
677-680: Miglioramenti e nuove funzionalità ben descritti.Le varie migliorie e nuove funzionalità sono spiegate chiaramente, mantenendo il formato di una frase per riga. Le informazioni su ARIA, variabili di sistema e supporto per Windows 10 sono presentate in modo conciso.
694-697: Aggiornamenti al supporto Braille e altri miglioramenti ben descritti.Gli aggiornamenti al supporto Braille e gli altri miglioramenti sono spiegati chiaramente, mantenendo il formato di una frase per riga. Le informazioni sulle nuove funzionalità e le correzioni sono presentate in modo conciso.
880-882: Correzioni di bug e miglioramenti ben descritti.Le varie correzioni di bug e miglioramenti sono spiegati chiaramente, mantenendo il formato di una frase per riga. Le informazioni sono presentate in modo conciso e comprensibile.
1176-1184: Aggiornamenti di versione e correzioni di sicurezza ben descritti.Le informazioni sugli aggiornamenti di versione e le correzioni di sicurezza sono presentate chiaramente, mantenendo il formato di una frase per riga. Il riferimento al problema di sicurezza è ben documentato con il link GitHub.
1196-1199: Patch per bug ben descritta.La descrizione della patch per correggere un bug introdotto in una versione precedente è chiara e concisa. Il testo mantiene il formato di una frase per riga.
Line range hint
1247-1251: Aggiornamenti e nuove funzionalità ben descritti.Le informazioni sugli aggiornamenti e le nuove funzionalità sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sui nuovi ruoli e le limitazioni della versione Windows Store sono ben spiegati.
Line range hint
1268-1273: Miglioramenti al supporto Braille e correzioni di bug ben descritti.Le informazioni sui miglioramenti al supporto Braille e le varie correzioni di bug sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle modifiche in Firefox, nel programma di installazione di NVDA e in altre applicazioni sono ben spiegati.
1308-1311: Changes for developers well described.The information about changes for developers is presented clearly, maintaining the format of one sentence per line. The deprecation notices and replacement instructions are well explained.
Line range hint
1389-1393: Cambiamenti e miglioramenti ben descritti.Le informazioni sui vari cambiamenti e miglioramenti sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle modifiche ai tasti rapidi e alle funzionalità sono ben spiegati.
Line range hint
1720-1724: Miglioramenti e nuove funzionalità ben descritti.Le informazioni sui vari miglioramenti e nuove funzionalità sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle aggiunte ai simboli matematici, miglioramenti alla guida utente e modifiche alle impostazioni sono ben spiegati.
Line range hint
1746-1750: Miglioramenti e correzioni di bug ben descritti.Le informazioni sui vari miglioramenti e correzioni di bug sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle modifiche in Visual Studio, Internet Explorer e altre applicazioni sono ben spiegati.
Line range hint
1881-1885: Aggiornamenti alle tabelle Braille e vari miglioramenti ben descritti.Le informazioni sugli aggiornamenti alle tabelle Braille e i vari miglioramenti sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle nuove tabelle, le modifiche alla funzionalità di ricerca e le mappature dei tasti sono ben spiegati.
1925-1928: Correzioni di bug e miglioramenti ben descritti.Le informazioni sulle varie correzioni di bug e miglioramenti sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle correzioni in Excel, nei display Braille Papenmeier e nei browser basati su Chromium sono ben spiegati.
2089-2093: Miglioramenti e correzioni di bug ben descritti.Le informazioni sui vari miglioramenti e correzioni di bug sono presentate chiaramente, mantenendo il formato di una frase per riga. I dettagli sulle modifiche nella modalità "dire tutto", nel tracciamento del mouse e in altre funzionalità sono ben spiegati.
source/locale/bg/symbols.dic (1)
120-120: LGTM!The translation for the paragraph symbol '¶' as 'маркер за абзац' is accurate and appropriate.
source/locale/es/symbols.dic (1)
111-111: Approved: The symbol definition for EN DASH (–) is appropriateThe symbol '–' is correctly defined as "guion corto," which aligns with Spanish typographical conventions.
source/locale/ru/symbols.dic (1)
338-338: Translation of '⇐' is correct.The symbol '⇐' (double left arrow) has been accurately translated as 'двойная стрелка влево'.
user_docs/ar/userGuide.md
Outdated
| يمكن ضبطُ كل من مفااتيح `الإدراج Insert` أو مفتاح `الإدراج في اللوحة الرقمية NumPad Insert` أو مفتاح `تثبيت وضعية تكبير الأحرف capsLock` كمفاتيح مصاحبة ل `NVDA`. | ||
| افتراضيا، يعمل كلٌ من مفتاح `الإدراج` ومفتاح `الإدراج على اللوحة الرقمية numpad Insert` كمفاتيح مصاحبة للبرنامج. | ||
|
|
||
| إذا أردت أن يؤدي أيٌ من المفاتيح المضبوطة للعمل كمفاتيح مصاحبة ل NVDA وظيفته الأساسية، كما لو أردتَ تفعيل مفتاح تكبير الحروف وقد أعددتَه ليعمل كمفتاح مصاحب لNVDA، فيمكنك الضغط عليه بسرعة مرتين متتاليتين. |
There was a problem hiding this comment.
Improve readability and fix spelling error.
The content is informative, but there are a few improvements that can be made:
- Split the long sentences into separate lines for better readability and to follow the one-sentence-per-line style.
- Correct the spelling of "مفااتيح" to "مفاتيح" on line 525.
Here's a suggested revision:
-يمكن ضبطُ كل من مفااتيح `الإدراج Insert` أو مفتاح `الإدراج في اللوحة الرقمية NumPad Insert` أو مفتاح `تثبيت وضعية تكبير الأحرف capsLock` كمفاتيح مصاحبة ل `NVDA`.
-افتراضيا، يعمل كلٌ من مفتاح `الإدراج` ومفتاح `الإدراج على اللوحة الرقمية numpad Insert` كمفاتيح مصاحبة للبرنامج.
+يمكن ضبطُ كل من مفاتيح `الإدراج Insert` أو مفتاح `الإدراج في اللوحة الرقمية NumPad Insert` أو مفتاح `تثبيت وضعية تكبير الأحرف capsLock` كمفاتيح مصاحبة ل `NVDA`.
+افتراضيا، يعمل كلٌ من مفتاح `الإدراج` ومفتاح `الإدراج على اللوحة الرقمية numpad Insert` كمفاتيح مصاحبة للبرنامج.
-إذا أردت أن يؤدي أيٌ من المفاتيح المضبوطة للعمل كمفاتيح مصاحبة ل NVDA وظيفته الأساسية، كما لو أردتَ تفعيل مفتاح تكبير الحروف وقد أعددتَه ليعمل كمفتاح مصاحب لNVDA، فيمكنك الضغط عليه بسرعة مرتين متتاليتين.
+إذا أردت أن يؤدي أيٌ من المفاتيح المضبوطة للعمل كمفاتيح مصاحبة ل NVDA وظيفته الأساسية، فيمكنك الضغط عليه بسرعة مرتين متتاليتين.
+على سبيل المثال، إذا أردتَ تفعيل مفتاح تكبير الحروف وقد أعددتَه ليعمل كمفتاح مصاحب لNVDA، يمكنك الضغط عليه مرتين بسرعة.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| يمكن ضبطُ كل من مفااتيح `الإدراج Insert` أو مفتاح `الإدراج في اللوحة الرقمية NumPad Insert` أو مفتاح `تثبيت وضعية تكبير الأحرف capsLock` كمفاتيح مصاحبة ل `NVDA`. | |
| افتراضيا، يعمل كلٌ من مفتاح `الإدراج` ومفتاح `الإدراج على اللوحة الرقمية numpad Insert` كمفاتيح مصاحبة للبرنامج. | |
| إذا أردت أن يؤدي أيٌ من المفاتيح المضبوطة للعمل كمفاتيح مصاحبة ل NVDA وظيفته الأساسية، كما لو أردتَ تفعيل مفتاح تكبير الحروف وقد أعددتَه ليعمل كمفتاح مصاحب لNVDA، فيمكنك الضغط عليه بسرعة مرتين متتاليتين. | |
| يمكن ضبطُ كل من مفاتيح `الإدراج Insert` أو مفتاح `الإدراج في اللوحة الرقمية NumPad Insert` أو مفتاح `تثبيت وضعية تكبير الأحرف capsLock` كمفاتيح مصاحبة ل `NVDA`. | |
| افتراضيا، يعمل كلٌ من مفتاح `الإدراج` ومفتاح `الإدراج على اللوحة الرقمية numpad Insert` كمفاتيح مصاحبة للبرنامج. | |
| إذا أردت أن يؤدي أيٌ من المفاتيح المضبوطة للعمل كمفاتيح مصاحبة ل NVDA وظيفته الأساسية، فيمكنك الضغط عليه بسرعة مرتين متتاليتين. | |
| على سبيل المثال، إذا أردتَ تفعيل مفتاح تكبير الحروف وقد أعددتَه ليعمل كمفتاح مصاحب لNVDA، يمكنك الضغط عليه مرتين بسرعة. |
user_docs/ru/userGuide.md
Outdated
| |Прокрутить дисплей Брайля вперёд |right| | ||
| |Читать всё |space+Backspace| | ||
| |Меню NVDA |Left+Right| | ||
| |Перемещение дисплея Брайля на предыдущую строку |LJ вверх| | ||
| |Перемещение дисплея Брайля на следующую строку |LJ вниз| | ||
| |Переключить привязку Брайля |LJ center| | ||
| |tab |LJ right| | ||
| |shift+tab |LJ left| | ||
| |upArrow key |RJ up| | ||
| |downArrow key |RJ down| | ||
| |leftArrow key |RJ left| | ||
| |rightArrow key |RJ right| | ||
| |Route to braille cell |routing| | ||
| |shift+upArrow key |Space+RJ up, Backspace+RJ up| | ||
| |shift+downArrow key |Space+RJ down, Backspace+RJ down| | ||
| |shift+leftArrow key |Space+RJ left, Backspace+RJ left| | ||
| |shift+rightArrow key |Space+RJ right, Backspace+RJ right| | ||
| |enter key |RJ center, dot8| | ||
| |escape key |Space+RJ center| | ||
| |windows key |Backspace+RJ center| | ||
| |space key |Space, Backspace| | ||
| |backspace key |dot7| | ||
| |pageup key |space+LJ right| | ||
| |Стрелка вверх |RJ up| | ||
| |Стрелка вниз |RJ down| | ||
| |Стрелка вправо |RJ left| | ||
| |Стрелка влево |RJ вправо| | ||
| |Переход к ячейке Брайля |routing| | ||
| |shift+стрелка верх |Space+RJ вверх, Backspace+RJ вверх| | ||
| |shift+стрелка вниз |Space+RJ вниз, Backspace+RJ вниз| | ||
| |shift+стрелка влево |Space+RJ left, Backspace+RJ left| | ||
| |shift+стрелка вправо |Space+RJ вправо, Backspace+RJ вправо| | ||
| |enter |RJ center, dot8| | ||
| |escape |Space+RJ center| | ||
| |клавиша windows |Backspace+RJ center| | ||
| |space |Space, Backspace| | ||
| |backspace |dot7| | ||
| |pageup |space+LJ right| | ||
| |pagedown key |space+LJ left| | ||
| |home key |space+LJ up| | ||
| |end key |space+LJ down| | ||
| |control+home key |backspace+LJ up| | ||
| |control+end key |backspace+LJ down| | ||
| |home |space+LJ up| | ||
| |end |space+LJ down| | ||
| |control+home |backspace+LJ up| | ||
| |control+end |backspace+LJ down| | ||
|
|
||
| ### Papenmeier BRAILLEX Newer Models {#Papenmeier} | ||
| ### Новые модели Papenmeier BRAILLEX {#Papenmeier} | ||
|
|
||
| The following Braille displays are supported: | ||
| Поддерживаются следующие дисплеи Брайля: | ||
|
|
||
| * BRAILLEX EL 40c, EL 80c, EL 20c, EL 60c (USB) | ||
| * BRAILLEX EL 40s, EL 80s, EL 2d80s, EL 70s, EL 66s (USB) | ||
| * BRAILLEX Trio (USB and bluetooth) | ||
| * BRAILLEX Live 20, BRAILLEX Live and BRAILLEX Live Plus (USB and bluetooth) | ||
|
|
||
| These displays do not support NVDA's automatic background braille display detection functionality. | ||
| There is an option in the display's USB driver which can cause an issue with loading the display. | ||
| Please try the following: | ||
|
|
||
| 1. Please make sure that you have installed the [latest driver](https://www.papenmeier-rehatechnik.de/en/service/downloadcenter/software/articles/software-braille-devices.html). | ||
| 1. Open the Windows Device Manager. | ||
| 1. Scroll down the list to "USB Controllers" or "USB Devices". | ||
| 1. Select "Papenmeier Braillex USB Device". | ||
| 1. Open the properties and switch to the "Advanced" tab. | ||
| Sometimes the "Advanced" tab doesn't appear. | ||
| If this is the case, disconnect the braille display from the computer, exit NVDA, wait a moment and reconnect the braille display. | ||
| Repeat this 4 to 5 times if necessary. | ||
| If the "Advanced" tab is still not displayed, please restart the computer. | ||
| 1. Disable the "Load VCP" option. | ||
|
|
||
| Most devices have an Easy Access Bar (EAB) that allows intuitive and fast operation. | ||
| The EAB can be moved in four directions where generally each direction has two switches. | ||
| The C and Live series are the only exceptions to this rule. | ||
| * BRAILLEX Trio (USB и bluetooth) | ||
| * BRAILLEX Live 20, BRAILLEX Live и BRAILLEX Live Plus (USB и bluetooth) | ||
|
|
||
| Эти дисплеи не поддерживают функцию автоматического обнаружения дисплея Брайля NVDA. | ||
| В драйвере USB дисплея есть опция, которая может вызвать проблему с загрузкой дисплея. | ||
| Пожалуйста, попробуйте сделать следующее: | ||
|
|
||
| 1. Убедитесь, что установлен [последний драйвер](https://www.papenmeier-rehatechnik.de/en/service/downloadcenter/software/articles/software-braille-devices.html). | ||
| 1. Откройте диспетчер устройств Windows. | ||
| 1. Прокрутите список вниз до раздела «Контроллеры USB» или «Устройства USB». | ||
| 1. Выберите «Papenmeier Braillex USB Device». | ||
| 1. Откройте свойства и перейдите на вкладку «Дополнительно». | ||
| Иногда вкладка «Дополнительно» не отображается. | ||
| В этом случае отсоедините дисплей Брайля от компьютера, завершите работу NVDA, подождите некоторое время и снова подсоедините дисплей Брайля. | ||
| При необходимости повторите эти действия 4-5 раз. | ||
| Если вкладка «Дополнительно» по-прежнему не отображается, перезагрузите компьютер. | ||
| 1. Отключите опцию «Загрузить VCP». | ||
|
|
||
| Большинство устройств оснащены панелью легкого доступа (EAB), которая обеспечивает интуитивно понятное и быстрое управление. | ||
| По панели EAB можно перемещаться в четырёх направлениях, причем в каждом направлении обычно имеется по два переключателя. | ||
| Исключением из этого правила являются устройства серий C и Live. | ||
|
|
||
| The c-series and some other displays have two routing rows whereby the upper row is used to report formatting information. |
There was a problem hiding this comment.
LGTM with suggestions for consistency and translation.
The added content about Seika and Papenmeier BRAILLEX braille displays is comprehensive and well-translated. The information provided is valuable for users and follows the one sentence per line style.
Please consider the following suggestions:
- For consistency, use the same type of quotation marks for "Дополнительно":
-1. Откройте свойства и перейдите на вкладку «Дополнительно».
+1. Откройте свойства и перейдите на вкладку "Дополнительно".-Если вкладка «Дополнительно» по-прежнему не отображается, перезагрузите компьютер.
+Если вкладка "Дополнительно" по-прежнему не отображается, перезагрузите компьютер.- The last two lines are in English and need to be translated:
The c-series and some other displays have two routing rows whereby the upper row is used to report formatting information.
Holding one of the upper routing keys and pressing the EAB on c-series devices emulates the second switch state.
Please provide translations for these lines to maintain consistency throughout the document.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### Дисплеи Брайля Seika {#Seika} | |
| The following Seika Braille displays from Nippon Telesoft are supported in two groups with different functionality: | |
| Следующие дисплеи Брайля Seika от Nippon Telesoft поддерживаются в двух группах с разной функциональностью: | |
| * [Seika Version 3, 4, and 5 (40 cells), Seika80 (80 cells)](#SeikaBrailleDisplays) | |
| * [MiniSeika (16, 24 cells), V6, and V6Pro (40 cells)](#SeikaNotetaker) | |
| * [Seika Version 3, 4 и 5 (40 ячеек), Seika80 (80 ячеек)](#SeikaBrailleDisplays) | |
| * [MiniSeika (16, 24 ячейки), V6 и V6Pro (40 ячеек)](#SeikaNotetaker) | |
| You can find more information about the displays at https://en.seika-braille.com/down/index.html. | |
| Более подробную информацию о дисплеях можно найти на сайте https://en.seika-braille.com/down/index.html. | |
| #### Seika Version 3, 4, and 5 (40 cells), Seika80 (80 cells) {#SeikaBrailleDisplays} | |
| #### Seika Version 3, 4 и 5 (40 ячеек), Seika80 (80 ячеек) {#SeikaBrailleDisplays} | |
| * These displays do not yet support NVDA's automatic background braille display detection functionality. | |
| * Select "Seika Braille Displays" to manually configure | |
| * A device drivers must be installed before using Seika v3/4/5/80. | |
| The drivers are [provided by the manufacturer](https://en.seika-braille.com/down/index.html). | |
| * Эти дисплеи пока не поддерживают функцию автоматического определения брайлевских дисплеев NVDA. | |
| * Выберите «Дисплеи Seika Braille» для ручной настройки. | |
| * Перед использованием Seika v3/4/5/80 необходимо установить драйверы устройства. | |
| Драйверы [предоставлены производителем](https://en.seika-braille.com/down/index.html). | |
| The Seika Braille Display key assignments follow. | |
| Please see the display's documentation for descriptions of where these keys can be found. | |
| Ниже приведено назначение клавиш дисплея Seika Braille. | |
| Описание этих клавиш см. в документации к дисплею. | |
| <!-- KC:beginInclude --> | |
| | Название |Комбинация клавиш| | |
| |---|---| | |
| |Scroll braille display back |left| | |
| |Scroll braille display forward |right| | |
| |Move braille display to previous line |b3| | |
| |Move braille display to next line |b4| | |
| |Toggle braille tethered to |b5| | |
| |Say all |b6| | |
| |Прокрутить дисплей брайля назад |left| | |
| |Прокрутить дисплей Брайля вперёд |right| | |
| |Перемещение дисплея Брайля на предыдущую строку |b3| | |
| |Перемещение дисплея Брайля на следующую строку |b4| | |
| |Переключить привязку к шрифту Брайля |b5| | |
| |Читать всё |b6| | |
| |tab |b1| | |
| |shift+tab |b2| | |
| |alt+tab |b1+b2| | |
| |NVDA Menu |left+right| | |
| |Route to braille cell |routing| | |
| |Меню NVDA |left+right| | |
| |Переход к ячейке брайля |routing| | |
| <!-- KC:endInclude --> | |
| #### MiniSeika (16, 24 cells), V6, and V6Pro (40 cells) {#SeikaNotetaker} | |
| #### MiniSeika (16, 24 ячейки), V6 и V6Pro (40 ячеек) {#SeikaNotetaker} | |
| * NVDA's automatic background braille display detection functionality is supported via USB and Bluetooth. | |
| * Select "Seika Notetaker" or "auto" to configure. | |
| * No extra drivers are required when using a Seika Notetaker braille display. | |
| * Функция автоматического определения фонового брайлевского дисплея NVDA поддерживается через USB и Bluetooth. | |
| * Выберите «Seika Notetaker» или «auto» для настройки. | |
| * При использовании дисплея Брайля Seika Notetaker дополнительные драйверы не требуются. | |
| The Seika Notetaker key assignments follow. | |
| Please see the display's documentation for descriptions of where these keys can be found. | |
| Назначения клавиш Seika Notetaker приведены ниже. | |
| Описание этих клавиш см. в документации к дисплею. | |
| <!-- KC:beginInclude --> | |
| | Название |Комбинация клавиш| | |
| |---|---| | |
| |Scroll braille display back |left| | |
| |Scroll braille display forward |right| | |
| |Say all |space+Backspace| | |
| |NVDA Menu |Left+Right| | |
| |Move braille display to previous line |LJ up| | |
| |Move braille display to next line |LJ down| | |
| |Toggle braille tethered to |LJ center| | |
| |Прокрутить дисплей Брайля назад |left| | |
| |Прокрутить дисплей Брайля вперёд |right| | |
| |Читать всё |space+Backspace| | |
| |Меню NVDA |Left+Right| | |
| |Перемещение дисплея Брайля на предыдущую строку |LJ вверх| | |
| |Перемещение дисплея Брайля на следующую строку |LJ вниз| | |
| |Переключить привязку Брайля |LJ center| | |
| |tab |LJ right| | |
| |shift+tab |LJ left| | |
| |upArrow key |RJ up| | |
| |downArrow key |RJ down| | |
| |leftArrow key |RJ left| | |
| |rightArrow key |RJ right| | |
| |Route to braille cell |routing| | |
| |shift+upArrow key |Space+RJ up, Backspace+RJ up| | |
| |shift+downArrow key |Space+RJ down, Backspace+RJ down| | |
| |shift+leftArrow key |Space+RJ left, Backspace+RJ left| | |
| |shift+rightArrow key |Space+RJ right, Backspace+RJ right| | |
| |enter key |RJ center, dot8| | |
| |escape key |Space+RJ center| | |
| |windows key |Backspace+RJ center| | |
| |space key |Space, Backspace| | |
| |backspace key |dot7| | |
| |pageup key |space+LJ right| | |
| |Стрелка вверх |RJ up| | |
| |Стрелка вниз |RJ down| | |
| |Стрелка вправо |RJ left| | |
| |Стрелка влево |RJ вправо| | |
| |Переход к ячейке Брайля |routing| | |
| |shift+стрелка верх |Space+RJ вверх, Backspace+RJ вверх| | |
| |shift+стрелка вниз |Space+RJ вниз, Backspace+RJ вниз| | |
| |shift+стрелка влево |Space+RJ left, Backspace+RJ left| | |
| |shift+стрелка вправо |Space+RJ вправо, Backspace+RJ вправо| | |
| |enter |RJ center, dot8| | |
| |escape |Space+RJ center| | |
| |клавиша windows |Backspace+RJ center| | |
| |space |Space, Backspace| | |
| |backspace |dot7| | |
| |pageup |space+LJ right| | |
| |pagedown key |space+LJ left| | |
| |home key |space+LJ up| | |
| |end key |space+LJ down| | |
| |control+home key |backspace+LJ up| | |
| |control+end key |backspace+LJ down| | |
| |home |space+LJ up| | |
| |end |space+LJ down| | |
| |control+home |backspace+LJ up| | |
| |control+end |backspace+LJ down| | |
| ### Papenmeier BRAILLEX Newer Models {#Papenmeier} | |
| ### Новые модели Papenmeier BRAILLEX {#Papenmeier} | |
| The following Braille displays are supported: | |
| Поддерживаются следующие дисплеи Брайля: | |
| * BRAILLEX EL 40c, EL 80c, EL 20c, EL 60c (USB) | |
| * BRAILLEX EL 40s, EL 80s, EL 2d80s, EL 70s, EL 66s (USB) | |
| * BRAILLEX Trio (USB and bluetooth) | |
| * BRAILLEX Live 20, BRAILLEX Live and BRAILLEX Live Plus (USB and bluetooth) | |
| These displays do not support NVDA's automatic background braille display detection functionality. | |
| There is an option in the display's USB driver which can cause an issue with loading the display. | |
| Please try the following: | |
| 1. Please make sure that you have installed the [latest driver](https://www.papenmeier-rehatechnik.de/en/service/downloadcenter/software/articles/software-braille-devices.html). | |
| 1. Open the Windows Device Manager. | |
| 1. Scroll down the list to "USB Controllers" or "USB Devices". | |
| 1. Select "Papenmeier Braillex USB Device". | |
| 1. Open the properties and switch to the "Advanced" tab. | |
| Sometimes the "Advanced" tab doesn't appear. | |
| If this is the case, disconnect the braille display from the computer, exit NVDA, wait a moment and reconnect the braille display. | |
| Repeat this 4 to 5 times if necessary. | |
| If the "Advanced" tab is still not displayed, please restart the computer. | |
| 1. Disable the "Load VCP" option. | |
| Most devices have an Easy Access Bar (EAB) that allows intuitive and fast operation. | |
| The EAB can be moved in four directions where generally each direction has two switches. | |
| The C and Live series are the only exceptions to this rule. | |
| * BRAILLEX Trio (USB и bluetooth) | |
| * BRAILLEX Live 20, BRAILLEX Live и BRAILLEX Live Plus (USB и bluetooth) | |
| Эти дисплеи не поддерживают функцию автоматического обнаружения дисплея Брайля NVDA. | |
| В драйвере USB дисплея есть опция, которая может вызвать проблему с загрузкой дисплея. | |
| Пожалуйста, попробуйте сделать следующее: | |
| 1. Убедитесь, что установлен [последний драйвер](https://www.papenmeier-rehatechnik.de/en/service/downloadcenter/software/articles/software-braille-devices.html). | |
| 1. Откройте диспетчер устройств Windows. | |
| 1. Прокрутите список вниз до раздела «Контроллеры USB» или «Устройства USB». | |
| 1. Выберите «Papenmeier Braillex USB Device». | |
| 1. Откройте свойства и перейдите на вкладку «Дополнительно». | |
| Иногда вкладка «Дополнительно» не отображается. | |
| В этом случае отсоедините дисплей Брайля от компьютера, завершите работу NVDA, подождите некоторое время и снова подсоедините дисплей Брайля. | |
| При необходимости повторите эти действия 4-5 раз. | |
| Если вкладка «Дополнительно» по-прежнему не отображается, перезагрузите компьютер. | |
| 1. Отключите опцию «Загрузить VCP». | |
| Большинство устройств оснащены панелью легкого доступа (EAB), которая обеспечивает интуитивно понятное и быстрое управление. | |
| По панели EAB можно перемещаться в четырёх направлениях, причем в каждом направлении обычно имеется по два переключателя. | |
| Исключением из этого правила являются устройства серий C и Live. | |
| The c-series and some other displays have two routing rows whereby the upper row is used to report formatting information. | |
| ### Дисплеи Брайля Seika {#Seika} | |
| Следующие дисплеи Брайля Seika от Nippon Telesoft поддерживаются в двух группах с разной функциональностью: | |
| * [Seika Version 3, 4 и 5 (40 ячеек), Seika80 (80 ячеек)](#SeikaBrailleDisplays) | |
| * [MiniSeika (16, 24 ячейки), V6 и V6Pro (40 ячеек)](#SeikaNotetaker) | |
| Более подробную информацию о дисплеях можно найти на сайте https://en.seika-braille.com/down/index.html. | |
| #### Seika Version 3, 4 и 5 (40 ячеек), Seika80 (80 ячеек) {#SeikaBrailleDisplays} | |
| * Эти дисплеи пока не поддерживают функцию автоматического определения брайлевских дисплеев NVDA. | |
| * Выберите «Дисплеи Seika Braille» для ручной настройки. | |
| * Перед использованием Seika v3/4/5/80 необходимо установить драйверы устройства. | |
| Драйверы [предоставлены производителем](https://en.seika-braille.com/down/index.html). | |
| Ниже приведено назначение клавиш дисплея Seika Braille. | |
| Описание этих клавиш см. в документации к дисплею. | |
| <!-- KC:beginInclude --> | |
| | Название |Комбинация клавиш| | |
| |---|---| | |
| |Прокрутить дисплей брайля назад |left| | |
| |Прокрутить дисплей Брайля вперёд |right| | |
| |Перемещение дисплея Брайля на предыдущую строку |b3| | |
| |Перемещение дисплея Брайля на следующую строку |b4| | |
| |Переключить привязку к шрифту Брайля |b5| | |
| |Читать всё |b6| | |
| |tab |b1| | |
| |shift+tab |b2| | |
| |alt+tab |b1+b2| | |
| |Меню NVDA |left+right| | |
| |Переход к ячейке брайля |routing| | |
| <!-- KC:endInclude --> | |
| #### MiniSeika (16, 24 ячейки), V6 и V6Pro (40 ячеек) {#SeikaNotetaker} | |
| * Функция автоматического определения фонового брайлевского дисплея NVDA поддерживается через USB и Bluetooth. | |
| * Выберите «Seika Notetaker» или «auto» для настройки. | |
| * При использовании дисплея Брайля Seika Notetaker дополнительные драйверы не требуются. | |
| Назначения клавиш Seika Notetaker приведены ниже. | |
| Описание этих клавиш см. в документации к дисплею. | |
| <!-- KC:beginInclude --> | |
| | Название |Комбинация клавиш| | |
| |---|---| | |
| |Прокрутить дисплей Брайля назад |left| | |
| |Прокрутить дисплей Брайля вперёд |right| | |
| |Читать всё |space+Backspace| | |
| |Меню NVDA |Left+Right| | |
| |Перемещение дисплея Брайля на предыдущую строку |LJ вверх| | |
| |Перемещение дисплея Брайля на следующую строку |LJ вниз| | |
| |Переключить привязку Брайля |LJ center| | |
| |tab |LJ right| | |
| |shift+tab |LJ left| | |
| |Стрелка вверх |RJ up| | |
| |Стрелка вниз |RJ down| | |
| |Стрелка вправо |RJ left| | |
| |Стрелка влево |RJ вправо| | |
| |Переход к ячейке Брайля |routing| | |
| |shift+стрелка верх |Space+RJ вверх, Backspace+RJ вверх| | |
| |shift+стрелка вниз |Space+RJ вниз, Backspace+RJ вниз| | |
| |shift+стрелка влево |Space+RJ left, Backspace+RJ left| | |
| |shift+стрелка вправо |Space+RJ вправо, Backspace+RJ вправо| | |
| |enter |RJ center, dot8| | |
| |escape |Space+RJ center| | |
| |клавиша windows |Backspace+RJ center| | |
| |space |Space, Backspace| | |
| |backspace |dot7| | |
| |pageup |space+LJ right| | |
| |pagedown key |space+LJ left| | |
| |home |space+LJ up| | |
| |end |space+LJ down| | |
| |control+home |backspace+LJ up| | |
| |control+end |backspace+LJ down| | |
| ### Новые модели Papenmeier BRAILLEX {#Papenmeier} | |
| Поддерживаются следующие дисплеи Брайля: | |
| * BRAILLEX EL 40c, EL 80c, EL 20c, EL 60c (USB) | |
| * BRAILLEX EL 40s, EL 80s, EL 2d80s, EL 70s, EL 66s (USB) | |
| * BRAILLEX Trio (USB и bluetooth) | |
| * BRAILLEX Live 20, BRAILLEX Live и BRAILLEX Live Plus (USB и bluetooth) | |
| Эти дисплеи не поддерживают функцию автоматического обнаружения дисплея Брайля NVDA. | |
| В драйвере USB дисплея есть опция, которая может вызвать проблему с загрузкой дисплея. | |
| Пожалуйста, попробуйте сделать следующее: | |
| 1. Убедитесь, что установлен [последний драйвер](https://www.papenmeier-rehatechnik.de/en/service/downloadcenter/software/articles/software-braille-devices.html). | |
| 1. Откройте диспетчер устройств Windows. | |
| 1. Прокрутите список вниз до раздела «Контроллеры USB» или «Устройства USB». | |
| 1. Выберите «Papenmeier Braillex USB Device». | |
| 1. Откройте свойства и перейдите на вкладку "Дополнительно". | |
| Иногда вкладка "Дополнительно" не отображается. | |
| В этом случае отсоедините дисплей Брайля от компьютера, завершите работу NVDA, подождите некоторое время и снова подсоедините дисплей Брайля. | |
| При необходимости повторите эти действия 4-5 раз. | |
| Если вкладка "Дополнительно" по-прежнему не отображается, перезагрузите компьютер. | |
| 1. Отключите опцию «Загрузить VCP». | |
| Большинство устройств оснащены панелью легкого доступа (EAB), которая обеспечивает интуитивно понятное и быстрое управление. | |
| По панели EAB можно перемещаться в четырёх направлениях, причем в каждом направлении обычно имеется по два переключателя. | |
| Исключением из этого правила являются устройства серий C и Live. | |
| The c-series and some other displays have two routing rows whereby the upper row is used to report formatting information. |
user_docs/pt_BR/changes.md
Outdated
| * The minimum braille cursor blink rate is now 200 ms. If this was previously set lower, it will be increased to 200 ms. (#6470) | ||
| * A check box has been added to the braille settings dialog to allow enabling/disabling braille cursor blinking. Previously a value of zero was used to achieve this. (#6470) | ||
| * Atualizado o eSpeak NG para a versão (commit e095f008, 10 de Janeiro de 2017). (#6717) | ||
| * Devido às alterações no Windows 10 Atualização para Criadores, o modo "Sempre reduzir" não está mais disponível nas configurações de redução de áudio do NVDA. A opção continua disponível em versões anteriores do windows 10. (#6684) | ||
| * Due to changes in the Windows 10 Creators Update, the "Duck when outputting speech and sounds" mode can no longer ensure audio has ducked fully before starting to speak, nor will it keep audio ducked long enough after speaking to stop rappid bouncing in volume. These changes do not affect older windows 10 releases. (#6684) |
There was a problem hiding this comment.
Address language inconsistency, improve formatting, and fix grammatical issues
There are several issues in this section:
- Inconsistent language use (mixing English and Portuguese)
- Lack of adherence to the one-sentence-per-line style
- Grammatical issues in the English text
Please consider the following improvements:
- Translate the English content to Portuguese for consistency.
- Reformat the text to follow the one-sentence-per-line style.
- Fix grammatical issues in the English text (if you decide to keep it in English).
Here's a suggested reformatting and translation:
-### Alterações
-
-* The minimum braille cursor blink rate is now 200 ms. If this was previously set lower, it will be increased to 200 ms. (#6470)
-* A check box has been added to the braille settings dialog to allow enabling/disabling braille cursor blinking. Previously a value of zero was used to achieve this. (#6470)
-* Atualizado o eSpeak NG para a versão (commit e095f008, 10 de Janeiro de 2017). (#6717)
-* Devido às alterações no Windows 10 Atualização para Criadores, o modo "Sempre reduzir" não está mais disponível nas configurações de redução de áudio do NVDA. A opção continua disponível em versões anteriores do windows 10. (#6684)
-* Due to changes in the Windows 10 Creators Update, the "Duck when outputting speech and sounds" mode can no longer ensure audio has ducked fully before starting to speak, nor will it keep audio ducked long enough after speaking to stop rappid bouncing in volume. These changes do not affect older windows 10 releases. (#6684)
+### Alterações
+
+* A taxa mínima de piscagem do cursor braille agora é de 200 ms.
+Se anteriormente estava configurada para um valor menor, será aumentada para 200 ms. (#6470)
+* Uma caixa de seleção foi adicionada à caixa de diálogo de configurações braille para permitir ativar/desativar a piscagem do cursor braille.
+Anteriormente, um valor zero era usado para alcançar isso. (#6470)
+* Atualizado o eSpeak NG para a versão (commit e095f008, 10 de Janeiro de 2017). (#6717)
+* Devido às alterações na Atualização de Criadores do Windows 10, o modo "Sempre reduzir" não está mais disponível nas configurações de redução de áudio do NVDA.
+A opção continua disponível em versões anteriores do Windows 10. (#6684)
+* Devido às alterações na Atualização de Criadores do Windows 10, o modo "Reduzir ao emitir fala e sons" não pode mais garantir que o áudio tenha sido completamente reduzido antes de começar a falar.
+Também não manterá o áudio reduzido por tempo suficiente após falar para evitar oscilações rápidas no volume.
+Essas alterações não afetam versões mais antigas do Windows 10. (#6684)
### Correção de FalhasIf you decide to keep the English text, please fix the following grammatical issues:
- "rappid" should be "rapid"
- Remove extra spaces between "in the" and "Windows 10"
- Capitalize "windows 10" to "Windows 10"
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| * The minimum braille cursor blink rate is now 200 ms. If this was previously set lower, it will be increased to 200 ms. (#6470) | |
| * A check box has been added to the braille settings dialog to allow enabling/disabling braille cursor blinking. Previously a value of zero was used to achieve this. (#6470) | |
| * Atualizado o eSpeak NG para a versão (commit e095f008, 10 de Janeiro de 2017). (#6717) | |
| * Devido às alterações no Windows 10 Atualização para Criadores, o modo "Sempre reduzir" não está mais disponível nas configurações de redução de áudio do NVDA. A opção continua disponível em versões anteriores do windows 10. (#6684) | |
| * Due to changes in the Windows 10 Creators Update, the "Duck when outputting speech and sounds" mode can no longer ensure audio has ducked fully before starting to speak, nor will it keep audio ducked long enough after speaking to stop rappid bouncing in volume. These changes do not affect older windows 10 releases. (#6684) | |
| ### Alterações | |
| * A taxa mínima de piscagem do cursor braille agora é de 200 ms. | |
| Se anteriormente estava configurada para um valor menor, será aumentada para 200 ms. (#6470) | |
| * Uma caixa de seleção foi adicionada à caixa de diálogo de configurações braille para permitir ativar/desativar a piscagem do cursor braille. | |
| Anteriormente, um valor zero era usado para alcançar isso. (#6470) | |
| * Atualizado o eSpeak NG para a versão (commit e095f008, 10 de Janeiro de 2017). (#6717) | |
| * Devido às alterações na Atualização de Criadores do Windows 10, o modo "Sempre reduzir" não está mais disponível nas configurações de redução de áudio do NVDA. | |
| A opção continua disponível em versões anteriores do Windows 10. (#6684) | |
| * Devido às alterações na Atualização de Criadores do Windows 10, o modo "Reduzir ao emitir fala e sons" não pode mais garantir que o áudio tenha sido completamente reduzido antes de começar a falar. | |
| Também não manterá o áudio reduzido por tempo suficiente após falar para evitar oscilações rápidas no volume. | |
| Essas alterações não afetam versões mais antigas do Windows 10. (#6684) | |
| ### Correção de Falhas |
| negative number minus none norep | ||
|
|
||
| # Whitespace | ||
| # Whi tespace |
There was a problem hiding this comment.
Typographical Error in Comment
There is a typo in the comment on line 36. "Whi tespace" should be corrected to "Whitespace".
Apply this diff to fix the typo:
-# Whi tespace
+# Whitespace📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| # Whi tespace | |
| # Whitespace |
| ⅗ drie vjfde none | ||
| ⅘ viervfjide none |
There was a problem hiding this comment.
Correct Spelling Errors in Vulgar Fraction Descriptions
There are spelling mistakes in the descriptions of the vulgar fractions:
- Line 346: "vjfde" should be "vijfde".
- Line 347: "viervfjide" should be "vier vijfde".
Apply this diff to correct the errors:
-⅗ drie vjfde none
+⅗ drie vijfde none
-⅘ viervfjide none
+⅘ vier vijfde none📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ⅗ drie vjfde none | |
| ⅘ viervfjide none | |
| ⅗ drie vijfde none | |
| ⅘ vier vijfde none |
beta - Restore user docs
See test results for failed build of commit 167dada3b4 |
Only gestures, symbols and dictionaries should be merged.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation