# Translation of oc.po to Occitan
# Occitan translation for platform-overview
# Copyright (C) 2007 THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Yannig MARCHEGAY (Kokoyaya) <yannig@marchegay.org> - 2006-2007
#
# Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>, 2007.
msgid ""
msgstr ""
"Project-Id-Version: oc\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2007-05-10 21:15+0100\n"
"PO-Revision-Date: 2007-12-23 12:17+0100\n"
"Last-Translator: Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>\n"
"Language-Team: Occitan <ubuntu-l10n-oci@lists.ubuntu.com>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: KBabel 1.11.4\n"

#: C/platform.xml:4(title)
msgid "Platform Overview"
msgstr ""

#: C/platform.xml:6(para)
msgid ""
"The GNOME platform provides a comprehensive development environment for "
"graphical applications and other software. Using the technologies in GNOME, "
"you can create high-quality software to meet and exceed your users' "
"expectations. This chapter provides a very brief overview of the components "
"that are discussed in this document."
msgstr ""

#: C/platform.xml:13(title) C/core-tech.xml:4(title)
msgid "Core Technologies"
msgstr ""

#: C/platform.xml:15(para)
msgid ""
"GNOME provides a number of libraries for constructing attractive graphical "
"interfaces. It provides libraries for displaying and manipulating common "
"user interface controls, for laying out and rendering text from most of the "
"world's writing systems, and for drawing sophisticated vector graphics to "
"the screen. The graphical technologies in GNOME are outlined in <xref "
"linkend=\"graphics\"/>."
msgstr ""

#: C/platform.xml:22(para)
msgid ""
"The GnomeVFS library provides a file system abstraction that allows users to "
"work with files on remote servers as well as the local file system. Using "
"GnomeVFS for file and folder operations allows your application to support "
"remote folders automatically. GnomeVFS is discussed in <xref linkend=\"gnome-"
"vfs\"/>."
msgstr ""

#: C/platform.xml:28(para)
msgid ""
"GNOME provides the GConf library and daemon for storing and retrieving user "
"preferences. GConf has a simple API that makes it easy to provide instant-"
"apply preferences in your application. Using GConf also allows "
"administrators to provide default and mandatory application settings for "
"their users. GConf is discussed in <xref linkend=\"gconf\"/>."
msgstr ""

#: C/platform.xml:34(para)
msgid ""
"GNOME provides facilities for internationalization and accessibility, "
"helping you reach the largest possible number of potential users. Much of "
"the internationalization and accessibility support is built right in, but "
"there are many issues you should be aware of when developing applications. "
"Internationalization is discussed in <xref linkend=\"i18n\"/>. Accessibility "
"is discussed in <xref linkend=\"a11y\"/>."
msgstr ""

#: C/platform.xml:41(para)
msgid ""
"GNOME ships with GStreamer, an extremely powerful multimedia framework for "
"creating, editing, and playing audio and video content. GStreamer is "
"discussed in <xref linkend=\"multimedia\"/>."
msgstr ""

#: C/platform.xml:45(para)
msgid ""
"GNOME also provides a complete print framework which leverages CUPS whenever "
"possible. The print framework in GNOME allows you to provide a consistent "
"interface to high-quality printing. The print framework is discussed in "
"<xref linkend=\"printing\"/>."
msgstr ""

#: C/platform.xml:52(title) C/ipc-network.xml:4(title)
msgid "IPC and Networking"
msgstr ""

#: C/platform.xml:54(para)
msgid ""
"The GNOME desktop has full support for transferring data using the clipboard "
"or with drag and drop. The APIs in GTK+ can help you create applications "
"that interoperate well with the rest of the desktop. Clipboard and drag and "
"drop functionality are discussed in <xref linkend=\"clipboard\"/>."
msgstr ""

#: C/platform.xml:60(para)
msgid ""
"With <ulink url=\"http://www.freedesktop.org/\">freedesktop.org</ulink>, "
"GNOME provides the D-Bus messaging system. D-Bus is a cross-desktop message "
"bus which allows all types of applications to communicate with one another. "
"D-Bus is discussed in <xref linkend=\"dbus\"/>."
msgstr ""

#: C/platform.xml:65(para)
msgid ""
"GNOME features the Bonobo component system, built on top of CORBA. Bonobo "
"allows programmers to create complex embeddable components which can be "
"reused inside other programs. Bonobo is discussed in <xref linkend=\"bonobo-"
"corba\"/>."
msgstr ""

#: C/platform.xml:70(para)
msgid ""
"To make networks more manageable for users, GNOME supports DNS Service "
"Discovery. DNS Service Discovery enables applications to find services "
"automatically on a local network, rather than requiring users to provide "
"network addresses. DNS Service Discovery is discussed in <xref linkend=\"dns-"
"sd\"/>."
msgstr ""

#: C/platform.xml:76(para)
msgid ""
"Finally, GNOME provides a number of libraries for working with XML and web "
"services. These technologies are becoming increasingly important to "
"application developers. XML and web services are discussed in <xref linkend="
"\"xml-web-services\"/>."
msgstr ""

#: C/platform.xml:83(title) C/desktop-tech.xml:4(title)
msgid "Desktop Technologies"
msgstr ""

#: C/platform.xml:85(para)
msgid ""
"The GNOME desktop features numerous places where applications can provide "
"better integration, such as providing panel applets or plugins for the file "
"manager. Many of these features are discussed in <xref linkend=\"desktop-tech"
"\"/>."
msgstr ""

#: C/platform.xml:90(para)
msgid ""
"GNOME provides comprehensive Human Interface Guidelines to help you create "
"more usable applications. GNOME's usability standards were a first among "
"free desktop environments, and they continue to improve through GNOME's "
"commitment to a better user experience. Usability is discussed in <xref "
"linkend=\"usability\"/>."
msgstr ""

#: C/platform.xml:96(para)
msgid ""
"GNOME also provides a complete help system, as well as style guidelines for "
"writing documentation. Though often under-appreciated, good user help can "
"significantly improve your software. Documentation is discussed in <xref "
"linkend=\"documentation\"/>."
msgstr ""

#: C/legal-fdl.xml:2(para)
msgid ""
"Permission is granted to copy, distribute and/or modify this document under "
"the terms of the GNU Free Documentation License (GFDL), Version 1.1 or any "
"later version published by the Free Software Foundation with no Invariant "
"Sections, no Front-Cover Texts, and no Back-Cover Texts. You can find a copy "
"of the GFDL at this <ulink url=\"ghelp:fdl\">link</ulink> or in the file "
"COPYING-DOCS distributed with this manual."
msgstr ""

#: C/legal-fdl.xml:11(para)
msgid ""
"This manual is part of a collection of GNOME manuals distributed under the "
"GFDL. If you want to distribute this manual separately from the collection, "
"you can do so by adding a copy of the license to the manual, as described in "
"section 6 of the license."
msgstr ""

#: C/legal-fdl.xml:17(para)
msgid ""
"Many of the names used by companies to distinguish their products and "
"services are claimed as trademarks. Where those names appear in any GNOME "
"documentation, and the members of the GNOME Documentation Project are made "
"aware of those trademarks, then the names are in capital letters or initial "
"capital letters."
msgstr ""

#: C/legal-fdl.xml:30(para)
msgid ""
"DOCUMENT IS PROVIDED ON AN \"AS IS\" BASIS, WITHOUT WARRANTY OF ANY KIND, "
"EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT "
"THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT IS FREE OF DEFECTS "
"MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE "
"RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR "
"MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR "
"MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL "
"WRITER, AUTHOR OR ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY "
"SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN "
"ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION "
"OF THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER; AND"
msgstr ""

#: C/legal-fdl.xml:47(para)
msgid ""
"UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER IN TORT (INCLUDING "
"NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY "
"CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION OF THE "
"DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON "
"FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF "
"ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, "
"WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER DAMAGES "
"OR LOSSES ARISING OUT OF OR RELATING TO USE OF THE DOCUMENT AND MODIFIED "
"VERSIONS OF THE DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE "
"POSSIBILITY OF SUCH DAMAGES."
msgstr ""

#: C/legal-fdl.xml:24(para)
msgid ""
"DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED UNDER THE TERMS "
"OF THE GNU FREE DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING THAT: "
"<placeholder-1/>"
msgstr ""

#: C/ipc-network.xml:7(title)
msgid "Clipboards and Drag and Drop"
msgstr ""

#: C/ipc-network.xml:9(para)
msgid ""
"As users work with more and more types of data in different applications, "
"they have an increasing need to share objects and data between their "
"applications. GNOME supports two related methods for transfering data "
"between applications: using drag and drop operations, and copying to and "
"pasting from a system-wide clipboard. Both the clipboard and drag and drop "
"work across multiple applications, including those not developed with GNOME."
msgstr ""

#: C/ipc-network.xml:17(para)
msgid ""
"The clipboard is used when a user explicitly copies data in an application. "
"The application then claims ownership of the clipboard. When the user pastes "
"the data into another application, that application requests the clipboard "
"data from the first application. Clipboard operations are fully supported in "
"GTK+."
msgstr ""

#: C/ipc-network.xml:23(para)
msgid ""
"Drag and drop operations are similar, but they require the pointer to be "
"tracked and updated as the user moves across potential drop targets. When an "
"application is notified a pointer is moving over it during an active drag, "
"it must update the cursor to indicate whether or not it can accept the drop. "
"GTK+ provides drag and drop support with a sophisticated API that makes it "
"easy to manage drop targets in your applications."
msgstr ""

#: C/ipc-network.xml:30(para)
msgid ""
"Both the clipboard and drag and drop operations support content negotation. "
"When an application has data to offer, it advertises which formats are "
"available for that data. Receiving applications can request the most "
"suitable formats. For instance, if a user copies text from a web browser, a "
"word processor can maintain formatting by requesting the data in HTML, while "
"a plain text editor can receive the text without formatting."
msgstr ""

#: C/ipc-network.xml:38(para)
msgid ""
"You should provide clipboard and drag and drop functionality for any data "
"your application operates on. The clipboard and drag and drop are useful for "
"more than just text: files, graphics, and sound clips are all examples of "
"data that can be transferred between applications. When you use GTK+, you "
"automatically get clipboard and drag and drop support for text areas, color "
"buttons, file choosers, and other built-in user interface controls. You "
"should use the APIs in GTK+ to provide support for any other data in your "
"application."
msgstr ""

#: C/ipc-network.xml:47(para)
msgid ""
"For more information, see <ulink url=\"http://www.newplanetsoftware.com/xdnd/"
"\">Drag-and-Drop Protocol for the X Window System</ulink>, <ulink url="
"\"http://www.freedesktop.org/wiki/Standards/clipboards_2dspec\">X Clipboard "
"Explanation</ulink>, and <ulink url=\"http://www.freedesktop.org/wiki/"
"Standards/clipboard_2dmanager_2dspec\">The Clipboard Manager Specification</"
"ulink>."
msgstr ""

#: C/ipc-network.xml:57(title)
msgid "D-BUS Messaging"
msgstr ""

#: C/ipc-network.xml:59(para)
msgid ""
"D-Bus is a cross-desktop message bus for sending events between various "
"applications, the desktop, and low-level components of the system. D-Bus "
"provides a simple API for sending messages to particular services and for "
"broadcasting messages to all interested services. D-Bus enables different "
"types of applications to communicate and integrate with each other and with "
"the desktop, providing better interaction and a richer experience for the "
"user."
msgstr ""

#: C/ipc-network.xml:67(para)
msgid ""
"D-Bus provides a session and a system bus. The session bus is used by "
"applications in a single user session, allowing them to share data and event "
"notifications and to integrate into the user's desktop. For example, movie "
"players can send a D-Bus message to prevent the screensaver from activating "
"when the user is watching a movie."
msgstr ""

#: C/ipc-network.xml:73(para)
msgid ""
"The system bus is a single message bus which runs independently of any user "
"sessions. It can communicate with applications in any session, enabling "
"those applications to interact with system components without dealing with "
"low-level system details. The system bus is used to provide important "
"functionality that users expect to work on their systems. For example, the "
"system bus is used to monitor when network interfaces go up or down, when "
"external drives get plugged in, and when laptop batteries are low."
msgstr ""

