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

Localization: Split strings into multiple file #1133

Open
arky opened this issue Oct 3, 2023 · 2 comments
Open

Localization: Split strings into multiple file #1133

arky opened this issue Oct 3, 2023 · 2 comments

Comments

@arky
Copy link
Contributor

arky commented Oct 3, 2023

Currently all the translation strings are stored in a single file. This makes it difficult to prioritize those strings that are most important for localizing first.
Perhaps it would be great to start thinking of split strings into different files such as base, UI etc. This would enable us to guide the localizers to work in order of their importance (User facing strings translated first).

https://support.crowdin.com/file-management/#prioritizing-files

@arky
Copy link
Contributor Author

arky commented Oct 3, 2023

I think this should be also done for mapeo-desktop project as well in future.

@arky
Copy link
Contributor Author

arky commented Oct 5, 2023

@gmaclennan Aliya pointed out there is another page with localization (https://docs.mapeo.app/~/changes/iOm3AFqdVz8g9c1IDE5m/complete-reference-guide/customization-options/translating)

Perhaps we could decide a good place for localization and merge the content.

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

No branches or pull requests

1 participant