⇒ See also Packaging:FontsPolicy#Naming we try to follow the same conventions for our wiki pages.

+

◆ Please remove the « lorem ipsum » filers once they are no longer necessary. Do the same for those comments.

+

◆ Do not forget to update the page categorization each time the font described in this page passes one packaging step.

+

-->

''Curabitur ut dui ac justo rhoncus facilisis''

''Curabitur ut dui ac justo rhoncus facilisis''

−

{{admon/note | Summary | Replace the preceding line with the package '''summary''' if the font is already packaged, or with a summary proposal if it's not packaged yet. For example « ''Foo decorative font'' ».}}

+

<!--

+

◆ Requester: replace the preceding line with a package summary proposal. For example: A decorative font inspired from xxx.

+

◆ Packager: correct the proposal and replace it with the final package summary.

* '''Format''' ② can be ''TTF'', ''OTF'' or any other font format. If the font includes advanced smart font '''features''' such as ''locl'' or ''hinting'', please document them too.

+

– Format ② :

−

* '''License''' ③ should correspond to an entry on our [[SIGs/Fonts/Legal#licenses|legal page]]. If that's not the case please follow the procedure documented on that page to check what can be done.

+

‣ we prefer modern TTF or OTF fonts,

−

* Once a package has entered the review stage, add a '''Review reference''' ④ such as [[rhbug:181994|181994]]. You can reference this wiki page in your review request as additionnal information. Please do not forget to CC ''fedora-fonts-bugs-list@redhat.com'' on your bugzilla ticket.

* Add as many lines as necessary in the preceding table. Be careful not to mix faces with different characteristics on the same line (for example if a font bundle includes a serif font with a regular and bold face, and a sans-serif font with regular, bold, italic and bold-italic faces, use two different lines).

+

— Add as many lines as necessary in the preceding table. Be careful not to mix faces with different characteristics on the same line (for example if a font bundle includes a serif font with a regular and bold face, and a sans-serif font with regular, bold, italic and bold-italic faces, use two different lines).

−

* Use ✘s to indicate a common feature is present.

+

— Use ✘s to indicate a common feature is present.

−

* '''Other''' features can be filled this way:

+

— « Other » features can be filled this way:

−

** other styles ①: ''fantasy'', ''cursive'', etc,

+

‣ other styles ①: fantasy, cursive, etc

−

** other faces ②: ''condensed'', ''extralight'', etc,

+

‣ other faces ②: condensed, extralight, etc

−

** other scripts ③: list the corresponding [http://www.unicode.org/iso15924/iso15924-codes.html IS0 15924] codes. Tools like '''gucharmap''' or [http://www.fileformat.info/info/unicode/font/custom.htm fileformat's online test] can be used to check coverage if upstream's information is not clear enough.

+

‣ other scripts ③: list the corresponding IS0 15924 codes.

−

}}

+

⇒ http://www.unicode.org/iso15924/iso15924-codes.html

−

+

⇒ tools you can use to check coverage: gucharmap, fontforge, http://www.fileformat.info/info/unicode/font/custom.htm

+

-->

== Caveats ==

== Caveats ==

Line 109:

Line 136:

# Aliquam dignissim luctus risus.

# Aliquam dignissim luctus risus.

−

{{admon/note | Packaging notes |

+

<!--

−

List there the elements you know of that will impact packaging activity, such as licensing that needs clarifying, an upstream that uses a specific non-english language to communicate, broken or incomplete build scripts, etc.

+

◆ Requester and packager: list there the elements you know of that will impact packaging activity, such as licensing that needs clarifying, an upstream that uses a specific non-english language to communicate, broken or incomplete build scripts, etc.

−

}}

+

◆ Packager: take care of those items and remove them from the page once they've been dealt with.