Translation, Missing sentence in source string admin:auths.oauth2_full_name_claim_name #14827

New Issue

GiteaMirror · 2025-11-02T11:23:51-06:00

GiteaMirror commented

2025-11-02 11:23:51 -06:00

Originally created by @Simandara on GitHub (Aug 1, 2025).

Description

There is a parsing issue with the key admin:auths.oauth2_full_name_claim_name

Full Name Claim Name. (Optional

It should be

Full Name Claim Name. (Optional — if set, the user's full name will always be synchronized with this claim)

I think there is a parsing issue with the - symbol that has been interpreted as an end of string.

Gitea Version

NA

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

NA

Database

None

Originally created by @Simandara on GitHub (Aug 1, 2025). ### Description There is a parsing issue with the key [admin:auths.oauth2_full_name_claim_name](https://crowdin.com/editor/gitea/68/enus-fr?view=comfortable#101530) > Full Name Claim Name. (Optional It should be > Full Name Claim Name. (Optional — if set, the user's full name will always be synchronized with this claim) I think there is a parsing issue with the `-` symbol that has been interpreted as an end of string. ### Gitea Version NA ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? NA ### Database None

GiteaMirror added the good first issue type/bug labels 2025-11-02 11:23:51 -06:00

GiteaMirror closed this issue

2025-11-02 11:23:51 -06:00

GiteaMirror commented

2025-11-02 11:23:52 -06:00

@satnam72 commented on GitHub (Aug 1, 2025):

Hi @SimonPistache, the issue is not with parsing, but with the semicolon (;), which was used instead of a hyphen (-) in the string. The semicolon is used for comments in .ini files, so the remaining part of the string was being ignored because it was interpreted as a comment. It has been addressed in PR #35199.

@satnam72 commented on GitHub (Aug 1, 2025): Hi @SimonPistache, the issue is not with parsing, but with the semicolon (;), which was used instead of a hyphen (-) in the string. The semicolon is used for comments in `.ini` files, so the remaining part of the string was being ignored because it was interpreted as a comment. It has been addressed in PR #35199.

GiteaMirror commented

2025-11-02 11:23:52 -06:00

@Simandara commented on GitHub (Aug 3, 2025):

@satnam72 thank for reaching back, I see the string has been updated in Crowdin accordingly, so I had proofread it in my language.

@Simandara commented on GitHub (Aug 3, 2025): @satnam72 thank for reaching back, I see the string has been updated in Crowdin accordingly, so I had proofread it in my language.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14827