-
Notifications
You must be signed in to change notification settings - Fork 497
Use consistent naming in this repository -- plus codes or open location code #431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Separately, this is mentioned in https://github.com/google/open-location-code/wiki/Naming-guidelines and that needs to be brought into one of the normative specifications |
Recommended tags: implementation specification documentation |
This is partially fixed at #463 The documentation is updated to make consistent and correct usage of Plus Code versus Open Location Code. Implementations are not updated. I hope this PR can please be reviewed and merged before I consider the implementations. |
The naming guidelines document says that Plus Codes should be in title case. If other docs are inconsistent they should be brought into line with that before we change that definition. |
Got it. So we want to update #650 to use title case "Plus Codes" because of specification at open-location-code/Documentation/Specification/Naming_Guidelines.md Lines 11 to 20 in 4d83aed
|
The README and FAQ here clarify:
This messaging is frustrated by several inconsistencies in this repository.
Work plan
/Open Location Codes?/i
and/plus.{0,5}codes/I
in this repo to find stray word misusage.Work plan outside this project (e.g. advocacy)
The text was updated successfully, but these errors were encountered: