github-linguist / linguist

Language Savant. If your repository's language is being reported incorrectly, send us a pull request!
MIT License
12.35k stars 4.27k forks source link

List of languages without a colour #5003

Closed wopian closed 3 years ago

wopian commented 4 years ago

Continuing from #4506. 49% (280) languages currently do not have a language assigned and show as grey (a lot of these are grouped languages that GitHub shows ungrouped in search results).

List generated with https://gist.github.com/wopian/8639e5d24119cbd99548b73c18321686

Early Sidenotes

Key

πŸ™… = No logo, no brand or lack of info for language ❓ = No suitable colour, but is grouped into a language that has a colour

Languages

Numbers

A

B

C

D

E

F

G

H

I

J

K

L

M

N

O

P

Q

R

S

T

U

V

W

X

Y

Z

wopian commented 4 years ago

Added C to D

smola commented 4 years ago

Gentoo Ebuild/Eclass could be#9400FF (source: gentoo.org. AFAIK that's the primary color, while there's a secondary green.

wopian commented 4 years ago

Added E, F and Gentoo Ebuild/Eclass

Haroenv commented 4 years ago
wopian commented 4 years ago

Added G, H, I and J. Incorporating suggestions from @Haroenv

Alhadis commented 4 years ago

GN ? maybe ninja logo?

What logo? Neither Ninja nor GN have logos of their own. I made this one several years back for the file-icons project, but it doesn't have a colour. Though I'd say deep, dark blue would be the appropriate colour for evoking midnight-draped shinobi. πŸ˜‰

a lot of these are grouped languages that GitHub shows ungrouped in search results

IMHO, grouped languages should inherit the colour of their parent language. They're represented on GitHub as their parent, so it makes sense they should inherit their parent's colour.

Glyph Bitmap Distribution Format #000 (source: no colours in spec)

Adobe invented that format, so we can just use #fa0f00 (taken from Adobe's logo)

Git Attributes #F44D27 (grouped in INI, source: logo) Git Config #F44D27 (grouped in INI, source: logo)

πŸ€” INI? Wait, that doesn't sound right... they might be config formats, but calling them INI is a stretch…

wopian commented 4 years ago

Glyph Bitmap Distribution Format #000 (source: no colours in spec)

Adobe invented that format, so we can just use #fa0f00 (taken from Adobe's logo)

I used the PostScript colour on Linguist as Adobe Postscript's logo was on both (that and Adobe Font Metrics) specification PDFs in greyscale.

I presumed they were the same shade of red but I guess it turns out Adobe's logo is brighter than Adobe PostScript's Linguist colour - likely a result of the axed colour similarity check πŸ‘€

Git Attributes #F44D27 (grouped in INI, source: logo) Git Config #F44D27 (grouped in INI, source: logo)

πŸ€” INI? Wait, that doesn't sound right... they might be config formats, but calling them INI is a stretch…

The grouped data is extracted from languages.yml, but yeah I too was surprised they were grouped under INI when I got to them.

Alhadis commented 4 years ago

I presumed they were the same shade of red but I guess it turns out Adobe's logo is brighter than Adobe PostScript's Linguist colour

Yup. Back in the day, Adobe's branding used a darker shade of red that matched PostScript's. They brightened that at some point in the last 30 years, but since PostScript's no longer an actively supported product, it still uses the old branding colour.

In any case, PostScript and GBDF have very, very little in common, so it's probably better to use a different colour anyway. 😁

but yeah I too was surprised they were grouped under INI when I got to them.

This might warrant a closer look. Some entries, like EditorConfig and NPM configs, are grouped under INI and only exist for dedicated highlighting purposes. But we can't go slapping the INI label anything that happens to be an unindented config file...

wopian commented 4 years ago

Added K and L and changed the Adobe languages to use Adobe's branding instead of Adobe PostScript.

@Alhadis: This might warrant a closer look. Some entries, like EditorConfig and NPM configs, are grouped under INI and only exist for dedicated highlighting purposes. But we can't go slapping the INI label anything that happens to be an unindented config file...

Should I open another issue to get discussion going for this? Since the group associations are in the Linguist YML file and out of scope for this issue.

@wopian: a lot of these are grouped languages that GitHub shows ungrouped in search results

@Alhadis: IMHO, grouped languages should inherit the colour of their parent language. They're represented on GitHub as their parent, so it makes sense they should inherit their parent's colour.

I'm somewhat conflicted on this but besides the embedded languages I'm more skewed to only using the parent if there's no suitable colour/branding for the sub-language. Django, Embedded Crystal/Elixir/Ruby, PHP and Razor are my only concerns where I currently agree with you to stick with the parent (i.e. HTML) language.

Nixinova commented 3 years ago

This will need to be updated once #5476 is merged

Nixinova commented 3 years ago

Okay I've now looked through every item in the list and attached a relevant colour #5476, this should be done.

Nixinova commented 3 years ago
Current list of languages without colours - ABNF - ASL - ASN.1 - Befunge - C-ObjDump - C2hs Haskell - CIL - COBOL - CODEOWNERS - CartoCSS - Charity - CoNLL-U - Cool - Cpp-ObjDump - Creole - Cue Sheet - Cycript - Cython - D-ObjDump - DIGITAL Command Language - DNS Zone - DTrace - Diff - E-mail - EBNF - Eagle - Edje Data Collection - Filterscript - Formatted - GDB - GN - Gettext Catalog - Glyph Bitmap Distribution Format - Graph Modeling Language - HCL - HyPhy - IRC log - Inform 7 - Kit - Kusto - LTspice Symbol - Lean - Limbo - Linker Script - Linux Kernel Module - Logos - LoomScript - M - M4 - M4Sugar - MUF - Maven POM - Microsoft Developer Studio Project - Microsoft Visual Studio Solution - MiniD - Module Management System - Monkey - Moocode - Muse - Myghty - NASL - NEON - NL - NSIS - Ninja - ObjDump - Object Data Instance Notation - Opa - OpenRC runscript - OpenStep Property List - OpenType Feature File - Ox - Parrot Assembly - Parrot Internal Representation - Pic - Pickle - PlantUML - Pod - Pod 6 - Pony - Proguard - Protocol Buffer - Public Key - Pure Data - QMake - REALbasic - RPC - RPM Spec - Raw token data - Readline Config - Redcode - Redirect Rules - RenderScript - Rich Text Format - SELinux Policy - SMT - SSH Config - STON - SWIG - Sage - ShellSession - Sieve - Smali - Soong - Spline Font Database - Tcsh - Tea - Texinfo - Text - Turtle - Type Language - Unix Assembly - Wavefront Material - Wavefront Object - WebIDL - WebVTT - Wget Config - X BitMap - X Font Directory Index - X PixMap - XCompose - XPages - XProc - XS - YANG - Zeek - cURL Config - desktop - dircolors - edn - robots.txt -
wopian commented 3 years ago

Thank you for finishing this issue up for me @Nixinova πŸŽ‰

mxmilkiib commented 2 years ago

Turtle is still lacking a colour. Example projects; https://github.com/moddevices/mod-lv2-data https://github.com/davemollen/dm-Octaver