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

[Feature Request]: [Translation] Always include variables in strings #524

Open
3 tasks done
smileyhead opened this issue Sep 25, 2024 · 0 comments · May be fixed by #662
Open
3 tasks done

[Feature Request]: [Translation] Always include variables in strings #524

smileyhead opened this issue Sep 25, 2024 · 0 comments · May be fixed by #662
Labels
Type: Enhancement New feature or request Type: Translation Translates or improves translation capabilities

Comments

@smileyhead
Copy link
Contributor

Checklist

  • I am using an up-to-date version.
  • I have read the documentation.
  • I have searched existing issues.

Description

There are some strings, namely:

  • open_library.library_creation_return_code
  • status.backup_success
  • status.search_library_query
  • file_opener.open_file
  • file_opener.not_found

…which are linked to / talking about a variable that immediately follows them, but isn't included in the strings themselves. Some languages would need to move these variables to the beginning or the middle of the sentences, but that's currently impossible.

Solution

No response

Alternatives

No response

@smileyhead smileyhead added the Type: Enhancement New feature or request label Sep 25, 2024
@CyanVoxel CyanVoxel added the Type: Translation Translates or improves translation capabilities label Sep 25, 2024
@Computerdores Computerdores linked a pull request Dec 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement New feature or request Type: Translation Translates or improves translation capabilities
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants