docs: fix a couple of typos in the manual

Spotted by Alexander Saprykin.

Fixes #622379.
This commit is contained in:
Tim-Philipp Müller 2010-07-01 19:58:09 +01:00
parent 70d1f1f177
commit 2f149355cd
6 changed files with 20 additions and 11 deletions

View file

@ -85,7 +85,7 @@
concept of typefinding for this. Typefinding is a normal part of a
pipeline, it will read data for as long as the type of a stream is
unknown. During this period, it will provide data to all plugins
that implement a typefinder. when one of the typefinders recognizes
that implement a typefinder. When one of the typefinders recognizes
the stream, the typefind element will emit a signal and act as a
passthrough module from that point on. If no type was found, it will
emit an error and further media processing will stop.

View file

@ -73,7 +73,7 @@
has timestamped control-values assigned one can change the GObject
property through <function>g_object_set()</function>.
This is highly useful when binding the GObject properties to GUI widgets.
When the user adjusts the value with the widget, one can set the GOBject
When the user adjusts the value with the widget, one can set the GObject
property and this remains active until the next timestamped value overrides.
This also works with smoothed parameters.
</para>

View file

@ -148,7 +148,7 @@
</note>
<para>
This interface is currently implemented by many elements, including
the ALSA, OSS, XVImageSink, Video4linux and Video4linux2 elements.
the ALSA, OSS, XVideo, Video4linux and Video4linux2 elements.
</para>
</sect1>

View file

@ -18,7 +18,7 @@
<title>Querying: getting the position or length of a stream</title>
<para>
Querying is defined as requesting a specific stream-property related
Querying is defined as requesting a specific stream property related
to progress tracking. This includes getting the length of a stream (if
available) or getting the current position. Those stream properties
can be retrieved in various formats such as time, audio samples, video

View file

@ -105,11 +105,11 @@
</listitem>
<listitem>
<para>
<option>--gst-debug-no-color</option> will disable color debugging
<option>--gst-debug-no-color</option> will disable color debugging.
You can also set the GST_DEBUG_NO_COLOR environment variable to 1
if you want to disable colored debug output permanently. Note that
if you are disabling color purely to avoid messing up your pager
output, trying using <command>less -R</command>.
output, try using <command>less -R</command>.
</para>
</listitem>
<listitem>

View file

@ -225,11 +225,20 @@ main (int argc,
$(pkg-config --cflags --libs gstreamer-&GST_MAJORMINOR;)
helloworld.c -o helloworld</command>. &GStreamer; makes use of
<command>pkg-config</command> to get compiler and linker flags
needed to compile this application. If you're running a
non-standard installation, make sure the
<classname>PKG_CONFIG_PATH</classname> environment variable is
set to the correct location (<filename>$libdir/pkgconfig</filename>).
application against the uninstalled location.
needed to compile this application.
</para>
<para>
If you're running a non-standard installation (ie. you've installed
GStreamer from source yourself instead of using pre-built packages),
make sure the <classname>PKG_CONFIG_PATH</classname> environment variable
is set to the correct location (<filename>$libdir/pkgconfig</filename>).
</para>
<para>
In the unlikely case that you are using an uninstalled GStreamer
setup (ie. gst-uninstalled), you will need to use libtool to build the
hello world program, like this: <command>libtool --mode=link gcc -Wall
$(pkg-config --cflags --libs gstreamer-&GST_MAJORMINOR;)
helloworld.c -o helloworld</command>.
</para>
<para>
You can run this example application with <command>./helloworld