
ACF: GOOGLE FONT SELECTOR
ACF: Google Font Selector compatibility with REEID Translate
ACF: Google Font Selector compatibility with REEID Translate is being reviewed using official plugin documentation. Font loading is enqueued automatically for fonts added to ACF options pages, and only enqueued on the specific post when fonts are added to post pages (conditional enqueueing). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What ACF: Google Font Selector does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
ACF: Google Font Selector is documented in the Performance category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How ACF: Google Font Selector compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Font loading is enqueued automatically for fonts added to ACF options pages, and only enqueued on the specific post when fonts are added to post pages (conditional enqueueing).
- The plugin can create a font request in the theme header to autoload fonts, enabling theme-level integration for font loading.
- Font list retrieval can use a static file included in the plugin by default, or pull from the Google API when an API key is configured.
- Optional Google API refresh behavior is configurable via the `ACFGFS_REFRESH` constant (controls how frequently the plugin checks the Google API for updates).
- Automatic enqueueing can be disabled via the `ACFGFS_NOENQUEUE` constant, limiting font enqueuing to manual/other mechanisms.
- Developers can modify which fonts (including variants and subsets/charsets) are enqueued via the `acfgfs/enqueued_fonts` filter, allowing more targeted font loading for performance optimization.
TRANSLATION BOUNDARY
ACF: Google Font Selector capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
ACF: Google Font Selector and REEID Translate FAQ.
What does ACF: Google Font Selector do?
ACF: Google Font Selector has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does ACF: Google Font Selector have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from ACF: Google Font Selector?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate ACF: Google Font Selector in a multilingual WordPress workflow.
REEID documents ACF: Google Font Selector functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.