The github RSS feeds seem to operate at the repository level, so narrowing for a particular file would have to be done client side. I'd be tempted to use a webhook that would just email some i18n-maintainers list when those files are updated. Or we could probably do something in jenkins...
On Wed, Jun 13, 2012 at 11:07:44AM -0400, Nate Angell wrote: > I was wondering if there was a way to use the watching/RSS features of > github to "watch" appropriate language files in the OAE github repository > so if one were maintaining a language translation/localization, one could > be notified of any changes to files that needed localization attention. > Perhaps one of the git gurus in this list might be able to suggest a path? > I haven't been able to figure it out obviously, tho I did find this page > on modifying the RSS of github's watch feature: > > [1]http://webapps.stackexchange.com/questions/20535/on-github-is-there-anyway-to-view-newsfeed-timeline-for-a-specific-repository > We might also think about how the OAE widget library might be able to > report on the i18n/localization status of contributed widgets. > = nate > > On Tue, Jun 12, 2012 at 4:10 PM, Harry Wang <[2]harryjw...@gmail.com> > wrote: > > Hi Alan, > It would be great if that reporting tool could be used for OAE. It will > provide great help for people who are working on OAE localizations. I > have been looking for such tool for a while :). > Thanks a lot for your help! > Harry > > On Tue, Jun 12, 2012 at 2:13 PM, Berg, Alan <[3]a.m.b...@uva.nl> wrote: > > Hi Harry, > > The LOI ([4]loi.nl) and UvA run a translation reporting tool for CLE. > Perhaps we can ask the LOI to update their Java application and if > they are motivated I can update the wrapping Perl script. > > Is this what you are looking for? > > Regards, > > Alan > Alan Berg > > Group Education and Research Services > Central Computer Services > University of Amsterdam > > -------------------------------------------------------------------------- > > From: [5]oae-dev-boun...@collab.sakaiproject.org > [[6]oae-dev-boun...@collab.sakaiproject.org] on behalf of Harry Wang > [[7]harryjw...@gmail.com] > Sent: 12 June 2012 17:32 > To: Fr�d�ric Dooremont > Cc: OAE Production; OAE-Dev List > Subject: Re: [oae-dev] Sakai OAE est disponible en fran�ais > Hi Steve and Frederic, > I have worked on Chinese translation of OAE before and found that > keeping track of changes is very difficult without a tool, e.g. new > strings are added/old strings are removed from the properties files. > Is there a good tool to scan �the code base to show the strings that > are not translated or no longer being used? > Thanks, > Harry > > On Fri, May 4, 2012 at 8:34 AM, Fr�d�ric Dooremont > <[8]frederic.doorem...@univ-littoral.fr> wrote: > > effectively it's a good tool for the translation. > My university think use sakai OAE. I think I can continue working. > But the tool is very useful Sakai CLE. > I use it with UPMC to translate Sakai CLE. > Nevertheless I still have three problems : > * some widgets use text in picture files. > � for example: the widget contentcomments > � see [9]https://jira.sakaiproject.org/browse/SAKIII-5543 > * in searchgroups/javascript/searchgroups.js line to 95 and 100 > there is text that we can not translate �see > [10]https://jira.sakaiproject.org/browse/SAKIII-5557 > * configurate the setting language of tinymce editor with the > personal settings. see > [11]https://jira.sakaiproject.org/browse/SAKIII-5560 > best regards > frederic dooremont > Le 4 mai 2012 � 03:17, Steve Swinsburg a �crit : > > The OAE project should consider setting up something like the > Internationalisation Dashboard, which we have for the CLE.� > It scans the translations in the code and give you a percent > coverage report. You can then drill in and see what needs to be > updated. It won't pickup changes within an existing language > property but just if they are missing. > [12]http://qa1-nl.sakaiproject.org/international/ > cheers, > Steve > On 04/05/2012, at 7:26 AM, Nate Angell wrote: > > Fantastic work�Frederic et al! > I note that this "language pack" involves 187 files, and I can > already anticipate the work that it would take to maintain it as > strings evolve and/or are added to OAE, which leads me to two > questions: > One to Frederic: Is your team thinking that you would have > capacity to steward the ongoing maintenance of a French > translation? > One to us in the OAE community: What can we > do�technically/socially�to help ensure a contribution like this > is easy for original contributors and/or others to maintain as > OAE evolves? For example: Would core code contributions and/or > widget library now require French translation to be official? > Can we put any mechanisms in place that would alert a language > team (even across institutions) to know that translation > stewardship was called for due to some other change in OAE? > -- > Nate Angell > Sakai Product Manager > rSmart > [13]http://www.rsmart.com > [14]http://twitter.com/xolotl > [15]http://xolotl.org > > On Thu, May 3, 2012 at 1:43 PM, Nicolaas Matthijs > <[16]nicolaas.matth...@caret.cam.ac.uk> wrote: > > Chouette! > On 3 May 2012, at 07:42, Christian Vuerings wrote: > > Hey everyone, > I want to bring to your attention that Sakai OAE is now > available in French [1]. > All this was made possible by a big contribution [2] by > Frederic Dooremont from l'Universit� du�Littoral�C�te > d'Opale�[3] in Dunkirk. > Merci Frederic, > Christian > [1]�[17]http://cl.ly/GKwv�(screenshot) > > [2]�[18]https://github.com/sakaiproject/3akai-ux/commit/12645a1c3f10460be2bbd83047bb391a93873dcc > [3]�[19]http://www.univ-littoral.fr/ > _______________________________________________ > oae-dev mailing list > [20]oae-dev@collab.sakaiproject.org > [21]http://collab.sakaiproject.org/mailman/listinfo/oae-dev > > _______________________________________________ > oae-dev mailing list > [22]oae-dev@collab.sakaiproject.org > [23]http://collab.sakaiproject.org/mailman/listinfo/oae-dev > > _______________________________________________ > oae-dev mailing list > [24]oae-dev@collab.sakaiproject.org > [25]http://collab.sakaiproject.org/mailman/listinfo/oae-dev > > _______________________________________________ > oae-dev mailing list > [26]oae-dev@collab.sakaiproject.org > [27]http://collab.sakaiproject.org/mailman/listinfo/oae-dev > > _______________________________________________ > oae-dev mailing list > [28]oae-dev@collab.sakaiproject.org > [29]http://collab.sakaiproject.org/mailman/listinfo/oae-dev > > _______________________________________________ > oae-production mailing list > [30]oae-product...@collab.sakaiproject.org > [31]http://collab.sakaiproject.org/mailman/listinfo/oae-production > > References > > Visible links > 1. > http://webapps.stackexchange.com/questions/20535/on-github-is-there-anyway-to-view-newsfeed-timeline-for-a-specific-repository > 2. mailto:harryjw...@gmail.com > 3. mailto:a.m.b...@uva.nl > 4. http://loi.nl/ > 5. mailto:oae-dev-boun...@collab.sakaiproject.org > 6. mailto:oae-dev-boun...@collab.sakaiproject.org > 7. mailto:harryjw...@gmail.com > 8. mailto:frederic.doorem...@univ-littoral.fr > 9. https://jira.sakaiproject.org/browse/SAKIII-5543 > 10. https://jira.sakaiproject.org/browse/SAKIII-5557 > 11. https://jira.sakaiproject.org/browse/SAKIII-5560 > 12. http://qa1-nl.sakaiproject.org/international/ > 13. http://www.rsmart.com/ > 14. http://twitter.com/xolotl > 15. http://xolotl.org/ > 16. mailto:nicolaas.matth...@caret.cam.ac.uk > 17. http://cl.ly/GKwv > 18. > https://github.com/sakaiproject/3akai-ux/commit/12645a1c3f10460be2bbd83047bb391a93873dcc > 19. http://www.univ-littoral.fr/ > 20. mailto:oae-dev@collab.sakaiproject.org > 21. http://collab.sakaiproject.org/mailman/listinfo/oae-dev > 22. mailto:oae-dev@collab.sakaiproject.org > 23. http://collab.sakaiproject.org/mailman/listinfo/oae-dev > 24. mailto:oae-dev@collab.sakaiproject.org > 25. http://collab.sakaiproject.org/mailman/listinfo/oae-dev > 26. mailto:oae-dev@collab.sakaiproject.org > 27. http://collab.sakaiproject.org/mailman/listinfo/oae-dev > 28. mailto:oae-dev@collab.sakaiproject.org > 29. http://collab.sakaiproject.org/mailman/listinfo/oae-dev > 30. mailto:oae-product...@collab.sakaiproject.org > 31. http://collab.sakaiproject.org/mailman/listinfo/oae-production > _______________________________________________ > oae-production mailing list > oae-product...@collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/oae-production -- D. Stuart Freeman Georgia Institute of Technology
signature.asc
Description: Digital signature
_______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