#: C/ipc-network.xml:82(para)
msgid ""
"D-Bus is developed jointly on <ulink url=\"http://www.freedesktop.org/"
"\">freedesktop.org</ulink>, so you can use it with different desktop "
"environments and applications. Because D-Bus is a cross-desktop project, you "
"use it to create portable and versatile software that seamlessly integrates "
"with the user's desktop, regardless of which desktop it is."
msgstr ""

#: C/ipc-network.xml:89(para)
msgid ""
"For more information on D-Bus, see <ulink url=\"http://dbus.freedesktop.org/"
"doc/dbus-tutorial.html\">The D-BUS Tutorial</ulink> and <ulink url=\"http://"
"dbus.freedesktop.org/doc/dbus-specification.html\">The D-BUS Specification</"
"ulink>."
msgstr ""

#: C/ipc-network.xml:97(title)
msgid "Bonobo and CORBA"
msgstr "Bonobo e CORBA"

#: C/ipc-network.xml:99(para)
msgid ""
"Bonobo is a framework for creating reusable components for use in "
"applications. Built on top of the industry-standard Common Object Request "
"Broker Architecture (CORBA), Bonobo provides all the common interfaces "
"needed to create and use well-behaved components in GNOME applications."
msgstr ""

#: C/ipc-network.xml:105(para)
msgid ""
"Bonobo components can be used in a variety of situations, and can help "
"create flexible and extensible software. For example, a component to display "
"multimedia content could be embedded inside a word processor, effectively "
"adding multimedia support to the word processor without the word processor "
"working directly with it. Bonobo components are also used to embed the "
"applets in the GNOME panel. Using Bonobo enables the applets to communicate "
"effectively with the panel, affording users a consistent interface."
msgstr ""

#: C/ipc-network.xml:114(para)
msgid ""
"Bonobo components are not limited to graphical controls. Bonobo is used by "
"Evolution, GNOME's email and groupware suite, to provide access to users' "
"addressbook and calendar. This allows users to keep all their information in "
"one place, where all applications can access it."
msgstr ""

#: C/ipc-network.xml:119(para)
msgid ""
"Bonobo is built off of CORBA, allowing components to run in seperate "
"processes. Components can be written in different languages and run on top "
"of different runtimes; they need only adhere to an interface specified with "
"the Interface Definition Language (IDL). CORBA's flexible design even allows "
"components to run on seperate machines over a network."
msgstr ""

#: C/ipc-network.xml:125(para)
msgid ""
"GNOME provides its own fast and lightweight CORBA implementation with ORBit. "
"The tools and libraries supplied with GNOME even allow components to be "
"written effectively in C, a language often excluded by other CORBA "
"implementations. ORBit is an incredibly fast CORBA implementation."
msgstr ""

#: C/ipc-network.xml:130(para)
msgid ""
"Bonobo helps fill the gaps in CORBA, providing the additional interfaces and "
"specifications needed to support consistent components. Although you will "
"rarely need to use CORBA without Bonobo, it can be used directly. For "
"instance, GNOME's accessibility infastructure uses CORBA to allow assistive "
"tools to inspect and interact with running applications."
msgstr ""

#: C/ipc-network.xml:137(para)
msgid ""
"You may wish to use Bonobo to provide complex graphical components that can "
"be embedded into applications. For most IPC needs, however, GNOME is moving "
"towards D-Bus, as integrating D-Bus into applications is considerably easier."
msgstr ""

#: C/ipc-network.xml:142(para)
msgid ""
"For more information on Bonobo, see <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/libbonobo/index.html\">The Libbonobo Reference Manual</ulink> "
"and <ulink url=\"http://developer.gnome.org/doc/API/2.0/libbonoboui/index."
"html\">The LibbonoboUI Reference Manual</ulink>. For information on ORBit, "
"GNOME's CORBA implementation, see <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/ORBit/index.html\">The ORBit2 Reference Manual</ulink>."
msgstr ""

#: C/ipc-network.xml:153(title)
msgid "Service Discovery"
msgstr ""

#: C/ipc-network.xml:155(para)
msgid ""
"DNS Service Discovery, or Zeroconf, is a technology for automatically "
"locating available services on a network. Zeroconf allows users to access "
"network resources without having to provide explicit addresses or configure "
"their applications manually."
msgstr ""

#: C/ipc-network.xml:160(para)
msgid ""
"DNS Service Discovery is already used in numerous places throughout GNOME, "
"and further support will be added in the future. For example, "
"<application>Nautilus</application>, the GNOME file manager, uses DNS "
"Service Discovery to locate various file servers on the local network. "
"<application>Ekiga</application>, the videoconferencing and telephony "
"application in GNOME, can locate and publish the user's presence and locate "
"other users on a local network using DNS Service Discovery."
msgstr ""

#: C/ipc-network.xml:168(para)
msgid ""
"Full DNS Service Discovery support is provided by the Avahi library. For "
"more information on Avahi, visit <ulink url=\"http://avahi.org/\">the Avahi "
"web site</ulink>. GNOME also provides limited support for locating services "
"in GnomeVFS. For more information, see <ulink url=\"http://developer.gnome."
"org/doc/API/2.0/gnome-vfs-2.0/gnome-vfs-20-gnome-vfs-dns-sd.html\">Zeroconf "
"networking support</ulink>."
msgstr ""

#: C/ipc-network.xml:177(title)
msgid "XML and Web Services"
msgstr ""

#: C/ipc-network.xml:179(para)
msgid ""
"In our increasingly inter-connected world, more and more applications need "
"to provide support for various web services. Sometimes web services simply "
"provide added functionality, while other times they are the core purpose of "
"the application. Even applications that have been providing a standalone "
"user experience for years have found innovative new uses for web services."
msgstr ""

#: C/ipc-network.xml:186(para)
msgid ""
"The GNOME Platform provides support for using web services from within your "
"application, as well as comprehensive libraries for consuming, managing, and "
"transforming XML, the language of the web."
msgstr ""

#: C/ipc-network.xml:191(title)
msgid "SOAP"
msgstr "SOAP"

#: C/ipc-network.xml:193(para)
msgid ""
"With the libsoup library, GNOME provides support for the SOAP, a widely-used "
"protocol for passing XML messages over HTTP. SOAP allows developers to "
"expose an interface over the web, which can then be used by applications to "
"retrieve information, send data, make transactions, or use any number of "
"other services provided."
msgstr ""

#: C/ipc-network.xml:199(para)
msgid ""
"SOAP can be used to search and retrieve information, to interact with an "
"online store, to manage users' accounts on other systems, or for many other "
"purposes. Web services are being used more and more to provide essential "
"functionality for users, and applications using SOAP can provide a more "
"integrated and featureful user experience."
msgstr ""

#: C/ipc-network.xml:205(para)
msgid ""
"The libsoup library contains an HTTP implementation and a set of API for "
"constructing and consuming SOAP messages. It also allows for secure "
"authentication, so you can use web services to access private accounts over "
"a secure connection. Using libsoup makes it easy to use web services without "
"manually parsing and interpreting the messages sent through SOAP."
msgstr ""

#: C/ipc-network.xml:212(para)
msgid ""
"For more information on libsoup, see <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/libsoup/index.html\">The libsoup Reference Manual</ulink>."
msgstr ""

#: C/ipc-network.xml:218(title)
msgid "XML Processing"
msgstr ""

#: C/ipc-network.xml:220(para)
msgid ""
"Since its formal introduction in 1998, XML (eXtensible Markup Langauge) has "
"been used in increasingly more applications. It is used for a wide variety "
"of purposes, from document formats like XHMTL and DocBook to internet "
"protocols like SOAP and Jabber. XML provides a clean and simple base syntax, "
"allowing applications to focus on their particular needs."
msgstr ""

#: C/ipc-network.xml:227(para)
msgid ""
"GNOME ships with the libxml2 library, and uses it extensively throughout the "
"desktop. The libxml2 library is a fast and fully standards-compliant XML "
"processing library, providing everything you need to use XML in your "
"application."
msgstr ""

#: C/ipc-network.xml:232(para)
msgid ""
"The libxml2 library provides a number of different APIs for working with "
"XML, so you can use whatever best suits your application development needs. "
"In addition to a native tree API, libxml2 also provides the callback-based "
"SAX2 API, streaming XML reader and writer interfaces, and complete support "
"for XPath."
msgstr ""

#: C/ipc-network.xml:238(para)
msgid ""
"In addition to DTD support, libxml2 also provides full support for validing "
"documents using RELAX NG, which allows a more flexible validation model "
"while remaining simple to use. There is also partial support for XML Schema, "
"the new schema language produced by W3C."
msgstr ""

#: C/ipc-network.xml:243(para)
msgid ""
"You should use libxml2 whenever you need to work directly with XML in your "
"application. Using libxml2 ensures that you have fully standards-compliant "
"parsing, processing, and XML output. This means developers can stop worrying "
"about incompatibilities between applications."
msgstr ""

#: C/ipc-network.xml:249(para)
msgid ""
"For more information on libxml2, see <ulink url=\"http://xmlsoft.org/"
"tutorial/index.html\">The Libxml Tutorial</ulink> and <ulink url=\"http://"
"xmlsoft.org/html/libxml-lib.html\">The Reference Manual for libxml2</ulink>."
msgstr ""

#: C/ipc-network.xml:256(title)
msgid "Transforming XML with XSLT"
msgstr ""

#: C/ipc-network.xml:258(para)
msgid ""
"XSLT is an XML-based language for transforming XML into other formats. XSLT "
"is a template-based language, allowing you to match particular types of XML "
"elements and create output accordingly. Based on XML and XPath, XSLT enables "
"developers to create clean and modularized templates to convert an XML "
"dialect into another format more suitable for the application."
msgstr ""

#: C/ipc-network.xml:265(para)
msgid ""
"GNOME ships with the libxslt library, a complete implementation of XSLT. The "
"libxslt library is built on top of the XML and XPath support in libxml2, "
"allowing it to be fast and fully standards-compliant."
msgstr ""

#: C/ipc-network.xml:269(para)
msgid ""
"You should use libxslt if you need to transform XML documents. Although XSLT "
"is not always the right solution for XML processing, it can often simplify "
"development. Since libxslt allows you to add extension elements and "
"extension functions, you can customize it to fit your application."
msgstr ""

#: C/ipc-network.xml:275(para)
msgid ""
"For more information on libxslt, see <ulink url=\"http://xmlsoft.org/XSLT/"
"html/index.html\">The XSLT C library for Gnome</ulink>."
msgstr ""

#: C/intro.xml:4(title)
msgid "Introduction"
msgstr "Introduccion"

#: C/intro.xml:6(para)
msgid ""
"GNOME is a powerful but simple desktop environment with a strong focus on "
"usability, accessibility, and internationalization. GNOME is designed to be "
"usable by everybody, regardless of technical expertise, disabilitites, or "
"native language. GNOME makes it easy for people to use their computers."
msgstr ""

#: C/intro.xml:11(para)
msgid ""
"GNOME provides a comprehensive developer platform that allow developers to "
"create professional software that is easy to use and aesthetically pleasing. "
"This document provides a high-level overview of the GNOME platform along "
"with links to detailed documentation on each part of the platform."
msgstr ""

#: C/intro.xml:17(title)
msgid "Who Should Read This Document"
msgstr ""

#: C/intro.xml:19(para)
msgid ""
"You should read this document if you want to create software using the GNOME "
"platform. Developing with the GNOME platform will help you create consistent "
"applications that integrate well into the user's desktop. This guide will "
"introduce you to the various components of the platform, so you know which "
"libraries can accomplish which tasks. This guide links to additional "
"detailed documentation, so you can explore each component of the platform in "
"more depth."
msgstr ""

