Git Product home page Git Product logo

intel-one-mono's Introduction

Intel One Mono Typeface

Image of Intel One Mono character set

Introducing Intel One Mono, an expressive monospaced font family that’s built with clarity, legibility, and the needs of developers in mind.

It’s easier to read, and available for free, with an open-source font license.

Identifying the typographically underserved low-vision developer audience, Frere-Jones Type designed the Intel One Mono typeface in partnership with the Intel Brand Team and VMLY&R, for maximum legibility to address developers' fatigue and eyestrain and reduce coding errors. A panel of low-vision and legally blind developers provided feedback at each stage of design.

Intel One Mono also covers a wide range of over 200 languages using the Latin script. The Intel One Mono fonts are provided in four weights — Light, Regular, Medium, and Bold — with matching italics, and we are happy to share both an official release of fonts ready to use as well as editable sources.

Using the Fonts

To install the fonts, please use the provided builds under Releases. Please refer to your software’s documentation for how to activate and use these fonts.

Activating the Fonts in Code Editors

  • VSCode - In Settings, search Font Family, then specify Intel One Mono
  • Sublime Text - Go to Sublime Text -> Preferences -> Settings and set font_face to Intel One Mono
  • IntelliJ Platform - Go to File -> Settings -> Editor -> Font and set Font to Intel One Mono

Font Formats

  • We recommend the .otf or .ttf format for desktop use.
  • The .ttf files are also well suited for mobile apps.
  • The .woff and .woff2 fonts are optimized for web use.

Screen Rendering and Size Ranges

We recommend using these fonts at 7 points and larger in print, 9 pixels and larger on screen. The .ttf, .woff and .woff2 fonts provided in the official release have been manually optimized for screen display, improving clarity and legibility, especially on Windows platforms.

Available OpenType Features

Outside of the default characters, there are a few extra features that are accessible in some applications, as well as via CSS:

  • Raised Colon: there is an option for a raised colon, either applied contextually between numbers or activated generally. The contextual option is available via ss11 (Stylistic Set #11), or use ss12 (Stylistic Set #12) or salt (Stylistic Alternates) for the global switch. Also, the colon will automatically be raised in operators, to align with math symbols.
  • Language Support: ccmp and locl features ensure correct display across a wide range of languages. These are usually activated by default. We recommend setting the language tag/setting in your software to the desired language for best results.
  • Superior/superscript and inferior/subscript figures are included via their Unicode codepoints, or you can produce them from the default figures via the sups (Superscript), subs (Subscript), and si (Scientific Inferior) features.
  • Fraction numerals are similarly available via the numr (Numerator) and dnom (Denominator) features. A set of premade fractions is also available in the fonts.

Viewing and Editing Sources

UFO Source Files: Instances

You will find editable sources in the sources directory. The instances subfolder contains separate source files for each style of the typeface. Sources are provided in .ufo files, which contain complete artwork, OpenType features, as well as meta information like naming and vertical alignments for each style of the typeface.

These are not installable fonts, but rather the source files that produce them: UFO (Unified Font Object) is an open, human-readable font source file format; you can find the file spec here. These sources were created using RoboFont. Many other font editors will also be able to open .ufo files; we recommend using RoboFont version 3.4 or up for the closest approximation of the original design and development environment.

Outline Formats

For instances, you will find postscript and truetype subfolders; these contain separate source files for the .otf format and the .ttf/.woff/.woff2 files respectively. Since the format for the outline drawings differs between these sets of formats, for best results we recommend using the postscript sources to create .otf fonts, and the TrueType sources to create .ttf, .woff, or .woff2 fonts.

Generating Fonts

After making your desired edits, you can generate installable fonts directly from the font editor using its “Generate Font” functionality. If you use RoboFont, any install options should default to the ideal settings, but here they are for reference:

  • For .otf builds, we recommend activating “Decompose” as well as “Autohint” options.
  • For .ttf, .woff and .woff2 builds, we recommend activating the “Autohint” option only for more compact files (see note on hinting below).
  • In any case, we recommend using the “Release Mode” setting for best results.

UFO Source Files: Masters

If you would like to apply edits across multiple weights, a more advanced yet potentially efficient way is to edit the masters. These are special sources that describe the extreme points in the design space — the lightest and heaviest weights for both roman and italic designs.

After editing masters, you will need to rerun interpolation to generate individual weights and styles within that design space. This requires the .designspace files enclosed with the masters; the designspace format is an open, XML-based format that describes interpolation spaces (format specification for reference). For a RoboFont-based workflow we recommend Skateboard for interpolation; you can also use the free DesignSpaceEditor extension to view and edit these files.

Note that masters are only available in postscript format, so they will be best for creating .otf fonts. If you need to make TrueType based builds from the masters, we recommend QuadraticConverter for best quality conversion of the curves before generating .ttf, .woff, or .woff2 files; mind that the results will not match the provided instances precisely.

NB: The prepared instances contain some additional data that cannot be stored in the masters and maintained through interpolation. For best results, compare new interpolations to the existing instance sources and update them accordingly, specifically the information accessible through the Font Info panels.

Other Files: Hinting Source

For TrueType-based formats (.ttf, .woff, .woff2 files), the official releases are manually optimized for screen rendering. These “hinting” sources are stored separately from the .ufo files, which do not contain any TrueType hinting information. When rebuilding TrueType-based formats, we recommend using the “autohint” option to achieve reasonable, though not identical screen rendering.

If you would like to access and edit manual hinting instructions, you will find these in the separate set of source files under other files/truetype hinting source. These special TTF files will be viewable and editable using Microsoft VTT.

Suggesting Edits

If you have suggestions for edits or additions to the official releases, please email [email protected].

intel-one-mono's People

Contributors

alirezaivaz avatar fredshallcrass avatar matthewturrini avatar ninastoessinger avatar rdower avatar sphars avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

intel-one-mono's Issues

css `font-stretch` is not working for Intel One Mono

@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-regular.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-regular.woff") format("woff");
    font-weight: 400;
    font-style: normal;
}


