This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
Localizing package metadata in Extension Manager #8953
Comments
A few different straw-man proposals:
Unfortunately, there's no precedent to follow in the NPM package format for translated metadata http://npmjs.org/doc/json.html. |
Per standup, medium priority assigned to @bchintx |
@jasonsanjose I've submitted PR #8987 which implements proposal #2 above. |
peterflynn
added a commit
that referenced
this issue
Sep 19, 2014
fix Issue #8953- "Localizing package metadata in Extension Manager"
FBNC -- @bchintx do you want to verify with a 'real' extension before closing? |
FBNC @jasonsanjose @bchintx either one may verify, assigned to Jason as he filed the issue. |
Closed |
Yup. Just confirmed this is Fixed with the Extract for Brackets (Preview) extension in both French and Japanese. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Extension manager and the package.json format https://github.com/adobe/brackets/wiki/Extension-package-format can't currently display locale specific metadata.
In order to meet specific translation needs per country, we need to display localized strings in the
ExtensionManagerView
for the following properties:title
- may not be applicable for trademarked names? e.g. Photoshop Expressdescription
keywords
- for translated searchThis is not to be confused with the current
i18n
property which describes which languages the extension has been localized in.The text was updated successfully, but these errors were encountered: