mk Tue Feb 5 13:42:13 2002 EDT
Added files:
/phpdoc/de/faq languages.xml
Modified files:
/phpdoc/de Translators
Log:
Started translation of faq/languages.xml
Index: phpdoc/de/Translators
diff -u phpdoc/de/Translators:1.257 phpdoc/de/Translators:1.258
--- phpdoc/de/Translators:1.257 Sat Feb 2 18:28:03 2002
+++ phpdoc/de/Translators Tue Feb 5 13:42:12 2002
@@ -52,6 +52,8 @@
intro.xml Michael Kaiser fertig
security.xml Catharina Paulsen
Thomas Sch�fbeck fertig (bis v1.23)
+------- chmonly -------------------------------------------------------------
+aboutchm.xml Mark Kronsbein fertig (bis 1.1)
------- faq -----------------------------------------------------------------
build.xml
com.xml
@@ -59,7 +61,7 @@
general.xml
html.xml
installation.xml
-languages.xml
+languages.xml Mark Kronsbein in Arbeit
mailinglist.xml
migration.xml Mark Kronsbein fertig (bis 1.9)
migration4.xml Mark Kronsbein fertig (bis 1.8)
Index: phpdoc/de/faq/languages.xml
+++ phpdoc/de/faq/languages.xml
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.1 $ -->
<!-- EN-Revision: 1.9 Maintainer: mk Status: working -->
<chapter id="faq.languages">
<title>PHP und andere Sprachen</title>
<titleabbrev>PHP und andere Sprachen</titleabbrev>
<para>
PHP ist die beste Sprache f�r Webanwendungen,
aber was ist mit anderen Sprachen?
</para>
<qandaset>
<qandaentry id="faq.languages.asp">
<question>
<para>PHP vs. ASP?</para>
</question>
<answer>
<para>
ASP ist eigentlich keine Sprache ansich, es ist ein Akronym f�r Active
Server Pages, die eigentlichen Sprachen in denen ASP programmiert wird sind
Visual Basic Script oder JScript. Der gr��te Nachteil von ASP ist, da�
es ein propriet�res System ist und nativ nur auf Microsofts
Internet Information Server (IIS) verwendet werden kann. Dies limitiert ASP auf
Win32 basierende Server. Es gibt einige Projekte, die die M�glichkeit bieten,
ASP unter anderen Umgebungen zu verwenden:
<ulink url="&faqurl.instantasp;">InstantASP</ulink>
von <ulink url="&faqurl.halcyon;">Halcyon</ulink> (kommerziell),
<ulink url="&faqurl.chilisoft.asp;">Chili!Soft ASP</ulink> von
<ulink url="&faqurl.chilisoft;">Chili!Soft</ulink>
(kommerziell) und <ulink url="&faqurl.openasp;">OpenASP von
ActiveScripting.org</ulink> (kostenlos). ASP wird nachgesagt, da�
es eine langsamere und schwerf�lligere Sprache als PHP ist, instabiler
noch dazu.Eines der Vorteile von ASP ist, da� es, weil VBScript verwendet wird,
relativ licht zu erlernen ist, wenn Sie bereits Visual Basic programmieren
k�nnen. Auch ist die ASP-Unterst�tzung im IIS Server standardm��ig vorhanden,
was es einfach macht, ASP zum laufen zu kriegen. Der Umfang von ASP ist
allerdings sehr limitiert. Wenn Sie also "fortgeschrittene" Features wie die
Verbindung zu FTP-Servern nutzen wollen, m�ssen Sie kommerzielle Komponenten
hinzukaufen.
</para>
</answer>
</qandaentry>
<qandaentry id="faq.languages.aspconverter">
<question>
<para>Gibt es eine Programm, was ASP in PHP konvertieren kann?</para>
</question>
<answer>
<para>
Ja, <ulink url="&faqurl.asp2php;">asp2php</ulink> wird
meistens als Antwort genannt.
</para>
</answer>
</qandaentry>
<qandaentry id="faq.languages.coldfusion">
<question>
<para>PHP vs. Cold Fusion?</para>
</question>
<answer>
<para>
PHP is commonly said to be faster and more efficient for complex
programming tasks and trying out new ideas. PHP is generally referred
to as more stable and less resource intensive as well. Cold Fusion
has better error handling, database abstraction and date parsing
although database abstraction is addressed in PHP 4. Another
thing that is listed as one of Cold Fusion's strengths is its excellent
search engine, but it has been mentioned that a search engine is not
something that should be included in a web scripting language. PHP
runs on almost every platform there is; Cold Fusion is only available
on Win32, Solaris, Linux and HP/UX. Cold Fusion has a good IDE
and is generally easier to get started with, whereas PHP initially
requires more programming knowledge. Cold Fusion is designed with
non-programmers in mind, while PHP is focused on programmers.
</para>
<para>
A great summary by Michael J Sheldon on this topic has
been posted to the PHP mailing list. A copy can be found
<ulink url="&faqurl.coldfusion.summary;">here</ulink>.
</para>
</answer>
</qandaentry>
<qandaentry id="faq.languages.perl">
<question>
<para>PHP vs. Perl?</para>
</question>
<answer>
<para>
The biggest advantage of PHP over Perl is that PHP was designed for
scripting for the web where Perl was designed to do a lot more and can
because of this get very complicated. The flexibility / complexity
of Perl makes it easier to write code that another author / coder
has a hard time reading. PHP has a less confusing and stricter format
without losing flexibility. PHP is easier to integrate into existing
HTML than Perl. PHP has pretty much all the 'good' functionality of
Perl: constructs, syntax and so on, without making it as complicated
as Perl can be. Perl is a very tried and true language, it's been
around since the late eighties, but PHP is maturing very quickly.
</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"../../manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->
