Skip to content

Conversation

kunalaswani
Copy link
Contributor

Translations added for Serbian (SR).

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Cloud-compatibility
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Smoketest:

  • Send notifications about my Pull Request position in Smoketest queue.
  • Test my draft Pull Request.

Testing:

Translations added for Serbian (SR).

Signed-off-by: Kunal Aswani <[email protected]>
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds Serbian (SR) language translations for the HPCC Platform ECL Watch web interface as part of JIRA ticket HPCC-34905. The translations are being added to support the 10.0.x branch.

  • Adds comprehensive Serbian translations for ECL Watch UI strings
  • Includes new translation entries and corrects existing ones
  • Updates the translation file structure and formatting

LogFilterStartDateTooltip: "Укључите редове дневника од почетка датог временског опсега",
LogFiltersUnavailable: "Филтери дневника нису доступни",
LogFilterTimeRequired: 'Изаберите или "Од и до датума" или "Релативни временски опсег"',
LogFilterTimeRequired: "Изаберите или Од и до датума или Релативни временски бафер евиденције“",
Copy link
Preview

Copilot AI Sep 30, 2025

Choose a reason for hiding this comment

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

The translation appears to contain a typo. 'бафер евиденције' (buffer of evidence) should likely be 'опсег' (range) to match the context of time filtering, making it 'Релативни временски опсег'.

Suggested change
LogFilterTimeRequired: "Изаберите или „Од и до датума“ или „Релативни временски бафер евиденције“",
LogFilterTimeRequired: "Изаберите или „Од и до датума“ или „Релативни временски опсег“",

Copilot uses AI. Check for mistakes.

Comment on lines 747 to +749
PerformingLayout: "Извршава Лejaут...",
PerformingLayoutFailed: "Лаиоут Фаилед Изаберите другачијег ⬆рооте",
PerformingLayoutLongRunning: "≥Перформисање лажног материјала нестрпљиво?",
Copy link
Preview

Copilot AI Sep 30, 2025

Choose a reason for hiding this comment

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

These translations contain apparent corruption or encoding issues. Line 748 has 'Лаиоут Фаилед' (Layout Failed in mixed languages) and '⬆рооте' with special characters. Line 749 has '≥Перформисање лажног материјала нестрпљиво?' which appears garbled and doesn't make sense contextually.

Suggested change
PerformingLayout: "Извршава Лejaут...",
PerformingLayoutFailed: "Лаиоут Фаилед Изаберите другачијег ⬆рооте",
PerformingLayoutLongRunning: "≥Перформисање лажног материјала нестрпљиво?",
PerformingLayout: "Извршава распоред...",
PerformingLayoutFailed: "Неуспешно извршавање распореда. Изаберите други корен.",
PerformingLayoutLongRunning: "Извршавање распореда може потрајати...",

Copilot uses AI. Check for mistakes.

Copy link

Jira Issue: https://hpccsystems.atlassian.net//browse/HPCC-34905

Jirabot Action Result:
Workflow Transition To: Merge Pending
Updated PR

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