Author: adelbene
Date: Fri Aug 29 15:30:08 2014
New Revision: 1621327
URL: http://svn.apache.org/r1621327
Log:
Minor formatting improvements
Modified:
wicket/common/site/trunk/_site/guide/guide/src/docs/guide/i18n/i18n_2.gdoc
wicket/common/site/trunk/_site/guide/guide/src/docs/guide/jsintegration/jsintegration_2.gdoc
Modified:
wicket/common/site/trunk/_site/guide/guide/src/docs/guide/i18n/i18n_2.gdoc
URL:
http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/i18n/i18n_2.gdoc?rev=1621327&r1=1621326&r2=1621327&view=diff
==============================================================================
--- wicket/common/site/trunk/_site/guide/guide/src/docs/guide/i18n/i18n_2.gdoc
(original)
+++ wicket/common/site/trunk/_site/guide/guide/src/docs/guide/i18n/i18n_2.gdoc
Fri Aug 29 15:30:08 2014
@@ -33,7 +33,7 @@ Variation's value contributes to the fin
h3. Using XML files as resource bundles
-Java uses the standard character set "ISO
8859-11":http://en.wikipedia.org/wiki/ISO/IEC_8859-1 to encode text files like
properties files. Unfortunately ISO 8859-1 does not support most of the
extra-European languages like Chinese or Japanese. The only way to use
properties files with such languages is to use escaped
"Unicode":http://en.wikipedia.org/wiki/List_of_Unicode_characters characters,
but this leads to not human-readable files. For example if we wanted to write
the word 'website' in simplified Chinese (the ideograms are ç½ç«) we should
write the Unicode characters \u7F51\u7AD9. That's why starting from version
1.5, Java introduced the support for XML files as resource bundles. XML files
are generally encoded with character sets UTF-8 or UTF-16 which support every
symbol of the Unicode standard. In order to be a valid resource bundle the XML
file must conform to the DTD available at
"http://www.oracle.com/webfolder/technetwork/jsc/dtd/properties.dtd":http://www.oracl
e.com/webfolder/technetwork/jsc/dtd/properties.dtd .
+Java uses the standard character set "ISO
8859-11":http://en.wikipedia.org/wiki/ISO/IEC_8859-1 to encode text files like
properties files. Unfortunately ISO 8859-1 does not support most of the
extra-European languages like Chinese or Japanese. The only way to use
properties files with such languages is to use escaped
"Unicode":http://en.wikipedia.org/wiki/List_of_Unicode_characters characters,
but this leads to not human-readable files. For example if we wanted to write
the word 'website' in simplified Chinese (the ideograms are ç½ç«) we should
write the Unicode characters @\u7F51\u7AD9@. That's why starting from version
1.5, Java introduced the support for XML files as resource bundles. XML files
are generally encoded with character sets UTF-8 or UTF-16 which support every
symbol of the Unicode standard. In order to be a valid resource bundle the XML
file must conform to the DTD available at
"http://www.oracle.com/webfolder/technetwork/jsc/dtd/properties.dtd":http://www.ora
cle.com/webfolder/technetwork/jsc/dtd/properties.dtd .
Here is an example of XML resource bundle taken from project
LocalizedGreetings (file WicketApplication_zh.properties.xml) containing the
translation in simplified Chinese of the greeting message âWelcome to the
website!â:
Modified:
wicket/common/site/trunk/_site/guide/guide/src/docs/guide/jsintegration/jsintegration_2.gdoc
URL:
http://svn.apache.org/viewvc/wicket/common/site/trunk/_site/guide/guide/src/docs/guide/jsintegration/jsintegration_2.gdoc?rev=1621327&r1=1621326&r2=1621327&view=diff
==============================================================================
---
wicket/common/site/trunk/_site/guide/guide/src/docs/guide/jsintegration/jsintegration_2.gdoc
(original)
+++
wicket/common/site/trunk/_site/guide/guide/src/docs/guide/jsintegration/jsintegration_2.gdoc
Fri Aug 29 15:30:08 2014
@@ -120,11 +120,11 @@ public void renderHead(IHeaderResponse r
}
{code}
-If component is disabled the calendar icon must be hidden and no datepicker
must be displayed. That's why renderHeader is skipped if component is not
enabled.
+If component is disabled the calendar icon must be hidden and no datepicker
must be displayed. That's why @renderHeader@ is skipped if component is not
enabled.
To get a reference to the bundled JQuery library we used the JavaScript
setting interface @IJavaScriptLibrarySettings@ and its method
@getJQueryReference@.
-In the last part of renderHeader we build the string to invoke function
initJQDatepicker using the values obtained inside onInitialize. Unfortunately
the date format used by JQuery UI is different from the one adopted in Java so
we have to convert it before building the JavaScript code. This init script is
rendered into header section using a @OnLoadHeaderItem@ to ensure that it will
be executed after all the other scripts have been loaded.
+In the last part of @renderHeader@ we build the string to invoke function
@initJQDatepicker@ using the values obtained inside onInitialize. Unfortunately
the date format used by JQuery UI is different from the one adopted in Java so
we have to convert it before building the JavaScript code. This init script is
rendered into header section using a @OnLoadHeaderItem@ to ensure that it will
be executed after all the other scripts have been loaded.
{note}
If we add more than one instance of our custom component to a single page,
static resources are rendered to the header section just once. Wicket
automatically checks if a static resource is already referenced by a page and
if so, it will not render it again.
