Skip to content
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

Plus Codes capitalization inconsistent with marketing website #441

Open
fulldecent opened this issue Apr 25, 2021 · 4 comments · May be fixed by #463
Open

Plus Codes capitalization inconsistent with marketing website #441

fulldecent opened this issue Apr 25, 2021 · 4 comments · May be fixed by #463

Comments

@fulldecent
Copy link
Contributor

The OLC naming guidelines specifies:

[Plus codes] should not be capitalised...

However, the Google marketing website at https://maps.google.com/pluscodes/ repeatedly fails to follow these specifications. Plus codes is used in title case. (There are some cases where it is used in a heading, but context shows that headings are using sentence case, not title case.)

I understand that those projects maybe not be directly related to this repository and the website is not under version control here (it should be!) but please work with me. I have a lot of work to do here and need some help...

Screen Shot 2021-04-24 at 22 54 38

Screen Shot 2021-04-24 at 22 54 42

@fulldecent
Copy link
Contributor Author

Recommended tag: documentation

@bilst bilst changed the title Plus Codes naming violation on marketing website Plus Codes capitalization inconsistent with marketing website Apr 27, 2021
@bilst
Copy link
Contributor

bilst commented Apr 27, 2021

Unfortunate given how the documentation here was so insistent on lowercase, but Google's new style preference is "Plus Codes". Will keep this issue to track inconsistencies in code/documentation.

@fulldecent
Copy link
Contributor Author

Understood. I'm on it.

@fulldecent fulldecent linked a pull request Jun 4, 2021 that will close this issue
9 tasks
@fulldecent
Copy link
Contributor Author

fulldecent commented Jun 4, 2021

This issue is partially fixed at #463.

All documentation is updated. And the implementations are not updated.

I would like to help more here. But requesting, please, a review of that PR first. We can merge that and then I can work on making the implementations conformant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants