Adding NotoSans subset font file which is required to test new language

LayoutTests/third_party/NotoSans/README.txt

Index: LayoutTests/third_party/NotoSans/README.txt
diff --git a/LayoutTests/third_party/NotoSans/README.txt b/LayoutTests/third_party/NotoSans/README.txt
new file mode 100644
index 0000000000000000000000000000000000000000..c07557ca40af0bde563e15f1838b0ffc2835bb2c
--- /dev/null
+++ b/LayoutTests/third_party/NotoSans/README.txt
@@ -0,0 +1,19 @@
+Noto Sans Font:
+
+1. Source Origin
+Google's Internationalisation team's: 
+    a) https://code.google.com/p/noto/
+    b) https://code.google.com/p/noto/source/browse/trunk/fonts/individual/
+
+2. LICENSE AND OPENSOURCE
+	For license information, see the LICENSE.txt file
+
+3. Reason:
+Font file included as a real-world example for testing fonts with same script but different language, Devanagari and Nepali in this case 
+with LayoutTests/fast/text/shaping/same_script_different_lang.html test case
+
+Command to generate subset font:
+$ pyftsubset ./NotoSansDevanagari-Regular.ttf <Unicode>

[Dominik Röttsches, 2014/05/20 08:49:25]

I believe Dirk meant the actual command here, not a placeholder for the
codepoint.

$ pyftsubset ./NotoSansDevanagari-Regular.ttf uni091D

(From Behdad's comment.)

Also, on blink-dev he recommends to call the file README.Chromium - but this may
not be as critical.

[Dirk Pranke, 2014/05/20 15:40:56]

Right.
Also, right. The general convention we use is README.chromium, so that it's
clear that this README is associated with instructions for Chromium devs, rather
than a README that might be carried over from the original project.

+
+where pyftsubset comes from https://github.com/behdad/fonttools
+