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

[pt] More verbs/nouns fixes in disambiguation.xml #11033

Merged
merged 1 commit into from
Nov 19, 2024

Conversation

marcoagpinto
Copy link
Member

@marcoagpinto marcoagpinto commented Nov 19, 2024

More tons of fixes.

Summary by CodeRabbit

  • New Features

    • Enhanced disambiguation rules for Portuguese grammar, improving accuracy in identifying verb forms and their interactions with nouns and adjectives.
    • Introduced new rules to better handle complex sentence structures involving conjunctions, prepositions, and adverbs.
    • Added examples for clarity on the application of specific rules.
  • Bug Fixes

    • Removed outdated rules that caused inaccuracies in verb tagging.

Copy link
Contributor

coderabbitai bot commented Nov 19, 2024

Walkthrough

The pull request introduces modifications to the disambiguation.xml file within the Portuguese language module of LanguageTool. Key changes include updates to postagging patterns for verbs and nouns, the introduction of new disambiguation rules, and the removal of outdated rules that previously caused inaccuracies. Additionally, examples have been added to clarify the application of certain rules, reflecting an effort to enhance the accuracy and relevance of the disambiguation logic for contemporary Portuguese grammar.

Changes

File Path Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml - Updated postag patterns for verbs in rules VERB_VNOUN_NOUN_VERBS_RARE and VERB_O_A_VERB_SPS00_VERBS_RARE.
- Introduced new rules for conjunctions, prepositions, and adverbs.
- Removed redundant rules causing conflicts.
- Added examples for clarification.

Possibly related PRs

Suggested reviewers

  • jaumeortola
  • p-goulart
  • susanaboatto

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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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: 0

🧹 Outside diff range and nitpick comments (1)
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (1)

Line range hint 3959-3977: LGTM! Pattern adjustments improve accuracy of verb disambiguation.

The changes are well thought out:

  1. Adding VMSP3S0 maintains consistency with other rules
  2. Removing VMP00SM helps prevent false positives with past participles

Consider adding a brief comment explaining why VMP00SM was removed, as it would help future maintainers understand the rationale.

- <token postag='VMSP3S0|VMIP3S0|VMM02S0|VMSP2S0|VMIP2S0|VMN02S0|VMSF2S0|VMIP1S0' postag_regexp="yes"/>
+ <!-- VMP00SM removed to prevent false positives with past participles -->
+ <token postag='VMSP3S0|VMIP3S0|VMM02S0|VMSP2S0|VMIP2S0|VMN02S0|VMSF2S0|VMIP1S0' postag_regexp="yes"/>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between c94f5df and f6db8c6.

📒 Files selected for processing (1)
  • languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (4 hunks)
🔇 Additional comments (1)
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml (1)

Line range hint 3928-3944: LGTM! The addition of VMSP3S0 tag improves verb/noun disambiguation.

The change to include the third person singular present subjunctive form (VMSP3S0) in the pattern is a good improvement. This helps correctly identify more cases where words could be ambiguously interpreted as either verbs or nouns.

Let's verify the impact of this change:

✅ Verification successful

The VMSP3S0 tag addition in the verb-noun disambiguation rule is correctly implemented

Based on the verification results, the rule is well-structured and the examples demonstrate proper disambiguation scenarios:

  • The pattern correctly matches verb forms (including VMSP3S0) followed by nouns
  • The rule has appropriate examples showing disambiguation cases like "torna rosas"
  • The tag is consistently used across similar patterns in the file
  • The exception handling for "tá" prevents false positives
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for cases where the new pattern would apply
# Expected: Find examples where VMSP3S0 verbs could be confused with nouns

# Search for potential verb-noun ambiguity cases
rg -U "VMSP3S0.*NC" ".*\.dict"

# Search for existing rule usage
rg -A 2 "VMSP3S0.*NC" "disambiguation.xml"

Length of output: 183


Script:

#!/bin/bash
# Let's try a more precise search in the language resources directory
# Search for the dictionary files and disambiguation rules
fd -e xml -e dict . languagetool-language-modules/pt/

# Then search for the specific pattern in the found files
rg -U "VMSP3S0" languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/

# Look for examples of verb-noun ambiguity rules
rg -A 5 "postag='VM.*NC" languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml

Length of output: 1937


Script:

#!/bin/bash
# Let's look at the specific rule context and similar patterns
rg -B 2 -A 10 "VMSP3S0\|VMIP3S0\|VMM02S0" languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml

# Also search for example sentences in comments near this pattern
rg -B 5 -A 15 "Examples:" --multiline languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml | rg -B 5 -A 15 "VMSP3S0"

Length of output: 1494

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant