Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Request] Variant without symbols

Abierto
  • ¿Algo no está bien?
#226 1 comentario 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Área
build-system, design, release

Línea de trabajo

Empieza leyendo los issues relacionados enlazados y el PR #213 para entender qué glifos de símbolos se han añadido y por qué los usuarios informan de problemas de fallback. La solicitud es una variante oficial de Source Code Pro que excluya los glifos de tipo símbolo/emoji y mantenga la fuente existente sin cambios. La tarea estaría completa cuando exista un alcance aprobado por un maintainer que defina qué glifos se trasladan fuera, junto con una ruta de release/build para esa variante.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

question

Some symbols don't really belong in fonts, especially when the support for them is cherry-picked from a larger set by request/preference. Most notably glyphs that have emoji coverage, as these will prevent the use of fallbacks to a system or user assigned/preferred font for covering those glyphs(monochromatic or colour).

As the font does not provide a replacement of such a large set(understandable), it makes little sense to keep them in the font as they will take priority and not be replaced, which can lead to inconsistent style/mix of fonts. Non-issue, if you're specifically using each of those glyphs/emoji for a given purpose in an editor, but if any unsupported ones are encountered, then there's not much that can be done to get consistency.

Here's an example of cases in VSCode, and this other issue specifically discusses a "Heavy Checkmark" glyph/emoji, that turns out to be one of the few included in Sarasa Gothic as the cause, preventing the user from having consistent presentation style for the checkmark and cross(neither of which are included in SCP afaik, although there is the regular checkmark, and the heavy and cross were requested in a related issue).

Related issues touch on a few cases of users being confused and thinking SCP was at fault, which most of the time, it wasn't(one time it was when it added a Coffee glyph). I've had it render the 263A smilely face as a fallback for sans-serif despite being a monospace font, and when a colour emoji font should have been used as fallback instead. I've addressed that since on the system side(other fonts have this same issue), but it'd be nice if there were a variant of the font that excluded them.

One of the related issues requests Music glyphs, another APL, and so forth. If the additions aren't really specific to the SCP style, it's mostly adding them and ensuring they have a fixed width to maintain a monospace font, along with ensuring those glyphs are used for when a user has less control over what font is used for fallback(Windows?).

Like Google has done with Noto fonts(and like what was suggested in the Music symbols request), splitting such glyphs out to their own fonts makes them composable elsewhere. I'm not sure if Google rebranded SCP under a Noto font name, but Source Han Code JP and later Source Han Mono have taken SCP and adjusted it(along with removing some glyphs?). If users were to want glyphs in those fonts that SCP gets, that's additional work to accomodate for, or if the user wanted to swap SCP for a different programming font family entirely, but keep the glyph style/coverage, that's not as easily doable.

Just to be clear, I'm not requesting the font drop the current symbol support(since I'm sure that'd probably upset existing users who enjoy them, or aren't able to assign fallbacks). But an official variant without them would be appreciated.

Related(Mix of request to support glyphs and issues/confusion they cause, all from this repo):
https://github.com/adobe-fonts/source-code-pro/issues/114
https://github.com/adobe-fonts/source-code-pro/issues/49
https://github.com/adobe-fonts/source-code-pro/issues/208
https://github.com/adobe-fonts/source-code-pro/issues/143
https://github.com/adobe-fonts/source-code-pro/issues/101
https://github.com/adobe-fonts/source-code-pro/issues/172
https://github.com/adobe-fonts/source-code-pro/issues/16
Powerline issue with April 2019 update about future support perhaps leaving PUA

PR for 79 math symbols(not as big of a concern personally since the main issues encountered are usually with emoji, that said on Linux math symbols are treated as their own font family in fontconfig, and defined as a language Zmth/und-zmth in Unicode via ISO 15924).

Lenguaje dominante
CSS
Estrellas
20.5k
Forks
1.6k
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de adobe-fonts/source-code-pro

Todos los issues de adobe-fonts/source-code-pro

Issues similares

Más issues de Build System

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.