Fix up some inaccuracies and omissions in ADM (#340609)

Original commit message from CVS:
Fix up some inaccuracies and omissions in ADM (#340609)

diff --git a/ChangeLog b/ChangeLog
index 62b4913..61a4494 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,30 @@
+2006-05-05  mathrick,,,  <set EMAIL_ADDRESS environment variable>
+
+       reviewed by: <delete if not using a buddy>
+
+       * docs/manual/basics-bus.xml:
+       * docs/manual/basics-pads.xml:
+       * po/af.po:
+       * po/az.po:
+       * po/bg.po:
+       * po/ca.po:
+       * po/cs.po:
+       * po/de.po:
+       * po/en_GB.po:
+       * po/fr.po:
+       * po/it.po:
+       * po/nb.po:
+       * po/nl.po:
+       * po/ru.po:
+       * po/sq.po:
+       * po/sr.po:
+       * po/sv.po:
+       * po/tr.po:
+       * po/uk.po:
+       * po/vi.po:
+       * po/zh_CN.po:
+       * po/zh_TW.po:
+
 2006-05-05  Maciej Katafiasz  <mathrick@freedesktop.org>
 
        * gst/gstghostpad.c:

diff --git a/docs/manual/basics-bus.xml b/docs/manual/basics-bus.xml
index 4a65f37..b958aa5 100644 (file)
--- a/docs/manual/basics-bus.xml
+++ b/docs/manual/basics-bus.xml
@@ -99,6 +99,36 @@ main (gint   argc,
       a &GStreamer; plug-in. It is very useful for its primary purpose,
       though: passing messages from pipeline to application.
     </para>
+    <para>
+      Note that if you're using the default GLib mainloop integration,
+      you can, instead of attaching a watch, connect to <quote>message</quote> 
+      signal on the bus. This way you don't have to <function>switch()</function> 
+      on all possible message types; just connect to the interesting 
+      ones in form <quote>message::&lt;type&gt;</quote>, where &lt;type&gt; 
+      is a specific message type (see the next section for explanation of 
+      message types).
+    </para>
+    <para>
+      The above snippet would be thus written as:
+    </para>
+    <programlisting>
+GstBus *bus;
+
+[..]
+
+bus = gst_pipeline_get_bus (GST_PIPELINE (pipeline);
+g_signal_connect(G_OBJECT(bus), "message::error", G_CALLBACK(cb_message_error));
+g_signal_connect(G_OBJECT(bus), "message::eos", G_CALLBACK(cb_message_eos));
+
+[..]
+    </programlisting>
+    <para>
+      If you aren't using GLib mainloop, the message signals won't be available 
+      by default. You can however use a small helper exported by to provide
+      integration with the mainloop you're using, and enable generation of bus
+      signals (see <ulink type="http"
+      url="&URLAPI;GstBus.html">documentation</ulink> for details)
+    </para>
   </sect1>
 
   <sect1 id="section-bus-message-types">

diff --git a/docs/manual/basics-pads.xml b/docs/manual/basics-pads.xml
index 112fc15..db8123b 100644 (file)
--- a/docs/manual/basics-pads.xml
+++ b/docs/manual/basics-pads.xml
@@ -235,8 +235,8 @@ link_to_multiplexer (GstPad     *tolink_pad,
         accept vorbis-encoded audio data, with the mime-type
         <quote>audio/x-vorbis</quote>. The source pad will be used
         to send raw (decoded) audio samples to the next element, with
-        a raw audio mime-type (either <quote>audio/x-raw-int</quote> or
-        <quote>audio/x-raw-float</quote>). The source pad will also
+        a raw audio mime-type (in this case, 
+       <quote>audio/x-raw-int</quote>) The source pad will also
         contain properties for the audio samplerate and the amount of
         channels, plus some more that you don't need to worry about
         for now.
@@ -532,8 +532,9 @@ link_pads_with_filter (GstPad *one,
     <para>
       <xref linkend="section-bin-ghost-img"/> is a representation of a
       ghost pad. The sink pad of element one is now also a pad of the bin.
-      Obviously, ghost pads can be added to any type of elements, not just
-      to a <classname>GstBin</classname>.
+      Because ghost pads look and work like any other pads, they can be added 
+      to any type of elements, not just to a <classname>GstBin</classname>,
+      just like ordinary pads.
     </para>
     <para>
       A ghostpad is created using the function