Open core-ai-bot opened 3 years ago
Comment by redmunds Tuesday Feb 11, 2014 at 16:00 GMT
@
davidbourguignon Thanks for bringing attention to this topic.
The Display Shortcuts extension has been localized (by@
SAPlayer) and should provide a good example of how extensions can be localized.
I was not aware of http://translate.adobe.com/, but that looks like a really good place for it :)
Comment by jasonsanjose Tuesday Feb 11, 2014 at 17:19 GMT
We opted not to directly use translate.adobe.com in our core development because we found it easier for our community to read our strings directly via our requirejs modules and pull requests (vs. the translate.adobe.com UI). If I recall correctly, our official French and Japanese translations do feed back into ALF and will appear on translate.adobe.com.@
ybayer correct me if I got that wrong.
Comment by MarcelGerber Wednesday Feb 12, 2014 at 15:28 GMT
Yes, some translations are on https://translate.adobe.com/adobe/products/51. But what is strange is that this site is not up-to-date with the github repo. So it could be that some strings are translated twice, which is not that good. We shouly maybe decide which translation method we want to use (I prefer GitHub).
Comment by davidbourguignon Saturday Feb 15, 2014 at 11:00 GMT
@
redmunds@
jasonsanjose@
SAPlayer Thanks a lot for your feedback! I agree, the solution we opt for must be minimalist, effective and reliable.
From what I see, Translate.Adobe.com might not be so FOSS community-friendly as other tools such as Transifex... Otherwise, we could indeed stay on GitHub.com, but this would lack graphical incentive for broadening i18n effort IMHO.
At least, what about stating up front the state of i18n of the various extensions? A suggestion: for each extension in Bracket extension manager, putting a series of two-letter language IDs (de, fr, etc.) under its description, in order to bring attention to its i18n coverage?
Comment by MarcelGerber Saturday Feb 15, 2014 at 13:24 GMT
Yes, it would be cool to have a little tag available in your language
(maybe with a tooltip containing all supported languages?) in the Extension Manager (we already have tags, keywords and so on, so this shouldn't be a problem.
We could also serve more info with a help translating this extension
for nls-ready extensions, but in this case we'd have to explain how to.
Comment by davidbourguignon Sunday Feb 16, 2014 at 19:28 GMT
@
SAPlayer Great proposal for two new features of the Extension Manger! BTW I have never seen any FOSS project dealing with the i18n issue in such an elegant and effective way... Many thanks!
Comment by redmunds Wednesday Feb 19, 2014 at 21:41 GMT
I like the idea to "Display localized languages for extensions", so I updated subject accordingly. Making this a starter bug.
Comment by MarcelGerber Monday Jul 21, 2014 at 17:41 GMT
This can be closed now that it's implemented.
Comment by redmunds Monday Jul 21, 2014 at 18:01 GMT
This is fixed. Closing.
@
davidbourguignon Do you have any experience implementing Transifex? They recently added support for the RequireJS i18n system used by Brackets, so I'm curious what it would take to integrate Transifex into Brackets?
Comment by davidbourguignon Monday Jul 21, 2014 at 19:52 GMT
@
redmunds Thanks for your inquiry. Unfortunately, I have no experience with implementing Transifex. I have only been using it through their web browser interface on projects not of my own. However, I am available for testing any integration... Brackets+Transifex: this should sound like a great idea to any people involved in i18n!
Comment by MarcelGerber Monday Jul 21, 2014 at 20:28 GMT
@
redmunds After looking around their website a bit, I got so far:
Comment by redmunds Monday Jul 21, 2014 at 20:49 GMT
@
SAPlayer Thanks. Care to try to get this working?
Comment by MarcelGerber Tuesday Jul 22, 2014 at 13:58 GMT
@
redmunds It looks like you already tried it? https://www.transifex.com/organization/brackets
Comment by redmunds Tuesday Jul 22, 2014 at 14:37 GMT
@
SAPlayer That was my first attempt when I discovered that RequireJS i18n (used by Brackets) was not supported. I sent in a feature request and they finally implemented it, but I have been either on vacation or too busy to try again since then. If you send me your id, I will add you to that org.
Comment by MarcelGerber Tuesday Jul 22, 2014 at 16:03 GMT
My id is MGerber
.
I've already created my own project and org, but it's hopefully not too complicated to do it all again.
Comment by redmunds Tuesday Jul 22, 2014 at 16:23 GMT
I think your org is ok if you make Me and Raymond as Admins.
Comment by MarcelGerber Tuesday Jul 22, 2014 at 16:31 GMT
So now that I transferred the project to your org, you need to give me admin/guardian rights again.
Issue by davidbourguignon Tuesday Feb 11, 2014 at 15:13 GMT Originally opened as https://github.com/adobe/brackets/issues/6835
Original Subject: How to foster translation efforts for Brackets extensions?
Dear all,
Many of the non-English speakers have noticed that, while Brackets internationalization is well under way on http://translate.adobe.com/ most extensions are still only available in English. This looks especially strange in the menus when an extension in English add options among options in another language...
Some tools such as http://www.transifex.com/ (I know it from Mozilla's projects) are pretty effective at fostering community translation efforts. Or would it be possible to use http://translate.adobe.com/ for this? In this case, how to standardize extension packages in order to provide the right translation-ready files, etc.?
Thanks in advance for your feedback.
Best regards,
David.