<p dir="auto">Hi,</p>
<p dir="auto">I used to have (with Symfony 2.6) parameters in app/config/config.yml in this form :</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="...
parameters:
    my-parameter: 123"><pre class="notranslate"><code class="notranslate">...
parameters:
    my-parameter: 123
</code></pre></div>
<p dir="auto">I was able to access these using <code class="notranslate">ContainerInterface-&gt;getParameter('my-parameter');</code>, however this now throws an InvalidArgumentException with the message "The parameter "my-parameter" must be defined." starting from Symfony 2.7.<br>
There's no trace of this change in the change log nor in the UPGRADE-2.7.md file, is this a bug or is this new behavior intended ?</p>
<p dir="auto">Thanks.</p>
<p dir="auto">The TimezoneType Field Type uses <code class="notranslate">\DateTimeZone::listIdentifiers()</code> to get the texts that are shown in the generated <code class="notranslate">select</code> HTML tag. Of course these are in perfect english. I've added all the texts needed to translate it in my AppBundle YAML translation files and configured the form like this so it gets translated with them:</p>
<div class="highlight highlight-text-html-php notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="class ProfileFormType extends AbstractType
{
...
    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $constraint = new UserPassword();

        $this-&gt;buildUserForm($builder, $options);

        $builder
            -&gt;add('timezone', 'timezone', array(
                'label' =&gt; 'form.timezone.label',
                'translation_domain' =&gt; 'AppBundle',
                'choice_translation_domain' =&gt; true,
            ))
        ;
    }
...
}"><pre class="notranslate"><span class="pl-k">class</span> <span class="pl-v">ProfileFormType</span> <span class="pl-k">extends</span> <span class="pl-v">AbstractType</span>
{
...
    <span class="pl-k">public</span> <span class="pl-k">function</span> <span class="pl-en">buildForm</span>(<span class="pl-smi"><span class="pl-smi">FormBuilderInterface</span></span> <span class="pl-s1"><span class="pl-c1">$</span>builder</span>, <span class="pl-smi">array</span> <span class="pl-s1"><span class="pl-c1">$</span>options</span>)
    {
        <span class="pl-s1"><span class="pl-c1">$</span>constraint</span> = <span class="pl-k">new</span> <span class="pl-v">UserPassword</span>();

        <span class="pl-s1"><span class="pl-c1">$</span><span class="pl-smi">this</span></span>-&gt;<span class="pl-en">buildUserForm</span>(<span class="pl-s1"><span class="pl-c1">$</span>builder</span>, <span class="pl-s1"><span class="pl-c1">$</span>options</span>);

        <span class="pl-s1"><span class="pl-c1">$</span>builder</span>
            -&gt;<span class="pl-en">add</span>(<span class="pl-s">'timezone'</span>, <span class="pl-s">'timezone'</span>, <span class="pl-en">array</span>(
                <span class="pl-s">'label'</span> =&gt; <span class="pl-s">'form.timezone.label'</span>,
                <span class="pl-s">'translation_domain'</span> =&gt; <span class="pl-s">'AppBundle'</span>,
                <span class="pl-s">'choice_translation_domain'</span> =&gt; <span class="pl-c1">true</span>,
            ))
        ;
    }
...
}</pre></div>
<p dir="auto"><a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/javiereguiluz/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/javiereguiluz">@javiereguiluz</a> suggested me that those texts may be could be included in the Intl component like other resource bundles as Currrency, Regions, etc. If the community thinks this could be a new feature I would be glad to do the Spanish translations and could try to do the PR itself.</p>