Refresh POT files

[developers-reference.git] / po4a / po / developer-duties.pot

diff --git a/po4a/po/developer-duties.pot b/po4a/po/developer-duties.pot
index 74dcb077dbedbb4bd6bb8b7160fd455051521d7c..709dd84401653087e338172790c4bf416a08708e 100644 (file)
--- a/po4a/po/developer-duties.pot
+++ b/po4a/po/developer-duties.pot
@@ -1,12 +1,13 @@
 # SOME DESCRIPTIVE TITLE
 # Copyright (C) YEAR Free Software Foundation, Inc.
+# This file is distributed under the same license as the PACKAGE package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-# 
+#
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2007-07-01 21:01+0000\n"
+"POT-Creation-Date: 2008-08-08 11:33-0300\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -254,8 +255,8 @@ msgid ""
 "Generally you should deal with bug reports on your packages as described in "
 "<xref linkend=\"bug-handling\"/> .  However, there's a special category of "
 "bugs that you need to take care of — the so-called release-critical bugs (RC "
-"bugs).  All bug reports that have severity <emphasis>critical</emphasis>, "
-"<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to "
+"bugs).  All bug reports that have severity <literal>critical</literal>, "
+"<literal>grave</literal> or <literal>serious</literal> are considered to "
 "have an impact on whether the package can be released in the next stable "
 "release of Debian.  These bugs can delay the Debian release and/or can "
 "justify the removal of a package at freeze time.  That's why these bugs need "