#: C/intro.xml:27(para)
msgid ""
"This guide will also be useful if you are picking a development platform for "
"your software project. It will provide an overview how you can use the GNOME "
"platform to build useful software."
msgstr ""

#: C/intro.xml:31(para)
msgid ""
"This guide also describes ways of extending the GNOME desktop with plugins, "
"panel applets, and other useful tools. If you want to develop additional "
"functionality to plug into the GNOME desktop, you should read this guide, "
"particularly <xref linkend=\"desktop-tech\"/>."
msgstr ""

#: C/intro.xml:36(para)
msgid ""
"If you have existing software that you want to port to the GNOME platform, "
"you should see the online <ulink url=\"http://live.gnome.org/GuideForISVs"
"\">Guide For ISVs</ulink> in addition to this guide."
msgstr ""

#: C/intro.xml:43(title)
msgid "The GNOME Family"
msgstr "La familha GNOME"

#: C/intro.xml:45(para)
msgid ""
"GNOME is a global effort, with many contributors all over the world. GNOME "
"is a success because of its contributors and users. This section lists the "
"web sites and conferences where you can learn more about GNOME, as well as "
"other organizations that work with GNOME."
msgstr ""

#: C/intro.xml:51(title)
msgid "Web Sites"
msgstr "Sits web"

#: C/intro.xml:53(ulink)
msgid "www.gnome.org"
msgstr "www.gnome.org"

#: C/intro.xml:54(para)
msgid ""
"The primary web site for GNOME users. It contains release information, "
"downloads, and documentation."
msgstr ""

#: C/intro.xml:58(ulink)
msgid "developer.gnome.org"
msgstr ""

#: C/intro.xml:59(para)
msgid ""
"The primary web site for people developing using the GNOME platform, as well "
"as core GNOME developers. It contains all the developer documentation, as "
"well as further information on the usability, documentation, and "
"translations teams."
msgstr ""

#: C/intro.xml:65(ulink)
msgid "foundation.gnome.org"
msgstr "foundation.gnome.org"

#: C/intro.xml:66(para)
msgid ""
"The web site for the GNOME Foundation, the not-for-profit foundation that "
"oversees the development of GNOME."
msgstr ""

#: C/intro.xml:70(ulink)
msgid "bugzilla.gnome.org"
msgstr "bugzilla.gnome.org"

#: C/intro.xml:71(para)
msgid ""
"The GNOME bug trackers. Use this site to submit a bug report or feature "
"request, or to track the status of a report."
msgstr ""

#: C/intro.xml:75(ulink)
msgid "live.gnome.org"
msgstr "live.gnome.org"

#: C/intro.xml:76(para)
msgid ""
"The GNOME wiki. Many projects within GNOME now use the wiki as their primary "
"web space. In additional, the wiki is often used to sketch out future "
"development."
msgstr ""

#: C/intro.xml:81(ulink)
msgid "mail.gnome.org"
msgstr "mail.gnome.org"

#: C/intro.xml:82(para)
msgid ""
"Information on GNOME mailing lists. This site contains full archives of all "
"GNOME mailing lists."
msgstr ""

#: C/intro.xml:86(ulink)
msgid "cvs.gnome.org"
msgstr "cvs.gnome.org"

#: C/intro.xml:87(para)
msgid ""
"The GNOME CVS repository, tracking all GNOME source code back to the "
"inception of the project."
msgstr ""

#: C/intro.xml:93(title)
msgid "Mailing Lists"
msgstr ""

#: C/intro.xml:96(ulink)
msgid "gnome-list"
msgstr "gnome-list"

#: C/intro.xml:97(para)
msgid "The primary mailing list for GNOME users."
msgstr ""

#: C/intro.xml:101(ulink)
msgid "gnome-devel-list"
msgstr "gnome-devel-list"

#: C/intro.xml:102(para)
msgid "Information and questions about development using the GNOME platform."
msgstr ""

#: C/intro.xml:107(ulink)
msgid "gnome-love"
msgstr "gnome-love"

#: C/intro.xml:108(para)
msgid "The first place to go to get involved with GNOME."
msgstr ""

#: C/intro.xml:112(ulink)
msgid "gnome-accessibility-list"
msgstr "gnome-accessibility-list"

#: C/intro.xml:113(para)
msgid "Information on accessibility in GNOME applications."
msgstr ""

#: C/intro.xml:117(ulink)
msgid "gnome-doc-list"
msgstr "gnome-doc-list"

#: C/intro.xml:118(para)
msgid "Information on writing documentation for GNOME applications."
msgstr ""

#: C/intro.xml:123(ulink)
msgid "gnome-i18n"
msgstr "gnome-i18n"

#: C/intro.xml:124(para)
msgid ""
"Information about internationalization and localization of GNOME "
"applications."
msgstr ""

#: C/intro.xml:129(ulink)
msgid "usability"
msgstr ""

#: C/intro.xml:130(para)
msgid "Information on usability for GNOME applications."
msgstr ""

#: C/intro.xml:135(title)
msgid "Conferences"
msgstr "Conferéncias"

#: C/intro.xml:137(ulink)
msgid "GUADEC"
msgstr "GUADEC"

#: C/intro.xml:138(para)
msgid ""
"The primary conference for GNOME users and developers. GUADEC is hosted "
"annually in May or June. Each year, it is hosted in a different European "
"city, making it an excellent excuse to see more of Europe. GUADEC features "
"talks aimed at users, developers, and vendors."
msgstr ""

#: C/intro.xml:145(term)
msgid "The GNOME Summit"
msgstr ""

#: C/intro.xml:146(para)
msgid ""
"The hacker get-together. The Summit is geared primarily at existing GNOME "
"developers, although there is often useful information for new developers. "
"The Summit is hosted annually in Boston."
msgstr ""

#: C/intro.xml:152(term)
msgid "GNOME.conf.au"
msgstr "GNOME.conf.au"

#: C/intro.xml:153(para)
msgid "A casual get-together hosted annually at linux.conf.au."
msgstr ""

#: C/intro.xml:160(title)
msgid "Other Organizations"
msgstr "Autras organizacions"

#: C/intro.xml:162(ulink)
msgid "freedesktop.org"
msgstr "freedesktop.org"

#: C/intro.xml:163(para)
msgid ""
"The collaborative effort for interoperability and shared technology among "
"desktop environments. Through freedesktop.org, GNOME works with projects "
"such as KDE and XFCE to make it easier for application developers to provide "
"better experiences for their users."
msgstr ""

#: C/intro.xml:169(ulink)
msgid "Mozilla"
msgstr "Mozilla"

#: C/intro.xml:170(para)
msgid ""
"The free web engine, and a whole lot more. GNOME maintains close ties to the "
"Mozilla development team to provide an overall better user interface."
msgstr ""

#: C/intro.xml:175(ulink)
msgid "OpenOffice.org"
msgstr "OpenOffice.org"

#: C/intro.xml:176(para)
msgid ""
"The free office suite. GNOME works with the OpenOffice.org development team "
"to help provide a more unified interface when using the free office suite on "
"GNOME."
msgstr ""

#: C/intro.xml:181(ulink)
msgid "Free Software Foundation"
msgstr ""

#: C/intro.xml:182(para)
msgid ""
"Freedom. Established in 1985, the Free Software Foundation has worked to "
"create a complete free operating systems, giving its users the freedom to "
"use, modify, and redistribute their software. As part of the GNU project, "
"GNOME aims to provide a fully free desktop environment."
msgstr ""

#: C/desktop-tech.xml:7(title)
msgid "Application and File Type Registries"
msgstr ""

#: C/desktop-tech.xml:8(para)
msgid ""
"In order for applications to be useful, users need to be able to find and "
"run them. Users of the GNOME desktop may run applications using the "
"applications menu, or they may run them by accessing files in the file "
"manager. The GNOME desktop allows you to add applications and file types "
"when you install your application. The mechanism for these is specified on "
"<ulink url=\"http://www.freedesktop.org/\">freedesktop.org</ulink>, so the "
"same data will allow your application to function in other desktop "
"environments."
msgstr ""

#: C/desktop-tech.xml:17(para)
msgid ""
"Adding your application is as simple as providing a desktop entry file with "
"the necessary information. Desktop entry files use a simple key-value "
"syntax, with extra provisions for providing translated content of particular "
"values. Your application's desktop entry file will contain the following "
"information:"
msgstr ""

#: C/desktop-tech.xml:24(para)
msgid ""
"A name and a comment, each translated into as many languages as your "
"application supports,"
msgstr ""

#: C/desktop-tech.xml:26(para)
msgid ""
"A list of categories from a fixed list, which are used to place your "
"application in the applications menu,"
msgstr ""

#: C/desktop-tech.xml:28(para)
msgid ""
"An icon, either as a full file path or as a simple name for the icon theme "
"system,"
msgstr ""

#: C/desktop-tech.xml:30(para)
msgid "A list of file types that your application supports, and"
msgstr ""

#: C/desktop-tech.xml:32(para)
msgid "The command to run your application."
msgstr ""

#: C/desktop-tech.xml:35(para)
msgid ""
"If your application handles custom file types that are not already known by "
"the system, you will need to add those types to the file type registry. All "
"file types are accessed with MIME types. For example, Ogg Vorbis audio files "
"have the MIME type <literal>application/ogg</literal>. To add a MIME type, "
"you need to provide a description of the type using a MIME information XML "
"file. These files provide a translated name for the type as well as "
"information on how to determine which files are of the type, either by "
"matching the file name or by inspecting the contents of the file."
msgstr ""

#: C/desktop-tech.xml:45(para)
msgid ""
"For more information on applications, see <ulink url=\"http://www."
"freedesktop.org/wiki/Standards/desktop_2dentry_2dspec\">The Desktop Entry "
"Specification</ulink> and <ulink url=\"http://www.freedesktop.org/wiki/"
"Standards/menu_2dspec\">The Desktop Menu Specification</ulink>. For more "
"information on file types, see <ulink url=\"http://www.freedesktop.org/wiki/"
"Standards/shared_2dmime_2dinfo_2dspec\">The Shared MIME Info Specification</"
"ulink>."
msgstr ""

#: C/desktop-tech.xml:56(title)
msgid "Panel Applets"
msgstr "Aplets del panèl"

#: C/desktop-tech.xml:57(para)
msgid ""
"The GNOME desktop features flexible and powerful panels to which users can "
"add any number of small applications, called panel applets. Panel applets "
"can provide all sorts of quick access to all sorts of useful information and "
"functionality. For instance, the GNOME desktop ships with panel applets to "
"switch between windows and workspaces, display the current weather "
"conditions, and display network activity, among many others."
msgstr ""

#: C/desktop-tech.xml:64(para)
msgid ""
"You may provide a panel applet to augment the functionality of your "
"application, or you may provide a simple stand-alone panel applet. If you "
"simply need to display quick notifications, you should consider using the "
"notification area instead, which is also displayed in the user's panel. "
"Panel applets should be used when you need to provide more functionality "
"than that provided by notification icons."
msgstr ""

#: C/desktop-tech.xml:71(para)
msgid ""
"Panel applets are independent processes that use Bonobo to communicate with "
"the panel. Bonobo allows applets to integrate with the panel to provide a "
"consistent user experience. For example, the context menu for every panel "
"applet contains standard items to remove, move, and lock the applet. Each "
"panel applet can then add items to the context menu to perform other "
"actions. The <application>Weather Report</application> panel applet, for "
"example, has context menu items to display a detailed report and to update "
"the displayed information."
msgstr ""

#: C/desktop-tech.xml:80(para)
msgid ""
"For more information on panel applets, see <ulink url=\"http://developer."
"gnome.org/doc/API/2.0/panel-applet/index.html\">The Panel Applet Library</"
"ulink>."
msgstr ""

#: C/desktop-tech.xml:86(title)
msgid "Notification Area"
msgstr "Zòna de notificacion"

#: C/desktop-tech.xml:87(para)
msgid ""
"In addition to launchers and panel applets, the GNOME panel also features a "
"notification area that applications can use to notify users of events. "
"Notifications can be used to alert the user of new emails, available "
"updates, upcoming meetings, or any number of other events."
msgstr ""

