gio2 0.90.3-x86-mingw32

data/vendor/local/share/man/man1/gettext.1

@@ -0,0 +1,69 @@
+.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.24.
+.TH GETTEXT "1" "June 2010" "GNU gettext-runtime 0.18.1" GNU
+.SH NAME
+gettext \- translate message
+.SH SYNOPSIS
+.B gettext
+[\fIOPTION\fR] [[\fITEXTDOMAIN\fR] \fIMSGID\fR]
+.br
+.B gettext
+[\fIOPTION\fR] \fI-s \fR[\fIMSGID\fR]...
+.SH DESCRIPTION
+.\" Add any additional description here
+The \fBgettext\fP program translates a natural language message into the
+user's language, by looking up the translation in a message catalog.
+.PP
+Display native language translation of a textual message.
+.TP
+\fB\-d\fR, \fB\-\-domain\fR=\fITEXTDOMAIN\fR
+retrieve translated messages from TEXTDOMAIN
+.TP
+\fB\-e\fR
+enable expansion of some escape sequences
+.TP
+\fB\-E\fR
+(ignored for compatibility)
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+display this help and exit
+.TP
+\fB\-n\fR
+suppress trailing newline
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+display version information and exit
+.TP
+[TEXTDOMAIN] MSGID
+retrieve translated message corresponding
+to MSGID from TEXTDOMAIN
+.PP
+If the TEXTDOMAIN parameter is not given, the domain is determined from the
+environment variable TEXTDOMAIN.  If the message catalog is not found in the
+regular directory, another location can be specified with the environment
+variable TEXTDOMAINDIR.
+When used with the \fB\-s\fR option the program behaves like the `echo' command.
+But it does not simply copy its arguments to stdout.  Instead those messages
+found in the selected catalog are translated.
+Standard search directory: c:/devel/target/33bc8ddfeabcf34f6317ef7b2e85485f/share/locale
+.SH AUTHOR
+Written by Ulrich Drepper.
+.SH "REPORTING BUGS"
+Report bugs to <bug-gnu-gettext@gnu.org>.
+.SH COPYRIGHT
+Copyright \(co 1995-1997, 2000-2007 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+.br
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+.SH "SEE ALSO"
+The full documentation for
+.B gettext
+is maintained as a Texinfo manual.  If the
+.B info
+and
+.B gettext
+programs are properly installed at your site, the command
+.IP
+.B info gettext
+.PP
+should give you access to the complete manual.

data/vendor/local/share/man/man1/glib-genmarshal.1

@@ -0,0 +1,312 @@
+'\" t
+.\"     Title: glib-genmarshal
+.\"    Author: [see the "Author" section]
+.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
+.\"      Date: 09/27/2010
+.\"    Manual: User Commands
+.\"    Source: User Commands
+.\"  Language: English
+.\"
+.TH "GLIB\-GENMARSHAL" "1" "09/27/2010" "User Commands" "User Commands"
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+glib-genmarshal \- C code marshaller generation utility for GLib closures
+.SH "SYNOPSIS"
+.HP \w'\fBglib\-genmarshal\fR\ 'u
+\fBglib\-genmarshal\fR [options...] [files...]
+.SH "DESCRIPTION"
+.PP
+\fBglib\-genmarshal\fR
+is a small utility that generates C code marshallers for callback functions of the GClosure mechanism in the GObject sublibrary of GLib\&. The marshaller functions have a standard signature, they get passed in the invoking closure, an array of value structures holding the callback function parameters and a value structure for the return value of the callback\&. The marshaller is then responsible to call the respective C code function of the closure with all the parameters on the stack and to collect its return value\&.
+.SH "INVOCATION"
+.PP
+\fBglib\-genmarshal\fR
+takes a list of marshallers to generate as input\&. The marshaller list is either read from standard input or from files passed as additional arguments on the command line\&.
+.SS "Options"
+.PP
+\fB\-\-header\fR
+.RS 4
+Generate header file contents of the marshallers\&.
+.RE
+.PP
+\fB\-\-body\fR
+.RS 4
+Generate C code file contents of the marshallers\&.
+.RE
+.PP
+\fB\-\-prefix=string\fR, \fB\-\-prefix string\fR
+.RS 4
+Specify marshaller prefix\&. The default prefix is
+`g_cclosure_marshal\'\&.
+.RE
+.PP
+\fB\-\-skip\-source\fR
+.RS 4
+Skip source location remarks in generated comments\&.
+.RE
+.PP
+\fB\-\-nostdinc\fR
+.RS 4
+Do not use the standard marshallers of the GObject library, and skip
+gmarshal\&.h
+include directive in generated header files\&.
+.RE
+.PP
+\fB\-\-g\-fatal\-warnings\fR
+.RS 4
+Make warnings fatal, that is, exit immediately once a warning occurs\&.
+.RE
+.PP
+\fB\-h\fR, \fB\-\-help\fR
+.RS 4
+Print brief help and exit\&.
+.RE
+.PP
+\fB\-v\fR, \fB\-\-version\fR
+.RS 4
+Print version and exit\&.
+.RE
+.SS "Marshaller list format"
+.PP
+The marshaller lists are processed line by line, a line can contain a comment in the form of
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+# this is a comment
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+or a marshaller specification of the form
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+\fIRTYPE\fR:\fIPTYPE\fR
+\fIRTYPE\fR:\fIPTYPE\fR,\fIPTYPE\fR
+\fIRTYPE\fR:\fIPTYPE\fR,\fIPTYPE\fR,\fIPTYPE\fR
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+(up to 16
+\fIPTYPE\fRs may be present)\&.
+.PP
+The
+\fIRTYPE\fR
+part specifies the callback\'s return type and the
+\fIPTYPE\fRs right to the colon specify the callback\'s parameter list, except for the first and the last arguments which are always pointers\&.
+.SS "Parameter types"
+.PP
+Currently, the following types are supported:
+.PP
+\fIVOID\fR
+.RS 4
+indicates no return type, or no extra parameters\&. If
+\fIVOID\fR
+is used as the parameter list, no additional parameters may be present\&.
+.RE
+.PP
+\fIBOOLEAN\fR
+.RS 4
+for boolean types (gboolean)
+.RE
+.PP
+\fICHAR\fR
+.RS 4
+for signed char types (gchar)
+.RE
+.PP
+\fIUCHAR\fR
+.RS 4
+for unsigned char types (guchar)
+.RE
+.PP
+\fIINT\fR
+.RS 4
+for signed integer types (gint)
+.RE
+.PP
+\fIUINT\fR
+.RS 4
+for unsigned integer types (guint)
+.RE
+.PP
+\fILONG\fR
+.RS 4
+for signed long integer types (glong)
+.RE
+.PP
+\fIULONG\fR
+.RS 4
+for unsigned long integer types (gulong)
+.RE
+.PP
+\fIINT64\fR
+.RS 4
+for signed 64bit integer types (gint64)
+.RE
+.PP
+\fIUINT64\fR
+.RS 4
+for unsigned 64bit integer types (guint64)
+.RE
+.PP
+\fIENUM\fR
+.RS 4
+for enumeration types (gint)
+.RE
+.PP
+\fIFLAGS\fR
+.RS 4
+for flag enumeration types (guint)
+.RE
+.PP
+\fIFLOAT\fR
+.RS 4
+for single\-precision float types (gfloat)
+.RE
+.PP
+\fIDOUBLE\fR
+.RS 4
+for double\-precision float types (gdouble)
+.RE
+.PP
+\fISTRING\fR
+.RS 4
+for string types (gchar*)
+.RE
+.PP
+\fIBOXED\fR
+.RS 4
+for boxed (anonymous but reference counted) types (GBoxed*)
+.RE
+.PP
+\fIPARAM\fR
+.RS 4
+for GParamSpec or derived types (GParamSpec*)
+.RE
+.PP
+\fIPOINTER\fR
+.RS 4
+for anonymous pointer types (gpointer)
+.RE
+.PP
+\fIOBJECT\fR
+.RS 4
+for GObject or derived types (GObject*)
+.RE
+.PP
+\fIVARIANT\fR
+.RS 4
+for GVariant types (GVariant*)
+.RE
+.PP
+\fINONE\fR
+.RS 4
+deprecated alias for
+\fIVOID\fR
+.RE
+.PP
+\fIBOOL\fR
+.RS 4
+deprecated alias for
+\fIBOOLEAN\fR
+.RE
+.SH "EXAMPLE"
+.PP
+To generate marshallers for the following callback functions:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+void   foo (gpointer data1,
+            gpointer data2);
+void   bar (gpointer data1,
+            gint     param1,
+            gpointer data2);
+gfloat baz (gpointer data1,
+            gboolean param1,
+            guchar   param2,
+            gpointer data2);
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+The marshaller list has to look like this:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+VOID:VOID
+VOID:INT
+FLOAT:BOOLEAN,UCHAR
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+The generated marshallers have the arguments encoded in their function name\&. For this particular list, they are
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+g_cclosure_marshal_VOID__VOID(),
+g_cclosure_marshal_VOID__INT(), 
+g_cclosure_marshal_FLOAT__BOOLEAN_UCHAR()\&.
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+They can be used directly for GClosures or be passed in as the GSignalCMarshaller c_marshaller; argument upon creation of signals:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+GClosure *cc_foo, *cc_bar, *cc_baz;
+
+cc_foo = g_cclosure_new (NULL, foo, NULL);
+g_closure_set_marshal (cc_foo, g_cclosure_marshal_VOID__VOID);
+cc_bar = g_cclosure_new (NULL, bar, NULL);
+g_closure_set_marshal (cc_bar, g_cclosure_marshal_VOID__INT);
+cc_baz = g_cclosure_new (NULL, baz, NULL);
+g_closure_set_marshal (cc_baz, g_cclosure_marshal_FLOAT__BOOLEAN_UCHAR);
+.fi
+.if n \{\
+.RE
+.\}
+.SH "SEE ALSO"
+.PP
+
+\fBglib\-mkenums\fR(1)
+.SH "BUGS"
+.PP
+None known yet\&.
+.SH "AUTHOR"
+.PP
+\fBglib\-genmarshal\fR
+has been written by Tim Janik
+timj@gtk\&.org\&.
+.PP
+This manual page was provided by Tim Janik
+timj@gtk\&.org\&.