@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-light.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-light.woff") format("woff");
    font-weight: 300;
    font-style: normal;
}

@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-medium.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-medium.woff") format("woff");
    font-weight: 500;
    font-style: normal;
}

@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-bold.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-bold.woff") format("woff");
    font-weight: 700;
    font-style: normal;
}



@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-italic.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-italic.woff") format("woff");
    font-weight: 400;
    font-style: italic;
}


@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-lightitalic.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-lightitalic.woff") format("woff");
    font-weight: 300;
    font-style: italic;
}

@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-mediumitalic.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-mediumitalic.woff") format("woff");
    font-weight: 500;
    font-style: italic;
}

@font-face {
    font-family: "Intel One Mono";
    src: url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff2/intelone-mono-font-family-bolditalic.woff2") format("woff2"),
    url("https://cdn.jsdelivr.net/gh/intel/intel-one-mono@main/fonts/woff/intelone-mono-font-family-bolditalic.woff") format("woff");
    font-weight: 700;
    font-style: italic;
}


html body {
    font-family: "Intel One Mono";
    font-stretch: 50%;
}

https://developer.mozilla.org/ja/docs/Web/CSS/font-stretch

Spacing mark are not dead marks (non-spacing)

Opening #46 (comment) as an issue:

The PR #46 reintroduces the glyph classes @deadMarks and @deadbelowMarks and the lookups DblMarks and CmbMarks using them to substitute spacing marks (modifier letters) by non-spacing marks (combining marks). These were removed in v1.2 but are now reused (except for /grave U+0060).

All spacing marks, no just /grave U+0060, must behave like spacing marks and remain spacing whether they follow a letter or not. Spacing marks characters should be used for spacing marks, non-spacing marks characters should be used for non-spacing marks. There should not be any substitution from spacing to non-spacing.

Dead keys are keyboard keys on mechanical typewriter that do not generate a character by themselves but modifies the character generated by the key struck immediately after.

Unicode 15.0, chapter 7, "Modifier Letters": Modifier letters are letters or symbols that are written adjacent to other letters and which modify their usage in some way. They are not formally combining marks and do no graphically combine with the base letter they modify

