Browse Source

Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.


git-svn-id: svn:// 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
toma 11 years ago
100 changed files with 12284 additions and 0 deletions
  1. +3
  2. +347
  3. +397
  4. +17
  5. +176
  6. +16
  7. +22
  8. +16
  9. +97
  10. +17
  11. +5
  12. +4
  13. +78
  14. +4
  15. +468
  16. BIN
  17. +480
  18. +4
  19. +3351
  20. +1072
  21. +102
  22. BIN
  23. BIN
  24. +184
  25. +146
  26. +4
  27. +234
  28. +4
  29. +755
  30. +4
  31. +1083
  32. BIN
  33. +2
  34. BIN
  35. BIN
  36. BIN
  37. BIN
  38. BIN
  39. BIN
  40. BIN
  41. BIN
  42. BIN
  43. BIN
  44. BIN
  45. BIN
  46. BIN
  47. BIN
  48. BIN
  49. BIN
  50. BIN
  51. +1501
  52. BIN
  53. BIN
  54. BIN
  55. BIN
  56. BIN
  57. BIN
  58. BIN
  59. BIN
  60. BIN
  61. BIN
  62. BIN
  63. BIN
  64. BIN
  65. BIN
  66. BIN
  67. BIN
  68. BIN
  69. BIN
  70. BIN
  71. BIN
  72. BIN
  73. BIN
  74. BIN
  75. BIN
  76. BIN
  77. BIN
  78. BIN
  79. BIN
  80. BIN
  81. BIN
  82. BIN
  83. BIN
  84. +4
  85. +747
  86. BIN
  87. BIN
  88. BIN
  89. BIN
  90. BIN
  91. BIN
  92. BIN
  93. BIN
  94. BIN
  95. +4
  96. BIN
  97. +932
  98. +4
  99. BIN
  100. BIN

+ 3
- 0

@@ -0,0 +1,3 @@

Look in the subdirs to get info about the authors.

+ 347
- 0

@@ -0,0 +1,347 @@
NOTE! The GPL below is copyrighted by the Free Software Foundation, but
the instance of code that it refers to (the kde programs) are copyrighted
by the authors who actually wrote it.

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.


The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and
modification follow.

0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.

In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.

If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.

5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software

10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.





How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

+ 397
- 0

@@ -0,0 +1,397 @@
GNU Free Documentation License
Version 1.2, November 2002

Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.


The purpose of this License is to make a manual, textbook, or other
functional and useful document "free" in the sense of freedom: to
assure everyone the effective freedom to copy and redistribute it,
with or without modifying it, either commercially or noncommercially.
Secondarily, this License preserves for the author and publisher a way
to get credit for their work, while not being considered responsible
for modifications made by others.

This License is a kind of "copyleft", which means that derivative
works of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft
license designed for free software.

We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free
program should come with manuals providing the same freedoms that the
software does. But this License is not limited to software manuals;
it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License
principally for works whose purpose is instruction or reference.


This License applies to any manual or other work, in any medium, that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. Such a notice grants a
world-wide, royalty-free license, unlimited in duration, to use that
work under the conditions stated herein. The "Document", below,
refers to any such manual or work. Any member of the public is a
licensee, and is addressed as "you". You accept the license if you
copy, modify or distribute the work in a way requiring permission
under copyright law.

