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

Plaintext in multiple languages on the licenses #289

Open
little-wow opened this issue Jan 5, 2018 · 7 comments
Open

Plaintext in multiple languages on the licenses #289

little-wow opened this issue Jan 5, 2018 · 7 comments
Labels
💻 aspect: code Concerns the software code in the repository 📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature help wanted Open to participation from the community legalcode 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@little-wow
Copy link

little-wow commented Jan 5, 2018

Description

Plain text formats for the 4.0 licenses and the CC0 public domain dedication were created using a manual process. Only the English versions of the legal tools were formatted as plain text. Additionally, that manual creation process was not without errors and is not sustainable.

Expectation

Extend the CC Legal Tools App to generate deterministic plain text versions of the 4.0 licenses and the CC0 public domain dedication (including all translations):

@CreativeCommons Suggestion: I often encounter a frustrating issue: the plaintext version of licenses is only available in English.
What I would like: just like you append .txt to get https://t.co/xj09QHxa8o, get https://t.co/7BinrQoJXI to work too.
Cleaning myself is long 😉

— Matti Schneider (@matti_sg) January 5, 2018

Requirements

Updated requirements given cc-legal-tools-app:

@peterspdx
Copy link

I'm fine with this so long as the plain text versions are limited to official translations of 4.0. We could rollout the plain text version every time we launch a new translation. I'd want to give more thought to doing this for pre-4.0 versions of the license. @little-wow @robmyers What do you think?

@rheaplex

This comment was marked as outdated.

@rheaplex rheaplex removed their assignment Sep 7, 2018
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Dec 2, 2020
@TimidRobot TimidRobot transferred this issue from creativecommons/creativecommons.org Aug 16, 2022
@yokwejuste
Copy link
Contributor

Hi @TimidRobot I'll like to give a try to this issue

@TimidRobot TimidRobot added help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work 🌟 goal: addition Addition of new feature 📄 aspect: text Concerns the textual material in the repository 💻 aspect: code Concerns the software code in the repository legalcode and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Nov 22, 2022
@TimidRobot
Copy link
Member

Hi @TimidRobot I'll like to give a try to this issue

@yokwejuste I updated the issue description with more information. This task is quite involved.

@yokwejuste
Copy link
Contributor

Alright, let me go through it then.

@yokwejuste
Copy link
Contributor

The source files mentioned here are those generated by in the legal-code folder right?

@TimidRobot
Copy link
Member

The "source" is a the combination of the data created with the load_html_files command and the translation files.

Also see the Data section of the creativecommons/cc-legal-tools-data README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 📄 aspect: text Concerns the textual material in the repository 🌟 goal: addition Addition of new feature help wanted Open to participation from the community legalcode 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

No branches or pull requests

7 participants