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

🌏 i18n: Improve clarity of English translation #3154

Merged
merged 4 commits into from
Jun 24, 2024

Conversation

KiGamji
Copy link
Contributor

@KiGamji KiGamji commented Jun 21, 2024

Summary

I made some updates to the English localization files to improve the clarity of some strings.

Change Type

  • Translation update

@KiGamji KiGamji marked this pull request as draft June 22, 2024 10:00
@KiGamji KiGamji marked this pull request as ready for review June 22, 2024 10:13
@KiGamji KiGamji force-pushed the english-i18n-clarity branch 3 times, most recently from c551f4f to baf45fa Compare June 22, 2024 11:04
@KiGamji
Copy link
Contributor Author

KiGamji commented Jun 22, 2024

About the 629260f (now — 423d4a8) commit. The thing is — English and Russian (and possibly even more langauges) do not use cases in the same way.

Let's take a look on the "Create Prompt" string. In Russian, the word "Prompt" would be written with small letter at the start. Moreover, Russian has lots of grammatical cases, so the word "prompt" would change form depending on its function.

With that being said, it's still used as a button/menu title, so it can't be changed that way either.

Replacing these strings addresses such linguistic complexities into account, adapting LibreChat to be more natural and grammatically accurate in languages where words change according to their grammatical usage.

@KiGamji KiGamji force-pushed the english-i18n-clarity branch 2 times, most recently from 9ac7acb to 8f50776 Compare June 22, 2024 20:28
This commit simplifies the internationalization approach for English language strings by removing the placeholder ones where they are used only once. This makes proper localization possible for Russian language, and possibly others.

Also renamed `com_ui_text_prompt` to `com_ui_prompt_text` to match the alphabetical order.
@KiGamji
Copy link
Contributor Author

KiGamji commented Jun 24, 2024

@danny-avila any reason of this not getting accepted ?

@danny-avila
Copy link
Owner

@danny-avila any reason of this not getting accepted ?

if a PR is not closed, it has not been rejected. I work on this as time allows

@danny-avila danny-avila merged commit eef894e into danny-avila:main Jun 24, 2024
2 checks passed
@KiGamji KiGamji deleted the english-i18n-clarity branch June 24, 2024 17:48
danny-avila pushed a commit that referenced this pull request Aug 5, 2024
* 🌏 i18n: Improve clarity of English translation

* 🔧 fix(useCategories): replace i18n string to `com_ui_select_a_category`

* 🔨 refactor: avoid using placeholder strings where possible

This commit simplifies the internationalization approach for English language strings by removing the placeholder ones where they are used only once. This makes proper localization possible for Russian language, and possibly others.

Also renamed `com_ui_text_prompt` to `com_ui_prompt_text` to match the alphabetical order.

* 🎨 style(CreatePromptForm): add missing margin-top to the submit button
kenshinsamue pushed a commit to intelequia/LibreChat that referenced this pull request Sep 17, 2024
* 🌏 i18n: Improve clarity of English translation

* 🔧 fix(useCategories): replace i18n string to `com_ui_select_a_category`

* 🔨 refactor: avoid using placeholder strings where possible

This commit simplifies the internationalization approach for English language strings by removing the placeholder ones where they are used only once. This makes proper localization possible for Russian language, and possibly others.

Also renamed `com_ui_text_prompt` to `com_ui_prompt_text` to match the alphabetical order.

* 🎨 style(CreatePromptForm): add missing margin-top to the submit button
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