#: C/desktop-tech.xml:92(para)
msgid ""
"Notifications are simple icons that your application can place in the "
"notification area on the user's panel. Your application can then take "
"further action when the user clicks on the icon. Currently, the notification "
"system is implemented in the experimental Egg library; however, the next "
"version of GTK+ will have support for notification icons."
msgstr ""

#: C/desktop-tech.xml:99(para)
msgid ""
"The notification area is a <ulink url=\"http://www.freedesktop.org/"
"\">freedesktop.org</ulink> specification, so your notification icons will "
"appear in other desktop environments as well. For more information on the "
"notification area, see <ulink url=\"http://freedesktop.org/wiki/Standards/"
"systemtray_2dspec\">The System Tray Protocol Specification</ulink>."
msgstr ""

#: C/desktop-tech.xml:108(title)
msgid "File Manager"
msgstr "Gestionari de fichièrs"

#: C/desktop-tech.xml:110(para)
msgid ""
"GNOME ships with <application>Nautilus</application>, an intuitive and "
"powerful file manager. Using the advanced GnomeVFS technology, "
"<application>Nautilus</application> is able to display remote folders just "
"like folders on the local file system, giving users access to all their "
"files everywhere with a single consistent interface."
msgstr ""

#: C/desktop-tech.xml:116(para)
msgid ""
"<application>Nautilus</application> provides a plugin interface, enabling "
"developers to extend its functionality to provide more information about "
"users' files. This provides a richer and more coherant experience for users, "
"removing the need for seperate applications to manage various types of files."
msgstr ""

#: C/desktop-tech.xml:122(para)
msgid ""
"<application>Nautilus</application> plugins can extend the file manager's "
"functionality in a number of ways. Plugins can add extra information to file "
"properties dialogs, providing users with everything they need to know about "
"files. For example, GNOME ships with a plugin to display extra information "
"about audio and video files, such as the codec used, the dimensions of the "
"video, and artist and album of music files extracted from a CD."
msgstr ""

#: C/desktop-tech.xml:130(para)
msgid ""
"Plugins can also add columns to the list view and automatically place "
"emblems on files. This can be used to provide pertinent information to the "
"user at a glance. For example, a <application>Nautilus</application> plugin "
"could provide version control information on folders checked out from a "
"version control system. Users could see directly in the file manager if a "
"file is up to date, or if changes have been made locally."
msgstr ""

#: C/desktop-tech.xml:137(para)
msgid ""
"<application>Nautilus</application> also allows developers to add items to "
"the context menu for files and folders. Context menu items can specify for "
"which types of files they should be displayed, so the context menu only "
"provides actions that are relevent for the selected files. For example, "
"<application>File Roller</application>, GNOME's archive file utility, adds "
"an item to the context menu to extract archive files directly. Extra context "
"menu items provide easy access to common operations on different types of "
"files."
msgstr ""

#: C/desktop-tech.xml:146(para)
msgid ""
"In addition to a flexible plugin architecture, <application>Nautilus</"
"application> can also display a thumbnail for any type of file for which a "
"thumbnailer has been provided. Thumbnails show a preview of the file, "
"helping users find the files they want. GNOME can automatically create "
"thumbnails for most image and movie files, and allows applications to "
"install additional thumbnailer programs to create thumbnails for application-"
"specific files. Thumbnail management is fully specified by <ulink url="
"\"http://www.freedesktop.org/\">freedesktop.org</ulink>, so any thumbnailers "
"you provide can be used by all applications."
msgstr ""

#: C/desktop-tech.xml:158(title)
msgid "Window Manager"
msgstr "Gestionari de fenèstras"

#: C/desktop-tech.xml:160(para)
msgid ""
"The window manager is a special program responsible for drawing the borders "
"and titlebars around windows. The window manager is responsible for handling "
"all the operations performed on windows, such as moving, resizing, "
"minimizing, and moving between workspaces. Windows are managed consistently "
"with little or no work from application developers. When applications need "
"to influence the window manager, they can provide hints on their windows "
"using function calls in GTK+."
msgstr ""

#: C/desktop-tech.xml:168(para)
msgid ""
"External programs can, however, interact directly with the window manager, "
"and even control its behavior. Using GNOME's libwnck library, applications "
"can get information about the placement and state of all the windows and "
"instruct the window manager to perform various actions on those windows."
msgstr ""

#: C/desktop-tech.xml:174(para)
msgid ""
"The libwnck library isn't specific to GNOME's window manager. All of its "
"functionality uses the Extended Window Manager Hints, or EWMH. EWMH was "
"developed jointly with <ulink url=\"http://www.freedesktop.org\">freedesktop."
"org</ulink> to provide unified window manager interaction across multiple "
"desktops."
msgstr ""

#: C/desktop-tech.xml:180(para)
msgid ""
"Window manager interaction with libwnck can be used for simple tasks, such "
"as displaying workspace and window list applets on the user's panel, as well "
"as for complex applications, such as performing automatic actions on new "
"windows based on certain window properties."
msgstr ""

#: C/desktop-tech.xml:187(title)
msgid "Control Center"
msgstr ""

#: C/desktop-tech.xml:188(para)
msgid ""
"The GNOME desktop provides a single menu of all the desktop-wide preferences "
"and system administration settings. Preferences and settings dialogs can be "
"placed in this menu to make them easily accessible. Dialogs can be placed in "
"the preferences menu by adding them to the applications registry with the "
"<literal>Setting</literal> category. Dialogs can be placed in the "
"administraion menu using both the <literal>Settings</literal> and "
"<literal>System</literal> categories."
msgstr ""

#: C/desktop-tech.xml:196(para)
msgid ""
"If you provide a dialog that allows administrators to configure desktop "
"systems, then you should add your dialog to the administration menu. If you "
"provide a dialog that allows users to adjust preferences that affect a "
"number of applications, then you should add your dialog to the preferences "
"menu. You should not use these global menus for individual application "
"preferences."
msgstr ""

#: C/desktop-tech.xml:205(title)
msgid "Storing Passwords"
msgstr ""

#: C/desktop-tech.xml:207(para)
msgid ""
"GNOME provides a modern and secure keyring manager to store users' passwords "
"and other sensitive data. Applications can use the keyring manager library "
"to store and access passwords, and users can manage their passwords using "
"GNOME's <application>Keyring Manager</application> application."
msgstr ""

#: C/desktop-tech.xml:213(para)
msgid ""
"The keyring manager provides any number of keyrings, where each keyring can "
"contain any number of keyring items. Items in a keyring store some piece of "
"data, often a password. Each keyring is locked individually, and users must "
"provide a password to unlock the keyring. Once a keyring has been unlocked, "
"the user has access to all of the items in that keyring."
msgstr ""

#: C/desktop-tech.xml:220(para)
msgid ""
"The keyring manager provides access control lists for each keyring item, "
"controlling with applications are allowed access to that item. If an unknown "
"application attempts to access a keyring item, the keyring manager will "
"prompt the user to allow or deny that application access. This helps prevent "
"malicious or poorly-written programs from accessing the user's sensitive "
"data."
msgstr ""

#: C/desktop-tech.xml:227(para)
msgid ""
"Keyring data stored on the file system is encrypted with the AES block "
"cipher, and SHA1 is used for hashes of the item's attributes. Using the "
"attributes hash, the keyring manager is able to look up items requested by "
"applications without ever unlocking the keyring. The keyring has to be "
"unlocked when a matching item is found and accessed."
msgstr ""

#: C/desktop-tech.xml:234(para)
msgid ""
"The keyring manager also provides a session keyring. Items in the session "
"keyring are never stored on disk, and are lost as soon as the user's session "
"ends. The session keyring can be used to store passwords to be used in the "
"current session only."
msgstr ""

#: C/desktop-tech.xml:239(para)
msgid ""
"If you use GnomeVFS to access remote servers, you automatically get the "
"benefits of the keyring manager. Whenever GnomeVFS needs to authenticate the "
"user, it provides the option to store the password, either in the default "
"keyring or in the session keyring."
msgstr ""

#: C/desktop-tech.xml:244(para)
msgid ""
"You should use the keyring manager whenever your application needs to store "
"passwords or other sensitive data for users. Using the keyring manager "
"provides a better user experience while still keeping user data safe and "
"secure."
msgstr ""

#: C/desktop-tech.xml:251(title)
msgid "Session Management"
msgstr ""

#: C/desktop-tech.xml:252(para)
msgid ""
"GNOME provides tools to allow your application to run smoothly from session "
"to session. Users can log out with running applications and have those "
"applications fully restored when they log back in. To provide this "
"functionality, your application must connect to the session manager and save "
"its state when the user logs out."
msgstr ""

#: C/desktop-tech.xml:258(para)
msgid ""
"GNOME provides a simple API for session management in the GNOME User "
"Interface Library. See the section <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/libgnomeui/GnomeClient.html\">GnomeClient</ulink> of <ulink url="
"\"http://developer.gnome.org/doc/API/2.0/libgnomeui/index.html\">The GNOME "
"UI Library Reference Manual</ulink> for more information on working with the "
"GNOME session manager."
msgstr ""

#: C/desktop-tech.xml:268(title)
msgid "Address Book and Calendar"
msgstr "Quasernet d'adreças e calendièr"

#: C/desktop-tech.xml:269(para)
msgid ""
"With Evolution Data Server, GNOME provides a single address book and "
"calendar that all applications can use to store and retrieve information. "
"Using Evolution Data Server means that users no longer have to maintain "
"separate lists of contacts in each application, or manually copy events to "
"their calendar."
msgstr ""

#: C/desktop-tech.xml:275(para)
msgid ""
"People use computers increasingly to interact with their friends and "
"colleagues. Applications such as email programs, instant messengers, and "
"telephony and video conferencing applications are used to communicate with "
"others. These applications often provide contact lists to help users. Using "
"Evolution Data Server, applications can store contact information in a "
"single location, allowing all applications to see all the pertinent data "
"about users' contacts."
msgstr ""

#: C/desktop-tech.xml:283(para)
msgid ""
"Applications can also use Evolution Data Server to store and retrieve "
"appointments on the user's calendar. For example, the clock on the panel "
"shows a simple calendar when clicked. If the user has any appointments "
"scheduled, they are shown alongside the calendar. This makes it easy to see "
"upcoming appointments without opening a full calendar application."
msgstr ""

#: C/desktop-tech.xml:289(para)
msgid ""
"For more information on the address book, see <ulink url=\"http://gnome.org/"
"projects/evolution/developer-doc/libebook/ch01.html\"> Evolution API "
"Reference: libebook</ulink>. For more information on the calendar, see "
"<ulink url=\"http://gnome.org/projects/evolution/developer-doc/libecal/index."
"html\"> Evolution API Reference: libecal</ulink>."
msgstr ""

#: C/desktop-tech.xml:298(title)
msgid "Usability"
msgstr ""

#: C/desktop-tech.xml:299(para)
msgid ""
"The GNOME desktop is designed around usability, and it aims to provide a "
"consistent and simple user experience. People use computers to get work done "
"(or to play!), not to figure out complicated user interface puzzles. When "
"designing your application, you should consider how well users can recognize "
"common user interface paradigms, how quickly they can learn the elements "
"that are unique to your application, and how efficiently they can execute "
"tasks once they've learned them."
msgstr ""

#: C/desktop-tech.xml:307(para)
msgid ""
"GNOME provides comprehensive Human Interface Guidelines to help you write "
"applications that are attractive and usable. While no guidelines can provide "
"a single answer for all usability concerns, understanding the GNOME Human "
"Interface Guidelines can make it easier to create a usable application. For "
"more information, please see <ulink url=\"http://developer.gnome.org/"
"projects/gup/hig/2.0/\">The GNOME Human Interface Guidelines</ulink>."
msgstr ""

#: C/desktop-tech.xml:317(title)
msgid "Documentation"
msgstr "Documentacion"

