diff options
| author | GMT 2000 Tony Gale <gale@gtk.org> | 2000-02-29 13:15:10 +0000 |
|---|---|---|
| committer | Tony Gale <gale@src.gnome.org> | 2000-02-29 13:15:10 +0000 |
| commit | 6ab2659931513e1ba79727cefc613dd3691801d8 (patch) | |
| tree | cfecf7113738687ceab805f8ab1125be5ad1450b /docs/faq | |
| parent | 160e3574ac503cf7337d1d57a071583587dcbe33 (diff) | |
| download | gdk-pixbuf-6ab2659931513e1ba79727cefc613dd3691801d8.tar.gz | |
Spelling/grammar fixes from Martin Buchholz <martin@xemacs.org>
Tue Feb 29 13:10:00 GMT 2000 Tony Gale <gale@gtk.org>
* gdk/gdkwindow.h gdk/x11/gxid.c gtk/gtkclist.c gtk/gtkclist.h
gtk/gtkctree.c gtk/gtkmenu.h gtk/gtkwidget.c gtk/testgtk.c
docs/styles.txt docs/refcounting.txt docs/gtkfaq.sgml
docs/gtk_tut.sgml docs/gtk.texi TODO:
Spelling/grammar fixes from Martin Buchholz <martin@xemacs.org>
Diffstat (limited to 'docs/faq')
| -rw-r--r-- | docs/faq/gtkfaq.sgml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/faq/gtkfaq.sgml b/docs/faq/gtkfaq.sgml index 89693940e..8b5f84091 100644 --- a/docs/faq/gtkfaq.sgml +++ b/docs/faq/gtkfaq.sgml @@ -741,7 +741,7 @@ are: You'll find these packages on the GNU main ftp server (<htmlurl url="ftp://ftp.gnu.org/" name="ftp://ftp.gnu.org/">) or on any GNU mirror. -In order to use the powerfull autoconf/automake scheme, you must create +In order to use the powerful autoconf/automake scheme, you must create a configure.in which may look like: <tscreen><verb> @@ -1521,7 +1521,7 @@ performance penalty. Its possible that, in the long term, the best solution to such problems might be just to change gtk to give labels X windows. A short term workaround is to put the label widget inside another -widget that does get it's own window - one possible candidate would +widget that does get its own window - one possible candidate would be the viewport widget. <tscreen><verb> @@ -1576,7 +1576,7 @@ carefully. There are two (easy) ways to attach some data to a gtk object. Using <tt/gtk_object_set_data()/ and <tt/gtk_object_get_data()/ seems to be the -most common way to do this, as it provides a powerfull interface +most common way to do this, as it provides a powerful interface to connect objects and data. <tscreen><verb> @@ -2594,7 +2594,7 @@ main (int argc, char *argv[]) /* give the error handler an idea on how the input is named */ scanner->input_name = "test text"; - /* scanning loop, we parse the input untill it's end is reached, + /* scanning loop, we parse the input until its end is reached, * the scanner encountered a lexing error, or our sub routine came * across invalid syntax */ @@ -2624,7 +2624,7 @@ main (int argc, char *argv[]) } </verb> -You need to understand that the scanner will parse it's input and +You need to understand that the scanner will parse its input and tokenize it, it is up to you to interpret these tokens, not define their types before they get parsed, e.g. watch gscanner parse a string: |