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 #11095

Merged
merged 3 commits into from
Dec 8, 2024

Conversation

marcoagpinto
Copy link
Member

@marcoagpinto marcoagpinto commented Dec 8, 2024

More verbs/nouns fixes for words not in the dictionary: “peixe-DOURADO” (“dourado” would appear as a past participle).

Summary by CodeRabbit

  • New Features
    • Introduced a new disambiguation rule for Portuguese to handle hyphenated nouns with past participles.
  • Bug Fixes
    • Modified an existing disambiguation rule to improve its functionality with the new rule structure.
  • Chores
    • Commented out an example sentence in the style rules for future reference.

Copy link
Contributor

coderabbitai bot commented Dec 8, 2024

Walkthrough

The changes in this pull request introduce a new rule in the disambiguation.xml file for the Portuguese language module of LanguageTool. The rule, NOUN_HYPHEN_PASTPARTICIPLE_VERBS_RARE, targets the removal of past participles from hyphenated nouns when they are not dictionary entries. Additionally, modifications were made to the existing rule PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE to ensure compatibility with the new rule structure. These adjustments enhance the disambiguation capabilities of the tool for Portuguese grammar.

Changes

File Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/resource/pt/disambiguation.xml - Added new rule: NOUN_HYPHEN_PASTPARTICIPLE_VERBS_RARE to remove past participles from hyphenated nouns.
- Modified existing rule: PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE for compatibility with the new rule.
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/style.xml - Commented out an example sentence related to a sensitive topic for future reference.

Possibly related issues

Possibly related PRs

Suggested reviewers

  • jaumeortola
  • p-goulart

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)

3819-3824: Consider adding more specific token restrictions.

The pattern could be more restrictive to avoid potential false positives. Consider adding specific exceptions for common cases where the past participle should retain its verb tag.

 <token postag="N.+|AQ.+" postag_regexp="yes"><exception postag_regexp='yes' postag='V.+|CS|RG|CC|SPS.+|[DP].+'/></token>
 <token regexp='yes' spacebefore='no'>&hifen;</token>
 <marker>
-    <token spacebefore='no' postag='VMP00.+' postag_regexp="yes"/>
+    <token spacebefore='no' postag='VMP00.+' postag_regexp="yes">
+      <exception regexp='yes'>estado|visto|feito|dito|posto</exception>
+    </token>
 </marker>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ed104c6 and 9e29bfc.

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

3816-3836: LGTM! Well-structured new rule for handling hyphenated nouns with past participles.

The rule correctly handles cases like "peixe-DOURADO" by removing verb tags when a noun/adjective is followed by a hyphenated past participle. The pattern matching and examples are comprehensive.


3827-3835: Great documentation with examples!

The examples provided are comprehensive and clearly illustrate the rule's purpose. This will help future maintainers understand the intended behavior.


3816-3837: Verify rule ordering impact.

The placement of the new rule before PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE seems correct, but let's verify there are no unintended interactions.

✅ Verification successful

Based on the search results, I can see that there are no other rules in the disambiguation.xml file that handle hyphenated words with past participles in a way that would conflict with the NOUN_HYPHEN_PASTPARTICIPLE_VERBS_RARE rule. The rule's pattern is unique in how it specifically targets:

  1. A noun or adjective followed by
  2. A hyphen followed by
  3. A past participle verb form

Let me verify the order by searching for the referenced rule:


Rule ordering is correct and no conflicts found

The placement of NOUN_HYPHEN_PASTPARTICIPLE_VERBS_RARE before PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE is appropriate since:

  1. The rules have distinct patterns that don't overlap - one handles hyphenated constructs while the other handles past participles followed by specific words
  2. The examples in both rules demonstrate different use cases
  3. The rules have different disambiguation actions that don't interfere with each other
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for potential rule conflicts by looking for similar patterns
# in other disambiguation rules

# Search for rules that also handle past participles
rg -A 5 'postag=.VMP00.+.' 

# Search for rules that handle hyphenated words
rg -A 5 '&hifen;'

Length of output: 68276


Script:

#!/bin/bash
# Search for the PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE rule and its context
rg -B 5 -A 5 'PELA_COMO_SOBRE_NADA_ACERCA_ELAR_VERBS_RARE'

Length of output: 1782

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)

3817-3818: Consider adding more context to the placement comment.

The comment about moving the rule down could be more descriptive about why this placement is necessary, e.g., what specific rules it needs to work with.

-    <!-- Moved the rule down to assure it works correctly. -->
+    <!-- Moved the rule down after other verb disambiguation rules to ensure correct processing order and avoid interference with verb pattern matching. -->
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 97db98a and f0ac8fe.

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

3816-3827: LGTM! Well-structured disambiguation rule for hyphenated words.

The rule correctly handles the disambiguation of past participles in hyphenated compounds like "peixe-DOURADO", removing verb readings when they follow nouns/adjectives. The pattern matching and exceptions are comprehensive.


3828-3835: LGTM! Well-documented examples.

The examples effectively demonstrate various use cases for the rule, including different types of hyphenated compounds where past participles should not be interpreted as verbs.

@marcoagpinto marcoagpinto merged commit 517a9a5 into master Dec 8, 2024
5 checks passed
@marcoagpinto
Copy link
Member Author

It DIDN'T break Premium!

Portuguese (Portugal): 729 total matches
Portuguese (Portugal): 949999 total sentences considered
Portuguese (Portugal): ø0.00 rule matches per sentence

1.txt

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