#: C/desktop-tech.xml:318(para)
msgid ""
"All applications should provide documentation to help their users understand "
"the application and troubleshoot problems that may arise. While a well-"
"designed application should not require reading the documentation before "
"use, documentation can nonetheless be an important tool for users, "
"particularly for complex applications."
msgstr ""

#: C/desktop-tech.xml:324(para)
msgid ""
"GNOME provides a unified framework for providing user documentation. You can "
"provide documentation in the industry-standard DocBook format. Using DocBook "
"means that you don't have to worry about formatting details. Instead, your "
"documentation will be automatically formatted with the same consistent "
"conventions as the rest of the system documentation."
msgstr ""

#: C/desktop-tech.xml:330(para)
msgid ""
"GNOME's help viewer, <application>Yelp</application>, displays and prints "
"documentation, provides a listing of all documentation on the system, and "
"allows the user to search the full text of all documentation. Using the "
"GNOME help system gives you all these features for free."
msgstr ""

#: C/desktop-tech.xml:335(para)
msgid ""
"For more information on writing documentation for your application, see "
"<ulink url=\"http://developer.gnome.org/projects/gdp/handbook/gdp-handbook/"
"\">The GNOME Handbook of Writing Software Documentation</ulink>, <ulink url="
"\"http://www.docbook.org/tdg/en/html/docbook.html\">DocBook: The Definitive "
"Guide</ulink>, and <ulink url=\"http://developer.gnome.org/documents/style-"
"guide/\">The GNOME Documentation Style Guide</ulink>."
msgstr ""

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: C/core-tech.xml:24(None)
msgid "@@image: 'figures/graphics.png'; md5=15da13eed39abd52d7cf7e56d01154ba"
msgstr "@@image: 'figures/graphics.png'; md5=15da13eed39abd52d7cf7e56d01154ba"

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: C/core-tech.xml:114(None)
msgid "@@image: 'figures/pango.png'; md5=e308eb839e5e70aea097a4cfe744e44c"
msgstr "@@image: 'figures/pango.png'; md5=e308eb839e5e70aea097a4cfe744e44c"

#. When image changes, this message will be marked fuzzy or untranslated for you.
#. It doesn't matter what you translate it to: it's not used at all.
#: C/core-tech.xml:359(None)
msgid "@@image: 'figures/i18n.png'; md5=75f5d47d566817d32f1ed76e4c761ffb"
msgstr "@@image: 'figures/i18n.png'; md5=75f5d47d566817d32f1ed76e4c761ffb"

#: C/core-tech.xml:7(title)
msgid "Graphical Interfaces"
msgstr ""

#: C/core-tech.xml:9(para)
msgid ""
"Most applications will need to provide a graphical interface to interact "
"with users. Graphical interfaces can create an intuitive and discoverable "
"medium for people to interact with software, and users expect applications "
"to provide usable and attractive user interfaces."
msgstr ""

#: C/core-tech.xml:14(para)
msgid ""
"The GNOME Platform features sophisticated graphics and user interface "
"technology, from standard user interface controls to an API for drawing high-"
"quality graphics to the screen. Using the graphics technologies in GNOME "
"allows you to create applications that are consistent, intuitive, and "
"aesthetically pleasing."
msgstr ""

#: C/core-tech.xml:21(title)
msgid "Layered Look at Graphics Libraries"
msgstr ""

#: C/core-tech.xml:30(title)
msgid "GTK+"
msgstr "GTK+"

#: C/core-tech.xml:32(para)
msgid ""
"GTK+ is the primary library used to construct user interfaces in GNOME. It "
"provides all the user interface controls, or widgets, used in a common "
"graphical application. Its modern, object-oriented API allows you to "
"construct attractive and sophisticated user interfaces without dealing with "
"the low-level details of drawing and device interaction."
msgstr ""

#: C/core-tech.xml:39(para)
msgid ""
"In addition to basic widgets, such as buttons, check boxes, and text "
"entries, GTK+ also provides powerful Model-View-Controller (MVC) APIs for "
"tree views, multi-line text fields, and menu and toolbar actions."
msgstr ""

#: C/core-tech.xml:44(para)
msgid ""
"Widgets in GTK+ are placed on windows using a box-packing model. Programmers "
"specify only how to pack widgets together in container boxes, rather than "
"position them directly with absolute coordinates. GTK+ ensures that windows "
"are sized correctly to fit their contents, and it automatically handles "
"window resizing."
msgstr ""

#: C/core-tech.xml:50(para)
msgid ""
"Because GTK+ offers a flexible API, developing additional widgets for use in "
"GTK+ applications is easy. A number of third-party libraries exist which "
"provide additional widgets, and many developers have created custom, special-"
"purpose widgets for their applications."
msgstr ""

#: C/core-tech.xml:55(para)
msgid ""
"GTK+ handles the difficult details of user interfaces and user interaction, "
"and provides a simple yet powerful API which allows you to focus on the "
"details of your application. Applications developed with GTK+ will "
"automatically follow the user's theme and font settings, will interact "
"properly with accessibility technologies, and will behave as users expect."
msgstr ""

#: C/core-tech.xml:62(para)
msgid ""
"For more information on GTK+, see <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/gtk/index.html\">The GTK+ Reference Manual</ulink> or visit "
"<ulink url=\"http://gtk.org/\">the GTK+ web site</ulink>."
msgstr ""

#: C/core-tech.xml:69(title)
msgid "Libglade"
msgstr "Libglade"

#: C/core-tech.xml:70(para)
msgid ""
"Libglade is a library for constructing user interfaces dynamically from XML "
"descriptions. You can use a graphical interface builder like "
"<application>Glade</application> to construct your user interface, and then "
"import the interface description into your application. This makes it easy "
"to construct complex layouts and adjust layout details."
msgstr ""

#: C/core-tech.xml:76(para)
msgid ""
"Libglade allows programmers to focus their code on the logic of their "
"applications, keeping it uncluttered by the actual construction of the "
"interface. Graphical interface builders also make it easy for dedicated "
"interface designers to construct the interfaces without having to know how "
"to program."
msgstr ""

#: C/core-tech.xml:82(para)
msgid ""
"For more information on Libglade, see <ulink url=\"http://developer.gnome."
"org/doc/API/2.0/libglade/index.html\">The Libglade Reference Manual</ulink>."
msgstr ""

#: C/core-tech.xml:88(title)
msgid "Pango"
msgstr "Pango"

#: C/core-tech.xml:93(para)
msgid ""
"The Pango layout engine can be used with different font backends and drawing "
"backends. On most GNOME systems, Pango will use FreeType, fontconfig, and "
"Cairo to access fonts and render text. On other systems, Pango will use the "
"native font systems, such as Uniscribe on Microsoft Windows and ATSUI on "
"MacOS"
msgstr ""

#: C/core-tech.xml:90(para)
msgid ""
"Pango is the core text and font handling library in the GNOME platform. It "
"is responsible for laying out and rendering text, and is used throughout GTK"
"+.<placeholder-1/>"
msgstr ""

#: C/core-tech.xml:100(para)
msgid ""
"Pango has extensive support for the various writing systems used throughout "
"the world. Many of the writing systems used for languages have complex rules "
"for laying out glyphs and composing characters. With Pango, nearly all "
"languages can be written and displayed correctly, allowing users everywhere "
"to view text in their native languages. Pango support for multiple writing "
"systems is automatic; application developers do not have to write any "
"special code to support other languages."
msgstr ""

#: C/core-tech.xml:110(title)
msgid "Displaying Multiple Languages With Pango"
msgstr ""

#: C/core-tech.xml:116(para)
msgid ""
"Screenshot of the <application>gedit</application> text editor displaying "
"phrases from multiple languages and writing systems."
msgstr ""

#: C/core-tech.xml:123(para)
msgid ""
"Pango supports the text styling used in typical documents and interfaces, "
"including italics, font weights, and underlines. Pango uses a simple XML-"
"like vocabulary called PangoMarkup which enables you to set font size, "
"color, styles, and other text attributes. Using PangoMarkup, you can specify "
"inline styles without manually iterating over text blocks. PangoMarkup can "
"be used directly from GTK+, enabling you to style text in your graphical "
"interfaces easily."
msgstr ""

#: C/core-tech.xml:132(para)
msgid ""
"You should use Pango directly whenever you need to lay text out on the "
"screen or on a different medium. Using Pango will allow your text layout to "
"work seamlessly with GTK+ and the rest of the GNOME platform. It will help "
"you create portable code, and most importantly, it will ensure that your "
"application can render text correctly in hundreds of different languages."
msgstr ""

#: C/core-tech.xml:140(para)
msgid ""
"For more information on Pango, see <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/pango/index.html\">The Pango Reference Manual</ulink>."
msgstr ""

#: C/core-tech.xml:146(title)
msgid "GDK"
msgstr "GDK"

#: C/core-tech.xml:153(para)
msgid ""
"GDK runs on a number of different platforms, including the X Window System, "
"Microsoft Windows, DirectFB, and Quartz. On any platform, GDK provides the "
"same consistent API, allowing GTK+ and GTK+ applications to run unmodified."
msgstr ""

#: C/core-tech.xml:148(para)
msgid ""
"GDK is the low-level library used by GTK+ to interact with the system for "
"graphics and input devices. Although you will rarely use GDK directly in "
"application code, it contains all the necessary functionality to draw "
"objects and text to the screen and to interact with the user with various "
"input devices.<placeholder-1/>"
msgstr ""

#: C/core-tech.xml:158(para)
msgid ""
"GDK features a graphics context and drawing primitives that are suitable for "
"drawing simple objects and rendering images on the screen. Since a more "
"extensive drawing system is provided by Cairo, GDK provides hooks to use "
"Cairo contexts within GDK."
msgstr ""

#: C/core-tech.xml:163(para)
msgid ""
"GDK enables you to access events from keyboards, mice, and other input "
"devices, rather than connect to the high-level signals used in GTK+. GDK "
"also provides low-level routines to access drag and drop and clipboard data "
"from the system. When implementing custom controls, you may need to access "
"these features to implement proper user interaction behavior."
msgstr ""

#: C/core-tech.xml:170(para)
msgid ""
"GDK provides other functionality which is needed to implement a complete "
"graphical toolkit like GTK+. Since GDK acts as a platform abstraction, "
"allowing GTK+ to run under multiple environments, it provides an API for all "
"of the system functionality needed by GTK+. This includes information about "
"multi-head displays, resolution and color depth, colormaps, and cursors."
msgstr ""

#: C/core-tech.xml:177(para)
msgid ""
"You should use GDK whenever you need low-level access to the underlying "
"windowing system, including low-level access to events, windows, and the "
"clipboard. Using GDK for these tasks ensures that your code is portable and "
"integrates with the rest of your GTK+ code. The simple drawing routines in "
"GDK should generally not be used. Instead, you should use the extensive "
"functionality provide by Cairo."
msgstr ""

#: C/core-tech.xml:185(para)
msgid ""
"For more information on GDK, see <ulink url=\"http://developer.gnome.org/doc/"
"API/2.0/gdk/index.html\">The GDK Reference Manual</ulink>."
msgstr ""

#: C/core-tech.xml:191(title)
msgid "Cairo"
msgstr "Cairo"

#: C/core-tech.xml:193(para)
msgid ""
"Cairo is a 2D graphics library featuring a sophisticated API for drawing "
"vector graphics, compositing images, and rendering anti-aliased text. Cairo "
"provides support for multiple output devices, including the X Window System, "
"Microsoft Windows, and image buffers, allowing you to write platform-"
"independent code to draw graphics on different media."
msgstr ""

#: C/core-tech.xml:199(para)
msgid ""
"The Cairo drawing model is similar to those provided by PostScript and PDF. "
"The Cairo API provides such drawing operations as stroking and filling cubic "
"Bézier splines, compositing images, and performing affine transformations. "
"These vector operations allow for rich, anti-aliased graphics without using "
"expensive pixel-based drawing in your application code."
msgstr ""

#: C/core-tech.xml:206(para)
msgid ""
"Cairo's rich drawing model allows for high-quality rendering to multiple "
"media. The same API can be used to create stunning on-screen graphics and "
"text, to render images, or create crisp output suitable for printing."
msgstr ""

