• At age 40, only half the light gets through to the retina as it did at age 20. For 60-year-olds, it’s just 20%. People in their 60s need three times more light for comfortable reading than those in their 20s(Reference)
• ​Nearly 9% of Americans are visually impaired, meaning their vision cannot be completely corrected with lenses.
• Most people, when sitting comfortably, are about 20 to 23 inches from their computer screens. In fact, 28 inches is the recommended distance, because this is where vergence is sufficiently low to avoid eye strain. This is much further than the distance at which we read printed text — most people do not hold magazines at arm’s length!(source)
• 16-pixel text on a screen is about the same size as text printed in a book or magazine; this is accounting for reading distance. Because we read books pretty close — often only a few inches away — they are typically set at about 10 points. If you were to read them at arm’s length, you’d want at least 12 points, which is about the same size as 16 pixels on most screens:(source)
• People don't zoom. The people who most need to increase font size are people 65+, which is the group least-likely to be skilled enough to have adjusted settings.(source)

• ​https://type-scale.com/ A tool to try and choose a scale rhythm(ratio of typeface sizes used for headings, body content
• Tim Brown’s modular typeface scales concept​

  • ​Modular Scale​
  • A set of js, css, sass libraries to implement this - https://github.com/modularscale​
  • Typesetting body text - Talk by Tim brown https://vimeo.com/156203722​
• using musical scales for better scale harmony - Owen Gregory Composing the New Canon: Music, Harmony, Proportion

• ar - Arabic
• bn- Bengali
• ml- Malayalam - This script has vertical stacking and the line height-font size ratio should be chosen to avoid parts of it not chopped off.
• fa- Persian
• gu- Gujarati
• hi - Hindi
• mr - Marathi
• as - Assamese
• kh - Khmer
• kn- Kannada
• my-Myanmar
• ne - Nepali
• pa-Panjabi
• si -Sinhala
• ta-Tamil
• te-Telugu
• th-Thai
• ur-Urdu
• ko-Korean - The height is mostly same as Latin but the density of glyphs are higher. Slightly higher linespacing expected
• vi -Vietnamese - Even though the script used is latin, it has many diacritic marks that are specific to vietnamese.
• bo-Tibetan - This script has multi level vertical stacking and no word spacing. bo.wikipedia.org increased the default font size to 125%(20px) using custom styling​

• bn- Bengali - Glyphs are very dense with strokes joining in accute angles. Need minimum 12pt/16px font size. Script example​
• ml- Malayalam
• gu- Gujarati
• hi - Hindi
• mr - Marathi
• as - Assamese
• kh - Khmer
• kn- Kannada
• my - Myanmar
• ne - Nepali
• pa - Panjabi
• si - Sinhala
• ta - Tamil
• te - Telugu
• th - Thai
• lo - Lao
• ur - Urdu
• vi - Vietnamese
• bo - Tibetan
• zh - Chinese - High script density and require larger fontsize. The Chinese wikipedia sets larger font size using custom styling.
• ja - Japanese- High script density and require larger fontsize. The Japanse wikipedia sets larger font size using custom styling.

The fixed restrictions of the UI metrics was the primary, non-negotiable term in the Nirmala UI design brief: whatever we did had to fit within the vertical metrics of the Segoe UI and other UI fonts. The core target size for UI use, despite the increase in screen resolutions on many Win8 devices, is still 9pt at 96ppi, i.e. 12 ppem, with some Office UI items displaying at 8pt (with further restrictions on ppi height through VDMX adjustments at some sizes). At 12 ppem, we have exactly 3 pixels below the baseline before we hit the OS/2 WinDescent limit, beyond which glyphs will be clipped. Many of the Indian writing systems make significant use of the space below the baseline, so we had to employ a number of strategies to squeeze subjoined letters and other descending shapes into the UI metrics. The results are not all pleasant, and some contravene the norms of these writing systems, achieving only a legible decipherability, rather than true readability.

• Noto being the default sans serif font in android phones(shipped by google), there is no need to mention in the font stack for them.
• Noto is not installed by default in any desktop operating systems. Each comes with their native fonts as default sans-serif, serif fonts. So adding Noto in font stack does not serve there too
• The smart phone market in south asian countries are owned by Xiami and others who ship their own theming and allows users to customize default UI fonts.
• Noto is designed as a graceful final fallback solution for all scripts. Using that as the "Choice" is a lazy solution. Not mentioning it in font stack also gives the same solution.

• ​Selecting Typefaces For Body Text​
• ​Five Principles For Choosing And Using Typefaces​
• ​Best Practices For Combining Typefaces​
• ​This page provides a (not exhaustive) list of fonts, grouped by script, that are available via the Windows 10 and Mac OS X operating systems, as well as Google's Noto fonts and SIL fonts.

• It is better to not justify if hyphenation support is not available. For other browsers or old versions https://github.com/mnater/Hyphenopoly can be used. This library uses hyphenation patterns I authored for Indic languages
• The hyphenation character defaults to Soft Hyphen(0x00AD) but that is not always optimal. Several scripts prefere non-visible hyphenation character at the place of word break. This can be controlled by hyphenate-character CSS property. But not widely implemented. -webkit-hyphenate-character: ''; works for webkit browsers
• Refer https://www.w3.org/TR/typography/#hyphenation ( which I contributed with content and examples)

• https://www.w3.org/TR/typography/#lists​

• font-smoothing - badly speced and unxpected results depending background and foreground color. Pick a good font instead.
• font-stretch - Don't override the designer of the font. The results won't be pretty, especially for complex scripts
• font-size-adjust - Don't override the designer of the font. The results won't be pretty, especially for complex scripts
• :dir() The :dir() CSS pseudo-class matches elements based on the directionality of the text contained in them. Be aware that the behavior of the :dir() pseudo-class is not equivalent to the [dir=…] attribute selectors. The latter match the HTML dir attribute, and ignore elements that lack it — even if they inherit a direction from their parent. (Similarly, [dir=rtl] and [dir=ltr] won't match the auto value.) In contrast, :dir() will match the value calculated by the user agent, even if inherited. it doesn’t have great support, is considered experimental​
• direction The direction CSS property sets the direction of text, table columns, and horizontal overflow. Use rtl for languages written from right to left (like Hebrew or Arabic), and ltr for those written from left to right (like English and most other languages). Note that text direction is usually defined within a document (e.g., with HTML's dir attribute) rather than through direct use of the direction property.
• letter-spacing Don't change this to support complex scripts. Just use defaults
• font-kerning By default kerning is enabled by browsers. Don't play with it.

• ​Syncope Syncope is a WYSIWYG tool for establishing vertical rhythm on websites.
• ​Archetype Create beautiful web typography designs, in the browser.
• ​Grid Lover Establish a typographic system with modular scale & vertical rhythm.
• ​Gutenberg A meaningful web typography starter kit.

• ​https://thereader.mitpress.mit.edu/habits-of-expert-software-designers/​
• ​https://distill.pub/2021/multimodal-neurons/​
• ​

• Can you typeset a book with CSS? https://www.w3.org/Talks/2013/0604-CSS-Tokyo/​