View Issue Details

IDProjectCategoryView StatusLast Update
0008440ScribusTypographypublic2016-12-12 12:12
Reporterfloid Assigned To 
Status newResolutionopen 
Platformamd64 LinuxOSUbuntuOS Version9.10a-something
Product Version1.3.3.13svn 
Target VersionFixed in Version 
Summary0008440: No leading (Y-position) "override" for individual characters
DescriptionTracking can be applied to a selection in a text box, but leading/line-height is a property of the text box or paragraph style only.

Being able to force a leading offset to selected characters would save much time and be less fragile vs. "doing it by hand" with multiple text boxes.
Steps To ReproduceCan you typeset the LaTeX logo in a single line of a Scribus text box?
Additional InformationI'm most often using Scribus to produce letterhead and business cards.
Unfortunately, some fonts (or maybe just one that I use..) set "@" on the baseline rather than dropping the curl around the 'a' into descender territory.

When they do, sometimes a 'DTP' project still calls for a little more emphasis than the font's designer had in mind - and the easiest way to get that is to crank up the size of the character, which then skews anything the font's designer did to help, oops!

Attached is an example where I went through the trouble on a recent project - manually positioning a large Arial @ in one text box while keeping the rest of the Bitstream Vera Sans Oblique address in another.

[Type critics: yes, that could be better; the manual positioning was a barrier to further experimentation, and I wish I'd noticed the regular Vera Sans "@" at the time! Still, Arial's @ is as ubiquitous as MSIE's 'e', and I just needed to make sure the email address would stick out to normal humans in a crowded layout. Notice how the size difference helps distinguish it from the loop in the preceding oblique 'd'.]



2009-09-18 02:51


2009-09-18 02:52


@ placement in fonts.png (28,954 bytes)
@ placement in fonts.png (28,954 bytes)


2009-09-18 03:16

reporter   ~0022499

Got a little crazy and added some examples of "questionable @s" -
From top to bottom:

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.

Issue History

Date Modified Username Field Change
2009-09-18 02:51 floid New Issue
2009-09-18 02:51 floid File Added: Scribus - per-character leading example.png
2009-09-18 02:52 floid File Added: @ placement in fonts.png
2009-09-18 03:16 floid Note Added: 0022499
2016-12-12 12:12 Kunda Tag Attached: scribusctl