A
REAL trouble I once suffered within a book and one that I've checked that the new Check Book doesn't inform you about either...
Remove the closing "}" from any style... It can drive you nuts as there's no information about something strange. And till the next closing "}" you have trouble in both styles. (
I suffered it in the middle of font declaration statements and I got crazy till I located what the hell happened in the book.).
I think it could be a good idea that, if parser finds an "entry/entity" inside any other one, it should arise a warning.
Another one I haven't suffered but I think it can be REALLY easy to have. Remove the closing ";" from any property (but final one). Then you have trouble inside a style. And Check Book doesn't tell you anything about it.
This situation would be a good catch too.
Quote:
Originally Posted by kovidgoyal
And no there is never going to be a "full" preview with support for page layout.
|
OK, I suppose page layout support is fully pointless. But, please, could you implement full font support? Fonts not being used because of their "conflictive" names can be REALLY distracting and completely user-
unfriendly. I fear you are going to receive a lot of complaints, like my original one, about "My font doesn't render" despite all the warnings you put in the tool opening.
And another suggestion related to the ";" issue. Currently, Beautify CSS removes the last ";". As a safety measure I would do the opposite action, I would
always add it even if not necessary...