Projects/kde.org/Capacity HOWTO - Revision history

Sheedy: URL chan

2012-11-29T19:11:36Z

URL chan

Sheedy: Note URL correction

2012-11-28T22:51:06Z

Note URL correction

Neverendingo: Text replace - "`" to ""`


2011-06-29T21:05:47Z
Text replace - "<code html4strict>" to "<syntaxhighlight lang="html4strict">"

				
				
				
				
			
			← Older revision
			Revision as of 21:05, 29 June 2011
			
Line 172:
Line 172:
  The main headline of a page is defined via <tt>$page_title</tt>.     The main headline of a page is defined via <tt>$page_title</tt>.  
  If a page has several sections with a headline each, &lt;h2&gt; is used for them (&lt;h3&gt; for subsections):   If a page has several sections with a headline each, &lt;h2&gt; is used for them (&lt;h3&gt; for subsections):
− <code html4strict> + <syntaxhighlight lang="html4strict">
  <h2><a name="section1" />Section Headline</h2>   <h2><a name="section1" />Section Headline</h2>
  <h3>Subsection Headline</h3>   <h3>Subsection Headline</h3>
Line 180:
Line 180:
    
  To allow better navigation through the site, each &lt;h2&gt; heading should be linked from a quicklinks section on top of the page:   To allow better navigation through the site, each &lt;h2&gt; heading should be linked from a quicklinks section on top of the page:
− <code html4strict> + <syntaxhighlight lang="html4strict">
  <div id="quicklinks"> [   <div id="quicklinks"> [
     <a href="section1">Section Headline</a> |      <a href="section1">Section Headline</a> |
Line 189:
Line 189:
    
  If you wish to link &lt;h3&gt; headlines as well, then you can use:     If you wish to link &lt;h3&gt; headlines as well, then you can use:  
− <code html4strict> + <syntaxhighlight lang="html4strict">
  <div id="quicklinks">   <div id="quicklinks">
  <p>   <p>



Neverendingo: Text replace - "" to ""

2011-06-29T20:59:28Z
Text replace - "<code php>" to "<syntaxhighlight lang="php">"
Show changes


Neverendingo: Text replace - "" to ""
2011-06-29T20:57:39Z
Text replace - "</code>" to "</syntaxhighlight>"
Show changes


Neverendingo at 22:34, 19 December 2010
2010-12-19T22:34:50Z


				
				
				
				
			
			← Older revision
			Revision as of 22:34, 19 December 2010
			
Line 1:
Line 1:
  + {{note|This projects page has been moved to [[http://community.kde.org/KDE.org/Capacity_HOWTO|community.kde.org]]. Please don't edit on techbase anymore.}}
  + 
  __TOC__   __TOC__
    



Albert Astals Cid: /* i18n - Translate interface to other languages */
2010-12-13T19:30:56Z
‎i18n - Translate interface to other languages

				
				
				
				
			
			← Older revision
			Revision as of 19:30, 13 December 2010
			
Line 346:
Line 346:
    
  Now the caption "Search" becomes german "Suche".   Now the caption "Search" becomes german "Suche".
  + 
  + If you want to translate random text of your web page you have to use one of the three i18n functions available, that is i18n(), i18n_var() and i18n_noop().
  + * i18n is the function you want to use if you simply want to show a text that would be translatable, e.g.
  + <code php>
  + <p><?php i18n("Some images of Okular in action...")?></p>
  + </code>
  + * i18n_var is the function you want to use if you want to get a translated text in a way you can assign it to a variable, e.g.
  + <code php>
  + <?php $site_title = i18n_var("Okular - more than a reader"); ?></p>
  + </code>
  + * i18n_noop is the function you want to use if you simply want to mark your text as translatable because you know the translation will happen at a later stage.
  + <code php>
  + <?php $page_title = i18n_noop('Frequently Asked Questions'); ?></p>
  + </code>
  + 
  + If you want to show a language selector in your webpage you have to define the site_languages variable to hold the supported languages.
  + <code php>
  + <?php $site_languages = array('en', 'es', 'pt_BR', 'uk'); ?></p>
  + </code>



Quique: Fix two typos
2008-12-10T07:23:01Z
Fix two typos

				
				
				
				
			
			← Older revision
			Revision as of 07:23, 10 December 2008
			
Line 28:
Line 28:
  which would be equal to the later documentroot on the server in many   which would be equal to the later documentroot on the server in many
  cases, may be created. This include is used by the {{path|header.inc}}, it   cases, may be created. This include is used by the {{path|header.inc}}, it
− should contain some information about your site, like it's name + should contain some information about your site, like its name
  and the email address of the webmaster, this will be used by header/footer   and the email address of the webmaster, this will be used by header/footer
  to setup the page correct.   to setup the page correct.
Line 204:
Line 204:
  ==Own Header-Logo==   ==Own Header-Logo==
    
− Each site can have it's own right-side header-logo, like http://conference2006.kde.org. You just need to add a {{path|site.png}} to the top-level directory of your site, the framework will add it automatically if it finds one. Look at http://conference2006.kde.org/site.png for the correct dimensions. While a transparent background would be preferred, atm the Internet Explorer has problems with transparent PNGs and GIFs are (were) problematic because of patents. Therefore the background needs atm to be duplicated in the image like done for the conference site. + Each site can have it's own right-side header-logo, like http://conference2006.kde.org. You just need to add a {{path|site.png}} to the top-level directory of your site, the framework will add it automatically if it finds one. Look at http://conference2006.kde.org/site.png for the correct dimensions. While a transparent background would be preferred, atm the Internet Explorer has problems with transparent PNGs, and GIFs are (were) problematic because of patents. Therefore the background needs atm to be duplicated in the image like done for the conference site.
    
  ==News==   ==News==



Tampakrap: /* Own Header-Logo */
2008-02-12T12:58:13Z
‎Own Header-Logo

				
				
				
				
			
			← Older revision
			Revision as of 12:58, 12 February 2008
			
Line 204:
Line 204:
  ==Own Header-Logo==   ==Own Header-Logo==
    
− Each site can have it's own right-side header-logo, like http://conference2006.kde.org. You just need to add a {{path|site.png}} to the toplevel directory of your site, the framework will add it automagically if it finds one. Look at http://conference2006.kde.org/site.png for the correct dimensions. While a transparent background would be prefered, atm the Internet Explorer has problems with transparent PNGs and GIFs are (were) problematic because of patents. Therefor the background needs atm to be duplicated in the image like done for the conference site. + Each site can have it's own right-side header-logo, like http://conference2006.kde.org. You just need to add a {{path|site.png}} to the top-level directory of your site, the framework will add it automatically if it finds one. Look at http://conference2006.kde.org/site.png for the correct dimensions. While a transparent background would be preferred, atm the Internet Explorer has problems with transparent PNGs and GIFs are (were) problematic because of patents. Therefore the background needs atm to be duplicated in the image like done for the conference site.
    
  ==News==   ==News==



Emilsedgh: /* Image Galleries */
2007-10-12T10:42:29Z
‎Image Galleries

				
				
				
				
			
			← Older revision
			Revision as of 10:42, 12 October 2007
			
Line 240:
Line 240:
    
  A PHP class has been written to make it easy to write image galleries. The image galleries can link to enlarged versions of the image, but this isn't compulsory. Using the class is simple:     A PHP class has been written to make it easy to write image galleries. The image galleries can link to enlarged versions of the image, but this isn't compulsory. Using the class is simple:  
  + 
  + {{Tip| If you want to have a fancy Image Gallery with Lightbox, pass <tt>True</tt> as the second argument to the <tt>imageGallery</tt> class.}}
    
  <code php>   <code php>
Line 268:
Line 270:
  * <tt>$description_text</tt> - A short description of the image which will appear underneath (optional)   * <tt>$description_text</tt> - A short description of the image which will appear underneath (optional)
    
− Note: the page won't be rendered until you call <tt>show()</tt>. + {{Warning| The page won't be rendered until you call <tt>show()</tt>}}
  Please use this class rather than hand constructing an image gallery to save your time and to improve consistency.   Please use this class rather than hand constructing an image gallery to save your time and to improve consistency.

← Older revision		Revision as of 19:11, 29 November 2012
Line 1:		Line 1:
−	{{~~note~~\|This ~~projects~~ page has been moved to [http://community.kde.org/KDE.org/Capacity_HOWTO community.kde.org]. Please don't edit on techbase anymore.}}	+	{{Remember\|2=Important!\|1=\|This project page has been moved to [http://community.kde.org/KDE.org/Capacity_HOWTO community.kde.org]. Please don't edit on techbase anymore.}}
		+

	__TOC__		__TOC__

← Older revision		Revision as of 22:51, 28 November 2012
Line 1:		Line 1:
−	{{note\|This projects page has been moved to [[http://community.kde.org/KDE.org/Capacity_HOWTO\|community.kde.org]]. Please don't edit on techbase anymore.}}	+	{{note\|This projects page has been moved to [http://community.kde.org/KDE.org/Capacity_HOWTO community.kde.org]. Please don't edit on techbase anymore.}}

	__TOC__		__TOC__

← Older revision		Revision as of 22:34, 19 December 2010
Line 1:		Line 1:
		+	{{note\|This projects page has been moved to [[http://community.kde.org/KDE.org/Capacity_HOWTO\|community.kde.org]]. Please don't edit on techbase anymore.}}
		+
	__TOC__		__TOC__

← Older revision		Revision as of 19:30, 13 December 2010
Line 346:		Line 346:

	Now the caption "Search" becomes german "Suche".		Now the caption "Search" becomes german "Suche".
		+
		+	If you want to translate random text of your web page you have to use one of the three i18n functions available, that is i18n(), i18n_var() and i18n_noop().
		+	* i18n is the function you want to use if you simply want to show a text that would be translatable, e.g.
		+	<code php>
		+	<p><?php i18n("Some images of Okular in action...")?></p>
		+	</code>
		+	* i18n_var is the function you want to use if you want to get a translated text in a way you can assign it to a variable, e.g.
		+	<code php>
		+	<?php $site_title = i18n_var("Okular - more than a reader"); ?></p>
		+	</code>
		+	* i18n_noop is the function you want to use if you simply want to mark your text as translatable because you know the translation will happen at a later stage.
		+	<code php>
		+	<?php $page_title = i18n_noop('Frequently Asked Questions'); ?></p>
		+	</code>
		+
		+	If you want to show a language selector in your webpage you have to define the site_languages variable to hold the supported languages.
		+	<code php>
		+	<?php $site_languages = array('en', 'es', 'pt_BR', 'uk'); ?></p>
		+	</code>