creativecommons / cc-legal-tools-data Goto Github PK

Problem

CC0 1.0 da Danish (dansk) translation was recently added to (legacy) production:

• creativecommons/creativecommons.org#1271

Description

Import/cherry pick the appropriate commits and publish files.

Import Process

1. creativecommons/creativecommons.org#1271
2. Clone this repository (creativecommons/cc-legal-tools-data)
   • Perform any needed configuration (ex. GnuPG signing)
3. Create working/destination branch (from main default branch)

   git checkout -b cc0-da

4. Add creativecommons/creativecommons.org as a remote (named legacy) and update branches

   git remote add legacy https://github.com/creativecommons/creativecommons.org.git

   git remote update

5. Cherry-pick relevant commits:

   git cherry-pick fd6ef563d3ff3533145328b3b81db5c9d047a242

   CONFLICT (file location): docroot/legalcode/zero_1.0_da.html added in fd6ef563d3 (Stage 1st version of Danish CC0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/zero_1.0_da.html.
   error: could not apply fd6ef563d3... Stage 1st version of Danish CC0

   git add legacy/legalcode/zero_1.0_da.html

   git cherry-pick --continue

   git cherry-pick 22d010bed9e56fdf913a8a3e0a05a0d34c931d1d

6. Verify history:

   git log --follow legacy/legalcode/zero_1.0_da.html

   commit 27e8ab5a33d147e5855f750336784b290e645d6a (HEAD -> cc0-da-legalcode)
   Author: Timid Robot Zehta <[email protected]>
   Date:   2022-12-09 14:18:54 -0800
   
       ran `../../tools/cc0_update.py zero_1.0*.html` to update translation links
   
   commit a15f61a5384f1fb45352eeff9128459c445b42ec
   Author: George Hari Popescu <[email protected]>
   Date:   2019-07-30 14:15:50 +0300
   
       Stage 1st version of Danish CC0
   

7. Verify difference from source branch (main default branch):

   git diff main...HEAD
   

8. Remove remote legacy and update branches

   git remote remove legacy
   

   git remote update

   git prune

9. Push cc0-da branch and create Pull Request

Related Documentation

• Accepted Answer - linux - How to copy commits from one Git repo to another? - Stack Overflow
• Reintegration example: src/scss/header.scss · Issue #1083 · creativecommons/vocabulary

Additional context

See previous related work:

• #112

Implementation

• I would be interested in implementing this feature.

Description

1. One paragraph is displayed in English
2. The Japanese translation of that paragraph is displayed some paragraphs later.
3. Section 1. should include items i - vii, but somehow those items are appearing before the beginning of the section 1.
4. the navigation box listing all the section headings somehow presents some texts beyond the section headings as well, and the box is very long as a result.

This is a result of the legacy legal code files have four paragraphs under the Statement of Purpose instead of three.

English:

Japanese:

Reproduction

• Visit https://creativecommons.org/publicdomain/zero/1.0/legalcode.ja
  • Wayback machine capture of error content (2023-11-26):
    • https://web.archive.org/web/20231126223025/https://creativecommons.org/publicdomain/zero/1.0/legalcode.ja
  • Wayback machine capture of previous/legacy content (2023-03-14):
    • https://web.archive.org/web/20230314175659/https://creativecommons.org/publicdomain/zero/1.0/legalcode.ja

Expectation

Translation and rendering there-of should be faithful to original.

Screenshots

Current/Error	Correct1

Additional context

The legacy HTML is loaded by the App.

creativecommons/cc-legal-tools-app: legal_tools/management/commands/load_html_files.py:
https://github.com/creativecommons/cc-legal-tools-app/blob/d65d9d0d7c9c7b873f8936f0214443cc65e89222/legal_tools/management/commands/load_html_files.py#L502-L580

Resolution

• I would be interested in resolving this bug.

Problem

Description

Add legacy data: legalcode, plaintext, RDF

Legacy data meaning "data not generated by creativecommons/cc-licenses".

We want all license data in this repository. The plaintext and RDF files will be served as-is until creativecommons/cc-licenses is updated to generate them.

Alternatives

Additional context

Implementation

• I would be interested in implementing this feature.

Problem

README.md says

The text of the Creative Commons public licenses is dedicated to the public domain under the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.

That statement is true, but it could be improved. All Creative Commons legal tools are dedicated to the public domain (see here and here), including CC0 which is not a license.

Description

It would be nice if the README was updated to clarify that all Creative Commons legal tools are CC0’d. For example, that quote could be changed to:

The text of the Creative Commons public licenses legal tools is dedicated to the public domain under the CC0 1.0 Universal (CC0 1.0) Public Domain Dedication.

Alternatives

We could just leave that sentence alone. There’s other documentation out there that clarifies that CC0 is CC0’d, so this change isn’t necessary.

Additional context

Other similar clarifications have been made in the past. See:

• creativecommons/cc-legal-tools-app#381
• #44
• #45
• creativecommons/.github#24

Implementation

• I would be interested in implementing this feature.

Problem

CC0 1.0 German translation was recently added to (legacy) production:

• Publish CC0 1.0 legalcode German translation by TimidRobot · Pull Request #1252 · creativecommons/creativecommons.org

Description

Import/cherry pick the appropriate commits and publish files.

Additional context

See previous related work:

• #101 (changes were duplicated, not imported/cherry picked)
• #14

(Was previously blocked by [Feature] Support separation Transifex projects for Deeds & UX and the lLegal Code translation domains · Issue #319 · creativecommons/cc-legal-tools-app)

Implementation

• I would be interested in implementing this feature.

Description

Each repo in the CC organisation should have a .cc-metadata.yml file. This one does not.

Expectation

The .cc-metadata.yml file should be present.

Resolution

• I would be interested in resolving this bug.

Description

The internationalization of the the license list is a pretty idea, but yet not yet working. Yet some parts of the code not working appropriately.

From the picture above, the page is not translated to the Spanish language after we toggled. I'll like to work on that too

Reproduction

To reproduce the bug, the URL is:

• Go to http://127.0.0.1:8005/licenses/list
• Then toggle trying to change a language. The bug is back :(

Problem

Legal code translation correction was added to current production:

• creativecommons/creativecommons.org#1269

Description

Cherry-pick commits to import legacy data into this repository

Import Process

1. creativecommons/creativecommons.org#1269
2. Clone this repository (creativecommons/cc-legal-tools-data)
   • Perform any needed configuration (ex. GnuPG signing)
   • (or use existing clone)
3. Create working/destination branch (from main default branch)

   git checkout -b cc4-fy-6c-correction

4. Add creativecommons/creativecommons.org as a remote (named legacy) and update branches

   git remote add legacy https://github.com/creativecommons/creativecommons.org.git

   git remote update

5. Identify commits in creativecommons/creativecommons.org:
   • There's only 1 commit in creativecommons/creativecommons.org#1269
6. Cherry-pick relevant commits::

   git cherry-pick 4dc44092bbeaf126c2dcaad6f75924b7dd05a9b6

7. Verify checksums of impacted files (in both this repo and creativecommons/creativecommons.org):

   md5sum legacy/legalcode/by-nc_4.0_fy.html

   f37fa07639d214e03c7c2bf39f533f65  legacy/legalcode/by-nc_4.0_fy.html
   

   md5sum docroot/legalcode/by-nc_4.0_fy.html

   f37fa07639d214e03c7c2bf39f533f65  docroot/legalcode/by-nc_4.0_fy.html
   

8. Remove remote legacy and update branches

   git remote remove legacy

   git remote update

9. Push cc4-fy-6c-correction branch and create Pull Request

Additional context

• Importing/Cherry-picking
  • Accepted Answer - linux - How to copy commits from one Git repo to another? - Stack Overflow
  • Git cherry-pick syntax and merge branches - Stack Overflow
    • NOTE: The merge commits should not be cherry-picked. If they are included, they will be empty because the underlying commits are included.
  • #124

Problem

Legal code translation was added to current production:

• creativecommons/creativecommons.org#1264

Description

Cherry-pick commits to import legacy data into this repository

Import Process

1. creativecommons/creativecommons.org#1264
2. Clone this repository (creativecommons/cc-legal-tools-data)
   • Perform any needed configuration (ex. GnuPG signing)
   • (or use existing clone)
3. Create working/destination branch (from main default branch)

   git checkout -b cc4-da

4. Add creativecommons/creativecommons.org as a remote (named legacy) and update branches

   git remote add legacy https://github.com/creativecommons/creativecommons.org.git

   git remote update

5. Identify commits in creativecommons/creativecommons.org:

   git log by*4.0_da.html

6. Cherry-pick relevant commits::

   git cherry-pick e4cc481f8680c08544eadcaaf45f2fd7634160a2

   CONFLICT (file location): docroot/legalcode/by-nc-nd_4.0_da.html added in e4cc481f86 (Stage 1st version of Danish 4.0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nc-nd_4.0_da.html.
   CONFLICT (file location): docroot/legalcode/by-nc-sa_4.0_da.html added in e4cc481f86 (Stage 1st version of Danish 4.0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nc-sa_4.0_da.html.
   CONFLICT (file location): docroot/legalcode/by-nc_4.0_da.html added in e4cc481f86 (Stage 1st version of Danish 4.0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nc_4.0_da.html.
   CONFLICT (file location): docroot/legalcode/by-nd_4.0_da.html added in e4cc481f86 (Stage 1st version of Danish 4.0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nd_4.0_da.html.
   CONFLICT (file location): docroot/legalcode/by-sa_4.0_da.html added in e4cc481f86 (Stage 1st version of Danish 4.0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-sa_4.0_da.html.
   CONFLICT (file location): docroot/legalcode/by_4.0_da.html added in e4cc481f86 (Stage 1st version of Danish 4.0) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by_4.0_da.html.
   error: could not apply e4cc481f86... Stage 1st version of Danish 4.0
   hint: After resolving the conflicts, mark them with
   hint: "git add/rm ", then run
   hint: "git cherry-pick --continue".
   hint: You can instead skip this commit with "git cherry-pick --skip".
   hint: To abort and get back to the state before "git cherry-pick",
   hint: run "git cherry-pick --abort".

   git add legacy/legalcode/by-nc-nd_4.0_da.html \
      legacy/legalcode/by-nc-nd_4.0_da.html \
      legacy/legalcode/by-nc-sa_4.0_da.html legacy/legalcode/by-nc_4.0_da.html \
      legacy/legalcode/by-nd_4.0_da.html legacy/legalcode/by-sa_4.0_da.html \
      legacy/legalcode/by_4.0_da.html

   git cherry-pick --continue

   git cherry-pick 3515afb1a8aa7719ed92a065168734af1dfee636

   git cherry-pick 4c42aed80b34635316c198ddc7d07117960e6c24

   git cherry-pick d4b69b7eb7b9b3baa9802773e60465647e508ea1

   git cherry-pick e883ce3259736a12f35e70760ff4c7f59c9d904d

   git cherry-pick acca95c8d064fdddd568936ba1be28c3522e24fd

7. Verify history:

   git log --follow legacy/legalcode/by-nc-nd_4.0_da.html

   commit 9465930529d6feee248d7722bd354130eb3ece01 (HEAD -> cc4-da, origin/cc4-da)
   Author: Timid Robot Zehta <[email protected]>
   Date:   2023-01-24 08:29:00 -0800
   
       Correct translation of "More considerations for licensors."--move into anchor text and adjust case
   
   commit 04608d56e44e1f7590c20c407c1b6b967d50ab75
   Author: Timid Robot Zehta <[email protected]>
   Date:   2023-01-17 08:55:23 -0800
   
       fix head icons (all licenses were using by-nc-sa icons. 2022-12-28 error 5)
   
   commit b2a1d14253e8b706596f388d84b312775d133de6
   Author: Timid Robot Zehta <[email protected]>
   Date:   2023-01-17 07:16:45 -0800
   
       remove hardcoded list number (2022-12-28 error #2)
   
   commit 91d17c241008ff213d166832b397294b9bab7092
   Author: Timid Robot Zehta <[email protected]>
   Date:   2022-12-09 14:21:08 -0800
   
       ran `../../tools/cc4_update.py` to update translation links
   
   commit 5a1fdff25db5489e20bff8f1d0209a6c8563da86
   Author: George Hari Popescu <[email protected]>
   Date:   2019-07-30 14:14:28 +0300
   
       Stage 1st version of Danish 4.0
   

8. Verify difference from source branch (main default branch):

   git diff main...HEAD
   

9. Remove remote legacy and update branches

   git remote remove legacy
   

   git remote update

10. Push cc4-da branch and create Pull Request

Additional context

• Importing/Cherry-picking
  • Accepted Answer - linux - How to copy commits from one Git repo to another? - Stack Overflow
  • creativecommons/vocabulary#1083
  • #112

This repo does not have a license and generally does not meet CC's repo guidelines.

Description

The msgid strings in the Gettext Files (PO Files) appear to be mostly (entirely?!) based on those from the legacy ccEngine instead of the cc-licenses application.

Currently, the most complete translations are listed at 97%. More accurately, they are at 49%.

Data syncing with Transifex is misleading as the msgid strings in the translations do not currently match the msgid strings in the source language (Transifex Resource).

Reproduction

docker-compose exec app coverage run manage.py \
    makemessages \
        --all \
        --symlinks \
        --ignore **/includes/legalcode_licenses_4.0.html \
        --ignore **/includes/legalcode_zero.html \
        --no-obsolete \
        --verbosity 2

(NOTE: it would be better for the Gettext Files to NOT have fuzzy entries)

Expectation

• The msigid strings should be based on the application text.
• The msgid strings in the translations should match the msgid strings in the source language (Transifex Resource)
• The translation status page should accurately communicate translation coverage (Percent Translated).

Additional context

• Gettext Files - Definitions - README.md
• Legacy ccEngine
  • creativecommons/cc.engine
  • creativecommons/cc.i18n
  • creativecommons/cc.license
  • creativecommons/cc.licenserdf
  • creativecommons/rdfadict

Description

This repo says that its license is CC0, but CC0 is a public domain dedication, not a license.

Reproduction

1. Look at the name of this file.
2. Look at this section of the README.
3. Open a PR. Notice how the DCO that this repo uses refers to “the open source license indicated in the file” and “the open source license(s) involved.” (moved to creativecommons/.github#24)

Expectation

HTML, RDF, Markdown and config files aren’t exactly software, but I would still expect this repo to follow CC’s recommendation for applying CC0 to software a little bit more closely. Specifically, I would expect the LICENSE file to be named COPYING. I would also expect that section of the README to be named “Copying” instead of “License”.

Resolution

• I would be interested in resolving this bug.

Description

On going through the legal code of this repository, noticed some bad styling at the level of some languages, This feature occurred because of a wrong import of the style.

Reproduction

To reproduce the bug check the cc-legal-tools-data/legacy/legalcode/by-nc-nd_2.0_ca_en.html and the french version at cc-legal-tools-data/legacy/legalcode/by-nc-nd_2.0_fr.html

Expectation

Screenshots

• Styled page
  

• Unstyled page:

Environment

• OS: Linux, distro: ubuntu(wayland 22.04)
• Browser: ( Firefox)

This bug is the data duplicate of [Bug] Deeds & UX: Clarify gettext translation domain and Transifex resource slug · Issue #164 · creativecommons/cc-licenses.

Problem

Legal code translation was added to current production:

• creativecommons/creativecommons.org#1264

Description

Cherry-pick commits to import legacy data into this repository

Import Process

1. creativecommons/creativecommons.org#1264
2. Clone this repository (creativecommons/cc-legal-tools-data)
   • Perform any needed configuration (ex. GnuPG signing)
   • (or use existing clone)
3. Create working/destination branch (from main default branch)

   git checkout -b cc4-fy

4. Add creativecommons/creativecommons.org as a remote (named legacy) and update branches

   git remote add legacy https://github.com/creativecommons/creativecommons.org.git

   git remote update

5. Identify commits in creativecommons/creativecommons.org:

   git log by*4.0_fy.html

6. Cherry-pick relevant commits::

   git cherry-pick 4444ee8779ac7b265594b36e1dedcb95f2d49ef3

   CONFLICT (file location): docroot/legalcode/by-nc-nd_4.0_fy.html added in 4444ee8779 (Added templates to start West-Frisian translation) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nc-nd_4.0_fy.html.
   CONFLICT (file location): docroot/legalcode/by-nc-sa_4.0_fy.html added in 4444ee8779 (Added templates to start West-Frisian translation) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nc-sa_4.0_fy.html.
   CONFLICT (file location): docroot/legalcode/by-nc_4.0_fy.html added in 4444ee8779 (Added templates to start West-Frisian translation) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nc_4.0_fy.html.
   CONFLICT (file location): docroot/legalcode/by-nd_4.0_fy.html added in 4444ee8779 (Added templates to start West-Frisian translation) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-nd_4.0_fy.html.
   CONFLICT (file location): docroot/legalcode/by-sa_4.0_fy.html added in 4444ee8779 (Added templates to start West-Frisian translation) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by-sa_4.0_fy.html.
   CONFLICT (file location): docroot/legalcode/by_4.0_fy.html added in 4444ee8779 (Added templates to start West-Frisian translation) inside a directory that was renamed in HEAD, suggesting it should perhaps be moved to legacy/legalcode/by_4.0_fy.html.
   error: could not apply 4444ee8779... Added templates to start West-Frisian translation
   hint: After resolving the conflicts, mark them with
   hint: "git add/rm ", then run
   hint: "git cherry-pick --continue".
   hint: You can instead skip this commit with "git cherry-pick --skip".
   hint: To abort and get back to the state before "git cherry-pick",
   hint: run "git cherry-pick --abort".

   git add legacy/legalcode/by-nc-nd_4.0_fy.html \
      legacy/legalcode/by-nc-nd_4.0_fy.html \
      legacy/legalcode/by-nc-sa_4.0_fy.html legacy/legalcode/by-nc_4.0_fy.html \
      legacy/legalcode/by-nd_4.0_fy.html legacy/legalcode/by-sa_4.0_fy.html \
      legacy/legalcode/by_4.0_fy.html

   git cherry-pick --continue

   git cherry-pick 37a04105af91fb86e5e74532df38676e753f518a

   git cherry-pick 79508d0deaf335e1c384a4af6e72e9f8ac200c70

   git cherry-pick 8078de871f6d29401ce0afb9920001bdda9edb8f

   git cherry-pick dd43a3b0844e9a26a501c01689f51a51ed0dfeed

   git cherry-pick 3d3700f5d9a14d1847a225afb66af8ef31b97b45

   git cherry-pick 56664070f366cbee182536b8930fe2e90f89047a

   git cherry-pick b5da18e08bff31474015e9e7d793f83e2435438e

   git cherry-pick 9a4bde46159633d94fe5f17b388c22f1de3e0acb

   git cherry-pick a278eee065059c104076088a31845a2c6de77c88

   git cherry-pick 06cfe331ec52cf16d020caf4e2e812c4a9ba29a2

   git cherry-pick 877fe3e75fa01ffa9dcaff9e7b0b348f063536c7

   git cherry-pick 6d7c4b67e6d3e6aa8cbcac5c505ac831ee2998f0

   git cherry-pick 580e082b2c51e3f6ae3223c622c7cffdd6d41098

   git cherry-pick ba6eb90e555ce5723cc932146bddf0b774b6e6c6

   git cherry-pick 40f6b3d287a224aee9c46b17a132ab74b9aec101

   git cherry-pick 0b3108558269967dcb1a5171be41b8daf9d68a56

   git cherry-pick c2c0648eb990602bb3953bf9abc72c7aab15ff7f

   git cherry-pick e2e0524d7950a709e12498eb24fa03a8b3d56d9a

7. Verify checksums of impacted files (in both this repo and creativecommons/creativecommons.org):

   md5sum by*4.0_da.html by*4.0_fy.html

   18253a979ce3f09e13c30fce31386b78  by-nc-nd_4.0_da.html
   f2691ec4485096bac1cef97021d559cb  by-nc-sa_4.0_da.html
   908ed94eb991a91821ab1a507c16bb0d  by-nc_4.0_da.html
   b03d3e4bce0c10cb59ee981d68237119  by-nd_4.0_da.html
   ae64a4fa5a67f533996e433404b99ee3  by-sa_4.0_da.html
   8e788b74ae852862ec525d44f5e0077e  by_4.0_da.html
   269aac1e9e0f096bb79dbd56576fd312  by-nc-nd_4.0_fy.html
   f45d62da8119a0deee4c38c4c2babf4c  by-nc-sa_4.0_fy.html
   2d5f235be22d6c6099dd9a4dc4b21631  by-nc_4.0_fy.html
   0cbecf4573bdec0cec11a9231046b84c  by-nd_4.0_fy.html
   7bf6a408aa8b47a4de2d3ed555e3720c  by-sa_4.0_fy.html
   f2b4199bcf5b8ad202e00edabee42f58  by_4.0_fy.html
   

8. Remove remote legacy and update branches

   git remote remove legacy

   git remote update

9. Push cc4-fy branch and create Pull Request

Additional context

• Importing/Cherry-picking
  • Accepted Answer - linux - How to copy commits from one Git repo to another? - Stack Overflow
  • Git cherry-pick syntax and merge branches - Stack Overflow
    • NOTE: The merge commits should not be cherry-picked. If they are included, they will be empty because the underlying commits are included.
  • creativecommons/vocabulary#1083
  • #112
  • #122

Description

Legal Code translation on Transifex contain QA messages and extraneous whitespace (note that this is a bug about Transifex data, not data contained within this repository).

Reproduction

Extraneous whitespace examples

• the local data is the red/- and is correct; the Transifex data is green/+ and is wrong
• the local data path is from a docker container

--- CC BY-SA 4.0 PO File /home/cc-licenses-data/legalcode/lt/LC_MESSAGES/by-sa_40.po
+++ CC BY-SA 4.0 Transifex by-sa_40 lt
@@ -1,11 +1,11 @@
 msgid ""
 "Nothing in this Public License constitutes or may be interpreted as a "
 "limitation upon, or waiver of, any privileges and immunities that apply to "
 "the Licensor or You, including from the legal processes of any jurisdiction "
 "or authority."
 msgstr ""
-"Jokia šios Viešosios licencijos nuostata nenustato ir negali būti aiškinama "
-"kaip nustatanti bet kokių Licenciarui ar Jums taikomų lengvatų ar išimčių "
-"(imuniteto) apribojimą ar atsisakymą, įskaitant dėl teisinių procedūrų, bet "
-"kokioje jurisdikcijoje atliekamų bet kokios institucijos."
+"Jokia šios Viešosios licencijos nuostata nenustato ir negali būti  aiškinama"
+" kaip nustatanti bet kokių Licenciarui ar Jums taikomų lengvatų ar  išimčių "
+"(imuniteto) apribojimą ar atsisakymą, įskaitant dėl teisinių  procedūrų, bet"
+" kokioje jurisdikcijoje atliekamų bet kokios institucijos."

--- CC BY-ND 4.0 PO File /home/cc-licenses-data/legalcode/lt/LC_MESSAGES/by-nd_40.po
+++ CC BY-ND 4.0 Transifex by-nd_40 lt
@@ -1,7 +1,7 @@
 msgid ""
 "a URI or hyperlink to the Licensed Material to the extent reasonably "
 "practicable;"
 msgstr ""
-"universalųjį ištekliaus identifikatorių (URI) ar interaktyvią nuorodą į "
+"universalųjį ištekliaus identifikatorių (URI) ar     interaktyvią nuorodą į "
 "Licencijuojamą Objektą, kiek tai įmanoma;"

QA messages example

• the local data is the red/- and is correct; the Transifex data is green/+ and is wrong
• the local data path is from a docker container

--- CC BY 4.0 PO File /home/cc-licenses-data/legalcode/de/LC_MESSAGES/by_40.po
+++ CC BY 4.0 Transifex by_40 de
@@ -1,3 +1,3 @@
 msgid "Attribution 4.0 International"
-msgstr "Namensnennung 4.0 International"
+msgstr "Namensnennung 4.0 International KAT EDIT"

--- CC BY 4.0 PO File /home/cc-licenses-data/legalcode/es/LC_MESSAGES/by_40.po
+++ CC BY 4.0 Transifex by_40 es
@@ -1,20 +1,21 @@
 msgid ""
 "By exercising the Licensed Rights (defined below), You accept and agree to "
 "be bound by the terms and conditions of this Creative Commons Attribution "
 "4.0 International Public License (\"Public License\"). To the extent this "
 "Public License may be interpreted as a contract, You are granted the "
 "Licensed Rights in consideration of Your acceptance of these terms and "
 "conditions, and the Licensor grants You such rights in consideration of "
 "benefits the Licensor receives from making the Licensed Material available "
 "under these terms and conditions."
 msgstr ""
 "Al ejercer los Derechos Licenciados (definidos a continuación), Usted acepta"
 " y acuerda estar obligado por los términos y condiciones de esta Licencia "
 "Internacional Pública de Atribución/Reconocimiento 4.0 de Creative Commons "
 "(\"Licencia Pública\"). En la medida en que esta Licencia Pública pueda ser "
 "interpretada como un contrato, a Usted se le otorgan los Derechos "
 "Licenciados en consideración a su aceptación de estos términos y "
 "condiciones, y el Licenciante le concede a Usted tales derechos en "
 "consideración a los beneficios que el Licenciante recibe por poner a "
-"disposición el Material Licenciado bajo estos términos y condiciones."
+"disposición el Material Licenciado bajo estos términos y condiciones. KAT "
+"TEST DELETE"

Expectation

Translations should be free of errors and cruft.

Additional context

Related PRs:

• Transifex push (code) by TimidRobot · Pull Request #201 · creativecommons/cc-licenses
• #43

Description

The Creative Commons webpage is currently using an outdated Twitter logo.

Reproduction

1. Visit the Hero section of the webpage
2. See the button which says "Follows us on Twitter"
3. Visit the footer section of the webpage
4. See the social media icons.

Expectation

The website should display the most up-to-date version of the Twitter logo, adhering to current branding guidelines.

Screenshots

Description

Published docs/ contains mixed-case files which cause an inconsistent experience between GitHub (case sensitive) and macOS development environments.

GitHub Pages failed to build your site.:

The symbolic link /data/pages-builds/pagebuilds/creativecommons/cc-licenses-data/licenses/by/3.0/cn/legalcode.html targets a file which does not exist within your site's repository.

Reproduction

• /docs/licenses/by-nc/3.0/cn/legalcode.zh-Hans.html is the current file name (mixed case)
• /docs/licenses/by-nc/3.0/cn/legalcode.zh-hans.html is the desired file name (all lowercase)

Expectation

The repository should not introduce complications for macOS developers

Additional context

I expect I introduced this bug in one of the following PRs if it is a data (git) issue:

• #28
• #29

If it is a code issue, I will open an a new issue in creativecommons/cc-licenses.

Description

Ensure Transifex is updated with NL changes in the following PRs and those changes are pulled down into updated .po and .mo files:

• partially fix layout / html formatting of BY*ND Dutch translations by TimidRobot · Pull Request #1160 · creativecommons/creativecommons.org
• Legacy Import 2021-05-19 by TimidRobot · Pull Request #18 · creativecommons/cc-licenses-data

Description

• CC BY 4.0 法律文本 | 署名 4.0 国际 | Creative Commons
• CC BY-NC 4.0 法律文本 | 署名-非商业性使用 4.0 国际 | Creative Commons
• CC BY-NC-ND 4.0 法律文本 | 署名-非商业性使用-禁止演绎 4.0 国际 | Creative Commons
• CC BY-NC-SA 4.0 法律文本 | 署名-非商业性使用-相同方式共享 4.0 国际 | Creative Commons
• CC BY-ND 4.0 法律文本 | 署名-禁止演绎 4.0 国际 | Creative Commons
• CC BY-SA 4.0 法律文本 | 署名-相同方式共享 4.0 国际 | Creative Commons

In Simplified Chinese Version of all CC 4.0 Licenses, there are 2 fatal mis-tranlations at their parts of Section 2(b)(1):

1. The corresponding translation to "but not otherwise" is missing;
2. The corresponding translation to "limited" of "to the limited extent necessary" is missing.

依据本公共许可协议，著作人身权，例如保护作品完整权、形象权、隐私权或其他类似的人格权利，不在许可范围内。但是，在条件允许的情况下，许可人可以在必要范围内放弃和/或同意不主张其权利，以便您行使本协议所授予的权利。

Reproduction

Section 2(b)(1) of CC BY-SA 4.0 is written as follows, and I quote:

Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.

In its Simplified Chinese Version, it is written as follows, and I quote:

依据本公共许可协议，著作人身权，例如保护作品完整权、形象权、隐私权或其他类似的人格权利，不在许可范围内。但是，在条件允许的情况下，许可人可以在[Missing 1]必要范围内放弃和/或同意不主张其权利，以便您行使本协议所授予的权利[Missing 2]。

In contrast, in the Tranditional Chinese Version, it is written as follows, and I quote:

著作人格權 / 精神權利，例如禁止不當修改權，形象權、隱私權及/或其他相似人格權，皆不在本公眾授權條款授權範圍內；然而，在可行範圍內，授權人放棄及/或同意在有限必要範圍內不主張該等授權人擁有的權利，以允許您行使本授權權利，但以前述情形為限。

Expectation

1. In the placeholder of [Missing 1], replace the placeholder with the word "有限"。
2. In the placeholder of [Missing 2], replace the placeholder with the phrase "，但以前述情形为限"。
3. Delete "可以"

依据本公共许可协议，著作人身权，例如保护作品完整权、形象权、隐私权或其他类似的人格权利，不在许可范围内。但是，在条件允许的情况下，许可人在有限必要范围内放弃和/或同意不主张其权利，以便您行使本协议所授予的权利，但以前述情形为限。

Resolution

• I would be interested in resolving this bug.

Problem

The title of this repo is misleading. This repo does contain data about Creative Commons licenses, but it also contains data about the CC0 Public Domain dedication and the Public Domain Mark.

Description

Rename this repo to “cc-legal-tools-data”.

Alternatives

Something could be added to the README that acknowledges the fact that the name isn’t quite accurate. cc-licenses already does this. I think that renaming is a better option though. It’s less misleading, requires less text and raises awareness that not all Creative Commons legal tools are licenses.

Implementation

• I would be interested in implementing this feature.