![]() ![]() ![]() I actually never use InDesign's baseline grid visually (it's always hidden), because I only need the snap of my own guides to properly align graphics with text (à la Müller-Brockmann). What I always do now is, once I found my page design grid and determined type size, I tweak InDesign's baseline grid accordingly to set its start point with a determined offset, so that I achieve the described behavior (it's the case in the first image above the lines displayed are not from the actual baseline grid, they're "my" set of guides the baseline grid is hidden and actually offset a little upwards). the lines on which characters "sit" not sure how to solve this, but maybe simply by the opportunity to set a vertical offset from the baseline grid (or "text setting grid") to place this virtual "sitting" line a bit above the visual, snapping guide line, to achieve the geometry shown in the previous image. This baseline grid cannot be the "text baseline", i.e. ![]() These values are related if you think for only a minute. The "Create guides." menu function should also determine "baseline grid" as a module of the design grid: one could choose a number of rows, and then a number of "text setting grid" lines per row, which would immediately make the whole spread entirely modular! The present disconnect between page design grid rows and baseline grid doesn't make sense (it doesn't to me, anyway maybe there could be an option for the two values to be linked in a clever manner like this).So, to be complete (and it would make InDesign 1.5× more powerful to my eyes, not a small feat for a 30+ y.o. Adobe need to pay more attention to Josef-Müller Brockmann and they would make things the right way here. The "baseline grid" is only completely useful when it encapsulates the complete character height, with ascenders and descenders - just like physical upper and lower limits of a composed lead type line! It's the only thing which makes sense, because the way it is now, the "baseline grid" cannot be used to align graphics with bodies of text. The text does not "sit" on the baselines instead, its whole height is "encapsulated" between the guides Instead it should be called "text setting grid", or "grid text subdivision", or something. It should not be called "baseline grid", because these divisions should not represent actual text baseline (at least not how it's implied at this time). There is something wrong at the very root of how InDesign implements, and even names this modular grid. Now, about what happens with baseline grid inside cells. Here I often find myself crying for flexibility and resolve to odd values. And, from experience, it's not very often that I can keep column widths modular throughout a substantial book. In this mode, the rows heights would automatically grow according to contents, but only in steps of baseline grid dimension.Ĭolumns could work the same way, although there is no real equivalent to baseline grid in the vertical domain. There should be a check box in some table styling dialog which allows you to force the table top edge, bottom edge and row divisions to snap to baseline grid. And I totally agree: not only must table rows heights match a multiple of baseline grid lines, but the insertion and exit points (top and bottom "edges") of the table must also occur on baseline guides. Please see this snapshot of an example document of my design:Įmpty page design grid with a correctly set "baseline grid"Ĭome in tables. And the corollary is that baseline grid height is equal to horizontal gutter height. The consequence is, if the baseline grid is to be of any real use, that the baseline grid height, from line to line, is a module (a sub-division) of your page design grid row height. Now, the horizontal division of this grid is the column, and the vertical one, the row. If you are half serious about text design, you can't work without a grid. But none address what I believe is a core issue in InDesign. I see all sorts of correct, yet incomplete, observations about how tables pose certain vertical alignment problems, both regarding cell limits and text within cells itself. If I go into more detail, though, I need to explain other things. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |