https://vimeo.com/435930677

"How to Kill a Writing System with Zachary Scheuren"

Monday, July 6, 2020

Letterform Archive

Writing systems live and breathe with the people who use them, but sometimes they can become difficult or impossible to use. In many cases a writing system has been deliberately pushed out of use or even out of existence. What does it take to kill a writing system? What does it take to bring one back to life? In the current digital world if a writing system is implemented in computing systems it can be immediately seen and used by billions of people around the world. However, if there is no support users must resort to other means. But why should they compromise?

www.letterformarchive.org/events/how-to-kill-a-writing-system

https://notofonts.github.io/noto-docs/technical/Noto-Weight-Width-Style-Specification/ has 2 images that are not rendering

I came across @twardoch's https://github.com/twardoch/noto-docs so filing this issue to track inspecting it more deeply and seeing if there's anything worth adding.

(I just saw https://github.com/notofonts/noto-docs/blob/main/docs/technical/Noto-Font-Submission-Requirements.md but my English is poor, need help😔)

Kana

https://github.com/MY1L/Ctrl/releases/tag/Kana
See also https://twitter.com/MY1Ltype/status/1626969047932801026 , 2023-2-18
support ALL the Kana Extended-B“𚿰𚿱𚿲𚿳𚿵𚿶𚿷𚿸𚿹𚿺𚿻𚿽𚿾”, some Kana Supplement, Kana Extended-A, Small Kana Extension, matching Noto Sans Japanese with a selection of glyphs.

Nüshu

https://github.com/nushu-script/Nyushu/releases
See also https://twitter.com/MY1Ltype/status/1633365482483990537 , 2023-3-8
base on actual Nüshu calligraphy, like《女书规范字书法字帖》(2017-5 ISBN: 9787302467052 by 胡欣(Hu Xin) ) and other actual samples, into a digital version.

I created this, and I can change the license to OFL.

https://github.com/notofonts/noto-docs/blob/main/docs/website/contribute.md#how-toopen-anissue

open an issue in the noto-fonts repository.

This repository has been archived by the owner. It is now read-only↑

btw, I also care about it notofonts/noto-fonts#2051 but… read-only.

I want to custom noto fonts and maintain only what I need.
So the problem is How can I generate noto emoji font via py scripts?

Ideally, all Noto fonts (the latest and the greatest) should be available via Linux distro's package management system, but we're not there yet.

In the meantime, an FAQ entry can be added to explain how to install Noto fonts, either as a non-super-user or as a superuser.

References:
https://www.freedesktop.org/software/fontconfig/fontconfig-user.html
https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

We offer otf, ttf, variable-ttf and slim-variable-ttf; we should explain what they are and why/when to not/use each

For Noto to work as a pan-Unicode font, systems must implement a specific fallback ordering. (Look for glyphs first in Noto-Foo, if not found try Noto-Bar, if not found try Noto-Baz, etc.) A partial version of this list must already exist somewhere in source.android.com, but we should document this ordering part of the Noto repository and make sure it’s kept current. Then, other clients than Android will have an easier way to package Noto into their systems.

One way to document the fallback ordering could be to publish it in CFR format, which afaik is a very simple and already ISO-standardized XML format that would allow for expressing this ordering.

This word is used in a few places, and someone mentioned to me that the word "free" is becoming trickier to use in the EU later this year, when its connected to products or services that involve any kind of data tracking.

While I personally think OFL fonts themselves should be fine to call "free" as they can be used outside of any data tracking, since we have GA on the noto site, I think its better to avoid this.

I think its OK to just remove it rather than replace it.

Hi, the repository description says "Unofficial Noto documentation" as does the website

So I presume "This repository contains official documentation about the Noto fonts project." in the README should use 'unofficial' instead.

Thanks

Similar to #4 @simoncozens has developed new FontBakery check for OT Shaping for an private nastaliq project:

• Checks expected vs actual shaping
• Checks for “forbidden” glyphs (e.g visible viramas, dotted circles, .notdef)
• Checks for glyph collisions
• Produces HTML report with SVG paths
• Integrates into CI
• Allows for test-driven layout development!

We should develop input data for this, for all Noto projects:

• expected shaping
• “forbidden” glyphs
• common glyph collisions

https://www.youtube.com/watch?v=7XUkhXCNl0s

EVENT: Internationalization & Unicode Conference 44 (IUC 44)
DATE: October 14-16, 2020

DESCRIPTION:
The Noto project attempts to develop a unified set of typefaces for everything defined in Unicode, which is all open-source. Noto fonts are used daily by billions of people because they ship on every Android and ChromeOS device, and many designs have versions that are adjusted to work within the vertical space constraints of labels and buttons. Now, with coverage up to and including Unicode 12+ (for some scripts), the set is intended to be visually harmonized. This presentation provides insights into the never-ending strife to cover new and emerging scripts while at the same time improving the fonts from a quality point of view. We will also describe the Noto font creation process, from the design brief with letter-form characteristics to how the fonts are built and tested.

BIO:
Marek Z Jeziorek
Marek Z Jeziorek, a native of Poland, worked for Google LLC as a Technical Program Manager managing the Noto Fonts program from 2015 until 20 January 2023. Marek had been passionate about ensuring that the Noto Font family covers all the world’s scripts. In his spare time, which he doesn’t usually have, Marek films various events that interest him and works on a full-length documentary on Confucius and the Confucian philosophy (while at the same time trying to figure out how to make his family history compelling short films :-)).

