-
Notifications
You must be signed in to change notification settings - Fork 2
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
Extension fields human-readable title translation support #185
Comments
When we discussed this on a call, I suggested that OCP could add this functionality to the ProfileBuilder. Right now, the Extension Explorer hosts translated versions of extensions. However, the extension URLs (used in the data) point to GitHub repositories, where the schema is only in English. So, the ProfileBuilder would have to look up the extensions in the Explorer, and extend the schema using a translated version, if available. Once that functionality is available, I think the current process of translating titles should work. One edge case might be extensions that don't have a title for a field. I think the current process handles this, though? |
@jpmckinney Currently, in such cases titles are derived from the fields that are humanized (e.g. camelcase/underscore split, capitalization) but not translated. |
I think we can defer to --schema, i.e. the user (or web tool) provides a schema that has been created by the ProfileBuilder. |
No description provided.
The text was updated successfully, but these errors were encountered: