mirrors/gstreamer
mirrors/gstreamer
1
1
Fork 0
mirror of https://gitlab.freedesktop.org/gstreamer/gstreamer.git synced 2025-01-30 11:08:34 +00:00
Code Issues 1 Projects Releases Wiki Activity

markdown: Fix typo in docs (2)

Browse source 
https://bugzilla.gnome.org/show_bug.cgi?id=797129
This commit is contained in:
H1Gdev 2018-09-13 13:24:24 +09:00 committed by Sebastian Dröge
parent 9f622daacb
commit 69ebd96fef
5 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
markdown/contribute/index.md
View file

@ -224,7 +224,7 @@ in the current directory. Attach these files to a bug report in bugzilla.
Please make sure your patches are as terse and precise as possible. Do not Please make sure your patches are as terse and precise as possible. Do not
include 'clean-ups' or non-functional changes, since they distract from the include 'clean-ups' or non-functional changes, since they distract from the
real changes and make things harder to review, and also lower the chances that real changes and make things harder to review, and also lower the chances that
the patch will still apply cleanly to the lastest version in git. If you feel the patch will still apply cleanly to the latest version in git. If you feel
there are things to clean up, please submit the clean-ups as a separate patch there are things to clean up, please submit the clean-ups as a separate patch
that does not contain any functional changes. that does not contain any functional changes.

2
markdown/design/stream-status.md
View file

@ -90,7 +90,7 @@ The existing `STREAM_STATUS` message will be further defined and implemented in
a pad, the message source will contain the owner as well. The idea a pad, the message source will contain the owner as well. The idea
is that the application should be able to see from the element/pad is that the application should be able to see from the element/pad
what function this thread has in the context of the application and what function this thread has in the context of the application and
configure the thread appropriatly. configure the thread appropriately.
- **`object`**: `G_TYPE`, `GstTask/GThread`: A `GstTask/GThread` controlling - **`object`**: `G_TYPE`, `GstTask/GThread`: A `GstTask/GThread` controlling
this streaming thread. this streaming thread.

2
markdown/installing/on-windows.md
View file

@ -107,7 +107,7 @@ liking, and work from there.
> ![Information](images/icons/emoticons/information.png) > ![Information](images/icons/emoticons/information.png)
> **64-bit Users** > **64-bit Users**
> >
>Use `%GSTREAMER_ROOT_X86_64%` if you have installed GStreamer binaries for 64-bit platforms. Both GStreamer binariess (32 and 64-bit) can be installed simultaneously, and hence the separate environment variables. >Use `%GSTREAMER_ROOT_X86_64%` if you have installed GStreamer binaries for 64-bit platforms. Both GStreamer binaries (32 and 64-bit) can be installed simultaneously, and hence the separate environment variables.
> >
>Make sure you select the Solution Configuration that matches GStreamer that you have installed: `Win32` for 32 bits or `x64` for 64 bits. >Make sure you select the Solution Configuration that matches GStreamer that you have installed: `Win32` for 32 bits or `x64` for 64 bits.
> >

4
markdown/plugin-development/advanced/allocation.md
View file

@ -19,8 +19,8 @@ GStreamer plugins. We will first talk about the lowlevel `GstMemory`
object that manages access to a piece of memory and then continue with object that manages access to a piece of memory and then continue with
one of it's main users, the `GstBuffer`, which is used to exchange data one of it's main users, the `GstBuffer`, which is used to exchange data
between plugins and with the application. We will also discuss the `GstMeta`. between plugins and with the application. We will also discuss the `GstMeta`.
This object can be placed on buffers to provide extra info about it an This object can be placed on buffers to provide extra info about it and
dits memory. We will also discuss the `GstBufferPool`, which allows to its memory. We will also discuss the `GstBufferPool`, which allows to
more-efficiently manage buffers of the same size. more-efficiently manage buffers of the same size.
To conclude this chapter we will take a look at the `GST_QUERY_ALLOCATION` To conclude this chapter we will take a look at the `GST_QUERY_ALLOCATION`

4
markdown/tutorials/basic/debugging-tools.md
View file

@ -51,7 +51,7 @@ amount of desired output:
| | | user-visible problems are expected to happen. | | | | user-visible problems are expected to happen. |
| 3 | FIXME | Logs all "fixme" messages. Those typically that a codepath that| | 3 | FIXME | Logs all "fixme" messages. Those typically that a codepath that|
| | | is known to be incomplete has been triggered. It may work in | | | | is known to be incomplete has been triggered. It may work in |
| | | most cases, but mauy cause problems in specific instances. | | | | most cases, but may cause problems in specific instances. |
| 4 | INFO | Logs all informational messages. These are typically used for | | 4 | INFO | Logs all informational messages. These are typically used for |
| | | events in the system that only happen once, or are important | | | | events in the system that only happen once, or are important |
| | | and rare enough to be logged at this level. | | | | and rare enough to be logged at this level. |
@ -64,7 +64,7 @@ amount of desired output:
| | | streaming and steady-state conditions. This is used for log | | | | streaming and steady-state conditions. This is used for log |
| | | messages that happen on every buffer in an element for example.| | | | messages that happen on every buffer in an element for example.|
| 7 | TRACE | Logs all trace messages. Those are message that happen very | | 7 | TRACE | Logs all trace messages. Those are message that happen very |
| | | very often. This is for example is each each time the reference| | | | very often. This is for example is each time the reference |
| | | count of a GstMiniObject, such as a GstBuffer or GstEvent, is | | | | count of a GstMiniObject, such as a GstBuffer or GstEvent, is |
| | | modified. | | | | modified. |
| 8 | MEMDUMP | Logs all memory dump messages. This is the heaviest logging and| | 8 | MEMDUMP | Logs all memory dump messages. This is the heaviest logging and|