OWNER: The Unicode Consortium

Is there a single mega-merged Noto Sans file available publicly, that users can substitute for eg Arial Unicode MS?

Use case: Rendering user generated text into PDFs after eSignature. This is possible with mixed language strings, but the PDF AcroForm Text field format only allows a single font to be set per text field (see eg stackoverflow.com/questions/47995062/pdfbox-api-how-to-change-font-to-handle-cyrillic-values-in-an-acroform-field), and has no support for a fallback stack.

I guess it would be helpful to have access to both OT1.9.x/BE versions, with 65k/all characters :)

Duployan shorthand (Sloan-Duployan shorthand, Duployan stenography) is an American alphabet, written left-to-right.

“Sloan-Duployan shorthand” is not a synonym for Duployan. It is one specific mode of Duployan among many. It does not make sense to list this mode and ignore the others. There are too many to list in this introductory sentence.

Duployan is not an American alphabet. It was invented in France.

later expanded and adapted for writing English, German, Spanish, Romanian, and Chinook Jargon

This is true, but it was adapted for plenty of other languages too. Why restrict the list to these five? Unicode’s current Duployan coverage was meant to cover French, English, Romanian, Chinook Jargon, and various Salishan languages. German, Spanish, and the rest were not in scope.

@simoncozens has set up a CI-driven, automated PDF proof generation process for a nastaliq project:

• Uses shaper and language-specific wordlist to determine set of words which can be correctly shaped.
• Allows both font designer and Google design side to evaluate progress of fonts under development
• Currently deployed on a private Github repo

As part of the long term plan to run all of Noto from this github org (https://github.com/notofonts), I'd love to see a generic proof generator project made out of the nastaliq one, which will require us to gather together language-specific wordlists for all languages that Noto supports, and then deployed to all font repos in the notofonts org repos.

There is a distinction between "proofs" and "specimens", the former being used by font designers to evaluate extremely specific things during font development, and the latter being used by prospective users to evaluate if/when they want to use the font family - but there is some overlap in these things, as a specimen with extreme depth will contain a lot of late-stage proofs.

What makes Simon's approach here important is that it fills a gap for complex scripts between something like https://www.adhesiontext.com and a specimen generator like https://variable.typespecimens.xyz

It also uses UX mocks to show the fonts in context of use, and since Noto is used for UIs, especially Material Design on Android, we will also need to gather together mocks for all languages.

https://github.com/notofonts/noto-docs/blob/main/src/miniarticles/NotoMusic.md