compared with
Current by Ben Scholzen
on Mar 21, 2012 12:10.

(show comment)
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (28)

View Page History
<p>This IRC Meeting is planned for 18:00 UTC on Wednesday, 21 March 2012.</p>

{html}<iframe src="http://free.timeanddate.com/countdown/i2vpvyb9/cf12/cm0/cu4/ct0/cs0/ca0/cr0/ss0/cac000/cpc000/pcfff/tcfff/fs100/szw320/szh135/tatTime%20left%20to%20Event%20in/tac000/tptTime%20since%20Event%20started%20in/tpc000/mac000/mpc000/iso2012-03-21T18:00:00" frameborder="0" width="350" height="64"></iframe>{html}
<ac:macro ac:name="html"><ac:plain-text-body><![CDATA[<iframe src="http://free.timeanddate.com/countdown/i2vpvyb9/cf12/cm0/cu4/ct0/cs0/ca0/cr0/ss0/cac000/cpc000/pcfff/tcfff/fs100/szw320/szh135/tatTime%20left%20to%20Event%20in/tac000/tptTime%20since%20Event%20started%20in/tpc000/mac000/mpc000/iso2012-03-21T18:00:00" frameborder="0" width="350" height="64"></iframe>]]></ac:plain-text-body></ac:macro>

Please feel free to add topics, according to the template on the [parent page|IRC Meetings].
<p>Please feel free to add topics, according to the template on the <ac:link><ri:page ri:content-title="IRC Meetings" /><ac:link-body>parent page</ac:link-body></ac:link>.</p>

h2. Forms RFC
<h2>Forms RFC</h2>

<p>Matthew has taken the various pieces of feedback on the ML and the RFC, and updated the RFC to reflect the various requirements discussed. He would like to get at least preliminary approval so he can begin development.</p>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{vote:Forms RFC - Should we discuss this?
|visibleVoters=true}
Yes
No
{vote}
{vote}]]></ac:plain-text-body></ac:macro>

h2. Removing automatic translations

Ben has pointed out in IRC that automatic translations are a huge problem when working with source code scanners like xgettext, which cannot detect message IDs from random arrays. A solution, to which many agreed, would be to explicitly translate strings for components, for instance:
<h2>Removing automatic translations</h2>

<p>Ben has pointed out in IRC that automatic translations are a huge problem when working with source code scanners like xgettext, which cannot detect message IDs from random arrays. A solution, to which many agreed, would be to explicitly translate strings for components, for instance:</p>
{code}
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
$form->addElement(
'foo' => array(
),
);
{code}
]]></ac:plain-text-body></ac:macro>

<p>Some people pointed out that it may hurt performance, if all strings are translated (e.g. for navigation containers, where subtrees may not be shown on the current page). This is subject of a later benchmark, but a suggested solution to the problem would be lazy translation. Basically, Zend\I18n\Translator could return a callback with a __toString() method, which the component using it would not have to care about whether it is a string or not, for instance:</p>

{code}
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
$form->addElement(
'foo' => array(
),
);
{code}
]]></ac:plain-text-body></ac:macro>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{vote:Removing automatic translations - Should we discuss this?
|visibleVoters=true}
Yes
No
{vote}
{vote}]]></ac:plain-text-body></ac:macro>