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

Standardize PKP PN naming #86

Merged
merged 2 commits into from
Apr 15, 2024
Merged

Standardize PKP PN naming #86

merged 2 commits into from
Apr 15, 2024

Conversation

cjwetherington
Copy link

@cjwetherington cjwetherington commented Feb 20, 2024

Based on this 2017 PKP announcement,

the network previously known as the PKP Private LOCKSS Network (PKP PLN) is now the PKP Preservation Network (PKP PN)

Standardizing various inconsistent references to the network in the plugin's localization files:

  • PLN -> PN
  • PKP-PN -> PKP PN
  • PKP|PN -> PKP PN
  • Private LOCKSS Network -> Preservation Network (English appearances)
  • Conservation Network -> Preservation Network (apparent mis-translation)
  • Rede Privada LOCKSS -> Rede de Preservação (Portuguese appearances)

Of note are the various references to "PKP-PLN" in the plugin's Terms of Use and Status sections, which seemingly come from the network itself, which is what led me to starting this work. It would be great to bring those into alignment as well, as the inconsistencies can be somewhat confusing.

@jonasraoni jonasraoni merged commit 90c91ba into pkp:main Apr 15, 2024
@cjwetherington
Copy link
Author

Thanks, @jonasraoni

@cjwetherington cjwetherington deleted the pln-rename branch April 15, 2024 21:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants