10 Deadly Semantic Mistakes in Web Typography

10 Deadly Semantic Mistakes in Web Typography
<br />This is from the content of Web front-end development design essentials written by Steven D.
Although many designers are already very proficient in using web standards, it is regrettable that many details of typography still run counter to traditional screen printing requirements. Here are 10 deadly semantic errors that you should avoid in your web typography:

1. Use hyphens instead of an em dash

Using em dashes is a very popular practice among web editors today.
2. Use periods, not ellipses

This is a specialized typographical ellipsis mark (especially in Western European characters) consisting of three dots, as distinguished from the Chinese ellipsis symbol.
3. Use correct quotation marks

In quoted sections, you should keep quotation marks where necessary, which will indicate whether the section is licensed for use or is freely available for distribution.
4. Strictly control the double spacing between sentences

This is a classic mistake from the ASCII era. Double spacing is no longer used, so please be aware of this.
5. Accurate use of copyright symbols

Using the wrong copyright symbol not only violates the copyright agreement but may also have a negative impact on your copyright protection. You should use McCoy (&copy;), which is the standard copyright symbol.
6. Don’t use too many emphasis expressions in your sentences

You can use bold, italics, or underlining to emphasize your content, but please don't use them on the same line.
7. Your hypertext link is underlined, not other content

This doesn’t make the content clearer to read. In fact, the reader can’t figure out why it’s important. If you really want to do this, you can try using border-bottom: solid 1px #00f; instead.
8. Design fake font styles through Photoshop

If your font does not provide bold, italic and other styles, please do not make them into pictures in Photoshop and then mix them into your web layout. This is very childish.
9. Don’t use accent characters

When you use words from other languages, especially names of people, please do not assume that your accent will determine the writing style. This is very impolite.
10. Don’t use CSS to define uppercase characters

Capital letters are difficult to read in the first place, so use them sparingly unless necessary for decoration, especially in full lines of text.

<<:  Solution to the problem of automatic restoration after modifying server.xml and content.xml in Tomcat

>>:  How to pass the value of the select drop-down box to the id to implement the code

Recommend

HTML page jump code

Save the following code as the default homepage fi...

In-depth analysis of the Linux kernel macro container_of

1. As mentioned above I saw this macro when I was...

Mysql SQL statement operation to add or modify primary key

Add table fields alter table table1 add transacto...

Implementation of webpack-dev-server to build a local server

Table of contents Preface webpack-deb-server webp...

CSS3 transition to achieve underline example code

This article introduces the sample code of CSS3 t...

Do you know how to optimize loading web fonts?

Just as the title! The commonly used font-family l...

A detailed guide to custom directives in Vue

Table of contents 1. What is a custom instruction...

Example of how to configure nginx to implement SSL

Environmental Description Server system: Ubuntu 1...

Detailed explanation of Tomcat directory structure

Table of contents Directory Structure bin directo...

Detailed process of building mongodb and mysql with docker-compose

Let's take a look at the detailed method of b...

KVM virtualization installation, deployment and management tutorial

Table of contents 1.kvm deployment 1.1 kvm instal...

Case study of dynamic data binding of this.$set in Vue

I feel that the explanation of this.$set on the I...