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
In Google Play metadata for fastlane, localized metadata is in the folder structure
├── fastlane
│ ├── metadata_play
│ │ ├── <language>
│ │ │ ├── description.txt
│ │ │ ├── ...
│ │ | └── <version>.txt <--- this is the changelog file for <language>
This is standardized to be recognized by translation software such as weblate. The format used by this plugin of a flat "changelogs" folder with all the languages as .txt is not recognized by various tools and requires an additional transform to work.
For my usage I have had to create shell scripts to alternate the file structure between the two (the suggested in this project's README and the one that is compliant with google play and our translation tools). Is there any reason we can't use this same file structure for amazon metadata (but metadata_amazon for example)?
The text was updated successfully, but these errors were encountered:
In Google Play metadata for fastlane, localized metadata is in the folder structure
This is standardized to be recognized by translation software such as weblate. The format used by this plugin of a flat "changelogs" folder with all the languages as .txt is not recognized by various tools and requires an additional transform to work.
For my usage I have had to create shell scripts to alternate the file structure between the two (the suggested in this project's README and the one that is compliant with google play and our translation tools). Is there any reason we can't use this same file structure for amazon metadata (but metadata_amazon for example)?
The text was updated successfully, but these errors were encountered: