Repository navigation
Complete English F-Droid listing descriptions - #101
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The English full description was empty and the short description covered only GPX import. Complete both Fastlane listing files using the earlier Google Play summary and the current feature set.
The full description covers map sources and overlays, GPX/KML, markers, nearby Wikipedia places, optional ORS routing and search, offline tile caching/import, and display settings. It explains offline coverage, connectivity and ORS API-key requirements, and identifies the F-Droid edition as ad-free.
Validation: checked against the current README, distribution configuration and maintainer clarification; short description is 73 characters and full description is 2,182 characters excluding its trailing newline, within the 80/4,000 limits. Only the two description files change; no app build is required.
Publication follow-up: include these files in a release recognized by F-Droid and submit a separate fdroiddata merge request removing the YAML Description (and Summary if present), so source metadata can take effect.