A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall subject
(or to related matters) and contains nothing that could fall directly
within that overall subject. (Thus, if the Document is in part a
textbook of mathematics, a Secondary Section may not explain any
mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding

The "Invariant Sections" are certain Secondary Sections whose titles
are designated, as being those of Invariant Sections, in the notice
that says that the Document is released under this License. If a
section does not fit the above definition of Secondary then it is not
allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant
Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed,
as Front-Cover Texts or Back-Cover Texts, in the notice that says that
the Document is released under this License. A Front-Cover Text may
be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the
general public, that is suitable for revising the document
straightforwardly with generic text editors or (for images composed of
pixels) generic paint programs or (for drawings) some widely available
drawing editor, and that is suitable for input to text formatters or
for automatic translation to a variety of formats suitable for input
to text formatters. A copy made in an otherwise Transparent file
format whose markup, or absence of markup, has been arranged to thwart
or discourage subsequent modification by readers is not Transparent.
An image format is not Transparent if used for any substantial amount
of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX input format, SGML
or XML using a publicly available DTD, and standard-conforming simple
HTML, PostScript or PDF designed for human modification. Examples of
transparent image formats include PNG, XCF and JPG. Opaque formats
include proprietary formats that can be read and edited only by
proprietary word processors, SGML or XML for which the DTD and/or
processing tools are not generally available, and the
machine-generated HTML, PostScript or PDF produced by some word
processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself,
plus such following pages as are needed to hold, legibly, the material
this License requires to appear in the title page. For works in
formats which do not have any title page as such, "Title Page" means
the text near the most prominent appearance of the work's title,
preceding the beginning of the body of the text.

A section "Entitled XYZ" means a named subunit of the Document whose
title either is precisely XYZ or contains XYZ in parentheses following
text that translates XYZ in another language. (Here XYZ stands for a
specific section name mentioned below, such as "Acknowledgements",
"Dedications", "Endorsements", or "History".) To "Preserve the Title"
of such a section when you modify the Document means that it remains a
section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which
states that this License applies to the Document. These Warranty
Disclaimers are considered to be included by reference in this
License, but only as regards disclaiming warranties: any other
implication that these Warranty Disclaimers may have is void and has
no effect on the meaning of this License.


You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies
to the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further
copying of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and
you may publicly display copies.


If you publish printed copies (or copies in media that commonly have
printed covers) of the Document, numbering more than 100, and the
Document's license notice requires Cover Texts, you must enclose the
copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
the back cover. Both covers must also clearly and legibly identify
you as the publisher of these copies. The front cover must present
the full title with all words of the title equally prominent and
visible. You may add other material on the covers in addition.
Copying with changes limited to the covers, as long as they preserve
the title of the Document and satisfy these conditions, can be treated
as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent

If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy
a computer-network location from which the general network-using
public has access to download using public-standard network protocols
a complete Transparent copy of the Document, free of added material.
If you use the latter option, you must take reasonably prudent steps,
when you begin distribution of Opaque copies in quantity, to ensure
that this Transparent copy will remain thus accessible at the stated
location until at least one year after the last time you distribute an
Opaque copy (directly or through your agents or retailers) of that
edition to the public.

It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.


You may copy and distribute a Modified Version of the Document under
the conditions of sections 2 and 3 above, provided that you release
the Modified Version under precisely this License, with the Modified
Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy
of it. In addition, you must do these things in the Modified Version:

A. Use in the Title Page (and on the covers, if any) a title distinct
from that of the Document, and from those of previous versions
(which should, if there were any, be listed in the History section
of the Document). You may use the same title as a previous version
if the original publisher of that version gives permission.
B. List on the Title Page, as authors, one or more persons or entities
responsible for authorship of the modifications in the Modified
Version, together with at least five of the principal authors of the
Document (all of its principal authors, if it has fewer than five),
unless they release you from this requirement.
C. State on the Title page the name of the publisher of the
Modified Version, as the publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications
adjacent to the other copyright notices.
F. Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
G. Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled "History", Preserve its Title, and add
to it an item stating at least the title, year, new authors, and
publisher of the Modified Version as given on the Title Page. If
there is no section Entitled "History" in the Document, create one
stating the title, year, authors, and publisher of the Document as
given on its Title Page, then add an item describing the Modified
Version as stated in the previous sentence.
J. Preserve the network location, if any, given in the Document for
public access to a Transparent copy of the Document, and likewise
the network locations given in the Document for previous versions
it was based on. These may be placed in the "History" section.
You may omit a network location for a work that was published at
least four years before the Document itself, or if the original
publisher of the version it refers to gives permission.
K. For any section Entitled "Acknowledgements" or "Dedications",
Preserve the Title of the section, and preserve in the section all
the substance and tone of each of the contributor acknowledgements
and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document,
unaltered in their text and in their titles. Section numbers
or the equivalent are not considered part of the section titles.
M. Delete any section Entitled "Endorsements". Such a section
may not be included in the Modified Version.
N. Do not retitle any existing section to be Entitled "Endorsements"
or to conflict in title with any Invariant Section.
O. Preserve any Warranty Disclaimers.

If the Modified Version includes new front-matter sections or
appendices that qualify as Secondary Sections and contain no material
copied from the Document, you may at your option designate some or all
of these sections as invariant. To do this, add their titles to the
list of Invariant Sections in the Modified Version's license notice.
These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties--for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a

You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of
Front-Cover Text and one of Back-Cover Text may be added by (or
through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or
by arrangement made by the same entity you are acting on behalf of,
you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.


You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its
license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by
adding at the end of it, in parentheses, the name of the original
author or publisher of that section if known, or else a unique number.
Make the same adjustment to the section titles in the list of
Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History"
in the various original documents, forming one section Entitled
"History"; likewise combine any sections Entitled "Acknowledgements",
and any sections Entitled "Dedications". You must delete all sections
Entitled "Endorsements".


You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.


A compilation of the Document or its derivatives with other separate
and independent documents or works, in or on a volume of a storage or
distribution medium, is called an "aggregate" if the copyright
resulting from the compilation is not used to limit the legal rights
of the compilation's users beyond what the individual works permit.
When the Document is included in an aggregate, this License does not
apply to the other works in the aggregate which are not themselves
derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these
copies of the Document, then if the Document is less than one half of
the entire aggregate, the Document's Cover Texts may be placed on
covers that bracket the Document within the aggregate, or the
electronic equivalent of covers if the Document is in electronic form.
Otherwise they must appear on printed covers that bracket the whole


Translation is considered a kind of modification, so you may
distribute translations of the Document under the terms of section 4.
Replacing Invariant Sections with translations requires special
permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the
original versions of these Invariant Sections. You may include a
translation of this License, and all the license notices in the
Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions
of those notices and disclaimers. In case of a disagreement between
the translation and the original version of this License or a notice
or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements",
"Dedications", or "History", the requirement (section 4) to Preserve
its Title (section 1) will typically require changing the actual


You may not copy, modify, sublicense, or distribute the Document except
as expressly provided for under this License. Any other attempt to
copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this
License will not have their licenses terminated so long as such
parties remain in full compliance.


The Free Software Foundation may publish new, revised versions
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See

Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.

ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and
license notices just after the title page:

Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
replace the "with...Texts." line with this:

with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the

If your document contains nontrivial examples of program code, we
recommend releasing these examples in parallel under your choice of
free software license, such as the GNU General Public License,
to permit their use in free software.

+ 17
- 0
ChangeLog View File

@@ -0,0 +1,17 @@
1998-12-05 Alex Zepeda <>

* README: Use a "new" style README.

1998-11-13 Alex Zepeda <>

* Makefile.cvs (all): Use an updated Makefile.cvs from kdenetwork that
tests for the admin directory.

* Remove comment about this being Alpha (quality)
software, and update version number (now it's at 1.1pre). Also, now
it uses the kde-common copy of the autoconf stuff.

1998-11-08 Alex Zepeda <>

* Makefile.cvs (all): Use the kde-common version of automoc.

+ 176
- 0

@@ -0,0 +1,176 @@
Basic Installation

These are generic installation instructions.

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

The file `' is used to create `configure' by a program
called `autoconf'. You only need `' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.

Running `configure' takes a while. While running, it prints some
messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Optionally, type `make check' to run any self-tests that come with
the package.

4. Type `make install' to install the programs and any data files and

5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.

Compilers and Options

Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another

Installation Names

By default, `make install' will install the package's files in
`/usr/local/kde/bin', `/usr/local/kde/lib', etc. You can specify an
installation prefix other than `/usr/local/kde' by giving `configure'
the option `--prefix=PATH'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type

There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:

See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults

If you want to set default values for `configure' scripts to share,
you can create a site shell script called `' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/' if it exists, then
`PREFIX/etc/' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls

`configure' recognizes the following options to control how it

Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.

Print a summary of the options to `configure', and exit.

Do not print messages saying which checks are being made.

Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.

Print the version of Autoconf used to generate the `configure'
script, and exit.

`configure' also accepts some other, not widely useful, options.

+ 16
- 0
Mainpage.dox View File

@@ -0,0 +1,16 @@
* @mainpage The KDE Graphics API Reference
* This section contains the KDE online class reference for the current
* development version of the KDE graphics package.
* - <a href="kviewshell/html/index.html"><b>kviewshell</b></a>
* (<a href="kviewshell/html/classes.html">classes</a>)\n
* <i>API for the implementation of kviewshell plugins.</i>
* More information about the KDE architecture in form of
* tutorials, HOWTOs,
* and FAQs can be found at
* the <a href="">KDE Developer's corner</a>.

+ 22
- 0 View File

@@ -0,0 +1,22 @@
## kdegraphics/ $Id$
## (C) 1997 Stephan Kulow

AUTOMAKE_OPTIONS = foreign 1.6.1

COMPILE_BEFORE_kooka = libkscan
COMPILE_BEFORE_kfaxview = kfax
COMPILE_BEFORE_kfile-plugins = kghostview
COMPILE_AFTER_kviewshell = kdvi kfaxview


EXTRA_DIST = admin debian README.pam kde.pamd

cd $(top_distdir) && perl $(top_srcdir)/admin/am_edit -padmin


include admin/
include admin/

+ 16
- 0
Makefile.cvs View File

@@ -0,0 +1,16 @@

@echo "This Makefile is only for the CVS repository"
@echo "This will be deleted before making the distribution"
@echo ""
@if test ! -d admin; then \
echo "Please recheckout this module!" ;\
echo "for cvs: use checkout once and after that update again" ;\
echo "for cvsup: checkout kde-common from cvsup and" ;\
echo " link kde-common/admin to ./admin" ;\
exit 1 ;\
$(MAKE) -f admin/Makefile.common cvs


+ 97
- 0
README View File

@@ -0,0 +1,97 @@
In this file:

* About kdegraphics
* Common Mistakes
* Debugging
* More Info

About kdegraphics
kdegraphics is a collection of graphic oriented applications:

* debian
Files needed to create Debian packages.

* doc
XML based documentation for the programs.

* kamera
Digital camera io_slave for Konqueror. Together gPhoto this allows you
to access your camera's picture with the URL kamera:/

* kcoloredit
Contains two programs: a color value editor and also a color picker.

* kdvi
Program (and embeddable KPart) to display *.DVI files from TeX.

* kfax
A program to display raw and tiffed fax images (g3, g3-2d, g4).

* kfaxview
An embeddable KPart to display tiffed fax images.

* kfile-plugins
Provide meta information for graphic files.

* kghostview
Program (and embeddable KPart) to display *.pdf and *.ps

* kiconedit
An icon editor.

* kmrml
Connects to a MRML server and find similar images

* kooka
A raster image scan program, based on SANE and libkscan.

* kolourpaint
An easy-to-use paint program designed for everyday tasks like drawing
simple diagrams/logos/icons and editing screenshots.
* kpovmodeler
Program to enter scenes for the 3D rendering engine PovRay.

* kruler
A ruler in inch, centimeter and pixel to check distances on the screen.

* ksnapshot
Make snapshots of the screen contents.

* kuickshow
Fast and comfortable imageviewer.

* kview
Picture viewer, provided as standalone program and embeddable KPart.

* kviewshell
Generic framework for viewer applications.

* libkscan
Library to access scanners used by kooka (and koffice), needs SANE to be

Common Mistakes
If configure claims Qt cannot be found, have a look at
to get a copy of latest Qt 3.3.x version.

You can use --enable-debug with the configure script, if you want to have
debug code in your KDE apps and libs. This will ensure useful and more
verbose backtraces, but will require a lot more disk space.

More Info
Please direct any bug reports to our bug list by visiting

General KDE discussions should go to the KDE mailing list (

+ 17
- 0 View File

@@ -0,0 +1,17 @@

dnl Checks for header files.
AC_CHECK_HEADERS(fcntl.h sys/time.h unistd.h stdlib.h paths.h)
dnl Checks for typedefs, structures, and compiler characteristics.


KDE_INIT_DOXYGEN([KDE Graphics API Reference], [Version $VERSION])

+ 5
- 0
doc/ View File

@@ -0,0 +1,5 @@


+ 4
- 0
doc/kamera/ View File

@@ -0,0 +1,4 @@


+ 78
- 0
doc/kamera/index.docbook View File

@@ -0,0 +1,78 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&kamera;">
<!ENTITY package "kdegraphics">
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE">

<book lang="&language;">

<title>The &kamera; Handbook</title>



<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(Major.minor.lesser), it could be used by automation scripts -->


<!-- Abstract about this handbook -->

&kamera; allows you to view and download images on a digital camera.



<chapter id="introduction"> <title>Introduction</title> <para>Sorry, but
the documentation for &kappname; was not finished when &kde; was installed on
this computer.</para> <para>If you need help, please check <ulink
url="">The &kde; Website</ulink> for updates, or by
submitting your question to <ulink url="">The
&kde; User Mailing list</ulink>.</para> <para><emphasis>The &kde;




Local Variables:
mode: sgml

// vim:ts=2:sw=2:tw=78:noet

+ 4
- 0
doc/kcoloredit/ View File

@@ -0,0 +1,4 @@


+ 468
- 0
doc/kcoloredit/index.docbook View File

@@ -0,0 +1,468 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
<!ENTITY kcoloredit "<application>KColorEdit</application>">
<!ENTITY kappname "&kcoloredit;">
<!ENTITY package "kdegraphics">
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE"> <!-- Change language only here -->

<book lang="&language;">
<title> The &kcoloredit; Handbook</title>





<para>&kcoloredit; is a palette files editor. It can be used for editing
color palettes and for color choosing and naming.</para>


<chapter id="introduction">

<para>&kcoloredit; is a palette files editor. It can be used for
editing color palettes and for color choosing and naming.</para>


<chapter id="file-operations">
<title>File operations</title>

<sect1 id="file">
<title>About palette files</title>

The palette files installed by &kde; can be either system-wide or the
user ones. The latter are in you private &kde; configuration
folders, and they are named <guilabel>Custom Colors</guilabel> and
<guilabel>Recent Colors</guilabel>.

In &kcoloredit;, you may open all of these palettes, as well as
palettes in arbitrary files.


<sect1 id="file-open">
<title>Opening a file</title>
In the <guilabel>Open File</guilabel> dialog, you may choose from a
list of installed palettes, or browse folders for files.


<chapter id="Edition">

<sect1 id="cursor">

<para>The cursor is visible as a line in the palette view. It can be
moved by clicking on an area beside a color.</para>

<para>The cursor has the following functions:</para>

It points to the color after it. The color, if any, is described below
the palette view. You may edit its name there.
It can be used to make a selection. A selection can be made by
clicking on an area beside a color, so to move the cursor there, and
by moving the mouse then with the left mouse button pressed.
<para>If the <guilabel>At cursor</guilabel> check-box near the
<guilabel>Add Color</guilabel> button is checked, a color from the
color chooser is put at the cursor. The color is either inserted
or it overwrites another one, depending on whether the
<guilabel>Overwrite</guilabel> mode is chosen. The mode can be chosen
by checking the <guilabel>Overwrite</guilabel> check-box, that is next
to the <guilabel>At cursor</guilabel> one.</para>


<sect1 id = "selection">
A selection, that can be made as it was written in the previous
section, can be used with the copy, cut and paste operations.

<sect1 id = "clipboard-format">
<title>Clipboard format</title>
&kcoloredit; uses the following format for clipboard data: for each
color three numbers for red, green and blue components, respectively,
and an optional color name, followed by a new line character if there
is another color. Therefore, if for example three numbers are in the
clipboard, they can be pasted by &kcoloredit; as a color.


<chapter id="color-selection">
<title>Selecting a color from an RGB space</title>

A color can be selected from an RGB space in &kcoloredit; in the
following ways:
By editing the HSV or RGB components.
By selecting a color from color gradient panels. In the left one, two
from HSV components can be selected, and in the right one, the third
one. The third component can be chosen by clicking on one of the
buttons labeled <guilabel>H:</guilabel>, <guilabel>S:</guilabel> and
<guilabel>V:</guilabel>. The one component panel display colors with
the other two components equal to these selected in the two components
panel. The two components panel may display colors with the third
component fixed, or, if the <guilabel>Variable</guilabel> check-box is
set, with a value equal to the one selected in the one component
panel. In the <guilabel>Replace</guilabel> mode, the color selected in
panels replaces the output one instantly, and in the
<guilabel>Change:</guilabel> mode it modifies the output color after
each click, or a mouse move while a mouse button is
pressed. Therefore, in the latter mode the color selected in the
gradient panels may be different from the output color. To synchronize
the colors, the <guibutton>Synchronize</guibutton> button can be used.

<!-- Someone energetic might want to write a small chapter here -->
<!-- describing RGB vs HSV etc -->

<chapter id="drag-and-drop">
<title>Drag and drop</title>
The palette colors and the color selection output color can be dragged
with a mouse.

<chapter id="menu-reference">
<title>Menu Reference</title>

<sect1 id="file-menu">
<title>The <guimenu>File</guimenu> Menu</title>

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Start a new palette in the current window.</action></para>

<guimenuitem>New Window</guimenuitem>
<para><action>Open a new window</action></para>

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Open a saved palette.</action></para>

<guimenuitem>Open Recent</guimenuitem>
<para><action>Reopen a palette that you have recently been

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Save the currently open palette.</action></para>

<guimenuitem>Save As...</guimenuitem>
<para><action>Save the currently open palette with a new

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Close</action> the current &kcoloredit; window</para>

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Quit</action> &kcoloredit;.</para>


<sect1 id="edit-menu">
<title>The <guimenu>Edit</guimenu> Menu</title>

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Cut the currently selected color to the

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Copy the currently selected color to the

<shortcut><keycombo action="simul">&Ctrl;
<para><action>Paste a color from the clipboard.</action></para>


<sect1 id="color-menu">
<title>The <guimenu>Color</guimenu> Menu</title>

<guimenuitem>From Palette</guimenuitem>
<para><action>Find the color currently selected in the palette, in the
color selector on the left.</action></para><!-- eww... needs rewrite -->

<guimenuitem>From Screen</guimenuitem>
<para><action>Pick a color from anywhere on the screen, and find it
in the color selector on the left.</action></para>


<sect1 id="settings-menu">
<title>The <guimenu>Settings</guimenu> Menu</title>

<guimenuitem>Hide/Show Toolbar</guimenuitem>
<para><action>Toggle on and off the toolbar icons.</action></para>

<guimenuitem>Hide/Show Statusbar</guimenuitem>
<para><action>Toggle on and off the status bar.</action></para>

<guimenuitem>Hide/Show Color Names</guimenuitem>
<para>If the currently open palette has color name, <action>display
them alongside the colors</action>.</para>

<guimenuitem>Configure Shortcuts...</guimenuitem>
<para><action>Configure</action> the keyboard keys you use to access the
different actions.</para>

<guimenuitem>Configure Toolbars...</guimenuitem>
<para><action>Configure</action> the items you want to put in the toolbar



<sect1 id="help-menu">
<title>The <guimenu>Help</guimenu> Menu</title>




<chapter id="credits-and-licenses">
<title>Credits and Licenses</title>

<para>&kcoloredit; copyright 2000 &Artur.Rataj;</para>

<para>Documentation copyright 2000 &Artur.Rataj;</para>



<appendix id="installation">




Local Variables:
mode: sgml
sgml-omittag: nil
sgml-shorttag: t

doc/kdvi/KDVI-features.dvi View File

+ 480
- 0
doc/kdvi/KDVI-features.tex View File

@@ -0,0 +1,480 @@


\newcommand{\KDVI}{{\sf KDVI 1.1}}


\title{Support for \TeX\ extensions in \KDVI}

\author{Stefan Kebekus}

This document describes the extensions to the standard format of DVI
files which \KDVI\ implements in order to support PostScript
inclusion and hyperlinks.
\KDVI\ is a program that displays DVI-files generated by the \TeX\
typesetting system. If you don't know what \TeX\ is then you are
most likely not interested in this. If you would like to know how to
use special features of \KDVI, then you can find examples here.


\section{What's all this}

The DVI-previewing program \KDVI\ is able to display standard
DVI-files as specified in \cite{Level0Std}. In order to support
graphics inclusion, hyperlinks and non-standard fonts, \KDVI\
implements a number of features which extend \cite{Level0Std}. In
particular, \KDVI\ supports a number of \TeX 's $\backslash${\tt
special} commands. The aim of this document is to describe these
extensions and give examples of their use.

Unfortunately, in spite of several attempts to find a sound standard
for the use of $\backslash${\tt special} commands, there is now a
wealth of competing and mutually incompatible definitions.

\KDVI\ does not attempt to support all possible features. Instead, we
tried to implement those which are most useful and used most commonly.
In this, we have tried to be consistent with the {\sf dvips} program.
\KDVI\ does not support a number of outdated and unsane standards, nor
does it support features which impair the system security.

\section{Virtual fonts}

\KDVI\ supports ``virtual fonts''. This enables \TeX\ to use
PostScript fonts. For more information, and a complete specification,
consult \cite{dvips}.


This text uses the ``Times'' family of fonts instead of the ``Computer
Modern'' fonts which are usually used by \TeX. This was realized in
\LaTeX 2$\epsilon$ by including the line
in the header of this document.

\section{PostScript support}

\KDVI\ implements basic facilities to include PostScript graphics in a
DVI file, which will enable the reader to conviently read most
scientific papers which use such features.

\subsection{Literal PostScript}

\KDVI\ supports the inclusion of PostScript into DVI-files by means of
the quote-special. The syntax follows the specification of
\special{" PostScript-commands}
The PostScript-commands are not directly included, in fact they are
sandwiched between a {\tt save} and {\tt restore} pair. That way
\KDVI\ ensures that the command cannot affect PostScript-commands
which appear somewhere else in your file.


Figure~\ref{quote-special} shows an example taken from \cite{dvips}.
The generating \TeX -code is
\vbox to 100bp{\vss
\special{" newpath 0 0 moveto 100 100 lineto
300 0 lineto closepath gsave 0.8 setgray fill
grestore stroke}}

\vbox to 100bp{\vss
\special{" newpath 0 0 moveto 100 100 lineto 300 0 lineto closepath gsave 0.8 setgray fill grestore stroke}}
\caption{Graphic generated by literal PostScript inclusion\label{quote-special}}

\subsection{Direct PostScript}

\KDVI\ supports the inclusion of PostScript into DVI-files by means of
the direct-special. The syntax follows the specification of
\special{ps: Postscript-commands}
The PostScript-commands are directly included, and there is no
protective {\tt save} and {\tt restore} pair. The use of this command
is not recommended, as it may have funny side effects on other
PostScript commands which appear later in your file.

\KDVI\ also supports the following syntactical variants which are
explained in \cite{dvips}:
\special{ps: Postscript-commands}
\special{ps::[begin] Postscript-commands}
\special{ps:: Postscript-commands}
\special{ps::[end] Postscript-commands}
The variant
\special{ps: plotfile filename}
is not currently supported.


The command
\includegraphics[height=3cm, angle=20]{}
which is used in section~\ref{chap:eps} uses the direct-special
internally in order to set the rotation.

\subsection{Literal headers}

Literal headers work as described in \cite{dvips}.
\special{! PostScript-Header-commands}

The following diagram, which was generated using the \Xy -pic macro
packages uses literal postscript inclusion which relies on literal
\xymatrix{ {\tilde X}
\ar@{-->}[rrd]_{\exists \alpha} \ar[rrrr]^{\eta}_{\txt{\tiny
normalization}} \ar@/_/ [rrdd]_ {\tilde \pi} & & & & {X}
\ar@/^/[lldd]^{\pi} \\ & & {X'}
\ar@{-->}[rru]_{\exists \beta} \ar@{-->}[d]_{\exists \pi'} & & \\ & &
{Y}& &}
Note that the actual headers are defined on the first page of the
document. This was a major source of trouble in earlier versions of

\subsection{PostScript headers}

PostScript headers work as described in \cite{dvips}. This command is
very similar to the literal header command, but expects the name of a
file which should be included.

\subsection{EPS inclusion}\label{chap:eps}

A popular way to include PostScript-files into \TeX\ documents uses
the PSFile $\backslash${\tt special} command. Again this is explained
in detail in \cite{dvips}. Currently \KDVI\ supports the syntax
\special{psfile=File keyword=value keyword=value ...}
Where keyword is one of the following
\item[llx] lower left corner of the bounding box, $x$-coordinate
\item[lly] lower left corner of the bounding box, $y$-coordinate
\item[urx] upper right corner of the bounding box, $x$-coordinate
\item[ury] upper right corner of the bounding box, $y$-coordinate
\item[rwi] width of the bounding box. If $llx-urx \not = rwi$, then
the boundig box is scaled accordingly.
\item[rhi] height of the bounding box If $lly-ury \not = rhi$, then
the boundig box is scaled accordingly.
\item[angle] rotates the picture counterclockwise
Unknown keywords are silently ignored. The keywords {\tt llx}, {\tt
lly}, {\tt urx}, {\tt ury} and {\tt rwi} are usually generated by
the {\tt epsf} macros. The keywords {\tt hoffset}, {\tt voffset},
{\tt hsize}, {\tt vsize}, {\tt hscale}, {\tt vscale}, {\tt angle} and
{\tt clip} are not currently implemented. The ``uncompression''
feature of {\sf dvips} and {\sf xdvi} which allows to execute
arbitrary commands in via the syntactical variant
\special{psfile="'shell-command" keyword=value ...}
is deliberately not implemented for security reasons.

Figure~\ref{epsf-special} shows an embedded postscript-file.
\includegraphics[height=3cm, angle=20]{}
\caption{Embedded PostScript graphic\label{epsf-special}}
This was easily realized by including the line
into the header of this document, and the lines
\includegraphics[height=3cm, angle=20]{}
at the place where the graphic should appear. It is strongly
recommended to use the {\tt graphicx} macro package for this purpose.
\includegraphics[height=2cm, bb=0 0 150 50]{}
\caption{Reference to a non-existent PS-file\label{nonex-special}}
Figure~\ref{nonex-special} shows how \KDVI\ warns you about
non-existent files.

\section{Hypertext support}

\KDVI\ supports commands for hyperlink support which commands
establish links between sections of documents in a manner exactly
analogous to the HTML of the WWW. For a detailed specification we
refer to \cite{HFAQ99} or \cite{Rah98}. Note, however, that \KDVI\
does currently not allow nested hyperlinks.


The commands
\special{html:<a name="namestring">}
labels the current point of the text for later reference.


The commands
\special{html:<a href="hrefstring">}
makes {\tt Text} a link to {\tt hrefstring}, where {\tt hrefstring} is
an absolute or relative URL in the standard format used on the
internel. If {\tt hrefstring} is of the form {\tt \#label} then it
points to the section of the current document which is labeled using
the labeling command described above:
\special{html:<a name="namestring">}

This document features a clickable table of contents, and also the
references can be clicked on. This has been achieved by using the {\tt
hyperref} macro package in \LaTeX\ by including the line
into the document preamble. Everything else is automatic.

Here is an external link which points to the \href{}{main
website of the KDE project}. For this, the command {\tt href} of the
{\tt hyperref} macro package was used:
website of the KDE project}

\paragraph{Warning.} On some installations, the {\tt
hyperref} macro package is configured to generate PostScript
hyperlinks for {\tt dvips} by default. On these systems, using the
will generate DVI file whose hyperlinks are not visible in KDVI.
Worse, KDVI will call the {\tt ghostview} PostScript interpreter for
every page, which makes the display very slow.

\section{Colored \Red{text} \Green{and} \Blue{background}}

The DVI specials for colored text are supported as they are described
in \cite{dvips}.

\paragraph*{Example} In this document, the following code was used to
generate the text below.


\textGreen This text is green but here we are
\Red{switching to red, \Blue{nesting blue},
recovering the red} and back to original green.
\textCyan The text from here on will be cyan
unless \Yellow{locally changed to yellow}. Now
we are back to cyan. \textBlack

This gave the following output:
\textGreen This text is green but here
we are \Red{switching to red, \Blue{nesting blue}, recovering the red}
and back to original green. \textCyan The text from here on will be
cyan unless \Yellow{locally changed to yellow}. Now we are back to
cyan. \textBlack

To set the background color of the page, the command
was used. To switch back to normal, the command
was placed somewhere on the following page. As you see, the background
command does not fit well into \LaTeX's philosophy and should be

\section{Rotated Text}

Rotated text can sometimes be useful, e.g. to fit large table onto a