Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Cyrillic Pro to language-based #224

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

simoncozens
Copy link
Collaborator

No description provided.

@yanone
Copy link
Collaborator

yanone commented Sep 21, 2024

I’m not tagged as a reviewer, but I have a comment anyway:

I would like to ask to preserve in the glyphset description the languages that aren’t currently defined in gflanguages and thus can’t be included at this point so that they can be restored later when they are defined, or can be inferred from a different data source such as hyperglot (which we could consider as a secondary data source anyway btw).

Once you're at it, please replace the entire description text with something meaningful. The headline typefaces note is nonsense, and so is the Slavic languages note. Many of these languages have no relation to Slavic.

@moyogo
Copy link
Contributor

moyogo commented Sep 21, 2024

There is data in gflanguages for other Non-Slavic languages. Should they be added to GF_Cyrillic_Pro?

@yanone
Copy link
Collaborator

yanone commented Sep 21, 2024

Are you asking to add all remaining defined Cyrillic languages to Cyrillic Pro or still just a subset?

@moyogo
Copy link
Contributor

moyogo commented Sep 21, 2024

Are you asking to add all remaining defined Cyrillic languages to Cyrillic Pro or still just a subset?

@yanone I don’t know what the rationale is for this GF glyphset besides "other Non-Slavic". If the set is defined as the current list of languages then my question is: should there be a GF_Cyrillic_Beyond with all remaining defined Cyrillic languages.

@yanone
Copy link
Collaborator

yanone commented Sep 21, 2024

I don’t know what the rationale is for this GF glyphset besides "other Non-Slavic"

We should ask this question in the chat, because I think around here nobody knows the answer.
Personally I will postpone that as I'm still on vacation. I had merged a few simple PRs earlier today and skimmed over this one.

We also don't need to keep this glyphset around at all if nobody knows why it exists, and resurrect a new one with a clear definition once we have a use case, as the assembly is so swift nowadays.

@vv-monsalve
Copy link
Contributor

vv-monsalve commented Sep 26, 2024

Hi @simoncozens

I've completed the cross-reference between the modifications made for the 'Cyrillic Pro' subset, the current 'Cyrillic Plus' list, and the language support in Playpen Sans.

The plan is to update the GF Cyrillic Plus definition using the list of languages currently supported by Playpen Sans, based on TT's revision to the current Plus glyphset. The font indeed supports many of the languages currently listed in Cyrillic Plus, while only a few languages listed in this PR for Cyrillic Pro are "nearly supported" and the others are not supported at all.

We can still use this PR to redefine the Pro, but we must also redefine the Plus. However, it would be key to establish criteria that could help define glyph sets. We could consider using a language population filter to better distinguish 'Plus' from 'Pro', instead of solely relying on the "Slavic" versus non-Slavic categorization.

What was your criteria for the current list of languages ​​included in this “Pro” redefinition?

Below is the lists of supported languages by Playpen Sans.

Playpen Sans - Cyrillic languages support

GF_Cyrillic_Core

be_Cyrl (Belarusian)
bs_Cyrl (Bosnian (Cyrillic))
bg_Cyrl (Bulgarian)
ru_Cyrl (Russian)
sr_Cyrl (Serbian)
uk_Cyrl (Ukrainian)

Languages that could inform the GF_Cyrillic_Plus redefinition

abq_Cyrl (Abaza)
ady_Cyrl (Adyghe)
av_Cyrl (Avaric)
bua_Cyrl (Buriat)
ce_Cyrl (Chechen)
cjs_Cyrl (Shor)
crh_Cyrl (Crimean Turkish, Cyrillic)
dar_Cyrl (Dargwa)
dng_Cyrl (Dungan)
gag_Cyrl (Gagauz (Cyrillic))
inh_Cyrl (Ingush)
kbd_Cyrl (Kabardian)
kaa_Cyrl (Kara-Kalpak)
kk_Cyrl (Kazakh)
koi_Cyrl (Komi-Permyak)
krc_Cyrl (Karachay-Balkar)
kum_Cyrl (Kumyk)
kv_Cyrl (Komi)
ky_Cyrl (Kyrgyz)
lez_Cyrl (Lezghian)
mdf_Cyrl (Moksha)
mn_Cyrl (Mongolian)
mrj_Cyrl (Western Mari)
nog_Cyrl (Nogai)
ro_Cyrl (Romanian (Cyrillic))
rue_Cyrl (Rusyn)
tab_Cyrl (Tabassaran)
tg_Cyrl (Tajik)
tk_Cyrl (Turkmen (Cyrillic))
tkr_Cyrl (Tsakhur)
ttt_Cyrl (Muslim Tat)
udm_Cyrl (Udmurt)
ug_Cyrl (Uyghur (Cyrillic))
uz_Cyrl (Uzbek (Cyrillic))
xal_Cyrl (Kalmyk)

Nearly supported languages

Simon’s Cyrillic Pro proposal

evn_Cyrl (Evenki)
kpy_Cyrl (Koryak)
mns_Cyrl (Mansi)
yrk_Cyrl (Nenets)
sah_Cyrl (Sakha)

Other nearly supported languages

aii_Cyrl (Assyrian Neo-Aramaic, Cyrillic)
alt_Cyrl (Southern Altai)
az_Cyrl (Azerbaijani (Cyrillic))
chm_Cyrl (Mari)
cv_Cyrl (Chuvash)
gld_Cyrl (Nanai)
kjh_Cyrl (Khakas)
os_Cyrl (Ossetic)
tly_Cyrl (Talysh (Cyrillic))

@vv-monsalve
Copy link
Contributor

I've opened a PR to redefine GF_Cyrillic_Plus based on a combination of languages and + number of speakers, regardless of whether they are Slavic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants