# translation of artsbuilder_helping.po to 
# translation of artsbuilder_helping.po to
# translation of artsbuilder_helping.po to
# Copyright (C) 2002 Free Software Foundation, Inc.
# Lwandle Mgidlana <lwandle@translate.org.za>, 2002
#
msgid ""
msgstr ""
"Project-Id-Version: artsbuilder_helping\n"
"POT-Creation-Date: 2001-02-09 01:25+0100\n"
"PO-Revision-Date: 2002-09-26 12:34+0200\n"
"Last-Translator: Lwandle Mgidlana <lwandle@translate.org.za>\n"
"Language-Team:  <xh@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-xml2pot; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.0beta2\n"

#: index.docbook:7
#, no-c-format
msgid "Contributing to &arts;"
msgstr ""

#: index.docbook:10
#, no-c-format
msgid "How You Can Help"
msgstr ""

#: index.docbook:12
#, no-c-format
msgid ""
"The &arts; project can use help from developers to make existing multimedia "
"applications &arts;-aware, write new multimedia applications, and enhance "
"the capabilities of &arts;. However, you don't have to be a developer to "
"contribute. We can also use help from testers to submit bug reports, "
"translators to translate the application text and documentation into other "
"languages, artists to design bitmaps (especially for "
"<application>artsbuilder</application> modules), musicians to create sample "
"&arts; modules, and writers to write or proofread documentation."
msgstr ""

#: index.docbook:25
#, no-c-format
msgid "Mailing Lists"
msgstr ""

#: index.docbook:27
#, no-c-format
msgid ""
"Most development discussions on &arts; take place on two mailing lists. This "
"is the place to discuss new feature and implementation ideas or ask for help "
"with problems."
msgstr ""

#: index.docbook:33
#, no-c-format
msgid ""
"The &kde; Multimedia mailing list is for general &kde; multimedia issues "
"including &arts; as well as the multimedia applications like &noatun; and "
"&aktion;. You can subscribe from the web page at <ulink "
"url=\"http://www.kde.org/mailinglists.html\"> "
"http://www.kde.org/mailinglists.html</ulink> or send an email with the "
"subject set to <userinput>subscribe "
"<replaceable>your-email-address</replaceable></userinput> to "
"<email>kde-multimedia-request@kde.org</email>. The list is also archived at "
"<ulink url=\"http://lists.kde.org\"> http://lists.kde.org</ulink>."
msgstr ""

#: index.docbook:45
#, no-c-format
msgid ""
"The &arts; mailing list is for issues specific to &arts;, including "
"non-&kde; use of &arts;. To subscribe, send an email containing the message "
"body <userinput>subscribe "
"<replaceable>your-email-address</replaceable></userinput> to "
"<email>arts-request@space.twc.de</email>. The list is archived at <ulink "
"url=\"http://space.twc.de/~stefan/arts-archive\"> "
"http://space.twc.de/~stefan/arts-archive</ulink>."
msgstr ""

#: index.docbook:58
#, no-c-format
msgid "Coding Standards"
msgstr ""

#: index.docbook:60
#, no-c-format
msgid ""
"For getting a consistent reading through all the sources, it is important to "
"keep the coding style the same, all over the &arts; source. Please, even if "
"you just write a module, try to write/format your source accordingly, as it "
"will make it easier for different people to maintain the source tree, and "
"easier to copy pieces of from one source to another."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Naming of member functions"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"&Qt;/&Java; style. That means capitalization on word breaks, and first "
"letter always without capitalization; no underscores."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "This means for instance:"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"createStructureDesc()\n"
"   updateWidget();\n"
"   start();"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Class members"
msgstr "Amalungu odidi"

#: index.docbook:69
#, no-c-format
msgid "Class members are not capitalized, such as menubar or button."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"When there are accessing functions, the standard should be the &MCOP; way, "
"that is, when having an long member <function>foo</function>, which "
"shouldn't be visible directly, you create:"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"foo(long new_value);\n"
"   long foo();"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"functions to get and set the value. In that case, the real value of "
"<function>foo</function> should be stored in "
"<returnvalue>&lowbar;foo</returnvalue>."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Class names"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"All classes should be wordwise capitalized, that means "
"<classname>ModuleView</classname>, <classname>SynthModule</classname>. All "
"classes that belong to the libraries should use the &arts; namespace, like "
"<classname>Arts::Soundserver</classname>."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"The implementations of &MCOP; classes should get called "
"<classname>Class&lowbar;impl</classname>, such as "
"<classname>SoundServer&lowbar;impl</classname>."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Parameters"
msgstr "Parameters"

#: index.docbook:69
#, no-c-format
msgid "Parameters are always uncapitalized."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Local variables"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"Local variables are always uncapitalized, and may have names like "
"<varname>i</varname>, <varname>p</varname>, <varname>x</varname>, &etc; "
"where appropriate."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Tab width (Shift width)"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "One tab is as long as 4 spaces."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Spaces in expressions"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"You normally don't need to use spaces in expressions. You can however use "
"them between operator and their operands. However, if you put a space before "
"an operator (i.e. +), you also need to put a space after the operator. The "
"only exception to this are list-like expressions (with ,), where you should "
"only put a space after the \",\", but not before. It's okay to omit the "
"space here, too."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "The following examples demonstrate good use of spaces:"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"{\n"
"    int a,b;\n"
"    int c, d, e;\n"
"    int f = 4;\n"
"\n"
"    a=b=c=d+e+f;\n"
"    a = b = c = d + e + f;\n"
"\n"
"    if(a == 4) {\n"
"        a = b = c = (d+e)/2;\n"
"    }\n"
"\n"
"    while(b&lt;3)\n"
"        c--;\n"
"\n"
"    arts_debug(\"%d\\n\", c);\n"
"}"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"The following examples demonstrate how <emphasis>not</emphasis> to use "
"spaces. For function calls, after if, while, for, switch and so on, no space "
"is being written."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"{\n"
"    // BAD: if you write a list, write spaces only after the \",\"\n"
"    int a , b , c , d , e , f;\n"
"\n"
"    // BAD: non-symmetric use of spaces for = operator\n"
"    a= 5;\n"
"\n"
"    // BAD: if is considered a function, and isn't followed by a space\n"
"    if (a == 5) {   \n"
"    }\n"
"\n"
"    // BAD: don't write a space after while\n"
"    while (a--)\n"
"        b++; \n"
"\n"
"    // BAD: functions names are not followed by a space\n"
"    arts_debug (\"%d\\n\", c);\n"
"\n"
"    // BAD: neither are member names\n"
"    Arts::Object o = Arts::Object::null ();\n"
"}"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid "Naming of source files"
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"Source files should have no capitalization in the name. They should have the "
"name of the class when they implement a single class. Their extension is "
"<literal role=\"extension\">.cc</literal> if they refer to &Qt;/&GUI; "
"independant code, and <literal role=\"extension\">.cpp</literal> if they "
"refer to &Qt;/&GUI; dependant code. Implementation files for interfaces "
"should be called <filename><replaceable>foo</replaceable>_impl</filename>, "
"if Foo was the name of the interface."
msgstr ""

#: index.docbook:69
#, no-c-format
msgid ""
"&IDL; files should be called in a descriptive way for the collection of "
"interfaces they contain, also all lower case. Especially it is not good to "
"call an &IDL; file like the class itself, as the .mcopclass trader and type "
"info entries will collide, then."
msgstr ""
