@javiereguiluz is this a new feature? Isn't that supported yet?
For now i resolved it by using php-translation/extractor, but I think this would be a important feature, if it really is not implemented by the symfony/translation yet. Like that, the component is not really usable because an important part of the translations are missing.
What do you think?

It's indeed a known limitation that extraction from form labels is not possible. That will be a new feature.

It's indeed a known limitation that extraction from form labels is not possible. That will be a new feature.

This blog says it is supported... not a new feature.
https://symfony.com/blog/new-in-symfony-4-3-improved-form-translation

I don't see anything in the blog post talking about the extraction of translations.

Yes, it's only about using variables in labels and helpers.
But it's funny that there are improvements on that, but the basics (extraction of simple labels) cannot be done yet with the symfony translation :)

That's probably because writing the code to extract the translations is a harder task. But if you would like to work on it, I will happily review a PR implementing this task. :)

Pretty sure this was working beforehand and it's not a feature but a bug ?

In a FormType:

$builder
            ->add('title', TextType::class, [
                'label' => 'My Title'
            ])

Used to work, but not anymore. It's supposed to as per documentation: https://symfony.com/doc/current/reference/forms/types/form.html#label-translation-parameters

Those strings are not extracted anymore. But maybe I dreamt and those strings were never extracted to begin with!

@Pixelshaped The documentation you linked to does not talk about the extraction of translations. It just shows how you can translate the label.

You're right. I think what mislead me was the debug toolbar reporting the right translation domain for the form once configured in configureOptions.

now with #37670 merged, we could think of 'label' => new Translatable('id') :) that could reduce the no. of related form options by a lot :)

Out of curiosity I tried to get the PhpExtractor to handle FormTypes but adding the path to twig setup.

twig:
    default_path: '%kernel.project_dir%/templates'

    paths:
        '%kernel.project_dir%/src/Form': ~

Using $label = new TranslatableMessage('Password'); in my Types the extractor seems to pick everything up correctly.

Maybe pointing PhpExtractor to FormTypes could make it into 5.2?

It's not easy to detect where to look for new translations. Maybe this should be a particular decision per case. A new option in related commands could help with this need:

bin/console translation:update en --extra-path=src/Controller --extra-path=src/Form

For the record: this PR #40229 was open to add the whole src/.

now with #37670 merged, we could think of 'label' => new Translatable('id') :) that could reduce the no. of related form options by a lot :)

@ro0NL I've opened #42077 to deprecate those outdated options

Thank you for this suggestion.
There has not been a lot of activity here for a while. Would you still like to see this feature?

Could I get a reply or should I close this?

Hey,

I didn't hear anything so I'm going to close it. Feel free to comment if this is still relevant, I can always reopen!