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
Describe the bug
When we run our bundle script we are not including strings from jetpack in the resulting bundle.
To Reproduce
Steps to reproduce the behavior:
npm run genstrings
Observe that the strings files (i.e., bundle/android/strings.xml) do not contain relevant strings from the jetpack repo: for example, "Link address to Google Maps").
Expected behavior
Relevant strings from the jetpack repos should be included in our bundles for translation.
The text was updated successfully, but these errors were encountered:
2. Observe that the strings files (i.e., bundle/android/strings.xml) do not contain relevant strings from the jetpack repo: for example, "Link address to Google Maps").
The string Link address to Google Maps is included in the Jetpack's GlotPress project (reference), so it's not expected that this string will be part of the localization strings files (i.e. bundle/android/strings.xml), as these files only contain the strings that are exclusively referenced in JS native files (i.e. *.native.js).
As an alternative example, the string Address Settings (code reference) is one that is only referenced in a JS native file, and besides is already included in the localization strings files (reference).
Describe the bug
When we run our bundle script we are not including strings from jetpack in the resulting bundle.
To Reproduce
Steps to reproduce the behavior:
npm run genstrings
bundle/android/strings.xml
) do not contain relevant strings from the jetpack repo: for example, "Link address to Google Maps").Expected behavior
Relevant strings from the jetpack repos should be included in our bundles for translation.
The text was updated successfully, but these errors were encountered: