I think "Same Sizer" looks ugly because characters are stretched mechanically, so each line has different width. Ideally, the lines should all keep their widths, and the position should be stretched.
I think a better application of "all words have the same size" principle can be seen in Vietnamese calligraphy, which sometimes combines Latin characters with Chinese-adjacent writing style, e.g. https://commons.m.wikimedia.org/wiki/File:%C4%90%E1%BB%91i_-... (this is written in Latin script split into equal squares)
Huh. I would never have noticed that your example image is actually in Latin script.
Because I don't read Chinese, anything that looks enough like Chinese seems to mentally go into the bin of "I can't understand this anyway." (I guess in this case it would help if I knew Vietnamese because then I would recognize familiar words and syllables in this calligraphy.)
I can read Chinese and still cannot process that image as Latin script. They've turned every letter into a Chinese character component. It makes my head hurt.
I had the problem that navigating the page in firefox almost set fire to my CPU on my 2yr old linux dev laptop. Really liked the visualisations, though.
Ok, I want the "Hyphenator" layout, but with more than just one word. I want the extra text to wrap around while the font keeps getting smaller to mimic how I used to take hand notes in college and need to shove in some stuff with no space left in the line.
In non-phoenitic languages, i.e. English, many of these methods are painful, especially "Last is First". See "I", but then it's "In", so you need to mentally backtrack some understanding. See "t", but then it's "that", so if you're subvocalizing to read, you need to reform the phoneme because 't' is a different phoneme from 'th'.
I think in casual speech at this point (at least in my experience) the two are used interchangeably. In professional or legal settings I'm sure the distinction matters more, but I feel like OP's usage here felt pretty natural to me even though it's not technically correct.
Isn't reading more like pattern recognition than parsing letter-for-letter? It seems to work like that for me. There's also the somewhat famous text where each word's letters are jumbled and people can still read it fluently. Maybe that's not the case for everyone, though, and people have different ways of making sense of written text.
I once attended a short workshop where the person presenting encouraged us to switch between two modes of reading away from sub-vocalizing and into pattern recognition. The result was much faster reading without loss of understanding.
He didn't use those terms but adopting them from this thread - I learned that day that these really are two distinct modes.
English is phonetic? The writing systems aren't regular in that the same letter can represent different sounds. But they still represent sounds. Indeed, your confusion wouldn't even be possible if they didn't represent sounds.
A short word like "that" is read at once, especially because it's common. So no need to backtrack.
A less common word like "phoenitic" or "subvocalizing" is read as you say. However by the end of the sentence we know how to read "phoneme" because we encountered it 3 times in one form or the other.
I think "Last Is First" is almost like a checksum for the people writing the text, so they don't lose their place as they are copying it.
I remember having to read the Torah and it was hard to move from learning to read with standard printed Hebrew, into not only the voweless text, but with the letters stretched. You had to learn how to sing the words correctly as well.
But it was a beautiful thing to see, handwritten, fully justified, columns written with ink on parchment.
I suspect that if it was common the reader would also use it to help find the right line to continue on. Especially for longer lines where it is fairly easy to try to read the same line again or skip one.
God, please don't make websites like this. I have a 1 Gbps connection, with a 1 Gbps network interface. Your server _cannot_ serve a site this large. Every single jpeg image which by design takes up no more than a few hundred pixels on a side when rendered on a screen is transferred over in 4K resolution, at sizes up to 9 MiB. Certain pages take upwards of 15 seconds to load with a total size of >40 MiB!!! I'm aware that it's partially due to the hug of death, but 3 Mbps is actually a respectable serving speed for most small servers, the site itself is just too large!
This is one of the cases where it seems more justified than usual. This is not a website intended for end users, maximizing for performance and conversion rate. It's a design showcase by a typographer, for typographers. Every pixel is crucial, and the intended audience would rather wait a few seconds to be able to scrutinize the output with the required detail.
"Last is first" very much reminds me of the custos/custodes seen often in Gregorian chant notation, which come at the end of a line and are a hint of the first note in the next line (so while your eye is finding the start of the next line, you already know the pitch, even though it typically does not include the syllable).
I have some eye issues, namely a lazy eye and double vision. I find same-sizer remarkably easy to read. Easier than standard text, which is very curious.
I almost wonder if the idea could be used as a sort of accessibility mode.
Related to "Last is first", old Spanish books sometimes put at the end of the page the first syllable of the next page. (It was quite disconcerting when I first saw it.)
That's called a "catchword", and it's common in many older texts (not just in Spanish). It serves two purposes - it makes it easier for a person reading the book aloud to read smoothly while turning a page, and it makes it easier for bookbinders to spot pages which are missing or out of order. (Page numbers were, believe it or not, a later development.)
It was common throughout Europe in the early modern era.
I've got a book of recipes from Williamsburg, Virginia, a kind of outdoor museum LARPing as 1775. The recipes are from various sources, but they typeset it as a period document, including those catchwords. I find it charming.
in devnagri script text is aligned at the top of the line instead of the bottom of the line. e.g. https://www.typotheque.com/research/devanagari-the-makings-o.... would be cool to see a version where roman scripts are top-aligned, bottom uneven instead of the other way round
fun read. a few years ago i got pretty obsessed with boustrophedon script, which feels to me in a similar category. still feels like such an elegant solution to 'oh these lines are getting too long'.
https://en.m.wikipedia.org/wiki/Boustrophedon
I find this: https://i0.wp.com/biblequestions.info/wp-content/uploads/202... surprisingly easy to read; although obviously I already know a lot of what's coming, I can still pick up on the working I'm unsure of. That said, words like "debts" still threw me b/c of the 'd' looking like a 'b' and vice-versa.
I wonder if typesetting like this can be combined with https://bionic-reading.com/ ?
The above emphesises text is a regular way, but I reckon you could train an AI on people reading different empesised text, and track where they slow-down or mis-speak; and as such figure out how a different emphesis could improve comprehension (of the text)?
B) squeeze the individual letters together in a font, extreme negative tracking while they're still distinguishable.
C) substitute frequent short words with symbols and prefix them to the next word, e.g.:
- 'not' with symbol: "!"
- 'and' with symbol: "&'
- 'or' with symbol: "|"
- 'the' with symbol: "`"
- 'a' with symbol: "*"
- 'at' with symbol: "@"
- 'about/around/circa' with symbol "~"
- 'of' with symbol '\'
- 'for/per' with symbol '%'
- 'in' with symbol '#'
- 'to' with symbol '>'
- 'from' with symbol '<'
- 'on' with symbol '^'
- 'as' with symbol '-'
- 'is' with symbol '='
- 'with' with symbols 'w/' & 'w/o' (without)
...
these layouts break kerning rules. render engines expect horizontal flow, steady spacing. but with same sizer or echoed lines, glyph logic goes off path. spacing's no longer font native, it's forced by layout. font stops being just visual, becomes part of layout logic. whole engine ends up doing things it wasn't ment for. then layout will start mutates typography logic iteslf
that's kind of the point here, i guess. to intentionally find nice ways of breaking rules to achieve some neat effects, to look into what can be done. it's a really neat thing to do.
I think "Same Sizer" looks ugly because characters are stretched mechanically, so each line has different width. Ideally, the lines should all keep their widths, and the position should be stretched.
I think a better application of "all words have the same size" principle can be seen in Vietnamese calligraphy, which sometimes combines Latin characters with Chinese-adjacent writing style, e.g. https://commons.m.wikimedia.org/wiki/File:%C4%90%E1%BB%91i_-... (this is written in Latin script split into equal squares)
Huh. I would never have noticed that your example image is actually in Latin script.
Because I don't read Chinese, anything that looks enough like Chinese seems to mentally go into the bin of "I can't understand this anyway." (I guess in this case it would help if I knew Vietnamese because then I would recognize familiar words and syllables in this calligraphy.)
Fascinating effect.
I can read Chinese and still cannot process that image as Latin script. They've turned every letter into a Chinese character component. It makes my head hurt.
I still can't read it despite trying.
1 reply →
It does not help that "hoa" is stylized as something resembling の口亽.
Along similar lines, the calligraphy here is quite impressive: https://www.reddit.com/r/language/comments/1gmzro8/what_scri...
Huh. That's a good way to explain how Hangul works I guess :)
FWIW, I call this approach 'square' writing, and have compiled some links at https://gwern.net/doc/design/typography/square/index
Probably the most interesting one is the 'Hangulatin' font (https://www.t26.com/fonts/22320-Hangulatin-EN), which is exactly what it sounds like, and unfortunately has been abandoned/linkrotten but you can see a lot of it in the old video: https://www.youtube.com/watch?v=T0syCsC0_4s
I really wanted to see the example you linked, but the link is broken
I don't know why. It works for me.
As an alternative, you can go to Wikipedia and paste File:Đối - Tết 2009.jpg into the search bar.
I had the problem that navigating the page in firefox almost set fire to my CPU on my 2yr old linux dev laptop. Really liked the visualisations, though.
1 reply →
Every once in a while I come across something so beautifully stupid that all I can see is the genius behind it, and it fills me with joy. Well done!
Did you try to read it aloud? Your voice instantly becomes robotic :D
Hahaha, actually I think I heard it in Jony Ives’s voice.
Ok, I want the "Hyphenator" layout, but with more than just one word. I want the extra text to wrap around while the font keeps getting smaller to mimic how I used to take hand notes in college and need to shove in some stuff with no space left in the line.
In non-phoenitic languages, i.e. English, many of these methods are painful, especially "Last is First". See "I", but then it's "In", so you need to mentally backtrack some understanding. See "t", but then it's "that", so if you're subvocalizing to read, you need to reform the phoneme because 't' is a different phoneme from 'th'.
Just trying to help: "i.e." stands for "id est", which means "that is".
In your text, you should rather say "e.g." (exempli gratia), which means "for instance", "for example".
I think in casual speech at this point (at least in my experience) the two are used interchangeably. In professional or legal settings I'm sure the distinction matters more, but I feel like OP's usage here felt pretty natural to me even though it's not technically correct.
6 replies →
Isn't reading more like pattern recognition than parsing letter-for-letter? It seems to work like that for me. There's also the somewhat famous text where each word's letters are jumbled and people can still read it fluently. Maybe that's not the case for everyone, though, and people have different ways of making sense of written text.
Edit: Quick search turned up this article about the jumbled-word phenomenon, containing the example text at the top: https://observer.com/2017/03/chunking-typoglycemia-brain-con...
I once attended a short workshop where the person presenting encouraged us to switch between two modes of reading away from sub-vocalizing and into pattern recognition. The result was much faster reading without loss of understanding.
He didn't use those terms but adopting them from this thread - I learned that day that these really are two distinct modes.
English is phonetic? The writing systems aren't regular in that the same letter can represent different sounds. But they still represent sounds. Indeed, your confusion wouldn't even be possible if they didn't represent sounds.
A short word like "that" is read at once, especially because it's common. So no need to backtrack.
A less common word like "phoenitic" or "subvocalizing" is read as you say. However by the end of the sentence we know how to read "phoneme" because we encountered it 3 times in one form or the other.
I think "Last Is First" is almost like a checksum for the people writing the text, so they don't lose their place as they are copying it.
I remember having to read the Torah and it was hard to move from learning to read with standard printed Hebrew, into not only the voweless text, but with the letters stretched. You had to learn how to sing the words correctly as well.
But it was a beautiful thing to see, handwritten, fully justified, columns written with ink on parchment.
I suspect that if it was common the reader would also use it to help find the right line to continue on. Especially for longer lines where it is fairly easy to try to read the same line again or skip one.
God, please don't make websites like this. I have a 1 Gbps connection, with a 1 Gbps network interface. Your server _cannot_ serve a site this large. Every single jpeg image which by design takes up no more than a few hundred pixels on a side when rendered on a screen is transferred over in 4K resolution, at sizes up to 9 MiB. Certain pages take upwards of 15 seconds to load with a total size of >40 MiB!!! I'm aware that it's partially due to the hug of death, but 3 Mbps is actually a respectable serving speed for most small servers, the site itself is just too large!
This is one of the cases where it seems more justified than usual. This is not a website intended for end users, maximizing for performance and conversion rate. It's a design showcase by a typographer, for typographers. Every pixel is crucial, and the intended audience would rather wait a few seconds to be able to scrutinize the output with the required detail.
Progressive loading?
I was so confused by there was no link to see the layouts. Turns out they were loading! It took like 3mins> on my network to even show the first one!
"Last is first" very much reminds me of the custos/custodes seen often in Gregorian chant notation, which come at the end of a line and are a hint of the first note in the next line (so while your eye is finding the start of the next line, you already know the pitch, even though it typically does not include the syllable).
See e.g. https://lilypond.org/doc/v2.18/Documentation/notation/ancien...
This is horrendous. I love it.
I have some eye issues, namely a lazy eye and double vision. I find same-sizer remarkably easy to read. Easier than standard text, which is very curious.
I almost wonder if the idea could be used as a sort of accessibility mode.
Other than a very slight astigmatism, I have no visuals issues, but also found the same-sizer text much easier to read than I thought it would be.
Their "imager" tool is really cool, though:
https://alternativelayoutsystem.com/imager/
I want to like this, but the page keeps reloading itself every few seconds. It’s really annoying.
Related to "Last is first", old Spanish books sometimes put at the end of the page the first syllable of the next page. (It was quite disconcerting when I first saw it.)
That's called a "catchword", and it's common in many older texts (not just in Spanish). It serves two purposes - it makes it easier for a person reading the book aloud to read smoothly while turning a page, and it makes it easier for bookbinders to spot pages which are missing or out of order. (Page numbers were, believe it or not, a later development.)
It was common throughout Europe in the early modern era.
I've got a book of recipes from Williamsburg, Virginia, a kind of outdoor museum LARPing as 1775. The recipes are from various sources, but they typeset it as a period document, including those catchwords. I find it charming.
so cool!
in devnagri script text is aligned at the top of the line instead of the bottom of the line. e.g. https://www.typotheque.com/research/devanagari-the-makings-o.... would be cool to see a version where roman scripts are top-aligned, bottom uneven instead of the other way round
fun read. a few years ago i got pretty obsessed with boustrophedon script, which feels to me in a similar category. still feels like such an elegant solution to 'oh these lines are getting too long'. https://en.m.wikipedia.org/wiki/Boustrophedon
I find this: https://i0.wp.com/biblequestions.info/wp-content/uploads/202... surprisingly easy to read; although obviously I already know a lot of what's coming, I can still pick up on the working I'm unsure of. That said, words like "debts" still threw me b/c of the 'd' looking like a 'b' and vice-versa.
I wonder if typesetting like this can be combined with https://bionic-reading.com/ ? The above emphesises text is a regular way, but I reckon you could train an AI on people reading different empesised text, and track where they slow-down or mis-speak; and as such figure out how a different emphesis could improve comprehension (of the text)?
Author made frequent reference to Hebrew text, is there a particular reason historical Hebrew texts uses these methods?
Yes. A combination of being hand copied and the text having no punctuation.
Could it also be an artifact of using scrolls, and needing to sharply delimit 'pages' of text?
2 replies →
"Same Sizer" is exactly how I feel about justified text
I'd like to see a layout system that maximizes rivers in the text. Lets make reading weird.
I make it more readable I want to squash the words further so the english becomes more logographic by:
A) using an alphabetic shorthand ike superwrite: https://www.reddit.com/r/shorthand/comments/pttlnn/superwrit...
B) squeeze the individual letters together in a font, extreme negative tracking while they're still distinguishable.
C) substitute frequent short words with symbols and prefix them to the next word, e.g.: - 'not' with symbol: "!" - 'and' with symbol: "&' - 'or' with symbol: "|" - 'the' with symbol: "`" - 'a' with symbol: "*" - 'at' with symbol: "@" - 'about/around/circa' with symbol "~" - 'of' with symbol '\' - 'for/per' with symbol '%' - 'in' with symbol '#' - 'to' with symbol '>' - 'from' with symbol '<' - 'on' with symbol '^' - 'as' with symbol '-' - 'is' with symbol '=' - 'with' with symbols 'w/' & 'w/o' (without) ...
The first one reminds me of this stylized Vietnamese prayer, which squishes Latin script syllables into Chinese-like blocks:
https://old.reddit.com/r/neography/comments/1gp6t8j/stylized...
These are so creative!
I love "Same Sizer" for titles and design, and I don't think I'd hate "Fill the Space" in body text if glyphs (such as the key) were used.
This applied to a fictionally motivated glyphs, like Klingon, would be interesting.
immediately ordered the book
fascinating checkout flow
It's giving time cube
Of course it's Swiss.
[dead]
these layouts break kerning rules. render engines expect horizontal flow, steady spacing. but with same sizer or echoed lines, glyph logic goes off path. spacing's no longer font native, it's forced by layout. font stops being just visual, becomes part of layout logic. whole engine ends up doing things it wasn't ment for. then layout will start mutates typography logic iteslf
that's kind of the point here, i guess. to intentionally find nice ways of breaking rules to achieve some neat effects, to look into what can be done. it's a really neat thing to do.
Thanks, I hate it. /s
Reminds me of the Dotsies system for fast reading, only this makes reading slow...
Or just use CSS
https://developer.chrome.com/docs/css-ui/css-text-wrap-balan...
This is a set of InDesign scripts. Not CSS.