[tomboy-list] Fwd: About addin repository,
jaredljennings at gmail.com
Mon Apr 18 14:54:29 PDT 2011
Luc, I agree with you or at least think you have valid points.
Banshee doesn't have support to add BCE through the application it's self.
The user must download the add-in and manage it.
We easily could reproduce the Banshee model with Gitorious or Github and not
really do much else in Tomboy. Maybe make a "Local File Browser" for add-ins
so the user doesn't have to dig through the local file system.
Making add-ins installable through the packageKit or other such application
would save us the hassle of having to write the infrastructure and find a
hosting location. Maybe the add-ins that are available through this method
are more "supported" than other applications that are maybe not as tested in
which case the user would download from the developers through Github or
I haven't talked to the MonoDevelop group yet, but this is what I have so
far from the Banshee group.
On Mon, Apr 18, 2011 at 5:09 PM, Luc Pionchon <pionchon.luc at gmail.com>wrote:
> On Tue, Apr 12, 2011 at 17:35, Greg Poirier <grep at binary-snobbery.com>
> > On Tue, Apr 12, 2011 at 7:15 AM, Luc Pionchon <pionchon.luc at gmail.com>
> > wrote:
> I understand the issue requires compromises.
> >> Another strong point is to get them into the gnome i18n loop,
> >> targeting at an uniform and coherent translation between addins and
> >> tomboy.
> > I18n for the add-ins would be nice, but I don't know much at all about
> > the i18n team works.
> You could read here . The basic is that the maintainer mark strings
> to be translated*. Gettext collects these strings into po/tomboy.pot.
> Then the l10n teams do their magic: they use the template to produce
> de.po, es.po, sv.po etc. Then the strings are substituted at run time.
> When you update strings, gettext updates tomboy.pot and merge it with
> the existing translations for update. The gnome translation teams do a
> fantastic job!
> (*) In fact there are a bit more for maintainers to consider than just
> marking strings.
> > I know that the BCE repo has some i18n done, but I'm
> > not sure if it's from community i18n contributions or GNOME contributors.
> banshee community extensions appear untranslated on my system. It
> feels like they are second class software.
> A grep gives me 51 languages for banshee, and 8 for community extensions.
> >> (*) One short note on "Add-ins" I would strongly recommend to be
> >> uniform across the GNOME platform. Today we have addins, addons,
> >> plugins, extensions (...)
> > I'm not sure that we have much control over that. Perhaps there is some
> > standardization that has occurred that we don't know about and that some
> > projects are lagging behind. If anyone finds out, let us know! We chose
> It's not much about control, more about agreeing within the community.
> As you are renaming, it might be a good opportunity to initiate the
> discussion with the others applications that have plug-ons... Overall
> I think it's English that is lagging behind. Developers tend to care
> less. The translations I saw did their magic.
> > "add-in", with the hyphen, because it was simply more "correct" than
> > "addin," which brings to mind a colloquialism of the Southeastern
> Southeastern is very relative :)
> So initially I meant that
> - It would be great if add-ins are (also) available through the
> distribution packages
> - It would be great if add-ins are included into the localization loop
> Tomboy-list mailing list
> Tomboy-list at lists.beatniksoftware.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tomboy-list