#: C/core-tech.xml:211(para)
msgid ""
"You should use Cairo whenever you need to draw graphics in your application "
"beyond the widgets provided by GTK+. Much of the drawing inside GTK+ is done "
"using Cairo. Using Cairo for your custom drawing will allow your application "
"to have high-quality, anti-aliased, and resolution-independent graphics."
msgstr ""

#: C/core-tech.xml:217(para)
msgid ""
"For more information on Cairo, see <ulink url=\"http://www.cairographics.org/"
"manual/\">Cairo: A Vector Graphics Library</ulink>."
msgstr ""

#: C/core-tech.xml:224(title)
msgid "Virtual File System"
msgstr ""

#: C/core-tech.xml:226(para)
msgid ""
"GnomeVFS is the core library used for all file and folder operations in "
"GNOME applications. GnomeVFS provides a file system abstraction with "
"pluggable backends, allowing you to use a single consistent API to access "
"files on the local file system, on FTP servers, on WebDAV servers, and over "
"various other protocols and transports."
msgstr ""

#: C/core-tech.xml:232(para)
msgid ""
"All resources, including local files, are accessed in GnomeVFS using Uniform "
"Resource Identifiers (URIs). An extension to the now-commonplace URL, this "
"standard identification scheme allows all resources to be addressed with a "
"simple and consistent syntax."
msgstr ""

#: C/core-tech.xml:237(para)
msgid ""
"GnomeVFS can provide extensive information about files and folders, "
"including the MIME type of the file and which applications can be used to "
"open the file. Since GnomeVFS uses the standard from <ulink url=\"http://www."
"freedesktop.org/\">freedesktop.org</ulink> to determine file types and file "
"associations, it works correctly on different free desktop environments, "
"helping independent software developers create software that can be run in "
"different environments."
msgstr ""

#: C/core-tech.xml:245(para)
msgid ""
"GnomeVFS also provides basic networking support, including routines for "
"network I/O, secure transfers with SSL, and DNS Service Discovery."
msgstr ""

#: C/core-tech.xml:249(para)
msgid ""
"GnomeVFS is used extensively throughout the GNOME desktop. The file manager, "
"Nautilus, uses GnomeVFS to display folders on local and remote systems. For "
"the user, this means that network servers act just like local folders: They "
"can drag and drop files between them, view the files' properties, and open "
"the files with an application. Using GnomeVFS will allow your application to "
"open all the files that users can access on their desktops."
msgstr ""

#: C/core-tech.xml:257(para)
msgid ""
"For more information on GnomeVFS, see <ulink url=\"http://developer.gnome."
"org/doc/API/2.0/gnome-vfs-2.0/index.html\">GnomeVFS - File system "
"Abstraction Library</ulink>."
msgstr ""

#: C/core-tech.xml:263(title)
msgid "Configuration and Lockdown"
msgstr ""

#: C/core-tech.xml:265(para)
msgid ""
"GConf is the system for storing and retrieving configuration settings in "
"GNOME. GConf consists of two parts: a client library for accessing settings, "
"and a session daemon which is responsible for the details of storing and "
"retrieving those settings. Using a daemon allows GConf to use different "
"storage backends, validate input, and provide simultaneous access to "
"different applications."
msgstr ""

#: C/core-tech.xml:272(para)
msgid ""
"Settings stored in GConf are stored and retrieved using a unique key, or "
"identifier string. Keys use a simple hierarchical namespace to avoid "
"collision among settings for applications and the desktop. You can provide a "
"schema file to detail your configuration keys. This allows GConf to validate "
"the type of the input, and to show localized documentation about the key. "
"This helps systems administrators, who can set multiple settings at once "
"without having to navigate preference dialogs."
msgstr ""

#: C/core-tech.xml:280(para)
msgid ""
"GConf can look up settings from different settings at once, typically from "
"different locations on the file system. By having appropriate system sources "
"configured, GConf enables systems administrators to provide both default and "
"mandatory settings for all users. Tools such as GNOME's "
"<application>Configuration Editor</application> and <application>Sabayon</"
"application> make it easy to deploy fully configured systems using GConf."
msgstr ""

#: C/core-tech.xml:288(para)
msgid ""
"The GConf client library provides notifications of changes to settings, "
"making it easy to provide instant-apply settings in your application, "
"regardless if settings are changed from within your application or using "
"another tool. Setting the value of a key will notify all interested "
"applications, allowing desktop-wide and other cross-application settings to "
"work instantly and effortlessly."
msgstr ""

#: C/core-tech.xml:295(para)
msgid ""
"GConf makes it easy to lock down systems by setting particular keys read-"
"only, preventing users from changing their values. In addition, GNOME "
"provides a number of high-level keys that can be used to disable actions "
"such as saving to disk and changing the panel layout. Tools such as "
"<application>Pessulus</application> make it easy for administrators to find "
"and lock down important keys."
msgstr ""

#: C/core-tech.xml:302(para)
msgid ""
"You should use GConf to store all user preferences in your application. "
"Using GConf will make it easy to provide instant-apply preferences, and it "
"will make your settings accessible to systems administrators and "
"configuration and backup tools."
msgstr ""

#: C/core-tech.xml:307(para)
msgid ""
"For more information on GConf, see <ulink url=\"http://developer.gnome.org/"
"doc/API/2.0/gconf/index.html\">The GConf Reference Manual</ulink>."
msgstr ""

#: C/core-tech.xml:313(title)
msgid "Internationalization"
msgstr "Internacionalizacion"

#: C/core-tech.xml:314(para)
msgid ""
"The GNOME Desktop and Developer Platform provides full support for "
"internationalizing and localizing applications. Internationalization is the "
"process of ensuring your application can be localized, including marking all "
"strings for translations, using numbers and format strings correctly, and "
"making adjustments for variations in conventions for times and dates, units, "
"and formatting."
msgstr ""

#: C/core-tech.xml:321(para)
msgid ""
"GNOME uses the standard gettext and related routines for accessing "
"localizations. Support for localization using gettext is built into every "
"component of the GNOME platform. Your source code can be scanned for "
"specially-marked tools by automated tools. Those strings are then placed in "
"PO files to allow translators to track their translations. Using gettext, "
"you can easily and efficiently access translated versions of all user-"
"visible strings in your application from translation domains installed along "
"with your application."
msgstr ""

#: C/core-tech.xml:330(para)
msgid ""
"These translation domains can be created using PO files, which can be used "
"by translators to track string changes and update their translations "
"accordingly. GNOME ships with intltool, a tool for managing translations in "
"PO files. Using intltool, translators can use PO files to translate not only "
"the strings in your application, but also other types of files that you use, "
"such as GConf schema files, desktop entry files, and XML files."
msgstr ""

#: C/core-tech.xml:338(para)
msgid ""
"GNOME also provides the xml2po tool as part of the gnome-doc-utils package. "
"This tool allows translators to use PO files to create translated versions "
"of documentation written in various XML formats, including XHTML and DocBook."
msgstr ""

#: C/core-tech.xml:343(para)
msgid ""
"Internationalization involves more than just allowing strings to be "
"translated, and GNOME supports your application development at every step of "
"the process. GTK+ will automatically adjust its presentation for languages "
"that are read right-to-left, and Pango has complete support for rendering "
"bidirectional text and text in various different writing systems. GTK+ "
"supports multiple input methods, allowing users from all language to input "
"text efficiently with their keyboards. The entire GNOME platform uses the "
"UTF-8 encoding of Unicode natively, providing access to the characters and "
"writing systems of the entire world."
msgstr ""

#: C/core-tech.xml:355(title)
msgid "<application>Gnumeric</application> in Multiple Languages"
msgstr ""

#: C/core-tech.xml:361(para)
msgid ""
"Screenshots of the <application>Gnumeric</application> spreadsheet "
"application running in Hebrew, Japanese, and Serbian."
msgstr ""

#: C/core-tech.xml:368(para)
msgid ""
"Internationalizing your application helps make it available to many more "
"users across the world. While skilled translators must provide translations "
"for any language, programmers must ensure the application is properly "
"internationalized before it can be fully localized."
msgstr ""

#. FIXME: where is danilo's awesome guide?
#: C/core-tech.xml:375(para)
msgid ""
"For more information on internationalization in GNOME, see <ulink url="
"\"http://www.gnome.org/~malcolm/i18n/\">Internationalizing GNOME "
"Applications</ulink>."
msgstr ""

#: C/core-tech.xml:381(title)
msgid "Accessibility"
msgstr "Accessibilitat"

#: C/core-tech.xml:383(para)
msgid ""
"Accessibility is the process of ensuring your application can be used by "
"people with various disabilities. Disabilities come in many forms: visual "
"impairments, movement impairments, hearing impairments, cognitive and "
"language impairments, and seizure disorders. Many people have some sort of "
"disability, and making your application accessibility will allow more people "
"to use your application effectively."
msgstr ""

#: C/core-tech.xml:390(para)
msgid ""
"GNOME provides support for accessibility devices using the ATK framework. "
"This framework defines a set of interfaces to which graphical interface "
"components adhere. This allows, for instance, screen readers to read the "
"text of an interface and interact with its controls. ATK support is built "
"into GTK+ and the rest of the GNOME platform using the GAIL library, so any "
"application using GTK+ will have reasonable accessibility support for free."
msgstr ""

#: C/core-tech.xml:398(para)
msgid ""
"Nonetheless, you should be aware of accessibility issues when when "
"developing your applications. Although GTK+ interfaces provide reasonable "
"accessibility by default, you can often improve how well your program "
"behaves with accessibility tools by providing additional information to ATK. "
"If you develop custom widgets, you should ensure that they expose their "
"properties to ATK. You should also avoid using sound, graphics, or color as "
"the sole means of conveying information to the user."
msgstr ""

#: C/core-tech.xml:407(para)
msgid ""
"The GNOME desktop ships with a number of accessibility tools which enable "
"users with disabilities to take full advantage of their desktop and "
"applications. Applications that fully implement ATK will be able to work "
"with the accessibility tools. GNOME's accessibility tools include a screen "
"reader, a screen magnifier, an on-screen keyboard, and <application>Dasher</"
"application>, an innovative predictive text entry tool."
msgstr ""

#: C/core-tech.xml:415(para)
msgid ""
"For extensive recommendations on accessibility, see <ulink url=\"http://"
"developer.gnome.org/projects/gap/guide/gad/index.html\">GNOME Accessibility "
"for Developers</ulink>. See also <ulink url=\"http://developer.gnome.org/doc/"
"API/2.0/atk/index.html\">ATK - Accessibility Toolkit</ulink> and <ulink url="
"\"http://developer.gnome.org/doc/API/2.0/gail/index.html\">The GAIL "
"Reference Manual</ulink>."
msgstr ""

#: C/core-tech.xml:425(title)
msgid "Multimedia"
msgstr "Multimedià"

#: C/core-tech.xml:427(para)
msgid ""
"GStreamer is a powerful multimedia library for playing, creating, and "
"manipulating sound, video, and other media. You can use GStreamer to provide "
"sound and video playback, record input from multiple sources, and edit "
"multimedia content. GStreamer supports encoding and decoding numerous "
"formats by default, and support for additional formats can be added with "
"plug-ins."
msgstr ""

#: C/core-tech.xml:434(para)
msgid ""
"GStreamer provides a flexible architecture wherein media is processed "
"through a pipeline of elements. Each element may apply filters to the "
"content, such as encoding or decoding, combining multiple sources, or "
"transforming the multimedia content. This architecture allows for an "
"arbitrary arrangement of elements, so that you can accomplish virtually any "
"effect using GStreamer. Furthermore, GStreamer is designed to have low "
"overhead, so it can be used in applications with high demands on latency."
msgstr ""

#: C/core-tech.xml:443(para)
msgid ""
"While GStreamer provides a powerful API for manipulating multimedia, it also "
"provides convenient routines for simple playback. GStreamer can "
"automatically construct a pipeline to read and playback files in any "
"supported format, allowing you to use sound and video in your application "
"easily."
msgstr ""

