Initial import of extracted KDE i18n tarballs

1 files changed, 643 insertions, 0 deletions

diff --git a/tde-i18n-pt/docs/kdewebdev/klinkstatus/index.docbook b/tde-i18n-pt/docs/kdewebdev/klinkstatus/index.docbook
new file mode 100644
index 00000000000..a30aca02cb8
--- /dev/null
+++ b/tde-i18n-pt/docs/kdewebdev/klinkstatus/index.docbook
@@ -0,0 +1,643 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
+  <!ENTITY klinkstatus "<application
+>KLinkStatus</application
+>">
+  <!ENTITY kappname "&klinkstatus;">
+  <!ENTITY package "kdewebdev">
+  <!ENTITY % addindex "IGNORE">
+  <!ENTITY % Portuguese "INCLUDE"
+><!-- change language only here -->
+]>
+<!-- kdoctemplate v0.8 October 1 1999
+     Minor update to "Credits and Licenses" section on August 24, 2000
+     Removed "Revision history" section on 22 January 2001
+     Changed to Installation/Help menu entities 18 October 2001
+     Other minor cleanup and changes 18 October 2001 -->
+
+
+<!--
+This template was designed by: David Rugge davidrugge@mindspring.com
+with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
+and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
+of the KDE DocBook team.
+
+You may freely use this template for writing any sort of KDE documentation.
+If you have any changes or improvements, please let us know.
+
+Remember:
+- in XML, the case of the <tags
+> and attributes is relevant ;
+- also, quote all attributes.
+
+Please don't forget to remove all these comments in your final documentation,
+thanks ;-).
+-->
+
+<!-- ................................................................ -->
+
+<!-- The language must NOT be changed here. -->
+
+<book lang="&language;">
+
+<!-- This header contains all of the meta-information for the document such
+as Authors, publish date, the abstract, and Keywords -->
+
+<bookinfo>
+<title
+>O Manual do &klinkstatus;</title>
+
+<authorgroup>
+<author
+><firstname
+>Paulo</firstname
+> <surname
+>Moura Guedes</surname
+> <affiliation
+> <address
+><email
+>moura&#64;kdewebdev&#46;org</email
+></address>
+</affiliation>
+</author>
+
+<othercredit role="translator"
+><firstname
+>José</firstname
+><surname
+>Pires</surname
+><affiliation
+><address
+><email
+>jncp@netcabo.pt</email
+></address
+></affiliation
+><contrib
+>Tradução</contrib
+></othercredit
+> 
+
+</authorgroup>
+
+<copyright>
+<year
+>2004</year>
+<holder
+>Paulo Moura Guedes</holder>
+</copyright>
+<!-- Translators: put here the copyright notice of the translation -->
+<!-- Put here the FDL notice.  Read the explanation in fdl-notice.docbook
+     and in the FDL itself on how to use it. -->
+<legalnotice
+>&FDLNotice;</legalnotice>
+
+<!-- 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 (YYYY-MM-DD) and of the version
+(V.MM.LL), it could be used by automation scripts.
+Do NOT change these in the translation. -->
+
+<date
+>2004-04-29</date>
+<releaseinfo
+>0&#46;1&#46;3</releaseinfo>
+
+<!-- Abstract about this handbook -->
+
+<abstract>
+<para
+>O &klinkstatus; é um verificador de ligações para o &kde;. </para>
+</abstract>
+
+<!-- This is a set of Keywords for indexing by search engines.
+Please at least include KDE, the KDE package it is in, the name
+ of your application, and a few relevant keywords. -->
+
+<keywordset>
+<keyword
+>KDE</keyword>
+<keyword
+>KLinkStatus</keyword>
+<keyword
+>verificador de ligações</keyword>
+<keyword
+>validação</keyword>
+</keywordset>
+
+</bookinfo>
+
+
+<chapter id="introduction">
+<title
+>Introdução</title>
+
+<para
+>O &klinkstatus; é um verificador de hiperligações para o &kde;. Permite-lhe procurar as referências por hiperligações internas e externas no seu 'site' Web inteiro, numa única página, escolhendo a profundidade da procura. Você poderá também verificar os ficheiros locais, de FTP, FISH, &etc;, dado que o &klinkstatus; usa o KIO. Por questões de performance, as ligações poderão ser verificadas em simultâneo. Por favor relate quaisquer problemas ou pedidos de funcionalidades para http://linkstatus.paradigma.co.pt/bugs/. </para>
+</chapter>
+
+<chapter id="using-klinkstatus">
+<title
+>Usar o &klinkstatus;</title>
+
+<para>
+
+<!-- Note that all graphics should be in .png format. Use no gifs because of
+patent issues. -->
+
+<screenshot>
+<screeninfo
+>Aqui está uma imagem do &klinkstatus;</screeninfo>
+	<mediaobject>
+	  <imageobject>
+	    <imagedata fileref="screenshot.png" format="PNG"/>
+	  </imageobject>
+	  <imageobject>
+	    <imagedata fileref="screenshot.eps" format="EPS"/>
+	  </imageobject>
+	  <textobject>
+	    <phrase
+>Imagem</phrase>
+	  </textobject>
+	</mediaobject>
+</screenshot>
+</para>
+
+</chapter>
+
+<chapter id="commands">
+<title
+>Referência de Comandos</title>
+
+<sect1 id="klinkstatus-mainwindow">
+<title
+>A janela principal do &klinkstatus;</title>
+
+<sect2>
+<title
+>O Menu Ficheiro</title>
+<para>
+<variablelist>
+<varlistentry>
+<term
+><menuchoice
+><shortcut
+> <keycombo action="simul"
+>&Ctrl;<keycap
+>N</keycap
+></keycombo
+> </shortcut
+> <guimenu
+>Ficheiro</guimenu
+> <guimenuitem
+>Nova Verificação de Ligações</guimenuitem
+> </menuchoice
+></term>
+<listitem
+><para
+><action
+>Cria uma nova sessão, se nenhuma estiver vazia</action
+></para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><menuchoice
+><shortcut
+> <keycombo action="simul"
+>&Ctrl;<keycap
+>O</keycap
+></keycombo
+> </shortcut
+> <guimenu
+>Ficheiro</guimenu
+> <guimenuitem
+>Abrir URL</guimenuitem
+> </menuchoice
+></term>
+<listitem
+><para
+><action
+>Abre um &URL;</action
+></para
+></listitem>
+</varlistentry>
+<varlistentry>
+<term
+><menuchoice
+><shortcut
+> <keycombo action="simul"
+>&Ctrl;<keycap
+>W</keycap
+></keycombo
+> </shortcut
+> <guimenu
+>Ficheiro</guimenu
+> <guimenuitem
+>Fechar a Página</guimenuitem
+> </menuchoice
+></term>
+<listitem
+><para
+><action
+>Fecha a página actual.</action
+></para
+></listitem>
+</varlistentry>
+</variablelist>
+</para>
+
+</sect2>
+
+<sect2>
+<title
+>O Menu <guimenu
+>Ajuda</guimenu
+></title>
+&help.menu.documentation; </sect2>
+
+</sect1>
+</chapter>
+
+<!--
+<chapter id="developers">
+<title
+>Developer's Guide to &klinkstatus;</title>
+-->
+<!-- (OPTIONAL) A Programming/Scripting reference chapter should be
+used for apps that use plugins or that provide their own scripting hooks
+and/or development libraries. -->
+<!--
+<para
+>FILL_ME</para>
+-->
+<!-- Use refentries to describe APIs.  Refentries are fairly complicated and you
+should consult the docbook reference for further details. The example below was
+taken from that reference and shortened a bit for readability.
+
+<refentry id="re-1007-unmanagechildren-1">
+<refmeta>
+<refentrytitle
+>XtUnmanageChildren</refentrytitle>
+<refmiscinfo
+>Xt - Geometry Management</refmiscinfo>
+</refmeta>
+<refnamediv>
+<refname
+>XtUnmanageChildren
+</refname>
+<refpurpose
+>remove a list of children from a parent widget's managed
+list.
+<indexterm id="ix-1007-unmanagechildren-1"
+><primary
+>widgets</primary
+><secondary
+>removing</secondary
+></indexterm>
+<indexterm id="ix-1007-unmanagechildren-2"
+><primary
+>XtUnmanageChildren</primary
+></indexterm>
+</refpurpose>
+
+</refnamediv>
+<refsynopsisdiv>
+<refsynopsisdivinfo>
+<date
+>4 March 1996</date>
+</refsynopsisdivinfo>
+<synopsis
+>
+void XtUnmanageChildren(<replaceable class="parameter">children</replaceable>, <replaceable class="parameter">num_children</replaceable>)
+    WidgetList <replaceable class="parameter">children</replaceable>;
+    Cardinal <replaceable class="parameter">num_children</replaceable>;
+</synopsis>
+
+<refsect2 id="r2-1007-unmanagechildren-1">
+<title
+>Inputs</title>
+<variablelist>
+<varlistentry>
+<term
+><replaceable class="parameter"
+>children</replaceable>
+</term>
+<listitem>
+<para
+>Specifies an array of child widgets. Each child must be of
+class RectObj or any subclass thereof.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+><replaceable class="parameter"
+>num_children</replaceable>
+</term>
+<listitem>
+<para
+>Specifies the number of elements in <replaceable class="parameter"
+>children</replaceable
+>.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+</refsect2
+></refsynopsisdiv>
+
+<refsect1 id="r1-1007-unmanagechildren-1">
+<title
+>Description
+</title>
+<para
+><function
+>XtUnmanageChildren()</function
+> unmaps the specified widgets
+and removes them from their parent's geometry management.
+The widgets will disappear from the screen, and (depending
+on its parent) may no longer have screen space allocated for
+them.
+</para>
+<para
+>Each of the widgets in the <replaceable class="parameter"
+>children</replaceable
+> array must have
+the same parent.
+</para>
+<para
+>See the &ldquo;Algorithm&rdquo; section below for full details of the
+widget unmanagement procedure.
+</para>
+</refsect1>
+
+<refsect1 id="r1-1007-unmanagechildren-2">
+<title
+>Usage</title>
+<para
+>Unmanaging widgets is the usual method for temporarily
+making them invisible.  They can be re-managed with
+<function
+>XtManageChildren()</function
+>.
+</para>
+<para
+>You can unmap a widget, but leave it under geometry
+management by calling <function
+>XtUnmapWidget()</function
+>.  You can
+destroy a widget's window without destroying the widget by
+calling <function
+>XtUnrealizeWidget()</function
+>.  You can destroy a
+widget completely with <function
+>XtDestroyWidget()</function
+>.
+</para>
+<para
+>If you are only going to unmanage a single widget, it is
+more convenient to call <function
+>XtUnmanageChild()</function
+>.  It is
+often more convenient to call <function
+>XtUnmanageChild()</function>
+several times than it is to declare and initialize an array
+of widgets to pass to <function
+>XtUnmanageChildren()</function
+>.  Calling
+<function
+>XtUnmanageChildren()</function
+> is more efficient, however,
+because it only calls the parent's <function
+>change_managed()</function>
+method once.
+</para>
+</refsect1>
+
+<refsect1 id="r1-1007-unmanagechildren-3">
+<title
+>Algorithm
+</title>
+<para
+><function
+>XtUnmanageChildren()</function
+> performs the following:
+</para>
+<variablelist>
+<varlistentry>
+<term
+>-
+</term>
+<listitem>
+<para
+>Ignores the child if it already is unmanaged or is being
+destroyed.
+</para>
+</listitem>
+</varlistentry>
+<varlistentry>
+<term
+>-
+</term>
+<listitem>
+<para
+>Otherwise, if the child is realized, it makes it nonvisible
+by unmapping it.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>
+<para
+>FILL_ME
+</para>
+</refsect1>
+
+<refsect1 id="r1-1007-unmanagechildren-4">
+<title
+>Structures</title>
+<para
+>The <type
+>WidgetList</type
+> type is simply an array of widgets:
+</para>
+<screen id="sc-1007-unmanagechildren-1"
+>typedef Widget *WidgetList;
+</screen>
+</refsect1>
+</refentry>
+
+</chapter>
+-->
+
+<!--
+<chapter id="faq">
+<title
+>Questions and Answers</title>
+-->
+<!-- (OPTIONAL but recommended) This chapter should include all of the silly
+(and not-so-silly) newbie questions that fill up your mailbox. This chapter
+should be reserved for BRIEF questions and answers! If one question uses more
+than a page or so then it should probably be part of the
+"Using this Application" chapter instead. You should use links to
+cross-reference questions to the parts of your documentation that answer them.
+This is also a great place to provide pointers to other FAQ's if your users
+must do some complicated configuration on other programs in order for your
+application work. -->
+<!--
+&reporting.bugs;
+&updating.documentation;
+
+
+<qandaset id="faqlist">
+<qandaentry>
+-
+<question>
+<para
+>My Mouse doesn't work. How do I quit &klinkstatus;?</para>
+</question>
+<answer>
+<para
+>You silly goose! Check out the <link linkend="commands"
+>Commands
+Section</link
+> for the answer.</para>
+</answer>
+</qandaentry>
+<qandaentry>
+<question>
+<para
+>Why am I unable to twiddle my documents?</para>
+</question>
+<answer>
+<para
+>You can only twiddle your documents if you have the foobar.lib
+installed.</para>
+</answer>
+
+</qandaentry>
+</qandaset>
+
+</chapter>
+-->
+
+<chapter id="credits">
+
+<!-- Include credits for the programmers, documentation writers, and
+contributors here. The license for your software should then be included below
+the credits with a reference to the appropriate license file included in the KDE
+distribution. -->
+
+<title
+>Créditos e Licença</title>
+
+<para
+>Usar o &klinkstatus; </para>
+<para
+>Programa copyright &copy; 2004 Paulo Moura Guedes <email
+>pmg&#64;netcabo&#46;pt</email
+> </para>
+<para
+>Documentação copyright &copy; 2004 Paulo Moura Guedes <email
+>pmg&#64;netcabo&#46;pt</email
+> </para>
+
+<para
+>Tradução de José Nuno Pires <email
+>jncp@netcabo.pt</email
+></para
+> 
+&underFDL; &underGPL; </chapter>
+
+<appendix id="installation">
+<title
+>Instalação</title>
+
+<sect1 id="getting-klinkstatus">
+<title
+>Como obter o &klinkstatus;</title>
+
+<!-- This first entity contains boiler plate for applications that are
+part of KDE CVS.  You should remove it if you are releasing your
+application -->
+
+<!--&install.intro.documentation;-->
+<para
+>http://kde-apps.org </para>
+
+</sect1>
+
+
+<!--
+<sect1 id="requirements">
+<title
+>Requirements</title>
+
+List any special requirements for your application here. This should include:
+.Libraries or other software that is not included in kdesupport,
+kdelibs, or kdebase.
+.Hardware requirements like amount of RAM, disk space, graphics card
+capabilities, screen resolution, special expansion cards, etc.
+.Operating systems the app will run on. If your app is designed only for a
+specific OS, (you wrote a graphical LILO configurator for example) put this
+information here.
+-->
+<!--
+<para>
+In order to successfully use &klinkstatus;, you need &kde; 1.1. Foobar.lib is
+required in order to support the advanced &klinkstatus; features. &klinkstatus; uses
+about 5 megs of memory to run, but this may vary depending on your
+platform and configuration.
+</para>
+
+<para>
+All required libraries as well as &klinkstatus; itself can be found
+on <ulink url="ftp://ftp.klinkstatus.org"
+>The &klinkstatus; home page</ulink
+>.
+</para>
+-->
+<!-- For a list of updates, you may refer to the application web site
+or the ChangeLog file, or ... -->
+<!--
+<para>
+You can find a list of changes at <ulink
+url="http://apps.kde.org/klinkstatus"
+>http://apps.kde.org/klinkstatus</ulink
+>.
+</para>
+</sect1>
+-->
+<sect1 id="compilation">
+<title
+>Compilação e Instalação</title>
+&install.compile.documentation; </sect1>
+<!--
+<sect1 id="configuration">
+<title
+>Configuration</title>
+
+<para
+>Don't forget to tell your system to start the <filename
+>dtd</filename>
+dicer-toaster daemon first, or &klinkstatus; won't work !</para>
+
+</sect1>
+-->
+</appendix>
+
+&documentation.index;
+</book>
+
+<!--
+Local Variables:
+mode: sgml
+sgml-minimize-attributes:nil
+sgml-general-insert-case:lower
+sgml-indent-step:0
+sgml-indent-data:nil
+End:
+
+vim:tabstop=2:shiftwidth=2:expandtab
+-->
+