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

Translation / localization of API strings #166

Closed
stanvass opened this issue Sep 28, 2020 · 4 comments
Closed

Translation / localization of API strings #166

stanvass opened this issue Sep 28, 2020 · 4 comments

Comments

@stanvass
Copy link

I can't see a parameter that allows me to localize/translate the POI details (to German, for example). Is this a feature? I see old discussions about it, but I see no parameters in the documentation. What would be the recommended approach here?

@webprofusion-chrisc
Copy link
Member

Hi, I'm not really sure what you mean? The API data field names are fixed and not translatable if that's what you mean (they are a direct serialization of our object model) - you can of course call them anything you like in a UI.

@stanvass
Copy link
Author

stanvass commented Oct 2, 2020

Hi,

Not field names, but UI strings under "Title" as seen throughout the core reference data for things like charger types, connection types, check-in types, etc.: https://api.openchargemap.io/v3/referencedata/ Ideally also the charging point comments, although I could see how that won't work if the submitter provides no translation. But at least the general purpose collections.

Thanks.

@webprofusion-chrisc
Copy link
Member

UI localisations can be found here, however they are community maintained and not regularly updated:
https://github.com/openchargemap/ocm-app/tree/master/src/assets/i18n

@webprofusion-chrisc
Copy link
Member

Updated topic on app localisation plans:

openchargemap/ocm-app#35

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

2 participants