#: C/core-tech.xml:449(para)
msgid ""
"The GStreamer architecture allows plugins to add encoders, decoders, and all "
"sorts of content filters. Third-party developers can provide GStreamer "
"plugins which will be automatically available to other applications using "
"GStreamer. Plugins can provide support for other multimedia formats or "
"provide additional functionality and effects."
msgstr ""

#: C/core-tech.xml:456(para)
msgid ""
"You should use GStreamer whenever you need to read or play multimedia "
"content in your application, or if your application needs to manipulate "
"sound or video. Using GStreamer makes your application development easy, and "
"it provides you well-tested elements for many of your needs."
msgstr ""

#: C/core-tech.xml:462(para)
msgid ""
"For comprehensive information on GStreamer, see <ulink url=\"http://"
"gstreamer.freedesktop.org/data/doc/gstreamer/head/manual/html/index.html"
"\">The GStreamer Application Development Manual</ulink>, <ulink url=\"http://"
"gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer/html/\">The "
"GStreamer 0.10 Core Reference Manual</ulink>, and <ulink url=\"http://"
"gstreamer.freedesktop.org/documentation/\">the GStreamer documentation page</"
"ulink>."
msgstr ""

#: C/core-tech.xml:472(title)
msgid "Printing"
msgstr "Estampatge"

#: C/core-tech.xml:474(para)
msgid ""
"Most applications need to provide support for printing. Users expect to be "
"able to print the contents they can view on-screen. The GNOME platform "
"provides libraries to help you add support for high-quality printing to your "
"application."
msgstr ""

#: C/core-tech.xml:480(title)
msgid "GNOME Print"
msgstr "GNOME Print"

#: C/core-tech.xml:482(para)
msgid ""
"The GNOME print framework consists of two libraries which help you provide "
"high-quality printing with a consistent interface in your application. At "
"the core of the printing framework is libgnomeprint, a library for creating "
"PostScript output to send to printers. On top of that is libgnomeprintui, "
"which provides standard print controls for your user interface."
msgstr ""

#: C/core-tech.xml:489(para)
msgid ""
"Work is currently underway to integrate printing directly into GTK+, "
"provding a cross-platform print API that all applications can use. While the "
"current GNOME print framework will be deprecated once GTK+ supports "
"printing, API and ABI stability guarantees ensures that it will continue to "
"be functional and supported throughout the GNOME 2 lifecycle."
msgstr ""

#: C/core-tech.xml:496(para)
msgid ""
"The libgnomeprint library implements the PostScript imaging model, which is "
"used by most printers. Printers which do not support PostScript can still be "
"supported through CUPS, described below. In addition to the standard "
"PostScript imaging, libgnomeprint also features alpha channel support and "
"anti-aliasing."
msgstr ""

#: C/core-tech.xml:502(para)
msgid ""
"The libgnomeprintui library provides a standard print dialog, a print "
"preview dialog, and various other controls and functionality required to "
"build printing into an intuitive user interface. The GNOME print framework "
"handles the details of locating printers and spooling print jobs, and also "
"provides PostScript and PDF export directly in the print dialog."
msgstr ""

#: C/core-tech.xml:508(para)
msgid ""
"You should use libgnomeprint whenever you need to render content to "
"PostScript for printing. You should use libgnomeprintui to construct your "
"printing user interface, even if your rendered output comes from another "
"source. Using the GNOME print framework provides your users a consistent "
"user interface with the features they expect of printing appliations."
msgstr ""

#: C/core-tech.xml:516(title)
msgid "CUPS"
msgstr "CUPS"

#: C/core-tech.xml:518(para)
msgid ""
"On most GNOME systems, CUPS (Common UNIX Printing System) acts as the low-"
"level printing system. CUPS provides a modern, feature-rich architecture for "
"printer discovery, printer option access, and spooling print jobs to "
"different types of printers."
msgstr ""

#: C/core-tech.xml:523(para)
msgid ""
"CUPS provides a set of utilities for automatically discovering printers "
"locally and on the network. This allows users not only to see all available "
"printers, but to use different types of printers without manual "
"configuration."
msgstr ""

#: C/core-tech.xml:528(para)
msgid ""
"CUPS provides a unified interface for printing, regardless of the location "
"or type of the printer. Multiple print protocols are handled seamlessly by "
"CUPS by automatically applying filters to content sent to the printers. "
"Applications can simply provide PostScript output, and CUPS will "
"automatically convert it for printers that do not support PostScript "
"natively."
msgstr ""

#: C/core-tech.xml:535(para)
msgid ""
"CUPS also provides printer configuration options in the form of PostScript "
"Printer Description (PPD) files. PPD configurations allow applications to "
"expose the capabilities of individual printers to the users with a "
"consistent user interface. For instance, PPD allows you to detect whether a "
"printer can collate and staple print jobs, and to provide an option in your "
"user interface."
msgstr ""

#: C/core-tech.xml:542(para)
msgid ""
"In most cases, you will not need to interface directly with CUPS in your "
"applications. By using the GNOME print framework, you have access to the "
"power and flexibility of CUPS automatically. Having CUPS underneath means a "
"better user experience with less programming."
msgstr ""

#: C/bindings.xml:4(title)
msgid "Language Bindings"
msgstr ""

#: C/bindings.xml:6(para)
msgid ""
"Although the GNOME platform is written primarily in C, it is written "
"intentionally to make it easy to bind to other programming languages. Using "
"language bindings, you can develop with the GNOME platform natively in your "
"programming language of choice."
msgstr ""

#: C/bindings.xml:11(para)
msgid ""
"Language bindings exist for many programming languages, and the GNOME "
"platform officially supports bindings for C++, Java, Perl, and Python."
msgstr ""

#: C/bindings.xml:15(title)
msgid "C++"
msgstr "C++"

#: C/bindings.xml:16(para)
msgid ""
"The C++ bindings provide complete coverage of the GNOME platform, including "
"GTK+, Glade, and GConf. The C++ bindings wrap all objects with native C++ "
"objects and allow programmers to provide custom widgets with normal C++ "
"inheritence. They provide a fully native API, with type-safe signal "
"handlers, full use of the standard C++ library, and complete C++ memory "
"management."
msgstr ""

#: C/bindings.xml:23(para)
msgid ""
"For more information on the GNOME C++ bindings, visit <ulink url=\"http://"
"www.gtkmm.org/\">the gtkmm web site</ulink>."
msgstr ""

#: C/bindings.xml:28(title)
msgid "Java"
msgstr "Java"

#: C/bindings.xml:29(para)
msgid ""
"The Java bindings provide complete coverage of the GNOME platform, including "
"GTK+, Cairo, and GConf. The Java bindings wrap all objects with native Java "
"objects and allow programmers to provide custom widgets with normal Java "
"inheritence. They provide a fully native API, using Java's class libraries "
"and interfaces wherever appropriate."
msgstr ""

#: C/bindings.xml:35(para)
msgid ""
"For more information on the GNOME Java bindings, visit <ulink url=\"http://"
"java-gnome.sourceforge.net/\">the Java-GNOME web site</ulink>."
msgstr ""

#: C/bindings.xml:40(title)
msgid "Perl"
msgstr "Perl"

#: C/bindings.xml:41(para)
msgid ""
"The Perl bindings provide native Perl interfaces for the GNOME platform, "
"including GTK+, GnomeVFS, and GConf. The Perl bindings wrap all objects with "
"Perl objects and allow programmers to use standard Perl practices to "
"manipulate them. They provide a fully native API, using Perl's native data "
"types wherever appropriate."
msgstr ""

#: C/bindings.xml:47(para)
msgid ""
"For more information on the GNOME Perl bindings, visit <ulink url=\"http://"
"gtk2-perl.sourceforge.net/\">the gtk2-perl web site</ulink>."
msgstr ""

#: C/bindings.xml:52(title)
msgid "Python"
msgstr "Python"

#: C/bindings.xml:53(para)
msgid ""
"The Python bindings provide native Python interfaces for the GNOME platform, "
"including GTK+, GnomeVFS, and GConf. The Python bindings wrap all objects "
"with native Python objects and allow programmers to provide custom widgets "
"with normal Python inheritence. They provide a fully native Python API which "
"automatically handles details like type casting and memory management."
msgstr ""

#: C/bindings.xml:60(para)
msgid ""
"For more information on the GNOME Python bindings, visit <ulink url=\"http://"
"www.pygtk.org/\">the PyGTK web site</ulink>."
msgstr ""

#: C/bindings.xml:65(title)
msgid "Other Languages"
msgstr "Autras lengas"

#: C/bindings.xml:66(para)
msgid ""
"Full or partial bindings exist for many other programming langauges, such as "
"C#, Eiffel, JavaScript, Ruby, and Scheme. Even though they may not currently "
"be officially supported by GNOME, many of these bindings are of the same "
"high quality as the official GNOME bindings, and some of them may be "
"included as official GNOME bindings in future releases."
msgstr ""

#: C/bindings.xml:72(para)
msgid ""
"For a list of language bindings, visit <ulink url=\"http://gtk.org/bindings."
"html\">the GTK+ bindings page</ulink>."
msgstr ""

#: C/apx-modules.xml:4(title)
msgid "Quick Module Overview"
msgstr ""

#: C/apx-modules.xml:6(para)
msgid ""
"This appendix provides a quick overview of the libraries included in the "
"GNOME desktop and developer platform. Libraries are listed by module with a "
"brief description and a link for more information in this document, where "
"possible."
msgstr ""

#: C/apx-modules.xml:12(title)
msgid "Platform Modules"
msgstr ""

#: C/apx-modules.xml:14(para)
msgid ""
"Modules in the GNOME developer platform make strict guarantees about API and "
"ABI stability. Applications developed against platform modules can be "
"assured of running unmodified for the duration of the GNOME 2 lifecycle."
msgstr ""

#: C/apx-modules.xml:21(term)
msgid "GConf"
msgstr "GConf"

#: C/apx-modules.xml:22(para)
msgid ""
"GConf provides the daemon and libraries for storing and retrieving "
"configuration data. GConf is discussed in <xref linkend=\"gconf\"/>."
msgstr ""

#: C/apx-modules.xml:27(term)
msgid "ORBit"
msgstr "ORBit"

#: C/apx-modules.xml:28(para)
msgid ""
"ORBit is a fast and lightweight CORBA server. GNOME's component "
"architecture, Bonobo, is built on top of CORBA. CORBA is discussed in <xref "
"linkend=\"bonobo-corba\"/>."
msgstr ""

#: C/apx-modules.xml:33(term)
msgid "atk"
msgstr "atk"

#: C/apx-modules.xml:34(para)
msgid ""
"ATK provides the set of accessibility interfaces that are implemented by "
"other toolkits and applications. Using the ATK interfaces, accessibility "
"tools have full access to view and control running applications. ATK is "
"discussed in <xref linkend=\"a11y\"/>."
msgstr ""

#: C/apx-modules.xml:41(term)
msgid "gail"
msgstr "gail"

#: C/apx-modules.xml:42(para) C/apx-modules.xml:200(para)
msgid ""
"GAIL provides an implementation of the ATK interfaces for GTK+ and GNOME "
"libraries, allowing accessibility tools to interact with applications "
"written using these libraries. Accessibility is discussed in <xref linkend="
"\"a11y\"/>."
msgstr ""

#: C/apx-modules.xml:48(term)
msgid "glib"
msgstr "glib"

#: C/apx-modules.xml:49(para)
msgid ""
"GLib provides the core application building blocks for libraries and "
"applications written in C. It provides the core object system used in GNOME, "
"the main loop implementation, and a large set of utility functions for "
"strings and common data structures."
msgstr ""

#: C/apx-modules.xml:55(term)
msgid "gnome-vfs"
msgstr "gnome-vfs"

