The designer of this FontStruction has chosen not to make it available for download from this website by choosing an “All Rights Reserved" license.
Please respect their decision and desist from requesting license changes in the comments.
If you would like to use the FontStruction for a specific project, you may be able to contact the designer directly about obtaining a license.
37 Comments
The original letters are hardly recognizable, if at all, since I've customised the lower case, fully reshaped the numbers, added the capitals, special characters, punctuation marks, as well as the extended latin glyphs. I opted for horizontal gaps, as it enhances the horizontal strokes nicely. It was a challenge to work with a 2x4 or 3x4 brick array, and wrestle with FS' limited capacity of spacing and kerning.
But i fell in love with the g.
makes me want to write gorgeous over and over. gorgeous!
I also enjoy the & and @, 4, but specially the +
@funk_king: The answer to your question was already given in my first comment. will.i.ૐ said basically the same thing. I've changed so many things, the original could not possibly be identified by just looking at it. I've provided the info and the hyperlink to be truthful and historically correct. I think my work won't be any less if I admit its origin.
@will.i.ૐ: Thank you for your comment. There is another way of
ripping off fontstructions: simply copy and paste glyph by glyph without a trace. It is a bit more tedious, but very clean method. I was thinking about to warn Rob Meek, and tell him the possible dangers before this feature had been introduced. But then I thought the benefits greatly outweigh the risks.
I've learned a new word, a slang: rad. Thanks.
I've changed the name from Chromosomes to the more specific Karyotype. The new name is also chromosome related (for details see Wikipedia.org) but has the "T word" in it.
* * *
We are aware of the problem reported by will.i.ૐ, and we're are working to fix it. Clones need not only to mantain the links to original FontStructions, but also honour its license – this somehow also got broken in this FontStruction.
In this case, the original license from Leaflet Stem is Attribution-Noncommercial-Share Alike. The “Share Alike” part says that If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. Karyotype has a Attribution-Noncommercial-No Derivative Works license, which violates the original license – clones need to remain clonable.
The correct statement would have been: “clones of FontStructions with Share-Alike licenses need to have the same license as the original FontStruction”. Since Leaflet Stem has a Attribution-Noncommercial-Share Alikelicense, Karyotype should be licensed under the same terms (because of the “Share Alike” part).
If you, frodo7, don't like the terms under which the original FontStruction was licensed, you shouldn't have cloned it in the first place. Licenses need to be carefully studied and considered up-front. We all need to get used to that.
Of course I can see the differences in the final design, and I do understand your feelings about it's future. (I have done a lot of work on GPL fonts, for example, and I can't change their license either). The solution for you to break free from the viral “Share-Alike” clause would be to rebuild your design from scratch. Small-grid FontStructions such as this one can be built quite quickly (in comparison to high-res ones or ‘real’ outline fonts). Once you have done that, you are free to choose whatever license you want, since it will be 100% your work and effort.
Copy & paste is indeed a grey zone. AFAIK, we don't have any mechanism in place to prevent copy&paste between fonts with incompatible licenses. In this particular case I would consider copy&paste cheating – the brick assembly work would still be someone else's, you just woudn't credit it. I wouldn't feel good about it.
(I'm not a lawyer, so all the above is not legal advice but my personal interpretation as a designer and user.)
Or even a way for the two parties (cloner and clonee) to contact the mods to request such a change?
- Lex
P.S. I love the 'E' in Karyotype. Very wiggly :-)
There are two things I'd like to see in the future: 1, More license options. 2, the ability for the original designer to know how many of the clones exist for any particular fontstruction, even if they are not yet shared.
Anyway, I wished for the ability to give a copy of a font to another specific user.
Then I can make a font public, but not cloneable. However, if there is someone I'm willing to give the "source" to, I can send them a copy.
As you and others suggested, I have a few options.
1. Unshare the font. I think in this case it would be a very ungentlemanly thing.
2. Rebuild it from scratch. That would be within the legal requirements, but I don't feel particularly good about it. No, this font remains open to cloning, and I'm happy with it. Let's hope to see some clever new mutations coming, and no malicious copy cats on those web sites (you know what I'm talking about).
3. While creating this font I have discarded some variations. I could dust them off and make a new font, with a slightly different flavour, free of any inherited limitations. Perhaps I may do this some day.
I feel somewhat embarrassed about the whole issue. To me this particular font was of lesser importance. I didn't want to make so much fuss about some ditzels. And I feel some times sympathy for you. It is the most difficult to deal with creative people. They are the worst of all kind: they are far too conceited, demanding, often impatient, have critical opinion and independent thinking. But what is left without them: only sheep.
Keep on producing you excellent designs and remain the generous, encouraging member of this community that you are.
Amogus
what
Please sign in to comment.