summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDarren Salt <linux@youmustbejoking.demon.co.uk>2008-05-11 18:31:42 +0100
committerDarren Salt <linux@youmustbejoking.demon.co.uk>2008-05-11 18:31:42 +0100
commit3d3343de9ffdae49eb24367c3df8b81e5f4eea55 (patch)
tree60aaeee4836f3198df6fea1e9e94ca34d4a2cf92
parent16a41a85516f6055918887938e9dd3f3f9fbcf28 (diff)
downloadxine-lib-3d3343de9ffdae49eb24367c3df8b81e5f4eea55.tar.gz
xine-lib-3d3343de9ffdae49eb24367c3df8b81e5f4eea55.tar.bz2
Correct some spelling & grocer's apostrophes.
-rw-r--r--include/xine.h.in22
1 files changed, 11 insertions, 11 deletions
diff --git a/include/xine.h.in b/include/xine.h.in
index ad79bebc6..f1d9d3119 100644
--- a/include/xine.h.in
+++ b/include/xine.h.in
@@ -431,7 +431,7 @@ int xine_get_param (xine_stream_t *stream, int param) XINE_PROTECTED;
* image data into a too small buffer.
*
* xine_get_current_frame_alloc() takes care of allocating
- * a buffer on it's own, so image data can be retrieved by
+ * a buffer on its own, so image data can be retrieved by
* a single call without the need to pause the stream.
*
* all functions return 1 on success, 0 failure.
@@ -1133,7 +1133,7 @@ typedef struct {
*
* this will be called by the video driver to find out
* how big the video output area size will be for a
- * given video size. The ui should _not_ adjust it's
+ * given video size. The ui should _not_ adjust its
* video out area, just do some calculations and return
* the size. This will be called for every frame, ui
* implementation should be fast.
@@ -1157,12 +1157,12 @@ typedef struct {
* frame output callback
*
* this will be called by the video driver for every frame
- * it's about to draw. ui can adapt it's size if necessary
+ * it's about to draw. ui can adapt its size if necessary
* here.
* note: the ui doesn't have to adjust itself to this
* size, this is just to be taken as a hint.
* ui must return the actual size of the video output
- * area and the video output driver will do it's best
+ * area and the video output driver will do its best
* to adjust the video frames to that size (while
* preserving aspect ratio and stuff).
* dest_x, dest_y: offset inside window
@@ -1233,7 +1233,7 @@ typedef struct {
*
* this will be called by the video driver to find out
* how big the video output area size will be for a
- * given video size. The ui should _not_ adjust it's
+ * given video size. The ui should _not_ adjust its
* video out area, just do some calculations and return
* the size. This will be called for every frame, ui
* implementation should be fast.
@@ -1257,12 +1257,12 @@ typedef struct {
* frame output callback
*
* this will be called by the video driver for every frame
- * it's about to draw. ui can adapt it's size if necessary
+ * it's about to draw. ui can adapt its size if necessary
* here.
* note: the ui doesn't have to adjust itself to this
* size, this is just to be taken as a hint.
* ui must return the actual size of the video output
- * area and the video output driver will do it's best
+ * area and the video output driver will do its best
* to adjust the video frames to that size (while
* preserving aspect ratio and stuff).
* dest_x, dest_y: offset inside window
@@ -1319,7 +1319,7 @@ typedef struct {
* So a frontend must at least support rgb.
* Be aware that rgb requires more cpu than yuv,
* so avoid its usage for video playback.
- * However, it's usefull for single frame capture (e.g. thumbs)
+ * However, it's useful for single frame capture (e.g. thumbs)
*/
int supported_formats;
@@ -1618,7 +1618,7 @@ int xine_config_lookup_entry (xine_t *self, const char *key,
/*
* update a config entry (which was returned from lookup_entry() )
*
- * xine will make a deep copy of the data in the entry into it's internal
+ * xine will make a deep copy of the data in the entry into its internal
* config database.
*/
void xine_config_update_entry (xine_t *self,
@@ -2013,8 +2013,8 @@ typedef struct {
* This is the mechanism to report async errors from engine.
*
* If frontend knows about the XINE_MSG_xxx type it may safely
- * ignore the 'explanation' field and provide it's own custom
- * dialog to the 'parameters'.
+ * ignore the 'explanation' field and provide its own custom
+ * dialogue to the 'parameters'.
*
* right column specifies the usual parameters.
*/