Please update debconf PO translation for the package flex 2.5.33-13
Hi,
The debian-l10n-english team has reviewed the debconf templates for
flex. This process has resulted in changes that may make your
existing translation incomplete.
A round of translation updates is being launched to synchronize all
translations.
Please send the updated file as a wishlist bug against the package.
The deadline for receiving the updated translation is Tuesday, November 13, 2007.
Thanks,
# flex po-debconf translation to Spanish
# Copyright (C) 2005 Software in the Public Interest
# This file is distributed under the same license as the flex package.
#
# Changes:
# - Initial translation
# César Gómez Martín <cesar.gomez@gmail.com>
#
# Traductores, si no conoce el formato PO, merece la pena leer la
# documentación de gettext, especialmente las secciones dedicadas a este
# formato, por ejemplo ejecutando:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
# Equipo de traducción al español, por favor, lean antes de traducir
# los siguientes documentos:
#
# - El proyecto de traducción de Debian al español
# http://www.debian.org/intl/spanish/
# especialmente las notas de traducción en
# http://www.debian.org/intl/spanish/notas
#
# - La guía de traducción de po's de debconf:
# /usr/share/doc/po-debconf/README-trans
# o http://www.debian.org/intl/l10n/po-debconf/README-trans
#
msgid ""
msgstr ""
"Project-Id-Version: flex\n"
"Report-Msgid-Bugs-To: srivasta@debian.org\n"
"POT-Creation-Date: 2007-10-30 07:26+0100\n"
"PO-Revision-Date: 2005-09-28 17:55+0100\n"
"Last-Translator: César Gómez Martín <cesar.gomez@gmail.com>\n"
"Language-Team: Debian l10n spanish <debian-l10n-spanish@lists.debian.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: Spanish\n"
"X-Poedit-Country: SPAIN\n"
"X-Poedit-SourceCharset: utf-8\n"
#. Type: boolean
#. Description
#: ../templates.master:2001
msgid "Are you sure you want to upgrade flex?"
msgstr "¿Está seguro de que quiere actualizar flex?"
#. Type: boolean
#. Description
#: ../templates.master:2001
#, fuzzy
#| msgid ""
#| "This version of Flex is a major upgrade from previous versions. There "
#| "have been extensive changes. Flex scanners are now reenterant, you may "
#| "have multiple scanners in the same program with differing sets of "
#| "defaults, and they play nicer with modern C and C++ compilers. The flip "
#| "side is that Flex no longer conforms to the POSIX lex behaviour, and the "
#| "scanners require conforming implementations when flex is used in ANSI C "
#| "mode. The package flex-old provides the same behaviour as version 2.5.4a "
#| "of Flex."
msgid ""
"The behavior of Flex has undergone a major change since version 2.5.4a. Flex "
"scanners are now reentrant: they can have multiple scanners in the same "
"program with differing sets of defaults, and they play nicer with modern C "
"and C++ compilers. The flipside is that Flex no longer conforms to the POSIX "
"lex behavior, and the scanners require conforming implementations when Flex "
"is used in ANSI C mode. The package flex-old provides the older behavior."
msgstr ""
"Esta versión de Flex es una actualización considerable de las versiones "
"anteriores. Hay grandes cambios. Los escáneres de Flex son ahora "
"reentrantes, puede tener múltiples escáneres en el mismo programa con "
"distintas configuraciones por omisión, y funciona mejor compiladores "
"modernos de C y C++. La parte mala es que ahora Flex no cumple con el "
"comportamiento del lex POSIX, y que los escáneres requieren implementaciones "
"que cumplan los estándares POSIX cuando flex se usa en en el modo ANSI C. El "
"paquete flex-old proporciona el mismo comportamiento que la versión 2.5.4a "
"de Flex."
#. Type: boolean
#. Description
#: ../templates.master:2001
msgid ""
"Please make sure you are prepared for these changes in Flex before "
"continuing with its upgrade."
msgstr ""
"Por favor, antes de continuar con esta actualización esté seguro de que está "
"preparado para estos cambios en Flex."
Reply to: