| newspaper |
- Have a room to add ''loose'' in future.
- It's is not at all clear that 'newspaper' means "less restrictive then loose".
- Newspapers could use different physical media than a real newspaper, which allowed for longer lines.
- I don't think using names associated with particular media is a good idea
- If you can come up with good sample applications, like ‘newspaper’, ‘magazine’, ‘book’, ‘letter’ or the like, you could also settle on them, but that’s not really what CSS does elsewhere.
|
| short-lines |
- would also work, though I suppose someone might want to use this when they don't have short lines or not use it when they do have short lines, so it suffers from the same problem as 'newspaper'.
|
| narrow-column |
- I don't like narrow-column as it may be confusing when used in the absence of explicit columns.
|
| newspaper-like |
- more indicative than first thought?
- It's an interesting thought, though I am not sure how you get a clear hierarchy of 4 levels that way.
|
| 20, 40, 60, 80, … |
- more indicative than first thought?
- It's an interesting thought, though I am not sure how you get a clear hierarchy of 4 levels that way.
- Absolutely no, that’s very unCSSy.
|
| loose |
- Used and known as an antonym of ''strict'' for HTML/CSS authors.
- "Loose" can be used in the sense of "not strict"; I think it's good enough for here.
- For strictness, the sequence ‘loose’, ‘normal’, ‘strict’ seems quite natural to me, disregarding the valid point that “lose” is often misspelled “loose” and probably vice versa.
- Looser and Loose are not good terms because they are not typical antonyms to Strict
- in a typographic setting the term loose usually applies to spatial relationships (e.g. loose letter spacing, loose line spacing) rather than something like linebreak logic.
- I have the same connotative problem with 'line-break: loose' as you have with 'line-break: minimal'. It suggests something different to me.
- i'd like to vote against using lose/loose or any variant in anything as misspelled/typo'd words go, that pair is pretty high on the list.
- Linebreaking is related to justification, which affects inter-word spacing. The purpose of what you are considering 'loose' linebreaking is relaxation of hyphenation rules in order to *avoid* loose word spacing, e.g. as occurs in narrow columns. So for anyone thinking about the text block as a whole, terms like 'loose' may be confusing because this is a term more commonly encountered in reference to spacing.
|
| looser |
- Have a room to add ''loose'' in future.
- Odd without ''loose'.
- Would ''looser'' be looser than ''loose'', or is ''loose'' looser than ''looser''?
|
| frequent |
- 'Frequent' or 'open' might work, but I prefer 'loose'.
|
| open |
- 'Frequent' or 'open' might work, but I prefer 'loose'.
|
| relaxed |
- Those sound good to me.
- ‘free’/‘minimal’ (= ‘loosest’) and ‘relaxed’ (= ‘loose’ with that becoming loosest), of which one is probably as good as the other.
|
| free |
- Those sound good to me.
- ‘free’/‘minimal’ (= ‘loosest’) and ‘relaxed’ (= ‘loose’ with that becoming loosest), of which one is probably as good as the other.
- Sounds like no rules, but actually a minimal set of rules does exist.
|
| minimal |
- ‘free’/‘minimal’ (= ‘loosest’) and ‘relaxed’ (= ‘loose’ with that becoming loosest), of which one is probably as good as the other.
- While that list seems reasonable in isolation,
I don't think "line-break: minimal" carries the right connotation: it seems to mean "minimize line breaks".
|
| lenient |
- the antonym to "strict" in this case is "lenient", but that's a little hard to spell.
- I could live with ‘lenient’, too
|
| basic |
- Since the idea of the least strict style is a minimal set of restrictions
- The problem is that "basic" then becomes confusable with "normal".
- I don’t share the objection that ‘basic’ implys the same level as ‘normal’.
|
| lax |
- How about 'lax', as a good antonym for strict?
- lax tends to have negative connotations.
|
| easy |
|
| permissive |
|
| torelant |
|
| Property name to 'prohibit-break' |
- ''prohibit-break:loose'' might work better than ''line-break:loose''.
- I don't think we should be renaming either the property or the two values 'normal' and 'strict' if we can reasonably avoid it.
|