pidgin/pidgin

Remove `PURPLE_PLUGIN_INIT` from docs.

2021-06-17, Elliott Sales de Andrade
19e53c9cab73
Parents f2f397659f30
Children f2abd04191b7
Remove `PURPLE_PLUGIN_INIT` from docs.

Though, the i18n docs need a complete rewrite anyway.

Reviewed at https://reviews.imfreedom.org/r/762/
2 files changed, 3 insertions(+), 3 deletions(-)
  • +2 -2
    doc/reference/libpurple/plugin_i18n.xml
  • +1 -1
    doc/reference/libpurple/plugin_ids.xml
    • --- a/doc/reference/libpurple/plugin_i18n.xml Thu Jun 17 23:40:07 2021 -0500
    +++ b/doc/reference/libpurple/plugin_i18n.xml Thu Jun 17 23:43:50 2021 -0500
    @@ -129,8 +129,8 @@
    description to NULL.
    </para></listitem>
    <listitem><para>
    -Next, locate your 'plugin_load' function. Your name for this function
    -may vary, but it's the third parameter to 'PURPLE_PLUGIN_INIT'.
    +Next, locate your 'plugin_load' function. Your name for this function will be
    +the first parameter to GPLUGIN_NATIVE_PLUGIN_DECLARE() plus '_load'.
    </para></listitem>
    <listitem><para>
    Now add the following within your 'plugin_load' function:
    --- a/doc/reference/libpurple/plugin_ids.xml Thu Jun 17 23:40:07 2021 -0500
    +++ b/doc/reference/libpurple/plugin_ids.xml Thu Jun 17 23:43:50 2021 -0500
    @@ -98,7 +98,7 @@
    <para>
    The <emphasis>pluginname</emphasis> is the name of your plugin. It is usually all
    lowercase letters and matches the static plugin ID (the first argument to
    -the PURPLE_PLUGIN_INIT() macro call), although it can be anything you
    +the GPLUGIN_NATIVE_PLUGIN_DECLARE() macro call), although it can be anything you
    like. Do <emphasis>not</emphasis> include version information in the plugin ID--the
    <literal>PurplePluginInfo</literal> object already has a property for this.
    </para>