mbutterick
/
pollen-tfl
Archived
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
master
dev-lp
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7f873d0b6c'
${ noResults }
pollen-tfl/trademark-and-copyright-sym...

17 lines
1.0 KiB
Perl
Raw Blame History Unescape Escape

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

This file contains ambiguous Unicode characters that may be confused with others in your current locale. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to highlight these characters.

#lang pollen
◊(define-meta title "trademark and copyright symbols")
◊hanging-topic[(topic-from-metas metas)]{Don't use alphabetic substitutes}
Your keyboard includes a ◊em{trademark symbol} ◊glyph{™}, a ◊em{registered trademark symbol} ◊glyph{®}, and a ◊em{copyright symbol} ◊glyph{©}.
Use these symbols when you need them. Don’t use alphabetic approximations like (TM) or (c).
◊captioned["wrong"]{◊font-scale[2]{(c) 2015 MegaCorp (TM)}}
◊captioned["right"]{◊font-scale[2]{© 2015 MegaCorp™}}
Trademark symbols are set as superscripts — smaller characters positioned above the baseline of the text (◊em{Roxy’s Pizza™}, ◊em{Caring Is Our Business®}). If you use proper trademark symbols, they’ll appear at the right size and height. No space is needed between the text and the trademark symbol.
Copyright symbols appear in line with the text (◊em{© 1999}). Use a ◊xref{nonbreaking space} between the copyright symbol and the year to ensure the two don’t end up on different lines or pages.
Reference in New Issue View Git Blame Copy Permalink