-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
d53dc2a
commit e10a68f
Showing
7 changed files
with
119 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Contributing to the Nupuram Project | ||
|
||
## Types of contributions | ||
|
||
**Issues** | ||
|
||
If you find something that’s not working as you expect, please file an issue | ||
|
||
**Documentation improvements** | ||
|
||
If you find a typo or something that seems out of date in the Readme, etc, please feel free to file a Pull Request with your suggested change(s) | ||
|
||
**Type design fixes/changes** | ||
|
||
Type design is a bit of a special case for open source projects, because type tends to benefit from a central, strong creative & technical direction. There are probably exceptions to this, but Recursive is not really one of them. | ||
|
||
That said, type design contributions are very highly valued here, but they require a connection and personal communication to go well. | ||
|
||
Have an idea for something that you think would be worth changing in the design? Cool! You have two good options: | ||
|
||
1. File an issue to point out the design problem, and mention your idea/request to fix it, if you have one. We will try to comment on the issue fairly promptly, and the proposed solution can be discussed before a course of action is decided. | ||
2. Alternatively, this project is [OFL-licensed](OFL.txt), so you are welcome to fork the repo and make whatever changes you like, so long as you keep the same license and respect its provisions. In this scenario, please be sure to change the font family name to avoid user confusion. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
## Can I help with improving Nupuram? | ||
|
||
Yes you can! Nupuram is an open-source project, meaning the source code—or "source design" if you will—that is used to build the font files are freely available to improve upon. Font making requires a fair bit of technical work and depending on what you'd like to do, some things might be more fun depending on your technical skills. Please start by reading and exploring the source code and design files provided. | ||
|
||
Also see [CONTRIBUTING.md](CONTRIBUTING.md) | ||
|
||
## I like to modify some of the glyphs or opentype rules and redistribute the font. What are the recommendations to do that? | ||
|
||
Nupuram is licensed as Open Font License, which gives you the freedom to modify the font for your need and redistribute it as per the license. However a few points should be noted: | ||
|
||
* If the modified and redistributed font has the same name of original font, it will overwrite existing font in operating systems. A user won't be able to use the original Nupuram font. If editable documents are opened and saved in same operating system, they will be re-rendered in the modified version, which the user might not want. So avoid this disruption by renaming the modified version of the font. | ||
* The glyphs, its design, its engineering, its opentype rules are the identity of the font. If you are renaming the font, please choose a completely different name that has no relation with Nupuram. For example, Nupuram New, Nupuram Modern etc would give a misunderstanding that the designer of Nupuram released new version of Nupuram and would attribute the new font with the designer. This is undesirable to the designer since the modified font cannot be supported by the designer. Please spare the designer of the original font from responding to support requests that actually stem from bugs in a modified version. | ||
* See section 3 and 4 of OFL license under "PERMISSION & CONDITIONS" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters