-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider renaming "Preformatted" to "Poetry" #1729
Comments
I think changing the font would be good so it's not just like code. Needs to be monospaced though. Not sure if I like "Poetry" because it can be used for much more. |
An alternative is that this is a separate block. But we have to answer the question whether we need both a Code block and a Preformatted block. |
So you can just write poetry already without doing anything special? :) That said, if you want to have it some special styling (like italic), it should probably be an enhanced text block? |
I does seem that |
Please not "Poetry". It would be strange for some websites for some companies. Keep it serious. |
I noticed that spaces are in fact saved, and respected, as Ella suggested. That's half of it. Multiple linebreaks are not, though — a So I still see a usecase. The question becomes — is Preformatted useful to anyone, given we have a Code block also? If yes, then Poetry should be a separate block. If Preformatted is just confusing and few use it (as some initial confusion suggested), perhaps we rename it? |
Yeah I agree there's still a use case. I would create a separate block called "Verse" or something like that, which could be used for poems, songs, and alternative forms such as a message where the spacing is important. Here's a wonderful example which illustrates a few use cases: http://www.gutenberg.org/files/11/11-h/11-h.htm I wouldn't classify all of these as poems:
A "tale":
A song:
Message:
Decoration (use case for preformatted text, certainly not code):
I guess you could argue that songs are poems, and ASCII art is code, but 🙃. |
Icon idea: Quill. |
I agree on your assessment @iseulde in terms of "not everything is a poem"... I'd personally still like "Poetry" as I feel it would send a strong message even if it can be used for far more than just poetry. Mostly because intuitively I feel people would get "Poetry" but other labels more semantically accurate like "Preformatted" would be hard to understand. And yes I agree it should be a separate block, as we might enrich it with specific properties like title and author, deal with cases like multiple spaces, which wouldn't make much sense for other uses. Also, would allow to better deal with fonts (instead of the monospaced one used for code). I'd add that semantically might be even make more sense to tag Poetry differently from Preformatted: shouldn't Poetry use
Great icon idea. 💯 |
I'm not sure what's better for poetry than https://www.w3.org/TR/html5/grouping-content.html#the-p-element So they'd say that if whitespace other than line breaks is important in a poem, it should be If you use |
Getting really into this. https://www.poetryfoundation.org/articles/69619/breaking-the-poetry-code |
I'm with you there. The state of ePub is one of the reason that made me in 2010 to create Baker Framework. :)
Good point on how to split it. Makes me prefer using |
Preformatted is a great way to write haikus and poetry, because spaces and linebreaks are respected.
Should we rename the block to "Poetry", perhaps change the font to be the same as the base font? Or should "poetry" be a separate new block? Or should we add a "style" choice to the block that lets you write with the same font as the body text has, but with the benefits of preformatting? Should we add word-break?
Let's work this out together.
The text was updated successfully, but these errors were encountered: