diff options
| -rw-r--r-- | help_text.php | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/help_text.php b/help_text.php index 3a8c3af4f9..ff044de7ea 100644 --- a/help_text.php +++ b/help_text.php @@ -4013,7 +4013,7 @@ case 'header': case 'header_search': $title=i18n::translate('Search box'); - $text=i18n::translate('This Search box is small but powerful. You can have <b>webtrees</b> search almost anything for you. When you click the <b>></b> or <b>Search</b> button, you will be linked to the Search page to see the results of your search. You will find extensive help about searching options on the Search page.'); + $text=i18n::translate('This Search box is small but powerful. You can have <b>webtrees</b> search almost anything for you. When you click the <b>></b> or <b>Search</b> button, you will be linked to the Search page to see the results of your search. You will find extensive help about searching options on the Search page.'); break; case 'header_theme': @@ -4183,7 +4183,7 @@ case 'index_favorites': case 'index_gedcom_news_adm': $title=i18n::translate('GEDCOM news block HTML'); - $text=i18n::translate('The GEDCOM News text allows the use of <b>HTML tags</b> and <b>HTML entities</b>. HTML should not be used in News titles.<br /><br />Be sure to always use both start and end tags. It may help to have an understanding of HTML appropriate for a web site administrator. This program uses <b>Cascading Style Sheets (CSS)</b> as well. A different CSS is implemented for each theme. You can use classes from these style sheets to control the appearance of your messages.<br /><br />If you need more help with this, the <b>webtrees</b> web site has some examples of how to use these tags in your GEDCOM News block.<br /><br />As with the FAQ list, GEDCOM News titles and News text allow embedded references to $pgv_lang, $factarray, and $GLOBALS variables to provide complete flexibility in the creation of News items that are sensitive to the currently active language.<br /><br />The following description, taken from the Help text for the FAQ list, is equally applicable to GEDCOM News items.<br /><br />HTML entities are a very easy way to add special characters to your FAQ titles and text. You can use symbolic names, decimal numbers, or hexadecimal numbers. A complete list of HTML entities, their coding, and their representation by your browser can be found here: <a href="http://htmlhelp.com/reference/html40/entities/" target="_blank">HTML entity lists</a><br /><br />On occasion, you may need to show a Tilde character <b>~</b> or a Number Sign <b>#</b> in your URLs or text. These characters have a special meaning to the <b>webtrees</b> Help system and can only be entered in their hexadecimal or decimal form. Similarly, the <b><</b> and <b>></b> characters that usually enclose HTML tags must be entered in their hexadecimal or decimal forms if they are to be treated as normal text instead of signalling an HTML tag.<ul><li><b>&#35;</b> or <b>&#x23;</b> will result in <b>#</b></li><li><b>&#60;</b> or <b>&#x3C;</b> will result in <b><</b></li><li><b>&#62;</b> or <b>&#x3E;</b> will result in <b>></b></li><li><b>&#126;</b> or <b>&#x7E;</b> will result in <b>~</b></li></ul>There is a <b>&tilde;</b> HTML entity, but this symbol is not interpreted as a Tilde when coded in URLs.<br /><br />You can insert references to entries in the language files or to values of global variables. Examples: <ul><li><b>#pgv_lang[add_to_cart]#</b> is a reference to the language variable "Add to Clippings Cart", and if it were to appear in this field, would show as <b>Add to Clippings Cart</b> when the FAQ list is viewed in the current language.</li><li><b>#factarray[AFN]#</b> is a reference to the Fact name $factarray["AFN"], and if it were to appear in this field, would show as <b>Ancestral File Number (AFN)</b> when the FAQ list is viewed in the current language. </li><li><b>#WT_VERSION# #WT_VERSION_RELEASE#</b> is a reference to the constant WT_VERSION, a space, and a reference to the constant WT_VERSION_RELEASE, and if they were to appear in this field, would show as <b>#WT_VERSION# #WT_VERSION_RELEASE#</b> when the FAQ list is viewed in the current language.</li><li><b>#GLOBALS[GEDCOM]#</b> is a reference to the global variable $GEDCOM, which is the name of the current GEDCOM file. If it were to appear in this field, it would show as <b>#GLOBALS[GEDCOM]#</b>.</li><li><b>#GLOBALS[GEDCOM_TITLE]#</b> is a reference to the global variable $GEDCOM_TITLE, which is the title of the current GEDCOM file. If it were to appear in this field, it would show as <b>#GLOBALS[GEDCOM_TITLE]#</b>.</li></uli></ul><br />This feature is useful when you wish to create FAQ lists that are different for each language your site supports. You should put your customized FAQ list titles and entries into the <i>languages/extra.xx.php</i> files (<i>xx</i> is the code for each language), using the following format:<br />$pgv_lang["faq_title1"] = "This is a sample FAQ title";<br />$pgv_lang["faq_body1"] = "This is a sample FAQ body.";'); + $text=i18n::translate('The GEDCOM News text allows the use of <b>HTML tags</b> and <b>HTML entities</b>. HTML should not be used in News titles.<br /><br />Be sure to always use both start and end tags. It may help to have an understanding of HTML appropriate for a web site administrator. This program uses <b>Cascading Style Sheets (CSS)</b> as well. A different CSS is implemented for each theme. You can use classes from these style sheets to control the appearance of your messages.<br /><br />If you need more help with this, the <b>webtrees</b> web site has some examples of how to use these tags in your GEDCOM News block.<br /><br />As with the FAQ list, GEDCOM News titles and News text allow embedded references to $pgv_lang, $factarray, and $GLOBALS variables to provide complete flexibility in the creation of News items that are sensitive to the currently active language.<br /><br />The following description, taken from the Help text for the FAQ list, is equally applicable to GEDCOM News items.<br /><br />HTML entities are a very easy way to add special characters to your FAQ titles and text. You can use symbolic names, decimal numbers, or hexadecimal numbers. A complete list of HTML entities, their coding, and their representation by your browser can be found here: <a href="http://htmlhelp.com/reference/html40/entities/" target="_blank">HTML entity lists</a><br /><br />On occasion, you may need to show a Tilde character <b>~</b> or a Number Sign <b>#</b> in your URLs or text. These characters have a special meaning to the <b>webtrees</b> Help system and can only be entered in their hexadecimal or decimal form. Similarly, the <b><</b> and <b>></b> characters that usually enclose HTML tags must be entered in their hexadecimal or decimal forms if they are to be treated as normal text instead of signalling an HTML tag.<ul><li><b>&#35;</b> or <b>&#x23;</b> will result in <b>#</b></li><li><b>&#60;</b> or <b>&#x3C;</b> will result in <b><</b></li><li><b>&#62;</b> or <b>&#x3E;</b> will result in <b>></b></li><li><b>&#126;</b> or <b>&#x7E;</b> will result in <b>~</b></li></ul>There is a <b>&tilde;</b> HTML entity, but this symbol is not interpreted as a Tilde when coded in URLs.<br /><br />You can insert references to entries in the language files or to values of global variables. Examples: <ul><li><b>#pgv_lang[add_to_cart]#</b> is a reference to the language variable "Add to Clippings Cart", and if it were to appear in this field, would show as <b>Add to Clippings Cart</b> when the FAQ list is viewed in the current language.</li><li><b>#factarray[AFN]#</b> is a reference to the Fact name $factarray["AFN"], and if it were to appear in this field, would show as <b>Ancestral File Number (AFN)</b> when the FAQ list is viewed in the current language. </li><li><b>#WT_VERSION# #WT_VERSION_RELEASE#</b> is a reference to the constant WT_VERSION, a space, and a reference to the constant WT_VERSION_RELEASE, and if they were to appear in this field, would show as <b>#WT_VERSION# #WT_VERSION_RELEASE#</b> when the FAQ list is viewed in the current language.</li><li><b>#GLOBALS[GEDCOM]#</b> is a reference to the global variable $GEDCOM, which is the name of the current GEDCOM file. If it were to appear in this field, it would show as <b>#GLOBALS[GEDCOM]#</b>.</li><li><b>#GLOBALS[GEDCOM_TITLE]#</b> is a reference to the global variable $GEDCOM_TITLE, which is the title of the current GEDCOM file. If it were to appear in this field, it would show as <b>#GLOBALS[GEDCOM_TITLE]#</b>.</li></ul></ul><br />This feature is useful when you wish to create FAQ lists that are different for each language your site supports. You should put your customized FAQ list titles and entries into the <i>languages/extra.xx.php</i> files (<i>xx</i> is the code for each language), using the following format:<br />$pgv_lang["faq_title1"] = "This is a sample FAQ title";<br />$pgv_lang["faq_body1"] = "This is a sample FAQ body.";'); break; case 'index_gedcom_news': @@ -4696,7 +4696,7 @@ case 'rss_feed': case 'search': $title=i18n::translate('Search information'); - $text=i18n::translate('This search box is small but powerful. You can have <b>webtrees</b> search almost anything for you. When you click the <b>></b> or <b>Search</b> button, you will be linked to the Search page to see the results of your search. You will find extensive help about searching options on the Search page.<ul><li><a href="?help=search.php">Search page</a></li><li><a href="?help=search_enter_terms">Enter search terms</a></li><li><a href="?help=soundex_search">Soundex search</a></li><li><a href="?help=search_replace">Search and replace</a></li></ul>'); + $text=i18n::translate('This search box is small but powerful. You can have <b>webtrees</b> search almost anything for you. When you click the <b>></b> or <b>Search</b> button, you will be linked to the Search page to see the results of your search. You will find extensive help about searching options on the Search page.<ul><li><a href="?help=search.php">Search page</a></li><li><a href="?help=search_enter_terms">Enter search terms</a></li><li><a href="?help=soundex_search">Soundex search</a></li><li><a href="?help=search_replace">Search and replace</a></li></ul>'); break; case 'search_enter_terms': @@ -4856,7 +4856,7 @@ case 'style': case 'talloffset': $title=i18n::translate('Page layout'); - $text=i18n::translate('With this option you determine the page layout orientation.<br /><br />Changing this setting might be useful if you want to make a screen print or if you have a different type of screen.<ul><li><b>Portrait</b> mode will make the tree taller, such that a 4 generation chart should fit on a single page printed vertically.</li><li><b>Landscape</b> mode will make a wider tree that should print on a single page printed horizontally.</li><li><b>Oldest at top</b> mode rotates the chart, but not its boxes, by 90 degrees counter-clockwise, so that the oldest generation is at the top of the chart.</li><li><b>Oldest at bottom</b> mode rotates the chart, but not its boxes, by 90 degrees clockwise, so that the oldest generation is at the bottom of the chart.</li></ul'); + $text=i18n::translate('With this option you determine the page layout orientation.<br /><br />Changing this setting might be useful if you want to make a screen print or if you have a different type of screen.<ul><li><b>Portrait</b> mode will make the tree taller, such that a 4 generation chart should fit on a single page printed vertically.</li><li><b>Landscape</b> mode will make a wider tree that should print on a single page printed horizontally.</li><li><b>Oldest at top</b> mode rotates the chart, but not its boxes, by 90 degrees counter-clockwise, so that the oldest generation is at the top of the chart.</li><li><b>Oldest at bottom</b> mode rotates the chart, but not its boxes, by 90 degrees clockwise, so that the oldest generation is at the bottom of the chart.</li></ul>'); break; case 'timeline_control': |