You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
PHP:
echo$translator->trans('welcome_message');
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:
PHP:
I extract the translations using the extract command (extracted for
en
andes
language). This generates:messages.en.xlf
messages.es.xlf
A as first thing I translate
messages.en.xlf
.welcome_message
is translated asHi!
.messages.en.xlf
When a user has
es
locale:prints
welcome_message
instead ofHi!
.This is because
<target state="new">welcome_message</target>
is considered as translated.The text was updated successfully, but these errors were encountered: