Support for multilanguage sites, Internationalization (I18N)

[Angryboy]

Is it necessary to wrap each i18n navigation call inside htmlspecialchars?

Anyone?

According to the PHP manual, htmlspecialchars encodes HTML characters. In their example, they give:

PHP Code:

$new = htmlspecialchars("<a href='test'>Test</a>", ENT_QUOTES);
echo $new; // &lt;a href='test'&gt;Test&lt;/a&gt; 


If you look at mvlcek's example code, e.g.:

PHP Code:

<a href="<?php echo htmlspecialchars(return_i18n_setlang_url('en')); ?>">english</a> 


He's using the function so that any valid HTML that incidentally made it into the return_i18n_setlang_url function is encoded, and so the <a></a> HTML tag is not broken by the contents of return_i18n_setlang_url. In short, it's a safety measure in case the language's url contains HTML-breaking characters, and thus should be used.

get/return_i18n_navigation on the other hand is supposed to return valid HTML. So if you want to display return_i18n_navigation properly, don't use htmlspecialchars on it.

Please help, what is the easiest way to display the "page title" in menu as subtitle?
get_i18n_navigation(return_page_slug(),0,1,I18N_SHOW_MENU, ???page title???);

I'm guessing that you want to custom render each navigation element? If so, check out the Custom Rendering documentation.