Doc needs "how to build" section

notofonts / notobuilder

Python module for building Noto fonts

9 stars 0 forks source link

Doc needs "how to build" section #15

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

For those of us who want to hack on these fonts, can you add a "how to build" 
section in the documentation ?

Original issue reported on code.google.com by s...@lambdacurry.com on 16 Jul 2014 at 7:10

GoogleCodeExporter commented 9 years ago

it would also be great if you could add the design specifications for each 
script (e.g. http://www.microsoft.com/typography/OpenTypeDev/oriya/intro.htm).

What you have built is  path breaking for a lot of languages (like Brahmi for 
example) and it will be great to preserve all the groundwork within the 
codebase !

Original comment by s...@lambdacurry.com on 16 Jul 2014 at 7:13

GoogleCodeExporter commented 9 years ago

Original comment by stua...@google.com on 16 Jul 2014 at 7:54

Added labels: Type-Enhancement
Removed labels: Type-Defect

GoogleCodeExporter commented 9 years ago

Original comment by roozbeh@google.com on 16 Jul 2014 at 6:17

GoogleCodeExporter commented 9 years ago

Original comment by roozbeh@google.com on 16 Jan 2015 at 5:59

GoogleCodeExporter commented 9 years ago

Original comment by stua...@google.com on 28 Feb 2015 at 12:22

hrhatada commented 7 years ago

Hi Xiangye, have we add this to the docs or FAQ yet?