HTML

Hello everyone,
I try to explain you the problem.

I created a typography that has both common (e.g. between "f" and "i") and custom (e.g. between "p" and "p") ligatures and used FontLab to export the font in ttf.
Now I want an HTML page to display the font and I write & #xFB01 for common ligature between "f" and "i".
But where should I operate to display custom ligature between "p" and "p"?

Thank you in advance for your attention!
Filippo

Hello everyone,
I try to explain you the problem.

I created a typography that has both common (e.g. between "f" and "i") and custom (e.g. between "p" and "p") ligatures and used FontLab to export the font in ttf.
Now I want an HTML page to display the font and I write & #xFB01 for common ligature between "f" and "i".
But where should I operate to display custom ligature between "p" and "p"?

Thank you in advance for your attention!
Filippo

As the title says: this is the html code of a table that should be displayed correctly within a typophile thread using the allowed tag iframe.

I made this introduction to typography website a couple weeks back for a class project. I wanted to give the basics of type in a super dumbed-down way. What do you guys think?

http://willryan.us/typefun01/

allefio's picture

Font ID html5

Hi everybody, i'm looking for the font of the number in the html5 logo.
Does anyone know?

Thank you.

Tool for creating HTML websites that want to stop using the suicidal "k"/"K" letter (http://Kalphabet.googlepages.com) and use another letter shape (i.e. क) instead.

Type your site's content text: http://HTMLtool.yolasite.com

Now that webfonts are supported by all major browsers, more and more professional fonts are available for web linking. These fonts usually contain a large set of OpenType features, which are only accessible in OpenType-savvy applications like InDesign, Illustrator or QuarkXPress. Browsers have barely supported such advanced typographic features so far. But with the latest Beta of Firefox 4 this is about to change …

http://bit.ly/9FVmg0

see also: http://typophile.com/node/73173

Every comment needs a permalink. A fragment identifier (starting with a letter, followed by letters, numbers, dashes, or periods) is sufficient if such is exposed to us without having to view source. (It doesn’t have to be like Twitter, where every Twit gets its own Web page.)

This bug is well known. We need BLOCKQUOTE, actual heading elements (perhaps just H2 through H6), possibly a few more.

However, enabling the IMG element is dangerous, as MetaFilter has learned the hard way. One can encode JavaScript exploits in URLs or the src of an image. Limiting images to attachments (kind of odd for a Web site, less so for a discussion forum) is a reasonable compromise.

I am a traditional typographer having difficulty understanding HTML tools, some are easy, such as emphasis; though why "ital" wasn't used rather than "em" is a mystery; shouldn't "em" have been reserved for an em-space?

The above example is easy to set in typographic programs such as QuarkXPress or InDesign, and the coding made sense on Quadex and other type systems, back in the day. Note that there are hanging numerals in bold, the text is set 9/11, with alignment for breaking lines, and 2 pts additional space between paragraph returns.

The same goes for the superior shown, again, easy in Quark or InDesign, nearly impossible (at least to me) in HTML.

I hate to bring this up, but it has always bothered me about Typophile:

Quotations are the backbone of discussion, but two positively mundane HTML elements, <q> and <blockquote>, are disallowed?

Because of this, the poor <cite> element is used and abused, although it is not the most appropriate markup for quotations.

According to the W3C, "<cite>" is markup for text which "contains a citation or a reference to other sources." (HTML 4.01 Specification § 9.2.1 Phrase elements)

Allowing <cite> is fine, even giving it a little semantic wiggle room, but not allowing <q> or <blockquote> is just plain silly.

Given that this is a forum for discussion, shouldn't the proper markup be allowed?

Syndicate content Syndicate content