For example with "a´a˝aˆaˇa˘a˜a¯a¨aꞈaˍa¸a˛ ":

Current behaviour
Screenshot 2023-08-05 at 06 18 46
Expected behaviour
Screenshot 2023-08-05 at 06 18 23

1.2 regressions for non spacing combining marks

Version 1.2 removed the ccmp feature lookup DblMarks and lookup CmbMarks that caused #3 but also removed the ccmp feature lookup Dotless and the mark feature block.
The ccmp feature lookup Dotless and the mark feature block should not have been removed.

The DblMarks and CmbMarks lookup were wrongly substituting the spacing marks (like ` U+0060 GRAVE ACCENT or ´ U+00B4 ACUTE ACCENT) by non spacing combining marks (like  ̀ U+0300 COMBINING GRAVE ACCENT or  ́ U+0301 COMBINING ACUTE ACCENT).
The spacing marks should not behave like non spacing combining marks, they were behaving incorrectly in version 1.0 and are now behaving correctly in version 1.2.

The Dotless lookup ensured i and j were substituted by their dotless forms when combined with a top non spacing combining mark or with a bottom and a top non spacing combining mark.
The mark feature ensured the non spacing combining marks are positioned on base letters they combine with.
The non spacing combining marks were behaving correctly in version 1.0 and are now behaving incorrectly in version 1.2.

For example, íj́ used in Dutch when the digraph ij has acute marks when indicating stress (i with acute is a single character in Unicode, j with acute is two characters: U+006A LATIN SMALL LETTER J and U+0301 COMBINING ACUTE ACCENT):

Version 1.0
(correct íj́, with dotless j
and positioned combining acute)
Version 1.2 (incorrect j́ in íj́)
Screenshot 2023-05-20 at 20 39 19 Screenshot 2023-05-20 at 20 39 11

The ǰ U+01F0 LATIN SMALL LETTER J WITH CARON is also broken in the process as the ccmp still has a lookup substituting jcaron by j caroncmb.

Version 1.0
(correct ǰ, with dotless j
and positioned combining caron)
Version 1.2
(incorrect ǰ with j
and mispositioned combining caron)
Screenshot 2023-05-20 at 21 03 55 Screenshot 2023-05-20 at 21 04 14

To fix this, restore the Dotless lookup in the ccmp feature and restore the mark feature.
Additionally the Dotless lookup should be extended for the ị LATIN SMALL LETTER I WITH DOT BELOW and į LATIN SMALL LETTER I WITH OGONEK to behave correctly when combining with top marks. The following ccmp feature Dotless lookup, based on https://googlefonts.github.io/gf-guide/diacritics.html#stacked-diacritics, can be used:

# Marks Above
@lcMarks =   [acutecmb     hungarumlautcmb     gravecmb     circumflexcmb     caroncmb     brevecmb     tildecmb     macroncmb     dieresiscmb     dotaccentcmb     ringcmb    ];

# Replace letters with dotless counterparts when followed by a combining mark.
lookup Dotless {
    lookupflag UseMarkFilteringSet @lcMarks;
    sub [i j]' @lcMarks by [dotlessi dotlessj];
    sub idotbelow' @lcMarks by dotlessi dotbelowcmb;
    sub iogonek' @lcMarks by dotlessi ogonekcmb;
} Dotless;

Bold, Light and medium considered a different font by LibreOffice

LibreOffice considers Bold, Medium and Light variants as different fonts, and that means that if you press Ctrl-B to turn normal text into bold, an artificial bold based on the regular one will be used instead of the real bold.

Plasma desktop group all intel-one variants as a single font, though.

stylistic sets for italics

Great work on the font 😄

Could stylistic alternatives be provided for some glyphs, such as f, a and y similar to other monospaced fonts?
e.g. a tail for f, single-storey a, and an italic y
These styles will give more character and distinction to the italic font.

intel one mono:
Screenshot 2023-08-17 at 1 53 35 PM

ibm plex mono:
Screenshot 2023-08-17 at 1 53 46 PM

input mono:
Screenshot 2023-08-17 at 1 53 59 PM

jetbrains mono:
Screenshot 2023-08-17 at 1 54 11 PM

The second question I had was regarding the tilt of the italics. It seems like the tilt axis of the current italic font is approximately 15˚. Could a stylistic set be created where the tilt axis is around 8-10˚ for a less drastic tilt?
The current skew makes it seem like the software in use is trying to render a regular font as italic.

The more I use this font, the more I like the ~15˚ tilt. Stylistic sets for italic characters would be great though.

Compressed kerning with trailing backtick

It would seem that text wrapped in backticks will have compressed kerning when the character is an alphabetic symbol. For example, this is how the following text is rendered:

This is an example of `alphabetic trailing backtick`, while this is a `non-alpha backtick!`.

image

Problem with RTL(Arabic, Persian, ...) strings

I was using other font in my IDE for several years and now I switch to Intel font.

My major problem is with Arabic/Persian strings between my code.
Editing the strings is confusing because the visual cursor position is not conformist with the real position that I want to edit!
11

Unexpected behavior of the backtick ( ` ) character

