Re: Gedit docs shouldn't mention extra plugins



Am 17.03.2012 23:18, schrieb Jim Campbell:
Hi Mario,

2012/3/17 Mario Blättermann <mario blaettermann gmail com>
Hi,

while translating the Gedit documentation I've seen that a lot of
plugins are part of the main manual which are _not_ part of the gedit
main package. This forces translators first to make sure that they have
all the GUIs of the appropriate plugins translated (which are in general
not part of the GNOME core release set).

Mallard has the ability to mix docs from different sources. Means, we
should actually move the plugin docs to the plugin packages
(gedit-plugins and perhaps some other from third party vendors. This is
not my first attempt to do so. Removing the plugin topics from the base
manual would it make easier to maintain the docs anyway, because we
don't have to mention things such as "If the xxx package is not
installed, you will be unable to use this feature".

Of course, it's too less time to get it into GNOME 3.4, but we should
keep an eye on 3.6.

Best Regards,
Mario
_______________________________________________
gnome-doc-list mailing list
gnome-doc-list gnome org
http://mail.gnome.org/mailman/listinfo/gnome-doc-list


You're absolutely right. There are some plugins that are installed by default in gedit, but some plugins are only available when you install the gedit-plugins package.

I'll move the extra plugins (those installed in the gedit-plugins package) into a separate repository for the next release.

Don't understand "extra repository" here. The one and only way is to move them to the gedit-plugins module and create a docs stack therein, means /help/C/ and Makefile.am and so on. The somewhat difficult part is to assign the docs pages to the right topics and subtopics in the gedit manual. Am I right?

Best Regards,
Mario


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]