License clarification for text specimens in the Source Han Code JP repository

[chrissimpkins]

We are developing a new CJK typeface gallery for developers in Codeface and one of our collaborators is interested in the use of the text / code specimens in your resources directory for all of the fonts that will be included in the gallery (issue report https://github.com/chrissimpkins/codeface/issues/114).

These are the specimens that we are interested in using:

• https://github.com/adobe-fonts/source-han-code-jp/blob/master/resources/img-AA.png
• https://github.com/adobe-fonts/source-han-code-jp/blob/master/resources/img-View.png

It is unclear from the SIL OFL license how we use and attribute these specimens in our project. Any guidance?

[kenlunde]

@chrissimpkins: I am replying on behalf of the project owner.

We understand that the license that is included with the project, OFL, is not appropriate for images. We didn't anticipate such a desire. Because the project owner has no problem with sharing the images in the project, please suggest an specific open source license that suits your purposes.

[chrissimpkins]

@kenlunde Thank you very much Ken. We are actually interested in the glyph patterns (i.e. the source code example and the glyph pattern that demonstrates vertical and horizontal metrics of the fonts with ASCII glyphs adjacent to CJK set glyphs) rather than the actual included images as released in your repository. We would like to generate our own images with other fonts using these text specimens, or something that uses these as a base and includes our own modifications, as examples over a number of available CJK typefaces that are aimed at source code developers. Perhaps MIT licenses on both?

[kenlunde]

@chrissimpkins: Ah. Brain fart. You don't want to use the images, but rather the text that was used to create them. Got it now.

If you feel that such text files, which would need to be added to the repository, require some form of license, please point us to a specific license (using a URL) so that @hatchzo, the project's owner, can add the text files, along with the appropriate license file.

[chrissimpkins]

@kenlunde The URL for the text of the MIT license is http://opensource.org/licenses/MIT and the body of the license is as follows:

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

@hatchzo: Masataka, please let me know if I can provide any additional information.

Thank you both very much for all of your help and willingness to share these with us. I greatly appreciate it.

[chrissimpkins]

Also, please let us know how it would be appropriate to provide attributions for these resources. I am happy to link back here with both/either of your names or Adobe. Whatever you feel is appropriate.

Thanks again.

[kenlunde]

@chrissimpkins: I just provided to @hatchzo a LICENSE.txt file, which he will place into the "resources" directory, along with ".txt" versions of the ".png" files that contain the text data for the images. Attributions can simply be in the form of links back to this project.

[chrissimpkins]

@kenlunde Thank you! This is extremely helpful Ken.

[kenlunde]

I know that I speak for @hatchzo when I state that it is our pleasure to help in this small way. 🍻

[kenlunde]

@hatchzo: Be sure to close this issue after you have added the LICENSE.txt and ".txt" files to the "resources" directory. For the encoding of the ".txt" files, I suggest UTF-8.

[hatchzo]

OK, I understood what I should do, I will look the text files that are used in the images.

[hatchzo]

I added img-AA.txt, img-View.txt and LICENSE.txt into the "resources" folder. I hope these files help you.

[chrissimpkins]

@hatchzo Thank you very much Masataka! I will have a look at them later today. I really appreciate your help. I will close the issue now that this has been addressed.