Here is a list of some characters followed by the backtick ` character:

backtick_demo

Programming languages use the backtick as a standalone character for different purposes and it shouldn't be combined with the preceding character.

For the grave accent placed over some letters in certain languages there are already standalone characters for them.
Example: à, è, ò, ...
These are already defined in the typeface.

Please add powerline font support

vim/tmux have some special fonts coding to display symbol. It will be great to have a font patch to support.
e.g.
\uE0B0
\uE0B1
\uE0B2
\uE0B3
w support
image

w/o support
image

Thanks!

Please add Thin, ExtraLight variations.

Due to optic/vision issues (Light sensitivity), I experience an exponentially better viewing/writing experience when I use a typeface that is extremely thin (IBM Plex Mono Thin for example) however the choices available are very limited.

Please consider adding Thin and/or ExtraLight variations.

About Idea

Why I can't choose it on jetbrains idea? I can see it in control panel.
image
image

Missing box drawing characters

It would be nice to have common box drawing characters.
From the well known UTF-8 test file:

Box drawing alignment tests:                                          █
                                                                      ▉
  ╔══╦══╗  ┌──┬──┐  ╭──┬──╮  ╭──┬──╮  ┏━━┳━━┓  ┎┒┏┑   ╷  ╻ ┏┯┓ ┌┰┐    ▊ ╱╲╱╲╳╳╳
  ║┌─╨─┐║  │╔═╧═╗│  │╒═╪═╕│  │╓─╁─╖│  ┃┌─╂─┐┃  ┗╃╄┙  ╶┼╴╺╋╸┠┼┨ ┝╋┥    ▋ ╲╱╲╱╳╳╳
  ║│╲ ╱│║  │║   ║│  ││ │ ││  │║ ┃ ║│  ┃│ ╿ │┃  ┍╅╆┓   ╵  ╹ ┗┷┛ └┸┘    ▌ ╱╲╱╲╳╳╳
  ╠╡ ╳ ╞╣  ├╢   ╟┤  ├┼─┼─┼┤  ├╫─╂─╫┤  ┣┿╾┼╼┿┫  ┕┛┖┚     ┌┄┄┐ ╎ ┏┅┅┓ ┋ ▍ ╲╱╲╱╳╳╳
  ║│╱ ╲│║  │║   ║│  ││ │ ││  │║ ┃ ║│  ┃│ ╽ │┃  ░░▒▒▓▓██ ┊  ┆ ╎ ╏  ┇ ┋ ▎
  ║└─╥─┘║  │╚═╤═╝│  │╘═╪═╛│  │╙─╀─╜│  ┃└─╂─┘┃  ░░▒▒▓▓██ ┊  ┆ ╎ ╏  ┇ ┋ ▏
  ╚══╩══╝  └──┴──┘  ╰──┴──╯  ╰──┴──╯  ┗━━┻━━┛           └╌╌┘ ╎ ┗╍╍┛ ┋  ▁▂▃▄▅▆▇█

Note that web browsers does not display them correctly in GitHub due to a 1.45 line height. With a 1.0 line height, they are correctly aligned.

Plans for Greek support

Hello,

Congratulations on creating a fantastic looking font! My eyes thank you first of all :)
Do you have plans to support Greek?
If yes I would be happy to help.

Small alignment issue for dash (U+002D)

As visible in this screenshot, the dash character is not vertically aligned with plus and equal characters. Programming fonts often try to maintain these characters vertically aligned because they are used for ASCII art, e.g. to represent boxes.

intelone

Lowercase R seems misfit

Although the letter i also has a small horizontal underline, the letter r has a completely different shape compared to other letters, and the horizontal lines drawn at the bottom and at the mouth of the letter aren't interesting.

@ stroke is too thin

The stroke width of @ symbol is visibly thinner than in other characters. It shouldn't be.
at

Looking forward to more text

I'm pretty sure that this is the best font that I'm using right now and I've been using consolar in the last episode but I would like to use this font with other fonts that look better like Chinese, Japanese, Russian

Additional widths

Opening issue to contain requests for additional widths:

And a variable width build.
#39 css font-stretch is not working for Intel One Mono

Nitpick: The README's example image set of characters

A friend and I were discussing this font, and it became confusing in our discussion because there are smart quotes in the example image, and these things are the bane of a developer's existence in one form or another. You'd never type them in an IDE except when generating them for copy, but the image is missing simple quote characters, and backticks. Just a little strange since this font is intended for developers.

But: I could be wrong about smart quotes and how developers use them. So the ideal scenario to me is there are just a few more characters so the difference between them is clear since they are commonly mistaken characters. I've refrained from including an updated screenshot as you may have specific requirements for branding and so on.

Ligature for backtick after g?

This line:

Clear with `exiftool -P -label= *.jpg`

Is rendered in VSCode as:

image

It looks like the back-tick is accidentally being ligatured with the g.

Support of DIN 91379 (Unicode subset for Europe)

Support of DIN 91379 (Unicode subset for Europe)

Please support all letters and sequences of DIN 91379 "Characters and defined character sequences in Unicode for the electronic processing of names and data exchange in Europe"

Current rendering

Some letters and diacritics are missing or positioned incorrectly.
(Rendering using
hb-view (HarfBuzz) 2.8.1
Ubuntu 22.04.2 LTS)
latin_letters_all_intelone-mono-font-family-regular.pdf
latin_list_all_intelone-mono-font-family-regular.pdf

Rendering with Arimo

latin_letters_all_Arimo-Regular.pdf
latin_list_all_Arimo-Regular.pdf

See also

@ is very thin on thicker weights

I first noticed this on the preview image, where each of the characters looks a different weight except ! and $. After installing the font, # looks fine, but @ stays thin for thicker weights which looks out of place to me. It is a more complex character to do thick and small, but I've seen some very good takes on that from other fonts, often by losing the hole in the center a.
image
image

{} too odd

Like the font, but the curly brackets confuse me or something

Please add glyphs (icons) support - Nerd Fonts Patch

Currently, the font is missing some icons. I wanted to use this font in my terminal, but the lacks of icons make the terminal ugly!

I don't actually know how to patch a Font, like Nerd Font, but something like that would be super cool!!

Additional weights

Opening issue to contain requests for additional weights:

#7 Please add Thin, ExtraLight variations
#16 Add ExtraBold variant

Incorrect font family name in Readme.md

OS: Windows 11 Pro
Font Version: 1.200 ttf

I found a bug in the Readme.md file of the project. The bug is that the font name is specified as "Intel One Mono" when explaining how to set the VSCode font family, but the actual correct spelling should be "IntelOne Mono".

I really like this font and appreciate the work done by the project team. I hope this issue can be resolved soon. Thank you.

Spacing in Eclipse editor

When using Intel One Mono in Eclipse SQL editor the bold size or spacing is bigger then the regular one:

Anotação 2023-07-14 153313

When using Consolas it is the same:

Anotação 2023-07-14 153628

Is it the expected behavior?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.