Go to file
Havoc Pennington 6446484667 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so
2001-10-22  Havoc Pennington  <hp@redhat.com>

	* gtk/gtktextlayout.h: add a #error unless you define
	GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so people don't use this accidentally

        * gtk/gtktext*.c: #define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API as appropriate.
2001-10-22 21:52:47 +00:00
contrib
debian
demos Remove handle_box from App demo. 2001-10-22 18:24:29 +00:00
docs add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
examples
gdk Remove handle_box from App demo. 2001-10-22 18:24:29 +00:00
gdk-pixbuf
gtk add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
m4macros
modules
po Update based on norwegian 2001-10-20 21:47:54 +00:00
tests Clarify behavior in docs, #61777 (gtk_text_iter_forward_search) 2001-10-22 19:13:28 +00:00
.cvsignore
acconfig.h
acinclude.m4
AUTHORS
autogen.sh
ChangeLog add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
ChangeLog.pre-1-0
ChangeLog.pre-1-2
ChangeLog.pre-2-0 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
ChangeLog.pre-2-2 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
ChangeLog.pre-2-4 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
ChangeLog.pre-2-6 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
ChangeLog.pre-2-8 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
ChangeLog.pre-2-10 add a #error unless you define GTK_TEXT_USE_INTERNAL_UNSUPPORTED_API, so 2001-10-22 21:52:47 +00:00
config.guess
config.h.win32.in
config.sub
configure.in
COPYING
gdk-2.0-uninstalled.pc.in
gdk-2.0.pc.in
gdk-pixbuf-2.0-uninstalled.pc.in
gdk-pixbuf-2.0.pc.in
gtk-config-2.0.in
gtk+-2.0-uninstalled.pc.in
gtk+-2.0.pc.in
gtk+.spec.in
HACKING
INSTALL
INSTALL.in
makecopyright
Makefile.am
NEWS
NEWS.pre-1-0
README
README.cvs-commits
README.in
README.nanox
README.win32
sanity_check
TODO
TODO.xml

General Information
===================

This is GTK+ version 1.3.9. GTK+, which stands for the Gimp ToolKit, 
is a library for creating graphical user interfaces for the X Window 
System. It is designed to be small, efficient, and flexible. GTK+ is 
written in C with a very object-oriented approach.

The official ftp site is:
  ftp://ftp.gtk.org/pub/gtk

The official web site is:
  http://www.gtk.org/

Information about mailing lists can be found at
  http://www.gtk.org/mailinglists.html

Installation
============

See the file 'INSTALL'

How to report bugs
==================

Bugs should be reported to the GNOME bug tracking system. 
(http://bugzilla.gnome.org, product gtk+.) You will need
to create an account for yourself.
  
In the bug report please include:
  
* Information about your system. For instance:

   - What operating system and version
   - What version of X
   - For Linux, what version of the C library

  And anything else you think is relevant.

* How to reproduce the bug. 

  If you can reproduce it with the testgtk program that is built 
  in the gtk/ subdirectory, that will be most convenient.  Otherwise, 
  please include a short test program that exhibits the behavior. 
  As a last resort, you can also provide a pointer to a larger piece 
  of software that can be downloaded.

* If the bug was a crash, the exact text that was printed out
  when the crash occured.

* Further information such as stack traces may be useful, but
  is not necessary. If you do send a stack trace, and the error
  is an X error, it will be more useful if the stacktrace
  is produced running the test program with the --sync command
  line option.

Patches
=======

Patches should also be submitted to bugzilla.gnome.org. If the
patch fixes an existing bug, add the patch as an attachment
to that bug report.

Otherwise, enter a new bug report that describes the patch,
and attach the patch to that bug report.

Bug reports containing patches should include the PATCH keyword
in their keyword fields. If the patch adds to or changes the GTK
programming interface, the API keyword should also be included.
  
Patches should be in unified diff form. (The -u option to GNU
diff.)