function quickHelp()
{
    ob_start();
    ?>
<h3 style="font: Arial"><font size="3" face="Arial" color="black">What you should know about the new <b>Dolphin</b> language management system.</font></h3>
<font size="2" face="Arial" color="black">
The new <b>Dolphin</b> language management system is developed to ease your work with language
strings by managing them via this specially designed web interface rather than editing them directly
in a language file, unlike it was in previous <b>Dolphin</b> versions. Note that, in <b>Dolphin</b>,
you should <b>NOT</b> edit language files manually – they’re now used by
the script as temporary files with partial language information only for the sake of performance.
All necessary language information is now stored in the database and can be managed via this web interface.
<br /><br />
You can see an option of compiling languages in the top section of the language management interface.
<b>Compiling a language</b> means creating and writing a fresh version of a corresponding language file
in the <b>langs</b> folder of the script with the updated information about language strings and keys
stored in the database. After you change/add a language string or a language key, a corresponding language
file (or files) needs to be recompiled so the changes are applied and shown on the pages where that string
is used. At the bottom of the forms for editing and adding language strings/keys there are checkboxes that
specify whether to recompile corresponding language files automatically after the changes are saved. These
checkboxes are checked by default. You can uncheck them before submitting a form not to recompile language
files every time in case you’re editing a lot of language strings one by one. This option is available
because compiling a language file is a relatively resource-intensive process, so you better recompile
language files once after you’ve finished with editing language strings rather than loading your server by
recompiling language files after editing each string.</font>

<?php 
    $contents = ob_get_contents();
    ob_end_clean();
    return PopupPageTemplate('Language Management System Notes', $contents);
}
/**
 * Prints payment provider setup help message
 *
 * @param int $providerID				- payment provider ID
 *
 * @return string 						- HTML content of help body
 *
 *
 */
function PPShowHelp($providerID)
{
    $styles = <<<EOS
\tp.help_text
\t{
\t\tfont-family: Arial;
\t\tfont-size: small;
\t\tfont-weight: normal;
\t\tcolor: black;
\t\ttext-align: justify;
\t}

\tp.help_caption
\t{
\t\tfont-family: Arial;
\t\tfont-size: medium;
\t\tfont-weight: bold;
\t\tcolor: black;
\t\ttext-align: left;
\t}
EOS;
    ob_start();
    $providerRes = db_res("SELECT `Caption`, `Help` FROM `PaymentProviders` WHERE `ID` = {$providerID}");
    $providerArr = mysql_fetch_assoc($providerRes);
    ?>
<h3 style="font-family: Arial; font-size: large; font-weight: normal; color: black;"><b><?php 
    echo process_line_output($providerArr['Caption']);
    ?>
</b> setup instructions</h3>
<?php 
    echo process_html_output($providerArr['Help'], 255);
    $content = ob_get_contents();
    ob_end_clean();
    return PopupPageTemplate('Payment provider setup instructions', $content, '', $styles);
}