French Typo

开发者	jaz_on audrasjb juliobox beryldlg
更新时间	2026年9月23日 04:18
捐献地址:	去捐款
PHP版本:	7.4 及以上
WordPress版本:	7.1.2
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.2.0 1.1.0 1.0.0 1.2.1 1.2.2 1.2.3 1.2.4

详情介绍:

French Typo applies French typography rules to your content as it is displayed. Your text stays exactly as you wrote it in the editor — only the rendered output is enriched. What it does:

Adds non-breaking spaces before : ; ! ? % and around « »
Replaces (c) with ©, (r) with ®, (tm) / (TM) with ™
Optionally normalizes French ordinals: 1ère → 1re, 3ème → 3e, n-ième → nième
Works across posts, pages, widgets, menus, comments, RSS, REST, ACF / Meta Box fields, and SEO output (Yoast, Rank Math, SEOPress)
On multilingual sites, can apply rules to French content only (Polylang and WPML auto-detected)

What it does not do:

Touch your raw HTML, code blocks, scripts, styles, or <textarea> content
Modify what's stored in the database

Settings highlights

Regular ( ) or thin ( ) non-breaking spaces
Enable / disable each content area (title, content, excerpt, widgets, RSS, REST, etc.)
Language restriction: off (default), auto French, or pick specific locales

安装:

Install through the WordPress plugins screen, or upload to /wp-content/plugins/french-typo.
Activate the plugin.
Configure in Settings > French Typo.

常见问题:

Does this plugin modify my content?

No. The text saved in the database is never altered. French Typo intercepts the output just before display and adds the typography rules there. Deactivate the plugin and your content comes back unchanged.

Regular or thin non-breaking spaces?

Regular ( ) is universally supported. Thin ( ) is typographically purer for : ; but may render too narrow or as a missing glyph on older fonts and browsers.

Can I limit rules to French content only?

Yes. In Settings > French Typo > Language restriction, choose Auto to apply only to fr_* locales, or Custom to pick specific locales. Polylang and WPML are detected per post; otherwise the site locale is used.

Will it run inside code blocks, scripts, or <textarea>?

No. Typography is skipped inside <script>, <style>, <pre>, <code> (nested), <textarea>, and embedded CSS (e.g. inline SVG). Gutenberg's Verse block stays typographic unless it is also a Code block.

Does it change English ordinals (1st, 2nd) or non-standard forms like 1ème?

No. Only the French forms listed in the description are converted.

My theme or editor already inserts non-breaking spaces. Will French Typo duplicate them?

No (since 1.2.2). All non-breaking space variants — , , ,  ,  , and literal U+00A0 / U+202F — are detected and collapsed to a single canonical entity.

更新日志:

Full history for all versions: CHANGELOG.md on GitHub. 1.2.4

Fixed: Settings page — the "Ordinal abbreviations" option is visible and can be toggled again.
Fixed: Settings page — clearer labels for the "Language restriction" fields.
Fixed: Shortcode attributes (e.g. [gallery caption="Merci !"]) are no longer altered by typography rules before the shortcode runs.

1.2.3

Fixed: HTML entities in plain-text titles (e.g. Foo & Bar) had a narrow no-break space inserted before their trailing ;, which downstream esc_html() then re-encoded into visible &#038 ; (e.g. in Yoast breadcrumbs). Entity protection now runs on any text containing &, not only on text containing tags. (#10)

French Typo

标签

下载

详情介绍:

安装:

常见问题:

更新日志: