Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update translations from l10n #17262

Closed
wants to merge 3 commits into from
Closed

Update translations from l10n #17262

wants to merge 3 commits into from

Conversation

SaschaCowley
Copy link
Member

@SaschaCowley SaschaCowley commented Oct 8, 2024

Rebased nvaccess/nvda-l10n:beta on nvaccess/nvda:beta, dropping commits that didn't touch source/locale, and editing commits that did but also touched user_docs to remove changes to user_docs.

  • L10n updates for: bg From translation svn revision: 83941 modified from l10n@7c384b337
  • L10n updates for: sr From translation svn revision: 83941 same as l10n@2768eba5c
  • L10n updates for: nl From translation svn revision: 83952 same as l10n@d3ac473f8

Summary by CodeRabbit

  • New Features

    • Enhanced symbol definitions for Bulgarian, Dutch, and Serbian locales, adding new symbols, punctuation marks, and mathematical operators.
    • Expanded coverage of whitespace characters and their translations.
  • Bug Fixes

    • Updated regex patterns for existing symbols to improve accuracy and clarity.
  • Documentation

    • Updated copyright year in the Dutch locale to 2024.

NVDA translation automation added 3 commits October 8, 2024 12:56
From translation svn revision: 83941

Authors:
Zahari Yurukov <[email protected]>
Kostadin Kolev <[email protected]>

Stats:
2	2	source/locale/bg/symbols.dic
341	316	user_docs/bg/changes.md
 2 files changed, 343 insertions(+), 318 deletions(-)
From translation svn revision: 83941

Authors:
Nikola Jovic <[email protected]>
Janko Valencik <[email protected]>
Zvonimir <[email protected]>
Danijela Popovic <[email protected]>

Stats:
2	2	source/locale/sr/symbols.dic
 1 file changed, 2 insertions(+), 2 deletions(-)
From translation svn revision: 83952

Authors:
Bram Duvigneau <[email protected]>
Bart Simons <[email protected]>
A Campen <[email protected]>
Leonard de Ruijter <[email protected]>

Stats:
43	51	source/locale/nl/symbols.dic
 1 file changed, 43 insertions(+), 51 deletions(-)
@SaschaCowley SaschaCowley requested a review from a team as a code owner October 8, 2024 02:14
Copy link
Contributor

coderabbitai bot commented Oct 8, 2024

Walkthrough

This pull request introduces comprehensive updates to the symbols.dic files for the Bulgarian, Dutch, and Serbian locales in the NVDA project. The changes include the addition of new symbols, modifications to existing entries, and updates to regex patterns and translations. Each locale's dictionary has been enhanced to improve the representation of punctuation, mathematical symbols, and whitespace characters, ensuring better usability and clarity for users.

Changes

File Path Change Summary
source/locale/bg/symbols.dic Added new entries for various punctuation marks, mathematical symbols, and braille representations. Updated definitions for existing symbols.
source/locale/nl/symbols.dic Updated copyright year, modified regex for decimal points, added new entries, and refined existing symbol definitions.
source/locale/sr/symbols.dic Expanded definitions for punctuation, whitespace, arithmetic, and logical operators with new entries and regex patterns.

Possibly related PRs

  • Add support for custom symbol dictionaries #16823: This PR adds support for custom symbol dictionaries, which is directly related to the changes made in the symbols.dic file for the Bulgarian locale, enhancing the handling of symbol definitions.
  • Update translations #17137: This PR updates translations, including entries in the localization files, which may relate to the updates made in the symbols.dic file for the Bulgarian locale, particularly regarding braille table names and translations.

Suggested labels

conceptApproved

Suggested reviewers

  • seanbudd

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (2)
source/locale/bg/symbols.dic (1)

Line range hint 108-109: Verify the mapping of single quotation marks

The single quotation marks are currently mapped as:

  • to "ляво ударение"
  • to "дясно ударение"

Since and represent left and right single quotation marks, consider mapping them to "леви единични кавички" and "десни единични кавички" respectively for clarity.

‘	леви единични кавички
’	десни единични кавички
source/locale/nl/symbols.dic (1)

188-190: Standardize division symbol descriptions

The division symbols and ÷ have different descriptions:

  • is mapped to gedeeld door
  • ÷ is mapped to delen door

To maintain consistency and avoid confusion, consider using the same description for both symbols, unless there is a specific reason for the distinction.

Apply this suggestion to unify the descriptions:

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c47ff17 and 06cc2a9.

