New to Typophile? Accounts are free, and easy to set up.
Technically it is possible to add both a ligature in the common form of "f_f_i" (and its accompanying Feature code) and a separate Unicode glyph for the same character -- U+FB03 for "ffi" -- to the same font.
Is this a good idea? I'm pretty sure it's not!
I only tested this with InDesign, but I vaguely recalled that it would automatically use "fi" and "fl" ligatures, if a font had these characters in the correct Unicode positions. However, a quick test with a freshly created OTF font shows it does not (in CS4, at least). Perhaps this is (or was) only true for Plain Old Type 1 fonts without any further OTF enhancements.
I am fairly new to vectorizing type and I would like some very constructive and critical feedback. I am very new to Glyphs and that is what I used to build this out (see the below to get all intimate with my nodes). Please let me know what you think! Where I can improve it, and other thoughts.
A colleague of mine is working on a book of Thoreau's letters and a question was raised as to whether we could use an AD ligature (as in A.D. or Anno Domini) in the text. I had never seen one and was curious to find out more about it.
A quick search revealed this Flickr photo of the ligature on a bell in Boston. The quality of the photograph is terrible and that's all I was able to find.
I'm hoping someone here is more familiar with this ligature and can point me to some other examples of it.
& (the ampersand) is a ligature for 'et', latin for 'and'. Although archaic you can use '&c' the same as 'etc' as a shortened 'Et cetera'. & (the ampersand) being a ligature for 'et', I am curious to whether there are any historical examples of ligatures being designed for 'etc'.
I created an example of what a ligature for 'etc' could look like: http://bit.ly/cKOH8v
Does anyone know of any actual historical examples?
I realised a few days ago I know nothing about ligatures involving ellipses - things such as "What did she ..?" or "I said, get your filthy ..!". I couldn't find any useful information from the general internets, and it's certainly not a kind of ligature ever considered for inclusion into the unicode standard. I also couldn't find a thread in the forums here concerning this type of ligature, so my question really is: who has thought about these?
Has anyone ever seen a discussion of this ligature in a book or on the internet? I'd love to know what history it has.
- Mike "Pomax" Kamermans
I'm putting together some secondary logo fields for a healthcare system's new identity and having major problems with the "rv" and "ry" pairings. I've searched the interwebs and haven't found any standard ligatures for these. I've had to keep the kerning pretty tight because some of the names get pretty long (ie: Physical Rehabilitation), but I don't think it's too tight.
The font is DIN Next Regular, and I've gone ahead and created my own ligatures. I'm not a type designer so I thought I'd post what I've got and see if anyone has ever had this problem themselves and to get any general feedback on my solution.
Fire away! And thanks for any help.
I run on Windows XP Pro. Over the last few years I've been "collecting" some good quality OpenType fonts, many from P22 Type Foundry in their "PRO" format. The "PRO" .otf files include a lot of the special characters: ligatures, glyphs, swash caps. small caps, etc., etc.
Problem: The Windows Character Map accessory program will only show me the standard 256 characters usually included in .ttf fonts.
I use a page layout program (Serif PagePlus X3) that is able to display and implement a font's special characters. But, having to open large, fullblown software just to view a character's map is ponderous.