#: C/apx-modules.xml:56(para)
msgid ""
"GnomeVFS is the core library used to access files and folders in GNOME "
"applications. It provides a file system abstraction which allows "
"applications to access local and remote files with a single consistent API. "
"GnomeVFS is discussed in <xref linkend=\"gnome-vfs\"/>."
msgstr ""

#: C/apx-modules.xml:63(term)
msgid "gtk+"
msgstr "gtk+"

#: C/apx-modules.xml:64(para)
msgid ""
"GTK+ is the primary library used to construct user interfaces in GNOME "
"applications. It provides user interface controls and signal callbacks to "
"control user interfaces. GTK+ is discussed in <xref linkend=\"gtk\"/>."
msgstr ""

#: C/apx-modules.xml:70(term)
msgid "libIDL"
msgstr "libIDL"

#: C/apx-modules.xml:71(para)
msgid ""
"libIDL is a library for parsing Interface Definition Language (IDL) files, "
"which are necessary for CORBA interfaces. libIDL is used by GNOME's CORBA "
"implementation, ORBit. CORBA is discussed in <xref linkend=\"bonobo-corba\"/"
">."
msgstr ""

#: C/apx-modules.xml:77(term)
msgid "libart_lgpl"
msgstr "libart_lgpl"

#: C/apx-modules.xml:78(para)
msgid ""
"libart is a graphics library which can render vector paths. It is used by "
"the GnomeCanvas widget."
msgstr ""

#: C/apx-modules.xml:82(term)
msgid "libbonobo"
msgstr "libbonobo"

#: C/apx-modules.xml:83(para)
msgid ""
"Bonobo is a framework for creating reusable components for use in GNOME "
"applications, built on top of CORBA. Bonobo is discussed in <xref linkend="
"\"bonobo-corba\"/>."
msgstr ""

#: C/apx-modules.xml:88(term)
msgid "libbonoboui"
msgstr "libbonoboui"

#: C/apx-modules.xml:89(para)
msgid ""
"The Bonobo UI library provides a number of user interface controls using the "
"Bonobo component framework. Bonobo is discussed in <xref linkend=\"bonobo-"
"corba\"/>."
msgstr ""

#: C/apx-modules.xml:94(term)
msgid "libglade"
msgstr "libglade"

#: C/apx-modules.xml:95(para)
msgid ""
"Libglade is a library for constructing user interfaces dynamically from XML "
"descriptions. Libglade allow programmers to construct their user interfaces "
"using a graphical interface builder application, and then import those "
"interface definitions. Libglade is discussed in <xref linkend=\"libglade\"/>."
msgstr ""

#: C/apx-modules.xml:102(term)
msgid "libgnome"
msgstr "libgnome"

#: C/apx-modules.xml:103(para)
msgid ""
"The libgnome library provides a number of useful routines for building "
"modern applications, including session management, activation of files and "
"URIs, and displaying help."
msgstr ""

#: C/apx-modules.xml:108(term)
msgid "libgnomecanvas"
msgstr "libgnomecanvas"

#: C/apx-modules.xml:109(para)
msgid ""
"The GnomeCanvas widget provides a flexible widget for creating iteractive "
"structrued graphics."
msgstr ""

#: C/apx-modules.xml:113(term)
msgid "libgnomeui"
msgstr "libgnomeui"

#: C/apx-modules.xml:114(para)
msgid ""
"The libgnomeui library provides additional widgets for applications. Many of "
"the widgets from libgnomeui have already been ported to GTK+."
msgstr ""

#: C/apx-modules.xml:119(term)
msgid "libxml2"
msgstr "libxml2"

#: C/apx-modules.xml:120(para)
msgid ""
"The libxml2 library provides a number of APIs for working with XML in a "
"standards-compliant manner. The libxml2 library is discussed in <xref "
"linkend=\"libxml2\"/>."
msgstr ""

#: C/apx-modules.xml:125(term)
msgid "libxslt"
msgstr "libxslt"

#: C/apx-modules.xml:126(para)
msgid ""
"The libxslt library provides a fast and complete implementation of XSLT, a "
"language for transforming XML. The libxslt library is discussed in <xref "
"linkend=\"libxslt\"/>."
msgstr ""

#: C/apx-modules.xml:131(term)
msgid "pango"
msgstr "pango"

#: C/apx-modules.xml:132(para)
msgid ""
"Pango is the core textand font handling library used in GNOME applications. "
"It has extensive support for the different writing systems used throughout "
"the world. Pango is discussed in <xref linkend=\"pango\"/>."
msgstr ""

#: C/apx-modules.xml:141(title)
msgid "Desktop Modules"
msgstr ""

#: C/apx-modules.xml:143(para)
msgid ""
"Modules in the GNOME desktop are not required to make the same API and ABI "
"stability guarantees as modules in the platform, although attempts are made "
"to keep them relatively stable. Often, modules are introduced in the desktop "
"release to mature, and are moved into the platform once they've stabilized."
msgstr ""

#: C/apx-modules.xml:151(term)
msgid "eel"
msgstr "eel"

#: C/apx-modules.xml:152(para)
msgid ""
"The eel library provides a number of additional widgets primarily for use "
"inside <application>Nautilus</application>, the GNOME file manager. Many of "
"the widgets in eel have since been provided in GTK+."
msgstr ""

#: C/apx-modules.xml:158(term)
msgid "evolution-data-server"
msgstr "evolution-data-server"

#: C/apx-modules.xml:159(para)
msgid ""
"Evolution Data Server provides a unified location for address book and "
"calendar information, allowing multiple applications to share the same data. "
"Evolution Data Server is discussed in <xref linkend=\"address-book-calendar"
"\"/>."
msgstr ""

#: C/apx-modules.xml:165(term)
msgid "gnome-panel"
msgstr "gnome-panel"

#: C/apx-modules.xml:166(para)
msgid ""
"In addition to the actual panel, the gnome-panel package provides the "
"libraries used to construct panel applets to run on the user's panel. Panel "
"applets are discussed in <xref linkend=\"panel-applets\"/>."
msgstr ""

#: C/apx-modules.xml:172(term)
msgid "gnome-keyring"
msgstr "gnome-keyring"

#: C/apx-modules.xml:173(para)
msgid ""
"The GNOME keyring manager provides a modern and secure means of storing "
"users' passwords and other sensitive data. Keys are encrypted and can only "
"be accessed by explicit user permission. The keyring manager is discussed in "
"<xref linkend=\"keyring\"/>."
msgstr ""

#: C/apx-modules.xml:179(term)
msgid "gstreamer"
msgstr "gstreamer"

#: C/apx-modules.xml:180(para)
msgid ""
"GStreamer is the powerful multimedia used throughout GNOME to play, create, "
"and manipulate sound and video. GStreamer is discussed in <xref linkend="
"\"multimedia\"/>."
msgstr ""

#: C/apx-modules.xml:185(term)
msgid "gtkhtml"
msgstr "gtkhtml"

#: C/apx-modules.xml:186(para)
msgid ""
"The gtkhtml library provides a lightweight HTML renderer with full support "
"for rich text editing. It is used inside the <application>Evolution</"
"application> mailer to allow users to compose and read HTML email."
msgstr ""

#: C/apx-modules.xml:192(term)
msgid "gtksourceview"
msgstr "gtksourceview"

#: C/apx-modules.xml:193(para)
msgid ""
"The gtksourceview library provides an extension of the GtkTextView widget "
"with support for automatic syntax highlighting and other functions that are "
"useful for source code editors. It is used in the <application>gedit</"
"application> text editor."
msgstr ""

#: C/apx-modules.xml:199(term)
msgid "libgail-gnome"
msgstr "libgail-gnome"

#: C/apx-modules.xml:206(term)
msgid "libgnomeprint"
msgstr "libgnomeprint"

#: C/apx-modules.xml:207(para)
msgid ""
"The libgnomeprint library provides an implementation of the PostScript "
"imaging model and can be used to create high-quality print renderings. The "
"GNOME print framework is discussed in <xref linkend=\"gnomeprint\"/>."
msgstr ""

#: C/apx-modules.xml:213(term)
msgid "libgnomeprintui"
msgstr "libgnomeprintui"

#: C/apx-modules.xml:214(para)
msgid ""
"The libgnomeprintui library provides a standart print dialog, a print "
"preview dialog, and various other controls required for printing. The GNOME "
"print framework is discussed in <xref linkend=\"gnomeprint\"/>."
msgstr ""

#: C/apx-modules.xml:220(term)
msgid "libgtop"
msgstr "libgtop"

#: C/apx-modules.xml:221(para)
msgid ""
"The libgtop library provides a portable API for obtaining information about "
"running processes. It is used in the <application>System Monitor</"
"application> applicatio."
msgstr ""

#: C/apx-modules.xml:226(term)
msgid "librsvg"
msgstr "librsvg"

#: C/apx-modules.xml:227(para)
msgid ""
"The librsvg library provides an implementation of Scalable Vector Graphics "
"(SVG). It is used throughout the desktop to render resolution-independent "
"vector graphics."
msgstr ""

#: C/apx-modules.xml:232(term)
msgid "libsoup"
msgstr "libsoup"

#: C/apx-modules.xml:233(para)
msgid ""
"The libsoup library provides an implementation of the Simple Object Access "
"Protocol (SOAP), as well as an HTTP implementation. SOAP can be used to "
"build web services into applications. The libsoup library is discussed in "
"<xref linkend=\"libsoup\"/>."
msgstr ""

#: C/apx-modules.xml:239(term)
msgid "libwnck"
msgstr "libwnck"

#: C/apx-modules.xml:240(para)
msgid ""
"The libwnck library provides a means of controlling any EWMH-compliant "
"window manager, including <application>Metacity</application>, the GNOME "
"default window manager. The libwnck library is discussed in <xref linkend="
"\"window-manager\"/>."
msgstr ""

#: C/apx-modules.xml:246(term)
msgid "libxklavier"
msgstr "libxklavier"

#: C/apx-modules.xml:247(para)
msgid ""
"The libxklavier library provides a high-level API for accessing and setting "
"keyboard layouts. It is used in the <application>Keyboard Preferences</"
"application> to allow users to set their keyboard layout and options."
msgstr ""

#: C/apx-modules.xml:253(term)
msgid "vte"
msgstr "vte"

#: C/apx-modules.xml:254(para)
msgid ""
"VTE is a terminal emulator widget for use in GTK+ applications. It provides "
"a consistent API and uses Pango for text drawing, allowing it to display all "
"internationalized text. VTE is used in GNOME's <application>Terminal</"
"application> application."
msgstr ""

#: C/platform-overview.xml:7(title) C/platform-overview.xml:10(title)
msgid "Overview of the GNOME Platform"
msgstr ""

#: C/platform-overview.xml:12(year)
msgid "2005"
msgstr "2005"

#: C/platform-overview.xml:13(year)
msgid "2006"
msgstr "2006"

#: C/platform-overview.xml:14(holder)
msgid "Shaun McCance"
msgstr "Shaun McCance"

#: C/platform-overview.xml:17(publishername)
msgid "GNOME Foundation"
msgstr "Fondacion GNOME"

#: C/platform-overview.xml:19(pubdate)
msgid "2007-03-16"
msgstr "16/03/2007"

#: C/platform-overview.xml:20(edition)
msgid "2.20"
msgstr "2.20"

#: C/platform-overview.xml:22(para)
msgid "Overview of the powerful technologies inside the GNOME platform."
msgstr ""

#: C/platform-overview.xml:27(firstname)
msgid "Shaun"
msgstr "Shaun"

#: C/platform-overview.xml:28(surname)
msgid "McCance"
msgstr "McCance"

#: C/platform-overview.xml:30(orgname)
msgid "GNOME Documentation Project"
msgstr "Projècte de documentacion de GNOME"

#: C/platform-overview.xml:32(email)
msgid "shaunm@gnome.org"
msgstr "shaunm@gnome.org"

#. Put one translator per line, in the form of NAME <EMAIL>, YEAR1, YEAR2.
#: C/platform-overview.xml:0(None)
msgid "translator-credits"
msgstr "Yannig Marchegay (Kokoyaya) <yannig@marchegay.org>"