Skip to content

Conversation

@swissspidy
Copy link
Member

There were some many things wrong with the internationalization.md document, I don't even know where to start.

What this PR does:

  • Uses correct examples for all the internationalization functions so people won't be _doing_it_wrong()
  • Mentions new wp_set_script_translations() function.
  • Actually adds some links to resources

Related: #12502

@swissspidy swissspidy added [Type] Enhancement A suggestion for improvement. [Type] Developer Documentation Documentation for developers Internationalization (i18n) Issues or PRs related to internationalization efforts labels Dec 4, 2018
Copy link
Contributor

@chrisvanpatten chrisvanpatten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall great, one thing I noticed was it switches from i18n and I18n (upper vs lowercase) on occasion and somewhat randomly. Would prefer, if possible, to standardize on one or the other (possibly only using capital I at the start of sentences or where title case is appropriate, e.g. headers. But this is great and makes sense to land sooner rather than later :)

@swissspidy swissspidy added this to the Documentation & Handbook milestone Dec 4, 2018
@mtias mtias merged commit fccbb4b into master Dec 5, 2018
@mtias mtias deleted the fix/i18n-docs branch December 5, 2018 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Internationalization (i18n) Issues or PRs related to internationalization efforts [Type] Developer Documentation Documentation for developers [Type] Enhancement A suggestion for improvement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants