Branch 'f11-tx' - as-IN/vnc_VNC_Whitepaper.po bn-IN/vnc_VNC_Whitepaper.po da/vnc_VNC_Whitepaper.po de-DE/vnc_VNC_Whitepaper.po el/vnc_VNC_Whitepaper.po en-US/vnc_VNC_Whitepaper.xml es-ES/vnc_VNC_Whitepaper.po fa/vnc_VNC_Whitepaper.po fr-FR/vnc_VNC_Whitepaper.po gu-IN/vnc_VNC_Whitepaper.po hi-IN/vnc_VNC_Whitepaper.po hu/vnc_VNC_Whitepaper.po id/vnc_VNC_Whitepaper.po it-IT/vnc_VNC_Whitepaper.po ja-JP/vnc_VNC_Whitepaper.po kn-IN/vnc_VNC_Whitepaper.po ko-KR/vnc_VNC_Whitepaper.po lv/vnc_VNC_Whitepaper.po ml-IN/vnc_VNC_Whitepaper.po mr-IN/vnc_VNC_Whitepaper.po ms/vnc_VNC_Whitepaper.po nb/vnc_VNC_Whitepaper.po nl/vnc_VNC_Whitepaper.po or-IN/vnc_VNC_Whitepaper.po pa-IN/vnc_VNC_Whitepaper.po pl/vnc_VNC_Whitepaper.po po/install-guide.pot pot/vnc_VNC_Whitepaper.pot pt-BR/vnc_VNC_Whitepaper.po pt/vnc_VNC_Whitepaper.po ru-RU/vnc_VNC_Whitepaper.po si-LK/vnc_VNC_Whitepaper.po sr-LATN/vnc_VNC_Whitepaper.po sr/vnc_VNC_Whitepaper.po sv/vnc_VNC_Whitepaper.po ta-IN/vnc_VNC_Whitepaper.po te-IN/vnc_VNC_Whitepaper.po zh-CN/vnc_VNC_Whitepaper.po zh-TW/vnc_VNC_Whitepaper.po
Rüdiger Landmann
rlandmann at fedoraproject.org
Tue Apr 28 20:57:52 UTC 2009
as-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
bn-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
da/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
de-DE/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
el/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
en-US/vnc_VNC_Whitepaper.xml | 47 +++++++++++++-----------------
es-ES/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
fa/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
fr-FR/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
gu-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
hi-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
hu/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
id/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
it-IT/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
ja-JP/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
kn-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
ko-KR/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
lv/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
ml-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
mr-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
ms/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
nb/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
nl/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
or-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
pa-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
pl/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
po/install-guide.pot | 65 ++++++++++++++++++------------------------
pot/vnc_VNC_Whitepaper.pot | 65 ++++++++++++++++++------------------------
pt-BR/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
pt/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
ru-RU/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
si-LK/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
sr-LATN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
sr/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
sv/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
ta-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
te-IN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
zh-CN/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
zh-TW/vnc_VNC_Whitepaper.po | 65 ++++++++++++++++++------------------------
39 files changed, 1123 insertions(+), 1394 deletions(-)
New commits:
commit 7f5120b66d9f83beb10e45615e602fc0f69d6636
Author: Ruediger Landmann <r.landmann at redhat.com>
Date: Wed Apr 29 06:57:39 2009 +1000
Make VNC less RHEL-specific
diff --git a/as-IN/vnc_VNC_Whitepaper.po b/as-IN/vnc_VNC_Whitepaper.po
index c8c123c..aafea0c 100644
--- a/as-IN/vnc_VNC_Whitepaper.po
+++ b/as-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/bn-IN/vnc_VNC_Whitepaper.po b/bn-IN/vnc_VNC_Whitepaper.po
index 4189e2c..be11582 100644
--- a/bn-IN/vnc_VNC_Whitepaper.po
+++ b/bn-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/da/vnc_VNC_Whitepaper.po b/da/vnc_VNC_Whitepaper.po
index b9e89a0..d8bc2fb 100644
--- a/da/vnc_VNC_Whitepaper.po
+++ b/da/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/de-DE/vnc_VNC_Whitepaper.po b/de-DE/vnc_VNC_Whitepaper.po
index f79e234..c757510 100644
--- a/de-DE/vnc_VNC_Whitepaper.po
+++ b/de-DE/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/el/vnc_VNC_Whitepaper.po b/el/vnc_VNC_Whitepaper.po
index b757cfb..fdce4b1 100644
--- a/el/vnc_VNC_Whitepaper.po
+++ b/el/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/en-US/vnc_VNC_Whitepaper.xml b/en-US/vnc_VNC_Whitepaper.xml
index 23b704d..2cf59e0 100644
--- a/en-US/vnc_VNC_Whitepaper.xml
+++ b/en-US/vnc_VNC_Whitepaper.xml
@@ -5,10 +5,17 @@
<chapter id="vncwhitepaperadded">
<title>Installing Through VNC</title>
<!-- <xi:include href="vnc_Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+
<para>
- Many enterprise customers perform interactive installations
- on systems in datacenters. These systems are often, but not
- always, installed in a rack environment and do not have a
+ The Red Hat Enterprise Linux and Fedora installer
+ (<application>anaconda</application>) offers you two
+ interactive modes of operation. The original mode is a
+ text-based interface. The newer mode uses GTK+ and runs in
+ the X Window environment. This chapter explains how you can use the graphical installation mode
+ in environments where the system lacks a
+ proper display and input devices typically associated with
+ a workstation. This scenario is typical of systems in datacenters, which are often
+ installed in a rack environment and do not have a
display, keyboard, or mouse. Additionally, a lot of these
systems even lack the ability to connect a graphical display.
Given that enterprise hardware rarely needs that ability at
@@ -17,28 +24,16 @@
</para>
<para>
- The <application>Red Hat Enterprise Linux</application>
- (RHEL) and <application>Fedora Linux</application> installer
- (<application>anaconda</application>) offers users two
- interactive modes of operation. The original mode is a
- text-based interface. The newer mode uses GTK+ and runs in
- the X Window environment. The purpose of this document is
- to explain how the graphical installation mode can be used
- in enterprise environments, even when the system lacks a
- proper display and input devices typically associated with
- a workstation.
-</para>
-
-<para>
- The primary driver behind the document is to encourage use
- of the graphical installer, even in enterprise environments.
+ Even in these environments, however, the graphical installer remains
+ the recommended method of installation.
The text mode environment lacks a lot of capabilities found
in the graphical mode. Many users still feel that the text
mode interface provides them with additional power or
configuration ability not found in the graphical version.
The opposite is true. Much less development effort is put
- in to the text mode environment and specific things (e.g.,
- LVM configuration) are deliberately left out of the text
+ in to the text-mode environment and specific things (for example,
+ LVM configuration, partition layout, package selection, and bootloader
+ configuration) are deliberately left out of the text
mode environment. The reasons for this are:
</para>
@@ -64,13 +59,13 @@
</itemizedlist>
<para>
- All of these reasons and more are why you, the enterprise
- customer, should be making using of the <application>Virtual
- Network Computing</application> (VNC) mode offered in
- <application>anaconda</application>. VNC allows the
+ <application>Anaconda</application> therefore includes a <application>Virtual
+ Network Computing</application> (VNC) mode that allows the
graphical mode of the installer to run locally, but display
- on a system connected to the network.
- </para>
+ on a system connected to the network. Installing in VNC mode
+ provides you with the full range of installation options, even
+ in situations where the system lacks a display or input devices.
+</para>
<xi:include href="vnc_Viewer_Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="vnc_Modes_Chapter.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/es-ES/vnc_VNC_Whitepaper.po b/es-ES/vnc_VNC_Whitepaper.po
index 17f4cc2..9e51703 100644
--- a/es-ES/vnc_VNC_Whitepaper.po
+++ b/es-ES/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/fa/vnc_VNC_Whitepaper.po b/fa/vnc_VNC_Whitepaper.po
index eedaa0c..82971ea 100644
--- a/fa/vnc_VNC_Whitepaper.po
+++ b/fa/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-28 01:51+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-28 01:51+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/fr-FR/vnc_VNC_Whitepaper.po b/fr-FR/vnc_VNC_Whitepaper.po
index 004bfd6..f43c4c3 100644
--- a/fr-FR/vnc_VNC_Whitepaper.po
+++ b/fr-FR/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/gu-IN/vnc_VNC_Whitepaper.po b/gu-IN/vnc_VNC_Whitepaper.po
index 42f45bb..38dc163 100644
--- a/gu-IN/vnc_VNC_Whitepaper.po
+++ b/gu-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/hi-IN/vnc_VNC_Whitepaper.po b/hi-IN/vnc_VNC_Whitepaper.po
index 4400dfd..215fa4a 100644
--- a/hi-IN/vnc_VNC_Whitepaper.po
+++ b/hi-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/hu/vnc_VNC_Whitepaper.po b/hu/vnc_VNC_Whitepaper.po
index 7e3e8bf..8b61e50 100644
--- a/hu/vnc_VNC_Whitepaper.po
+++ b/hu/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/id/vnc_VNC_Whitepaper.po b/id/vnc_VNC_Whitepaper.po
index ee131b1..7d988ab 100644
--- a/id/vnc_VNC_Whitepaper.po
+++ b/id/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/it-IT/vnc_VNC_Whitepaper.po b/it-IT/vnc_VNC_Whitepaper.po
index e4adeb2..86726ce 100644
--- a/it-IT/vnc_VNC_Whitepaper.po
+++ b/it-IT/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/ja-JP/vnc_VNC_Whitepaper.po b/ja-JP/vnc_VNC_Whitepaper.po
index 8e51145..ea809d6 100644
--- a/ja-JP/vnc_VNC_Whitepaper.po
+++ b/ja-JP/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/kn-IN/vnc_VNC_Whitepaper.po b/kn-IN/vnc_VNC_Whitepaper.po
index 25df6a8..09f9576 100644
--- a/kn-IN/vnc_VNC_Whitepaper.po
+++ b/kn-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/ko-KR/vnc_VNC_Whitepaper.po b/ko-KR/vnc_VNC_Whitepaper.po
index 987c6d0..a4e0343 100644
--- a/ko-KR/vnc_VNC_Whitepaper.po
+++ b/ko-KR/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/lv/vnc_VNC_Whitepaper.po b/lv/vnc_VNC_Whitepaper.po
index 3c5fab3..bb0657f 100644
--- a/lv/vnc_VNC_Whitepaper.po
+++ b/lv/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -22,11 +22,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -34,35 +39,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -70,24 +62,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/ml-IN/vnc_VNC_Whitepaper.po b/ml-IN/vnc_VNC_Whitepaper.po
index a96789a..660ce71 100644
--- a/ml-IN/vnc_VNC_Whitepaper.po
+++ b/ml-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/mr-IN/vnc_VNC_Whitepaper.po b/mr-IN/vnc_VNC_Whitepaper.po
index 91cedb0..7a97b17 100644
--- a/mr-IN/vnc_VNC_Whitepaper.po
+++ b/mr-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/ms/vnc_VNC_Whitepaper.po b/ms/vnc_VNC_Whitepaper.po
index d716721..8b93685 100644
--- a/ms/vnc_VNC_Whitepaper.po
+++ b/ms/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/nb/vnc_VNC_Whitepaper.po b/nb/vnc_VNC_Whitepaper.po
index c3e6463..6bfa6c3 100644
--- a/nb/vnc_VNC_Whitepaper.po
+++ b/nb/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/nl/vnc_VNC_Whitepaper.po b/nl/vnc_VNC_Whitepaper.po
index f47636f..e0e0e7e 100644
--- a/nl/vnc_VNC_Whitepaper.po
+++ b/nl/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/or-IN/vnc_VNC_Whitepaper.po b/or-IN/vnc_VNC_Whitepaper.po
index 8cdb96e..094532b 100644
--- a/or-IN/vnc_VNC_Whitepaper.po
+++ b/or-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/pa-IN/vnc_VNC_Whitepaper.po b/pa-IN/vnc_VNC_Whitepaper.po
index 77d298b..013b77c 100644
--- a/pa-IN/vnc_VNC_Whitepaper.po
+++ b/pa-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/pl/vnc_VNC_Whitepaper.po b/pl/vnc_VNC_Whitepaper.po
index 7d18f9c..c2c54ec 100644
--- a/pl/vnc_VNC_Whitepaper.po
+++ b/pl/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -22,11 +22,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -34,35 +39,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -70,24 +62,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/po/install-guide.pot b/po/install-guide.pot
index 52e0bed..f6b3042 100644
--- a/po/install-guide.pot
+++ b/po/install-guide.pot
@@ -5507,7 +5507,7 @@ msgstr ""
"#-#-#-#-# vnc_VNC_Whitepaper.pot (PACKAGE VERSION) #-#-#-#-#\n"
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-28 06:44+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -33251,11 +33251,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33263,35 +33268,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
-#, no-c-format
-msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -33299,26 +33291,27 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
#. Tag: title
diff --git a/pot/vnc_VNC_Whitepaper.pot b/pot/vnc_VNC_Whitepaper.pot
index 5242b5a..6155dc2 100644
--- a/pot/vnc_VNC_Whitepaper.pot
+++ b/pot/vnc_VNC_Whitepaper.pot
@@ -6,7 +6,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-28 06:44+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL at ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc at kde.org>\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/pt-BR/vnc_VNC_Whitepaper.po b/pt-BR/vnc_VNC_Whitepaper.po
index 579769e..0edaae5 100644
--- a/pt-BR/vnc_VNC_Whitepaper.po
+++ b/pt-BR/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/pt/vnc_VNC_Whitepaper.po b/pt/vnc_VNC_Whitepaper.po
index 087752f..a2828a6 100644
--- a/pt/vnc_VNC_Whitepaper.po
+++ b/pt/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/ru-RU/vnc_VNC_Whitepaper.po b/ru-RU/vnc_VNC_Whitepaper.po
index a9e2986..0711065 100644
--- a/ru-RU/vnc_VNC_Whitepaper.po
+++ b/ru-RU/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/si-LK/vnc_VNC_Whitepaper.po b/si-LK/vnc_VNC_Whitepaper.po
index d11c3a3..fd9245d 100644
--- a/si-LK/vnc_VNC_Whitepaper.po
+++ b/si-LK/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/sr-LATN/vnc_VNC_Whitepaper.po b/sr-LATN/vnc_VNC_Whitepaper.po
index 0bb92da..e86f7fb 100644
--- a/sr-LATN/vnc_VNC_Whitepaper.po
+++ b/sr-LATN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/sr/vnc_VNC_Whitepaper.po b/sr/vnc_VNC_Whitepaper.po
index d34d50d..b259831 100644
--- a/sr/vnc_VNC_Whitepaper.po
+++ b/sr/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -22,11 +22,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -34,35 +39,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -70,24 +62,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/sv/vnc_VNC_Whitepaper.po b/sv/vnc_VNC_Whitepaper.po
index 6a9e1b1..609fe86 100644
--- a/sv/vnc_VNC_Whitepaper.po
+++ b/sv/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -21,11 +21,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -33,35 +38,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -69,24 +61,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/ta-IN/vnc_VNC_Whitepaper.po b/ta-IN/vnc_VNC_Whitepaper.po
index 5451ce5..0dc6344 100644
--- a/ta-IN/vnc_VNC_Whitepaper.po
+++ b/ta-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/te-IN/vnc_VNC_Whitepaper.po b/te-IN/vnc_VNC_Whitepaper.po
index e6e107b..45806b0 100644
--- a/te-IN/vnc_VNC_Whitepaper.po
+++ b/te-IN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/zh-CN/vnc_VNC_Whitepaper.po b/zh-CN/vnc_VNC_Whitepaper.po
index 0d4e479..c420c9a 100644
--- a/zh-CN/vnc_VNC_Whitepaper.po
+++ b/zh-CN/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
diff --git a/zh-TW/vnc_VNC_Whitepaper.po b/zh-TW/vnc_VNC_Whitepaper.po
index c520dd4..e8da055 100644
--- a/zh-TW/vnc_VNC_Whitepaper.po
+++ b/zh-TW/vnc_VNC_Whitepaper.po
@@ -5,7 +5,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Installation_Guide VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2009-04-01 19:05+0000\n"
+"POT-Creation-Date: 2009-04-28 20:43+0000\n"
"PO-Revision-Date: 2009-04-01 19:05+0000\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
@@ -20,11 +20,16 @@ msgid "Installing Through VNC"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:8
+#: vnc_VNC_Whitepaper.xml:9
#, no-c-format
msgid ""
-"Many enterprise customers perform interactive installations on systems in "
-"datacenters. These systems are often, but not always, installed in a rack "
+"The Red Hat Enterprise Linux and Fedora installer (<application>anaconda</"
+"application>) offers you two interactive modes of operation. The original "
+"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
+"Window environment. This chapter explains how you can use the graphical "
+"installation mode in environments where the system lacks a proper display "
+"and input devices typically associated with a workstation. This scenario is "
+"typical of systems in datacenters, which are often installed in a rack "
"environment and do not have a display, keyboard, or mouse. Additionally, a "
"lot of these systems even lack the ability to connect a graphical display. "
"Given that enterprise hardware rarely needs that ability at the physical "
@@ -32,35 +37,22 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:19
+#: vnc_VNC_Whitepaper.xml:26
#, no-c-format
msgid ""
-"The <application>Red Hat Enterprise Linux</application> (RHEL) and "
-"<application>Fedora Linux</application> installer (<application>anaconda</"
-"application>) offers users two interactive modes of operation. The original "
-"mode is a text-based interface. The newer mode uses GTK+ and runs in the X "
-"Window environment. The purpose of this document is to explain how the "
-"graphical installation mode can be used in enterprise environments, even "
-"when the system lacks a proper display and input devices typically "
-"associated with a workstation."
+"Even in these environments, however, the graphical installer remains the "
+"recommended method of installation. The text mode environment lacks a lot of "
+"capabilities found in the graphical mode. Many users still feel that the "
+"text mode interface provides them with additional power or configuration "
+"ability not found in the graphical version. The opposite is true. Much less "
+"development effort is put in to the text-mode environment and specific "
+"things (for example, LVM configuration, partition layout, package selection, "
+"and bootloader configuration) are deliberately left out of the text mode "
+"environment. The reasons for this are:"
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:32
-#, no-c-format
-msgid ""
-"The primary driver behind the document is to encourage use of the graphical "
-"installer, even in enterprise environments. The text mode environment lacks "
-"a lot of capabilities found in the graphical mode. Many users still feel "
-"that the text mode interface provides them with additional power or "
-"configuration ability not found in the graphical version. The opposite is "
-"true. Much less development effort is put in to the text mode environment "
-"and specific things (e.g., LVM configuration) are deliberately left out of "
-"the text mode environment. The reasons for this are:"
-msgstr ""
-
-#. Tag: para
-#: vnc_VNC_Whitepaper.xml:47
+#: vnc_VNC_Whitepaper.xml:42
#, no-c-format
msgid ""
"Less screen real estate for creating user interfaces similar to those found "
@@ -68,24 +60,25 @@ msgid ""
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:54
+#: vnc_VNC_Whitepaper.xml:49
#, no-c-format
msgid "Difficult internationalization support."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:59
+#: vnc_VNC_Whitepaper.xml:54
#, no-c-format
msgid "Desire to maintain a single interactive installation code path."
msgstr ""
#. Tag: para
-#: vnc_VNC_Whitepaper.xml:66
+#: vnc_VNC_Whitepaper.xml:61
#, no-c-format
msgid ""
-"All of these reasons and more are why you, the enterprise customer, should "
-"be making using of the <application>Virtual Network Computing</application> "
-"(VNC) mode offered in <application>anaconda</application>. VNC allows the "
-"graphical mode of the installer to run locally, but display on a system "
-"connected to the network."
+"<application>Anaconda</application> therefore includes a "
+"<application>Virtual Network Computing</application> (VNC) mode that allows "
+"the graphical mode of the installer to run locally, but display on a system "
+"connected to the network. Installing in VNC mode provides you with the full "
+"range of installation options, even in situations where the system lacks a "
+"display or input devices."
msgstr ""
More information about the Fedora-docs-commits
mailing list