📒 Files selected for processing (3)
  • source/locale/bg/symbols.dic (2 hunks)
  • source/locale/nl/symbols.dic (13 hunks)
  • source/locale/sr/symbols.dic (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
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. When providing code suggestions, particularly when requested, ensure GitHub's suggestion format is used, i.e.: suggestion <code changes>

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. When providing code suggestions, particularly when requested, ensure GitHub's suggestion format is used, i.e.: suggestion <code changes>

source/locale/sr/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. When providing code suggestions, particularly when requested, ensure GitHub's suggestion format is used, i.e.: suggestion <code changes>

🔇 Additional comments (5)
source/locale/nl/symbols.dic (4)

22-23: Ensure consistency in thousands separator representation

The term punt is used as the replacement for thousands separator. Since punt can mean both 'point' and 'period' in Dutch, ensure that this does not cause confusion with the decimal point (komma in Dutch).

Consider clarifying the replacement text if necessary.


184-184: Updated multiplication symbol description improves clarity

The symbol × now has the description maal, which accurately represents multiplication in Dutch. This change enhances user understanding.


219-219: Confirm the accuracy of mathematical term for '≈'

The symbol is described as bijna gelijk aan ('almost equal to'). Ensure that this term is the standard mathematical expression used in Dutch for this symbol.


9-11: Verify the correctness of the updated regular expressions

The regular expressions for decimal point, thousands separator, and begin-word ' have been updated. Please ensure that they correctly match the intended patterns for the Dutch locale:

  • decimal point should match commas used as decimal separators (e.g., 123,45).
  • thousands separator should match periods used as thousands separators (e.g., 1.234).
  • begin-word ' should match apostrophes at the beginning of words (e.g., 't in 't is waar).

You can run the following script to test these regex patterns:

✅ Verification successful

Regular expressions for Dutch locale verified successfully

  • All updated regular expressions for decimal point, thousands separator, and begin-word ' are functioning as intended.
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Test the updated regular expressions for Dutch locale.

# Test decimal point regex
echo "Testing decimal point regex:"
echo "Number: 123,45" | rg -o '(?<![^\d -])\,(?=\d)'

# Test thousands separator regex
echo "Testing thousands separator regex:"
echo "Number: 1.234" | rg -o '(?<=\d)\.(?=\d{3})'

# Test begin-word apostrophe regex
echo "Testing begin-word apostrophe regex:"
echo "Phrase: 't is waar" | rg -o "((?<=\s)|(?<=^))'(?=\w(\s|$|[-.,?!]))"

Length of output: 1108


Script:

#!/bin/bash
# Description: Test the updated regular expressions for Dutch locale with PCRE2 enabled.

# Test decimal point regex
echo "Testing decimal point regex:"
echo "Number: 123,45" | rg --pcre2 -o '(?<![^\d -])\,(?=\d)'

# Test thousands separator regex
echo "Testing thousands separator regex:"
echo "Number: 1.234" | rg --pcre2 -o '(?<=\d)\.(?=\d{3})'

# Test begin-word apostrophe regex
echo "Testing begin-word apostrophe regex:"
echo "Phrase: 't is waar" | rg --pcre2 "((?<=\s)|(?<=^))'(?=\w(\s|$|[-.,?!]))"

Length of output: 461

source/locale/sr/symbols.dic (1)

106-107: Symbols for single quotation marks added correctly

The entries for the left and right single quotation marks ( and ) have been appropriately added with their Serbian translations levi polunavodnik and desni polunavodnik.

Comment on lines +95 to 98
леви кавички
′ прим
″ секонд
‴ терц
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Potential inconsistencies in prime symbol translations

The prime symbols are mapped as follows:

  • to "прим"
  • to "секунд"
  • to "терц"

While "прим" for is appropriate, using "секунд" (which means "second") for and "терц" (which can mean "third") for may cause confusion, especially if interpreted as units of time rather than mathematical notation.

Consider revising the translations to reflect their mathematical meaning to avoid ambiguity.

Comment on lines +104 to 107
десни кавички
” десни кавички
‘ ляво ударение
’ дясно ударение
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Incorrect mapping of double quotation marks

The symbols for double quotation marks are mapped as:

  • mapped to "десни кавички"
  • mapped to "десни кавички"

However, is the LEFT DOUBLE QUOTATION MARK and should be mapped to "леви кавички" (left quotation marks). Mapping both symbols to "десни кавички" could lead to confusion in distinguishing opening and closing quotes.

Please apply the following correction:

Suggested change
“ десни кавички
” десни кавички
‘ ляво ударение
’ дясно ударение
“ леви кавички
” десни кавички

@SaschaCowley SaschaCowley marked this pull request as draft October 8, 2024 02:36
@github-actions github-actions bot added this to the 2025.1 milestone Oct 8, 2024
@SaschaCowley SaschaCowley removed this from the 2025.1 milestone Oct 8, 2024
@SaschaCowley SaschaCowley deleted the updateTranslations branch October 8, 2024 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant