Sebilar, you are flying in the face of convention. When one makes special versions of accents for majuscule letters, the habitual solution is smaller/more compact marks, so that a line of all-caps - or several lines of all-caps - stay as compact as possible.

Also, you should just use the Unicode index for each of the accented majuscule letters. If you want to have the large accents AND an additional set of compact accented caps, you can name them things like Aacute.alt or something, then write a SS01 feature to swap out the one with the other. (Since you already have Titling variants.)

And in the case of Titling versions of majuscules, you can name them Aacute.titl etc. and assign them Unicode indexes from the PUA (Personal Use Area). Without indices, they can only be accessed through the application of an OT feature; with indices they can be accessed using the Character Palette or InDesign's glyph palette.

And in the case of Titling versions of majuscules, you can name them Aacute.titl etc. and assign them Unicode indexes from the PUA (Personal Use Area). Without indices, they can only be accessed through the application of an OT feature; with indices they can be accessed using the Character Palette or InDesign’s glyph palette.

What do you mean by "without indices?" I didn't assign Unicode values to everything in the font I'm working on -- Greek small caps, some ligatures, etc. -- but they still show up in the InDesign glyph palette. And I'm still writing the features for them. And I've been staying out of the PUA because David Lemon told me to.

As for sizing I also change the angles of acute, grave, etc. so their shallower than those for the lc.

George

I felt bad because I had no shoes, until I met a man who had no Bodoni

I can see why this might be appropriate on a sans serif face.

But if you flatten the angle of the accent for the cap (or squash down the circumflex), and drop it a bit closer to the letter, then the difference won't be so obvious.

And those things are important to do, because otherwise any setting other than with lots of leading will result in collisions with descenders.

The convention is to change the angle for cap accents, to improve leading, rather than change the weight to improve color, which makes leading worse.

In fact, flattening the angle of accents does make them visually bolder, because horizontal lines are perceived as thicker than vertical lines of the same weight!

I will try this, Nick, this should work for me too.

btw: your avatar is scaring me...

Sebilar

Regarding Unicode: As Chester notes you should use the precomposed diacritic character codes where possible. However, if you are supporting OpenType layout for combining mark characters, either through GSUB in the 'ccm' feature or through GPOS in the 'mark' anchor positioning feature, then you should include glyph variants of the combining marks for uppercase and smallcap letters as appropriate. So, for instance, you might have three glyphs for the combining acute accent. The default form is the lowercase, which is encoded as U+0301; the other glyph variants are unencoded, but are instead accessed using OpenType Layout features. They would be named something like this:

acutecomb
acutecomb.cap
acutecomb.sc

If you are using the 'ccmp' feature to map from sequences of base letter plus combining mark(s) to precomposed, unencoded glyphs in the font, e.g.

Adiaresis acutecomb -> Adiaresisacute

then you don't need the variant combining mark glyphs for such sequences. But you obviously need them if doing GPOS mark positioning, and it is useful to have them in the font even if you are supporting precomposed diacritic glyphs, since some user may employ some combining mark sequence for which you have not provided a precomposed glyph. You might have a precomposed glyph for /Adiaresisacute/, for instance, but not have one for the sequence

A dotbelowcomb acutecomb

in which case you want to ensure that the combining acute that follows the capital letter is the correct form and height, even if you have not refined the horizontal positioning using GPOS mark positioning.

To do this, you need to use a contextual lookup to substitute the cap variant combining mark glyph when it follows an uppercase letter. Since this is a contextual alternate substitution, you may consider using the 'calt' feature, and I think this would be valid. However, since this is probably not something that you want to be turned off by the user along with stylistic contextual substitutions, I recommend putting this lookup in the 'ccmp' feature.

btw: your avatar is scaring me…

Thanks!