6 ms·
Typeset: An HTML pre-processor for web typography
- jdnsndnjd 2y agoIronic that the website is unreadable on mobile due to improper flow
- thangngoc89 2y agoThe correct term would be non-responsive. I think if the second column be moved to the bottom, it would be hard to read on mobile.
- knallfrosch 2y agoMy iOS/Safari on a 13 mini detects bad CSS immediately. You can easily tell some sites are unresponsive or Chrome-only.
- deleted 2y ago[deleted]
- pglevy 2y agoHave to agree. With as much reading that's done on small screens these days, I find it discouraging that a project about good web typography looks broken on my phone. I see adapting parameters like size, measure, and line height to different screen sizes (and the related reading distances) as one of the main challenges of web typography. Not as sophisticated of a project but I've tinkered with a stylesheet to address some of these issues here: https://pglevy.github.io/typeset.css/ https://pglevy.github.io/typeset.css/
- drawfloat 2y agoI see this dates back a decade, which makes sense given this is now achievable in modern CSS without a preprocessor.
- nicbou 2y agoNot quite. Hyphenation is rather unreliable in my experience.
- dietr1ch 2y agoYeah, last time I experimented with it `hyphens: auto;` and `word-break: auto-phrase;` were simply not ready to try even in beta/nightly browsers. - https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens - https://developer.mozilla.org/en-US/docs/Web/CSS/word-break https://developer.mozilla.org/en-US/docs/Web/CSS/word-break
- nicbou 2y agoIn my case, it really struggled with over-hyphenation when a line break would be completely fine.
- 8bitsrule 2y agoAchievable, I suppose. But 10yo CSS is a big-enough PITA that, if the machine can learn to do it, it should.
- red_trumpet 2y agoSupport for ``hanging-punctuation`` is not there yet.
- coolio1232 2y agoSorry if I'm sounding harsh, but do people aside from hardcore typographists really care about this and similar font/text tweaking projects? I felt no noticeable difference in readability in either of the modes and for a second I even thought the before example is the "better" version they are advertising because it felt more streamlined in my eyes. Maybe this might help people with dyslexia but don't proper dyslexia focused fonts and aids exist already?
- ianstormtaylor 2y agoOne way to gain a different perspective could be to ask a similar question, but replace typographic adjustments with something in your domain of expertise that requires deeper experience to see the value in. Assuming programming, it might be things like linting, refactoring, testing, version controlling, etc.
- coolio1232 2y agoLinting, refactoring and testing all have obvious benifits for anyone who has done any small to medium sized project and has had to rewrite and debug some amount of code, even if they don't know the concepts by name. Even version contolling is ubiquitous in almost any entry-level programming job, even if it wasn't before. Most people who have made a website with CSS before would at best change the font size, the line spacing and the font face and tweak it to a point that feels easily readable and call it a day. Introducing variable widths between the characters of the font, digraphs and so on feels like more like exercising artisanship that only the experts would see value in rather than solving a technical problem. Perhaps advanced web design/typesetting is the main application of this and it has a chance of inducing a better subconscious effect on the viewer. Sort of how magazines and books were designed back in the day I suppose.
- miunau 2y agoYou missed the point entirely. This is basic stuff that all designers work with.
- 2y ago
- dngit 2y agoNow, it's been a very long time since I see a mention of "Internet Explore 5". Kudos for highlighting the support for it but does it matter, who in the world are still using Internet Explorer 5?
- swiftcoder 2y agoThe website is nearly a decade old. presumably folks did still care about IE5 in that time period.
- nick__m 2y agoA decade ago (2014) IE5 was completely dead. Some people were still force to care about IE6 but it was marginal. The default browser from that period was IE9 !
- dngit 2y agoAh, sorry, I didn't notice the website itself was that old.
- naniwaduni 2y agoIE5 was never a relevant contemporary of npm. The one that cast a long shadow on the web was IE6, pretty much exclusively, due to the unusual circumstances around antitrust intervention in the US and Europe putting MS off of really pushing their browser for nearly a decade (IE7 was pretty much DOA). IE5 was quickly replaced by IE6; nobody cared about it much even in 2005, let alone 2015. That was already an age of Chrome-first dev, complaining about Apple's lagging support for web ""standards"", and Firefox I guess more relevant than today but already increasingly an afterthought. The IE you'd be targeting, if any, was probably 8, unless you knew you wanted the userbase that was stuck with IE6.
- ninalanyon 2y agoThe most annoying thing about the page is that the before and after are not presented side by side making it difficult to see all the changes at once.
- deleted 2y ago[deleted]
- hexo 2y agoWeb "typography" is so awful I had to disallow web fonts a long time ago. Now its time to write some greasemonkey lube to fix line heights and font weights, as thin fonts are nonreadable and finally somehow fix gray text low-contrast nonsense.
- nosioptar 2y agoI really like the Stylus plugin for that. I think it takes a bit less effort than changing CSS with greasemonkey.
- deleted 2y ago[deleted]
- kibibu 2y agoBe aware that this appears by default to swap character pairs with unicode ligatures, which is fine, but those characters aren't included in many web fonts. It's better today (both for the above issue and also for usability) to disable the ligature substitution and let browser engines manage ligature replacement.
- starkparker 2y agoThis also breaks naive/literal search. For an example, copy and paste the "After" text into VSCode and try to search for "taking", "coladas", or "Exhibits". It won't match because of the ligatures. Browser search can typically parse Unicode ligatures, so it's not a huge usability problem. But saving, copying, or scraping the output and using tools that don't process ligatures into their component letters will fail. This also (very slightly, but still notably) abuses empty contentless <span>s to inject space through CSS margins. Also, the attempt to brute-force small caps by applying a font subset via a span doesn't work at all for me, in either Chrome or Firefox. It's a good effort, but I also can't think of a use case where the result is worth what this does to the markup.
- v1ne 2y agoNice to see we're getting there again and that people care about typography. Yet, the optical margin correction looks mechanistic and only concerned with symbols, not with characters: The "Y" at the start of the first line doesn't move a bit, even though it's clearly optically too light on the left. The next three lines all start optically pretty heavy with a bar. So I'd nudge to "Y" to the left. I think it's just a pity that LaTeX with microtype is still the pinnacle of automatic typesetting, after all these years. I really enjoy good typography, but the Web, App and even Desktop world seems not to care about such details, apart from a few programs like Ableton.
- PaulDavisThe1st 2y agoWhat does "Ableton" (which is a company that makes a piece of software called "Live" among other things) do with typography on the desktop?
- vntok 2y agoThey genuinely care about their software's UI.
- PaulDavisThe1st 2y agoI'm a typography nerd, and the author of another DAW. I think that Live looks pretty good, but it doesn't have much to do with typography in my eyes. Now, their education website(s) ... that stuff is gorgeous, and I think does represent somebody's typographic imagination, to the extent that HTML/CSS makes it possible (which is .. a lot).
- throw_pm23 2y agoAlso the " in the second paragraph feels a bit too far out to me, microtype does these things more subtly a bit.
- taikon 2y agoI think this package can reduce readability. The content under Before looked better than the After to me. For example, it changes the word "duplex" to "du-plex" split over two lines, which is less readable.
- benjamaan 2y ago[flagged]
- pier25 2y agoThere's a bug on mobile (Android). For some reason the page is twice a wide as it needs to be. Edit: I missed that on the top of the page there's an example section on a second column which is not responsive.
- gr4vityWall 2y agoI feel bad that, after looking at the Before/After comparison, it wasn't clear to me which one looked better to my eyes. But I wouldn't mind having such a feature built-in in browsers if it brings value to other people.
- WillAdams 2y agoAny prospect of getting this into an ePub reader? They are ripe for any sort of typographic improvement --- the only things which keep me reading on my Kindle are the convenience and the ability to report errors.
- msephton 2y agoI don't think so as epub renderers target the spec which is pretty entrenched at this point.