Skip to content

Conversation

FadeMind
Copy link

Updated Polish Language file.
Regards

Copy link

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors and Warnings Count
❌ forbidden-pattern 22
⚠️ non-alpha-in-dictionary 13

See ❌ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

  • binary file (or some other file you wouldn't want to check at all).

    Please add a file path to the excludes.txt file matching the containing file.

    File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

    ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

  • well-formed pattern.

    If you can write a pattern that would match it,
    try adding it to the patterns.txt file.

    Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

    Note that patterns can't match multiline strings.

Copy link
Contributor

coderabbitai bot commented Jun 14, 2025

📝 Walkthrough

Walkthrough

The update modifies the Polish localization file for Flow Launcher, correcting existing translations, adding missing Polish strings, and improving consistency across UI elements. No changes were made to the application's logic, structure, or exported entities; all edits are confined to translation and textual improvements.

Changes

File(s) Change Summary
Flow.Launcher/Languages/pl.xaml Corrected and improved Polish translations; fixed typos; added missing strings; updated UI terms

Poem

In fields of code where languages grow,
Polish strings now shimmer and glow.
Each word aligned, each typo gone,
The interface sings a clearer song.
From menus to tips, all polished anew—
A rabbit's hop brings clarity through! 🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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: 3

🔭 Outside diff range comments (1)
Flow.Launcher/Languages/pl.xaml (1)

443-445: ⚠️ Potential issue

Typo in custom query shortcut keys
Keys customeQueryShortcutTitle, customeQueryShortcutTips, and customeQueryShortcutGuide should be customQueryShortcutTitle, customQueryShortcutTips, and customQueryShortcutGuide to align with code.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 566b7d3 and 92c0663.

📒 Files selected for processing (1)
  • Flow.Launcher/Languages/pl.xaml (8 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Check Spelling
🔇 Additional comments (16)
Flow.Launcher/Languages/pl.xaml (16)

61-61: Approve translation adjustment for cursor tracking key
SearchWindowScreenCursor value correctly updated to “Podążaj za kursorem myszy”.


126-127: Approve translation for Korean IME links
KoreanImeOpenLink and its tooltip are accurately translated and contextually consistent.


129-130: Approve translation for Korean IME registry setting
KoreanImeRegistry and its tooltip clearly convey the setting instructions.


131-135: Approve home page UI strings
Translations for homePage, homePageToolTip, historyResultsForHomePage, historyResultsCountForHomePage, and homeToggleBoxToolTip are clear and consistent.


136-137: Approve topmost window strings
showAtTopmost and its tooltip are translated correctly.


217-217: Approve corrected spelling for opacity
opacity value changed to correct Polish “Przezroczystość”.


358-358: Approve translation for cache folder
cachefolder translation is accurate and matches context.


366-366: Approve translation for advanced settings tab
advanced value “Zaawansowane” correctly matches UI context.


373-377: Approve release notes window updates
Translations for seeMoreReleaseNotes, checkNetworkConnectionTitle, checkNetworkConnectionSubTitle, appUpdateTitle, and appUpdateButtonContent are coherent and accurate.


381-381: Approve “learn more” link in File Manager dialog
fileManager_learnMore translation is clear and inviting.


384-384: Approve corrected spelling for File Manager
fileManager_name updated from “Menadżer plików” to correct “Menedżer plików”.


389-390: Approve File Manager path error messages
fileManagerPathNotFound and fileManagerPathError translations are accurate and user-friendly.


418-418: Approve translation for copy failure message
failedToCopy value is clear, concise, and matches application tone.


426-427: Approve home section titles
homeTitle and homeTips properly reflect the feature and its usage.


483-486: Approve File Manager not found error translations
fileManagerNotFoundTitle and the associated message are translated correctly and clearly.


488-489: Approve folder and browser open error messages
folderOpenError and browserOpenError translations are precise and informative.

Comment on lines +115 to +125
<system:String x:Key="KoreanImeGuide">
Metoda wprowadzania tekstu w języku koreańskim używana w systemie Windows 11 może powodować pewne problemy w Flow Launcher.

If you experience any problems, you may need to enable &quot;Use previous version of Korean IME&quot;.
Jeśli napotkasz jakiekolwiek trudności, możesz potrzebować włączyć opcję „Użyj poprzedniej wersji koreańskiego IME.

Otwórz Ustawienia w systemie Windows 11 i przejdź do:

Open Setting in Windows 11 and go to:
Czas i język &gt; Język i region &gt; Koreański &gt; Opcje języka &gt; Klawiatura – Microsoft IME &gt; Zgodność,

Time &amp; Language &gt; Language &amp; Region &gt; Korean &gt; Language Options &gt; Keyboard - Microsoft IME &gt; Compatibility,

and enable &quot;Use previous version of Microsoft IME&quot;.


</system:String>
<system:String x:Key="KoreanImeOpenLink">Open Language and Region System Settings</system:String>
<system:String x:Key="KoreanImeOpenLinkToolTip">Opens the Korean IME setting location. Go to Korean &gt; Language Options &gt; Keyboard - Microsoft IME &gt; Compatibility</system:String>
a następnie włącz opcję „Użyj poprzedniej wersji Microsoft IME”.
</system:String>
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Preserve whitespace in multiline Korean IME guide
The <system:String x:Key="KoreanImeGuide"> block contains line breaks that will be collapsed unless you add xml:space="preserve" to the tag.

🤖 Prompt for AI Agents
In Flow.Launcher/Languages/pl.xaml around lines 115 to 125, the multiline string
for the Korean IME guide lacks the attribute xml:space="preserve", causing line
breaks to be collapsed. To fix this, add xml:space="preserve" to the
<system:String x:Key="KoreanImeGuide"> tag to ensure all whitespace and line
breaks are preserved as intended.

Comment on lines 429 to +430
<!-- Custom Query Hotkey Dialog -->
<system:String x:Key="customeQueryHotkeyTitle">Skrót klawiszowy niestandardowych zapyta</system:String>
<system:String x:Key="customeQueryHotkeyTitle">Skrót klawiszowy niestandardowych zapytań</system:String>
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

Typo in custom query hotkey keys
Keys customeQueryHotkeyTitle and customeQueryHotkeyTips include an extra “e” and won’t map correctly. Rename to customQueryHotkeyTitle and customQueryHotkeyTips.

🤖 Prompt for AI Agents
In Flow.Launcher/Languages/pl.xaml around lines 429 to 430, the keys
'customeQueryHotkeyTitle' and 'customeQueryHotkeyTips' contain a typo with an
extra 'e'. Rename these keys to 'customQueryHotkeyTitle' and
'customQueryHotkeyTips' respectively to ensure correct mapping.

<system:String x:Key="general">Ogólne</system:String>
<system:String x:Key="portableMode">Tryb przenośny</system:String>
<system:String x:Key="portableModeToolTIp">Przechowuj wszystkie ustawienia i dane użytkownika w jednym folderze (Przydatne, gdy używane na dyskach wymiennych lub usługach chmurowych).</system:String>
<system:String x:Key="portableModeToolTIp">Przechowuj wszystkie ustawienia i dane użytkownika w jednym folderze (przydatne, gdy używane na dyskach wymiennych lub usługach chmurowych).</system:String>
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Typo in ‘portableModeToolTIp’ key
The property name should be portableModeToolTip (camel-case ‘Tip’) to match the naming convention of other tooltip keys; otherwise this tooltip won’t be applied.

🤖 Prompt for AI Agents
In Flow.Launcher/Languages/pl.xaml at line 52, the key name
'portableModeToolTIp' contains a typo with an uppercase 'I' in 'Tip'. Rename the
key to 'portableModeToolTip' using camel-case to match other tooltip keys and
ensure the tooltip is correctly applied.

@Jack251970
Copy link
Member

Thanks for your contribution in localization! And please follow steps in README.md, thanks!

@Jack251970
Copy link
Member

Our project localization is based on Crowdin. If you would like to change them, please go to https://crowdin.com/project/flow-launcher.

@Jack251970 Jack251970 closed this Jun 14, 2025
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.

2 participants