data/vendor/local/share/man/man1/glib-mkenums.1

@@ -0,0 +1,246 @@
+'\" t
+.\"     Title: glib-mkenums
+.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
+.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
+.\"      Date: 09/27/2010
+.\"    Manual: User Commands
+.\"    Source: User Commands
+.\"  Language: English
+.\"
+.TH "GLIB\-MKENUMS" "1" "09/27/2010" "User Commands" "User Commands"
+.\" -----------------------------------------------------------------
+.\" * set default formatting
+.\" -----------------------------------------------------------------
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
+.\" -----------------------------------------------------------------
+.\" * MAIN CONTENT STARTS HERE *
+.\" -----------------------------------------------------------------
+.SH "NAME"
+glib-mkenums \- C language enum description generation utility
+.SH "SYNOPSIS"
+.HP \w'\fBglib\-mkenums\fR\ 'u
+\fBglib\-mkenums\fR [options...] [files...]
+.SH "DESCRIPTION"
+.PP
+\fBglib\-mkenums\fR
+is a small perl\-script utility that parses C code to extract enum definitions and produces enum descriptions based on text templates specified by the user\&. Most frequently this script is used to produce C code that contains enum values as strings so programs can provide value name strings for introspection\&.
+.SH "INVOCATION"
+.PP
+\fBglib\-mkenums\fR
+takes a list of valid C code files as input\&. The options specified control the text that is output, certain substitutions are performed on the text templates for keywords enclosed in @ characters\&.
+.SS "Options"
+.PP
+\fB\-\-fhead\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+prior to processing input files\&.
+.RE
+.PP
+\fB\-\-fprod\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+everytime a new input file is being processed\&.
+.RE
+.PP
+\fB\-\-ftail\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+after all input files have been processed\&.
+.RE
+.PP
+\fB\-\-eprod\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+everytime an enum is encountered in the input files\&.
+.RE
+.PP
+\fB\-\-vhead\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+before iterating over the set of values of an enum\&.
+.RE
+.PP
+\fB\-\-vprod\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+for every value of an enum\&.
+.RE
+.PP
+\fB\-\-vtail\fR \fItext\fR
+.RS 4
+Put out
+\fItext\fR
+after iterating over all values of an enum\&.
+.RE
+.PP
+\fB\-\-comments\fR \fItext\fR
+.RS 4
+Template for auto\-generated comments, the default (for C code generations) is
+"/* @comment@ */"\&.
+.RE
+.PP
+\fB\-\-template\fR \fIfile\fR
+.RS 4
+Read templates from the given file\&. The templates are enclosed in specially\-formatted C comments
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+/*** BEGIN section ***/
+/*** END section ***/
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+where section may be
+file\-header,
+file\-production,
+file\-tail,
+enumeration\-production,
+value\-header,
+value\-production,
+value\-tail
+or
+comment\&.
+.RE
+.PP
+\fB\-\-help\fR
+.RS 4
+Print brief help and exit\&.
+.RE
+.PP
+\fB\-\-version\fR
+.RS 4
+Print version and exit\&.
+.RE
+.SS "Production text substitutions"
+.PP
+Certain keywords enclosed in @ characters will be substituted in the emitted text\&. For the substitution examples of the keywords below, the following example enum definition is assumed:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+typedef enum
+{
+  PREFIX_THE_XVALUE    = 1 << 3,
+  PREFIX_ANOTHER_VALUE = 1 << 4
+} PrefixTheXEnum;
+.fi
+.if n \{\
+.RE
+.\}
+.PP
+@EnumName@
+.RS 4
+The name of the enum currently being processed, enum names are assumed to be properly namespaced and to use mixed capitalization to separate words (e\&.g\&. PrefixTheXEnum)\&.
+.RE
+.PP
+@enum_name@
+.RS 4
+The enum name with words lowercase and word\-separated by underscores (e\&.g\&. prefix_the_xenum)\&.
+.RE
+.PP
+@ENUMNAME@
+.RS 4
+The enum name with words uppercase and word\-separated by underscores (e\&.g\&. PREFIX_THE_XENUM)\&.
+.RE
+.PP
+@ENUMSHORT@
+.RS 4
+The enum name with words uppercase and word\-separated by underscores, prefix stripped (e\&.g\&. THE_XENUM)\&.
+.RE
+.PP
+@VALUENAME@
+.RS 4
+The enum value name currently being processed with words uppercase and word\-separated by underscores, this is the assumed literal notation of enum values in the C sources (e\&.g\&. PREFIX_THE_XVALUE)\&.
+.RE
+.PP
+@valuenick@
+.RS 4
+A nick name for the enum value currently being processed, this is usually generated by stripping common prefix words of all the enum values of the current enum, the words are lowercase and underscores are substituted by a minus (e\&.g\&. the\-xvalue)\&.
+.RE
+.PP
+@valuenum@
+.RS 4
+The integer value for the enum value currently being processed\&. This is calculated by using
+\fBperl\fR
+to attempt to evaluate the expression as it appears in the C source code\&. If evaluation fails then
+\fBglib\-mkenums\fR
+will exit with an error status, but this only happens if
+@valuenum@
+appears in your value production template\&. (Since: 2\&.26)
+.RE
+.PP
+@type@
+.RS 4
+This is substituted either by "enum" or "flags", depending on whether the enum value definitions contained bit\-shift operators or not (e\&.g\&. flags)\&.
+.RE
+.PP
+@Type@
+.RS 4
+The same as
+@type@
+with the first letter capitalized (e\&.g\&. Flags)\&.
+.RE
+.PP
+@TYPE@
+.RS 4
+The same as
+@type@
+with all letters uppercased (e\&.g\&. FLAGS)\&.
+.RE
+.PP
+@filename@
+.RS 4
+The name of the input file currently being processed (e\&.g\&. foo\&.h)\&.
+.RE
+.PP
+@basename@
+.RS 4
+The base name of the input file currently being processed (e\&.g\&. foo\&.h)\&. (Since: 2\&.22)
+.RE
+.SS "Trigraph extensions"
+.PP
+Some C comments are treated specially in the parsed enum definitions, such comments start out with the trigraph sequence
+/*<
+and end with the trigraph sequence
+>*/\&. Per enum definition, the options "skip" and "flags" can be specified, to indicate this enum definition to be skipped, or for it to be treated as a flags definition, or to specify the common prefix to be stripped from all values to generate value nicknames, respectively\&. The "lowercase_name" option can be used to specify the word separation used in the *_get_type() function\&. For instance, /*< lowercase_name=gnome_vfs_uri_hide_options >*/\&.
+.PP
+Per value definition, the options "skip" and "nick" are supported\&. The former causes the value to be skipped, and the latter can be used to specify the otherwise auto\-generated nickname\&. Examples:
+.sp
+.if n \{\
+.RS 4
+.\}
+.nf
+typedef enum /*< skip >*/
+{
+  PREFIX_FOO
+} PrefixThisEnumWillBeSkipped;
+typedef enum /*< flags,prefix=PREFIX >*/
+{
+  PREFIX_THE_ZEROTH_VALUE,	/*< skip >*/
+  PREFIX_THE_FIRST_VALUE,
+  PREFIX_THE_SECOND_VALUE,
+  PREFIX_THE_THIRD_VALUE,	/*< nick=the\-last\-value >*/
+} PrefixTheFlagsEnum;
+.fi
+.if n \{\
+.RE
+.\}
+.sp
+.SH "SEE ALSO"
+.PP
+
+\fBglib-genmarshal\fR(1)