[pt-PT] Broke down rulegroup ID:INFORMALITIES into two rulegroups:COLOQUIALISMOS_PT_PT

[marcoagpinto]

Like promised (with a bit of delay), I broke the rulegroup into two and cleaned the suggestion messages.

Summary by CodeRabbit

• New Features

  • Enhanced language processing capabilities for Portuguese (Portugal) with new and refined rules.
  • Added rules targeting colloquialisms, redundancy, and pleonasm to improve clarity in language use.
  • Introduced antipatterns to identify and suggest corrections for informal phrases.

• Improvements

  • Updated existing rules for better clarity and effectiveness, including more examples to illustrate usage.

[coderabbitai]

Walkthrough

The pull request introduces extensive updates to the style.xml file in the Portuguese language modules of LanguageTool. Key changes include the addition of new rules, modifications to existing rules, and restructuring of rule groups to enhance clarity and effectiveness in language processing for Portuguese. New rules target colloquialisms and aim to reduce redundancy, while example corrections have been made to better illustrate the rules' applications.

Changes

File Path	Change Summary
languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml	- Added multiple new rules for improving language usage, including rules for colloquialisms and formal expressions. - Modified existing rules for clarity and effectiveness, such as enhancing rules for "prazer" and "ciclo vicioso." - Restructured rule groups for better organization.

Possibly related PRs

• [pt-PT] Fixed FPs in rule ID:VERBO_PRONOMINAL_DE_V3 #10907: Modifies the same rules in style.xml, enhancing the rules for "prazer" and "ciclo vicioso."
• [pt-PT] Added colloquialism rule to rulegroup ID:INFORMALITIES #10911: Adds a new rule related to colloquialisms, aligning with the main PR's focus.
• [pt-PT] Removed "temp_off" from rule ID:VERBO_PRONOMINAL_DE_V3 #10912: Involves modifications to the "VERBO_PRONOMINAL_DE_V3" rule, which is also mentioned in the main PR.
• [pt-PT] Improved rule ID:CONFUSÃO_CAIXA_EMBALAGEM and cleaned other rule #10932: Improves the "CONFUSÃO_CAIXA_EMBALAGEM" rule, directly related to changes in the main PR.
• [pt-PT] Removed "temp_off" from rules #10935: Removes the "temp_off" designation from the "CONFUSÃO_CAIXA_EMBALAGEM" rule, relevant to the main PR's updates.
• [pt-PT] Better suggestion in rule ID:CICLO_VICIOSO #10934: Enhances the "CICLO_VICIOSO" rule, which is also modified in the main PR.
• [pt-PT] Removed "temp_off" from rule ID:VERBO_PARA_PRONOME_PESSOAL_V2 #10933: Removes the "temp_off" designation from the "VERBO_PARA_PRONOME_PESSOAL_V2" rule, relevant to the main PR's updates.

Suggested reviewers

• 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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (3)

languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml (3)

Line range hint 597-1271: LGTM: Comprehensive informal language detection.

The INFORMALITIES rule group effectively targets a wide range of informal expressions in Portuguese. The use of antipatterns to avoid false positives is commendable.

Consider breaking down this large rule group into smaller, more focused sub-groups for easier maintenance and updates. This could improve the overall organization and make it easier to manage in the future.

---

Line range hint 1274-2122: LGTM: Extensive coverage of European Portuguese colloquialisms.

The COLOQUIALISMOS_PT_PT rule group provides comprehensive coverage of colloquial expressions specific to European Portuguese. The patterns and suggestions are well-defined and appropriate.

Consider organizing these rules into sub-categories based on the type of colloquialism (e.g., idioms, informal verbs, etc.) to improve maintainability and readability.

Adding more inline comments or documentation to explain the rationale behind certain rules would be beneficial for future maintenance and for contributors who might not be familiar with all the nuances of European Portuguese.

---

Line range hint 1-3484: LGTM: Comprehensive and well-structured Portuguese style rules.

This file demonstrates a thorough approach to addressing style and formality issues in European Portuguese. The rules are well-crafted and make good use of LanguageTool's features such as antipatterns and exceptions.

To further improve this excellent ruleset:

1. Consider grouping similar rules together or creating a hierarchical structure for easier navigation and maintenance.
2. Add more high-level comments explaining the purpose and scope of each major section or rule group.
3. Implement a consistent naming convention for all rules to enhance readability and maintainability.

These suggestions aim to make the already strong ruleset even more robust and easier to maintain in the long term.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 2a0ef5a and e282f3c.

📒 Files selected for processing (1)

• languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml (58 hunks)

🧰 Additional context used

🔇 Additional comments (1)

languagetool-language-modules/pt/src/main/resources/org/languagetool/rules/pt/pt-PT/style.xml (1)

Line range hint 597-1271: LGTM: Well-structured rule for pharmaceutical terminology.

The rule CONFUSÃO_CAIXA_EMBALAGEM is well-implemented and addresses an important distinction in pharmaceutical terminology. It correctly suggests using "embalagem" instead of "caixa" in the context of medications. The pattern matching and exceptions are appropriately defined.