The background
Here's my recent Latin/Cyrillic design that works on the contrast between wide/tall/decorative uppercases and low/condensed lowercases. I'm thinking about how to translate it into Hebrew, because Hebrew has no upper/lower-case logic, and there is the dilemma of adaptation. So if I adapt only the lowercase shapes into Hebrew, the design balance of upper/lowercases will be lost, although it will be an acceptable neutral solution. And if I adapt only the design of uppercases, it will look just wrong, too decorative and difficult to read.
Looking for a combined adaptation for Hebrew
One of ideas was to make the first letter of the Hebrew text sequence wider (not higher) within the Hebrew unicase framework, and a bit more decorative. Hrant and I have a discussion about that in the replies
to this tweet. It may feels more like a Latin concept (throw a stone at me if you think I'm trying to Latinize Hebrew), and I don't even know how it can be perceived by a Hebrew reader.
Substitution
Here's an approach with using default wide letters (to ensures that the first letter in the sequence will be wide), and all the others (except ignore period+space) will be (contextually) substituted with a condensed versions. This approach however is technically overloaded so I not sure about efficiency. Here's how the substitution (where hbWide are default glyphs) looks like:
ignore sub period space @hbWide';
sub @hbWide @hbWide' by @hbNarrow;
sub @hbNarrow @hbWide' by @hbNarrow;
sub @punctuation @hbWide' by @hbNarrow;
Multiline text issue
The first tests reminded me that multi-line text is processed as separate text sequences (for each line) and the OpenType cannot look back to the previous line. So the substitution didn't work as I expected, and every first character of a new line appears wide unfortunately (marked with red).
A questions
Have you faced such a dilemma and how did you solve it?
Is there a cases of use an Initials in Hebrew (maybe like a decorative ones for the book chapters)?
Should I abandon this idea of wide/decorative first Hebrew letter, and just find an optimal unicase design which will probably be closer to the Latin lowercase shapes?
Comments
Text in bicameral scripts like Latin are encoded with combinations of upper- and lowercase letters because the rules of capitalisation—which also vary by language—cannot be reliably captured contextually, and even with dictionary support may fail.
@Ray Larabie that's pretty interesting train of thought. That's not active by default (required the user to type the modifier key) but many people here may agreed that such experimental things should not be active by default. So this is an option. And I agree that substitution should isolated just for the current script.
However, the difficulty with this approach is educational – how to make sure users have seen the instruction poster with explanation or read the feature description?
This may be a case where a stylistic set feature is the simplest and least damaging way to implement the special letter forms.