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

[pl]: Missing keys + stylistical fixes, better comprehension #4761

Merged
merged 5 commits into from
May 6, 2024

Conversation

makowskid
Copy link
Contributor

No description provided.

@makowskid makowskid merged commit ad17d01 into Laravel-Lang:main May 6, 2024
1 of 3 checks passed
@dinhquochan
Copy link
Member

@makowskid can you check the tests? All test cases failed now because of [pl] locale.

@dinhquochan
Copy link
Member

cc @andrey-helldar

@makowskid
Copy link
Contributor Author

sh**, but why? I have only changed translation strings, checking

@andrey-helldar andrey-helldar changed the title [pl] missing keys + stylistical fixes, better comprehension [pl]: Missing keys + stylistical fixes, better comprehension May 6, 2024
"not_regex": "Format pola jest nieprawidłowy.",
"numeric": "Pole musi być liczbą.",
"password.letters": "To pole musi zawierać przynajmniej jedną literę.",
"password.mixed": "To pole musi zawierać co najmniej jedną wielką i jedną małą literę.",
"password.numbers": "To pole musi zawierać co najmniej jedną cyfrę.",
"password.symbols": "To pole musi zawierać przynajmniej jeden symbol.",
"password.uncompromised": "Podane pole pojawiło się w wycieku danych. Proszę wybrać inną wartość pola.",
"password.uncompromised": "Pole :attribute pojawiło się w wycieku danych. Należy wybrać inną wartość.",
Copy link
Member

Choose a reason for hiding this comment

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

The inline translation must not contain a reference to the attribute name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

found it, pushing the fix, sorry

Copy link
Member

Choose a reason for hiding this comment

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

Exactly!

Copy link
Member

Choose a reason for hiding this comment

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

I can assume it should be like this here (wrote it by analogy with other fields):

Suggested change
"password.uncompromised": "Pole :attribute pojawiło się w wycieku danych. Należy wybrać inną wartość.",
"password.uncompromised": "To pole musi pojawiło się w wycieku danych. Należy wybrać inną wartość.",

Copy link
Contributor Author

Choose a reason for hiding this comment

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

pushed, hope all works now, sorry again, fat fingers

Copy link
Member

Choose a reason for hiding this comment

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

No problem 👌

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@andrey-helldar I think now we have a different problem
https://github.com/Laravel-Lang/lang/actions/runs/8966720071/job/24622816598#step:5:35

1) Tests\PluginTest::testInline
The locales/pl/json-inline.json file must not contain the value: :attribute
Podane pole :attribute pojawiło się w wycieku danych. Wybierz inną wartość pola :attribute.
Failed asserting that true is false.

"The given :attribute has appeared in a data leak. Please choose a different :attribute.": "Podane pole :attribute pojawiło się w wycieku danych. Wybierz inną wartość pola :attribute."

This test assertion is obviously wrong.

Copy link
Member

Choose a reason for hiding this comment

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

No, the test is correct. The inline translation file must not contain a reference to the attribute name.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK, you're right, this is the original EN version:

    "The given :attribute has appeared in a data leak. Please choose a different :attribute.": "The given field has appeared in a data leak. Please choose a different field."

I was a bit confused about the :attribute key here, weird.
fix pushed, again

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

Successfully merging this pull request may close these issues.

3 participants