|
2009-09-18 02:51
|
Scribus - per-character leading example.png (8,691 bytes) |
|
2009-09-18 02:52
|
@ placement in fonts.png (28,954 bytes) |
|
|
Got a little crazy and added some examples of "questionable @s" - From top to bottom: Arial, URW Palladio "Roman", URW Palladio "Roman" with a cranked up @, Bitstream Vera Sans "Roman", Bitstream Vera Sans Oblique with a cranked up Vera Sans "Roman" @ Arial actually comes closest to 'getting it right' as far as the relative size of the @ and its contrast with other characters. But who dares use Arial? I happen to have some logotype that 'depends' on Palladio; it might be the big offender here. But in other uses, having an @ on the baseline is nicer - try "@ $300" in Palladio vs. Arial! Vera Sans has the right idea but the relative size of its @ is small, not so good for attracting the eye on, say, a business card. ...and Vera Sans Oblique with the larger non-oblique @ is how I would've set that first snippet, but shows the problem - without the ability to force the bigger @ to shift down, it's floating too high above the baseline and you have to resort to all sorts of manual tricks and manual alignment instead of just having text in a text box. Another place this shows up is with tweaking superscripts and subscripts: for a book layout, yes, you want to set the defaults and have them match everywhere, but 'design' may call for some fiddling to find the exact right size and vertical offset - or to figure out what you want to set as the document or style-wide defaults in the first place. |
- Anonymous
