Pluf's i18n parser stumbles upon nested {literal} tags in {blocktrans} sections,

so rewrite the opening bracket as HTML entity to make both, the parser and the
output function happy.
This commit is contained in:
Thomas Keller 2012-03-22 01:17:05 +01:00
parent b529c05d11
commit a07d2be837

View File

@ -55,7 +55,7 @@
<p>The content of the page can use the <a href="{$burl}">Markdown syntax</a> with the <a href="{$eurl}"><em>Extra</em> extension</a>.</p> <p>The content of the page can use the <a href="{$burl}">Markdown syntax</a> with the <a href="{$eurl}"><em>Extra</em> extension</a>.</p>
<p>Additionally, the following macros are available:<br /> <p>Additionally, the following macros are available:<br />
<ul> <ul>
<li><code>{literal}{{/literal}projectlist, label=..., order=(name|activity), limit=...}</code> - Renders a project list that can optionally be filtered by label, ordered by 'name' or 'activity' and / or limited to a specific number of projects.</li> <li><code>&#x7b;projectlist, label=..., order=(name|activity), limit=...}</code> - Renders a project list that can optionally be filtered by label, ordered by 'name' or 'activity' and / or limited to a specific number of projects.</li>
</ul> </ul>
</p> </p>
{/blocktrans} {/blocktrans}