12 Months, 850 Languages, 63 Fonts, No Waiting Or: Thank God for Google Noto
curiousnotions.com
curiousnotions.com
Disabling the font makes it a nicer reading experience.
There is something similarly strange about the writing style of the article. I feel like I'm supposed to sit down, breathe out, make a cup of tea, and delve into this "intriguing, hand-crafted story."
In reality, I'd guess most people will attempt to read this story on their phone while on the toilet.
Love the effort in writing the book though. Not sure why exactly the author focused on months in particular while there are so many things they could have added (such as name of the days, counting systems, and everything else necessary that would make it possible for someone to implement a clock by using full words from that language).
If translating content to 1000+ languages interests you, the JWs have released, at times, some articles explaining how they achieve simultaneous publishing in 1034 languages using a piece of software from Oxford called MEPS [ https://www.jw.org/en/choose-language ].
This is honestly amazing, never did I think that the most translated website would be for something like JWs.
And then I realized that the article was published in 1984 (!) so it appears that MEPS / IPS dates back to that time and is almost 40 years old now.
Is MEPS still in use? I'm assuming it has been superseded by newer technologies, Unicode, etc?
While not being directly involved with meps development ( there is so many different depts and service to volunteer and help out), I know that the MEPS has always been an umbrella for the multi lingual publishing tools. At its origin it was a revolutionary system that helped layout, compositing and preprint workflows and scaled to a Hundred something langs an provided features we take for granted today (typesetting and automatic layouting in 120+ Lang’s well before it was cool)
Nowadays it’s highly probable that the meps also encompasses web publishing workflows (now in 1000+ Langs), pdf, Braille and print, using whatever industry standard appropriate and filling the gaps where commercial products fall short ( its a quite unique set of challenge that would stress test any CMS and publishing software)
Finally I have lots of friends working as volunteers in the content translation itself and I’m even more amazed by the quality of training, quality assurance process and attention to detail.
For instance small teams of translators are geographically located where the target language are spoken idiomatically (even for small communities) to ensure smooth and practical translations. Just imagine having to coordinate hundreds of distributed teams in every single country and region of the world, all volunteers, and maintaining high quality translation while most of translators are locals with only goodwill and no formal training in translation ( sometimes even dictionaries does not exist )
And of course, no corporate backing, and strictly every single member is a volunteer !
I also faced the challenge of combining Arabic and/or Hebrew (which read right-to-left) and Roman in the same line. It drove both my browser and text editor nuts. In at least one such case in the book, Mozarabic, where I needed all three, separated by slashes, I just went for the nuclear option of simply bitmapping them.
As the title implies, I was able to exploit Google's Noto series to the hilt for my book. The Cardo I'm using for the body copy (sorry that some don't care for the ligatures, which I deliberately sought) was originally a web display-only font, but that's been fixed. Also, its italics wouldn't respond to CSS; fixed, also.
But you don't mention the connection to Google Noto. I had to look it up. It's a font (family) that has extremely wide coverage of glyphs for different languages.
I usually don't like to comment on page issues, but since yours is the top comment, just wanted to put down my objection, lest I see in horror someone else copy this design.
If you have a "dual scroll bar" problem, just stop right there, your site is broken. I didn't even bother reading the whole thing because I thought scrolling was highjacked and I couldn't tell how long the article was. I despised everything about this design.
And then the site uses two fixed divs set to overflow hidden, which causes the site to have three scrollbars, one window scrollbar and one for each of the divs.
I think the site design hasn't been updated in a long while.
Those things could be easily fixed without having to do a complete redesign.
but a new layout doesn't make this much easier to read. the writing style mirrors the site layout - it's more for the author's amusement than the benefit of the reader.
If I hit page down, it scrolls the size of the frame, and not my screen. The frame is taller than my screen, so page down scrolls more than a screen full. I would have to use arrow keys or the mouse wheel to read it.
I tried scaling the page down so that the frame fits on screen, but page down still scrolls too far, somehow?
Just put the content on the page, with each section left to size itself based on however-much content is in it, instead of giving each section its own scrollbar at least?
I remember doing this 15 years ago.
Today this is a problem that was solved dozens of times, from Bootstrap, to Zurb and Tailwind - with productivity, accessibility and variety of devices and screen-sizes in mind.
Your website is unpleasant to use and scroll. It feels you're reinventing the wheel just for the sake of it?
It’s a lot easier to start with a good, semantic html structure and come up with exactly the CSS that one needs, rather than continually fight a system aimed at no one in particular.
Not to mention the bloat of unnecessary CSS/JS that you don’t actually need.
:root { font-variant-alternates: normal !important; }