Does it make sense to skip translations marked as new ?
The reason for this is that new strings are in 99% of cases not translated. Currently the loader considers them as translated and does not fallback on the default locale setting.
In my case i have:
1)
PHP:
echo $translator->trans('welcome_message');
2)
I extract the translations using the extract command (extracted for en and es language). This generates:
This is not a bug issue.
Is more of a RFC.
Currently Translation/Loader/Symfony/XliffLoader.php loads all the translations in the symfony catalogue.
Does it make sense to skip translations marked as
new
?The reason for this is that
new
strings are in 99% of cases not translated. Currently the loader considers them as translated and does not fallback on the default locale setting.In my case i have:
1) PHP:
2) I extract the translations using the extract command (extracted for
en
andes
language). This generates:messages.en.xlf
messages.es.xlf
3) A as first thing I translate
messages.en.xlf
.welcome_message
is translated asHi!
.messages.en.xlf
4) When a user has
es
locale:prints
welcome_message
instead ofHi!
.This is because
<target state="new">welcome_message</target>
is considered as translated.