pax_global_header 0000666 0000000 0000000 00000000064 12646401513 0014514 g ustar 00root root 0000000 0000000 52 comment=08a91f24445853e63705abea129a7cea639ca1d8
noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/ 0000775 0000000 0000000 00000000000 12646401513 0020542 5 ustar 00root root 0000000 0000000 noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/FAQ.md 0000664 0000000 0000000 00000011175 12646401513 0021500 0 ustar 00root root 0000000 0000000 Q: How do I file a bug?
A: Visit our project bug list at - https://github.com/googlei18n/noto-fonts/issues Please be sure to give as much detail as possible. If it’s a technical issue then list the software and operating system being used as well as versions. If it’s a design issue then images and diagrams are very helpful.
Q: When will language or script X be supported by Noto?
A: We do intend to support all scripts encoded by Unicode. That takes time and the ordering is based on a complex changing mix of factors including but not limited to: complexity of the script, product and project needs, availability of script experts and designers, and number and responsiveness of language reviewers.
Q: Why did you do a font for script X before script Y?
A: No matter what order you choose to develop the fonts some scripts will come before others. Think of it like serving a banquet meal for 1000 people. You can either serve the meals as they are ready which means that some will get served before others or you can wait until all the meals are ready before you serve anybody. We’ve taken the approach of serving as each is ready.
Q: What is the Noto design?
A: Noto provides pan-language harmony, yet maintains authenticity. The goal is great online readability across languages without losing the character that makes each script special. The intention is to create the equivalent of the stylish yet conservative item of clothing that you can keep in your wardrobe forever rather than the highly stylish item that goes out of style in a single season.
Q: Who designs Noto?
A: Google provides the direction, planning, and final aesthetic decisions. We employ and collaborate with “native speakers” with type and design experience and some of the best talent in the font industry to develop fonts for each script to meet the Noto design goals.
Q: How is a Noto font developed?
A: Noto fonts for each script are developed in a collaborative approach. We work together with font foundries, design houses, and talented designers to develop requirements for each script and for the languages that use that script. Those requirements then lead to design proposals. We then work with reviewers who are native readers of the languages (for living languages) for which the fonts are being designed (often they are experts in the language or it’s typography) to refine the design proposals. Sometimes this requires working through conflicting design reviews and the careful tweezing out of personal preference. Once the design proposal has been fully vetted, a cycle of font development along with review at each step goes on. How long this takes will vary for each script based on a range of factors including the complexity, number and responsiveness of reviewers, number of glyphs required, and conflicting resource allocation. At the end of all this a technical review of the font is made to hopefully catch any issues. This isn’t foolproof and just like every shipping software system on the planet there will be issues. If you find one then file a bug and we’ll look after it.
Q: Is Noto just a copy of font X?
A: Noto Sans for Latin was designed by the same person, Steve Matteson, who has worked with us on other Latin script fonts before. Noto Sans for Latin and these earlier designs have some of the same design goals and with the same designer working on them they do share some resemblance.
Q: What's the difference between the UI and non-UI versions?
A: These fonts were initially prepared for use in Android's UI. They have tighter vertical metrics, and some glyphs that would therefore be clipped are redrawn to fit within the constrained space. They can be used anywhere that has limited vertical space. There are no UI verions of scripts that do not need such adjustment, and the non-UI versions should be preferred for use in body text.
Q: What about Han unification?
A: Whether or not Han unification is a good thing is really a moot point at this time. It’s a fact of life that needs to be worked with when designing fonts or text processing systems for the CJK languages. We are building fonts to be used in systems that exist now and that means working within the frameworks that exist.
If somebody would like to change those frameworks then they should get involved with the standards bodies and contribute to the development of the standard and change the direction they are going.
Q: When will Google support Klingon / Elvish / etc.?
A: Once Klingon / Elvish / etc. is included in Unicode :). Please contact the Unicode consortium to encourage them to support your favourite invented language.
The Unicode Consortium
P.O. Box 391476
Mountain View, CA 94039-1476
U.S.A.
noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/LICENSE 0000664 0000000 0000000 00000010315 12646401513 0021547 0 ustar 00root root 0000000 0000000 This Font Software is licensed under the SIL Open Font License,
Version 1.1.
This license is copied below, and is also available with a FAQ at:
http://scripts.sil.org/OFL
-----------------------------------------------------------
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
-----------------------------------------------------------
PREAMBLE
The goals of the Open Font License (OFL) are to stimulate worldwide
development of collaborative font projects, to support the font
creation efforts of academic and linguistic communities, and to
provide a free and open framework in which fonts may be shared and
improved in partnership with others.
The OFL allows the licensed fonts to be used, studied, modified and
redistributed freely as long as they are not sold by themselves. The
fonts, including any derivative works, can be bundled, embedded,
redistributed and/or sold with any software provided that any reserved
names are not used by derivative works. The fonts and derivatives,
however, cannot be released under any other type of license. The
requirement for fonts to remain under this license does not apply to
any document created using the fonts or their derivatives.
DEFINITIONS
"Font Software" refers to the set of files released by the Copyright
Holder(s) under this license and clearly marked as such. This may
include source files, build scripts and documentation.
"Reserved Font Name" refers to any names specified as such after the
copyright statement(s).
"Original Version" refers to the collection of Font Software
components as distributed by the Copyright Holder(s).
"Modified Version" refers to any derivative made by adding to,
deleting, or substituting -- in part or in whole -- any of the
components of the Original Version, by changing formats or by porting
the Font Software to a new environment.
"Author" refers to any designer, engineer, programmer, technical
writer or other person who contributed to the Font Software.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed,
modify, redistribute, and sell modified and unmodified copies of the
Font Software, subject to the following conditions:
1) Neither the Font Software nor any of its individual components, in
Original or Modified Versions, may be sold by itself.
2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
3) No Modified Version of the Font Software may use the Reserved Font
Name(s) unless explicit written permission is granted by the
corresponding Copyright Holder. This restriction only applies to the
primary font name as presented to the users.
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
Software shall not be used to promote, endorse or advertise any
Modified Version, except to acknowledge the contribution(s) of the
Copyright Holder(s) and the Author(s) or with their explicit written
permission.
5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created using
the Font Software.
TERMINATION
This license becomes null and void if any of the above conditions are
not met.
DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.
noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/NEWS 0000664 0000000 0000000 00000001602 12646401513 0021240 0 ustar 00root root 0000000 0000000 September 29, 2015
All Noto fonts now licensed under Open Font License 1.1
=======================================================
With the new release we have moved from Apache 2.0 to Open Font License 1.1 (OFL 1.1). We
are making this change because it makes it easier for you, the end users of Noto, to use
the fonts that we produce. When we first released the Noto fonts the OFL license was
still a bit of an unknown entity and the Apache license looked familiar to us. Over the
years the OFL license has become the most commonly used and understood license to use for
open source fonts.
All of our fonts going forward from this release will be available only under the OFL
license. If you still want the fonts under the Apache license you can get them from the
repo using the tag 'v2015-09-29-license-apache'. However, new fonts and updates to
existing fonts will use the OFL license.
noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/README.md 0000664 0000000 0000000 00000005175 12646401513 0022031 0 ustar 00root root 0000000 0000000 
# Noto fonts
Noto's goal is to provide a beautiful reading experience for everyone and for all languages. With visual harmony when multiple languages share a page. With multiple styles and weights. And **_Freely available to all._**
Currently, Noto covers all major languages of the world and many others, including European, African, Middle Eastern, Indic, South and Southeast Asian, Central Asian, American, and East Asian languages. Several minority and historical languages are also supported.
Support for Simplified Chinese, Traditional Chinese, Japanese, and Korean was first added in July 2014.
You can preview and download the Noto fonts at http://www.google.com/get/noto.
Noto fonts are open source. All fonts are published under the [SIL Open Font License, Version 1.1](http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&id=OFL). (Prior to September 29, 2015, Noto fonts other than CJK were published under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html).)
Use unhinted fonts for Android and Mac (Android and Mac ignore hinting information embedded in fonts). Use hinted fonts for other platforms.
## Development
All Noto fonts are included in this repository, except:
* Noto CJK fonts are in [noto-cjk](https://github.com/googlei18n/noto-cjk),
* Noto Emoji and Noto Color Emoji are in [noto-emoji](https://github.com/googlei18n/noto-emoji).
Tools used for testing fonts are in [nototools](https://github.com/googlei18n/nototools).
Noto was moved from Google Code to github in June 2015.
Development and user discussions happen on the [noto-font Google Group](https://groups.google.com/d/forum/noto-font).
## News
* [2015-09-29](NEWS): All Noto fonts now licensed under Open Font License 1.1.
* 2015-06-08: Noto project moved from Google Code to github.
* 2015-04-20: Noto Sans CJK Version 1.002 released.
* 2015-03-30: Noto Sans Oriya and and a new design for Armenian fonts released.
* 2014-10-23: Experimental version of Noto Nastaliq Urdu released.
## Special Note on Droid and Noto
Droid fonts have been superseded by Noto. We renamed Droid fonts to Noto and only update the Noto family since renaming. Now, Noto not only gives better support to all languages covered by Droid (in terms of more characters and fewer bugs), but also covers many more languages. Both Android and Chrome OS have switched to Noto. We strongly recommend everyone to replace Droid with Noto and check out new languages supported by Noto in this repo.
Find Noto Sans CJK that replaces Droid Sans Fallback at https://github.com/googlei18n/noto-cjk.
Have fun!
Google Internationalization Team
noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/alpha/ 0000775 0000000 0000000 00000000000 12646401513 0021627 5 ustar 00root root 0000000 0000000 noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/alpha/COPYING 0000777 0000000 0000000 00000000000 12646401513 0024075 2../LICENSE ustar 00root root 0000000 0000000 noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/alpha/LICENSE 0000777 0000000 0000000 00000000000 12646401513 0024047 2../LICENSE ustar 00root root 0000000 0000000 noto-fonts-08a91f24445853e63705abea129a7cea639ca1d8/alpha/NotoSansHistoric-Regular.ttf 0000664 0000000 0000000 00004416034 12646401513 0027232 0 ustar 00root root 0000000 0000000 `GDEFD=* GPOST nGSUB6I
OS/2Hx h `cmapu : gasp glyfMI {\ |Iheado 6hhea+(( $ $hmtxGh 8loca[ B 8maxpu H name% posti f I_<