Level up your WordPress site with premium tools trusted by professionals worldwide. Get 20% off today and join our community of successful site builders!
Limited time offer: Save 20% on your purchase. Transform your WordPress experience today.
SleekView for TranslatePress Multilingual: dictionary tables as customizable tables
TranslatePress writes translations into per-language dictionary tables like trp_dictionary_en_us_fr_fr and trp_gettext_*. SleekView reads those tables directly so missing, draft, and machine-translated strings surface as one filterable table without leaving WP admin.
TranslatePress saves translations into custom dictionary tables, one per source-target language pair, plus separate trp_gettext_* tables for theme and plugin strings. Each row holds the original string, the translation, status, first-seen date, and last-edited timestamp. The default admin pushes editors into the front-end visual editor, which is excellent for context-heavy translations and slow for bulk audits.
SleekView reads the per-language dictionary tables and the gettext tables directly and surfaces them as sortable, filterable tables in WP admin. Each row is a string with original, translation, language pair, status, and source flag (page, theme, plugin) as columns. Saved views remember the slice each translator works through.
Inline edits route through TranslatePress's API for one-liners where context is obvious. Strings that need to be seen in their surrounding page still open in the front-end editor, where TranslatePress was designed to shine.
Workflow
How SleekView reads TranslatePress dictionaries
1
Index dictionary tables
SleekView discovers per-language trp_dictionary_* tables and the trp_gettext_* tables and exposes original, translation, status, and source columns.
2
Filter to gaps
Save views for empty translations, draft entries from the last week, or strings first seen during a launch window.
3
Edit inline where context is obvious
Translate clear one-liners directly in the row. Context-heavy strings still open in the TranslatePress overlay where the editor sees the surrounding page.
4
Export translator briefs
Filter to missing-in-Spanish and export CSV with the visible columns. Translators get a clean list of original-and-context, not a screenshot tour of every page.
Sample columns
A typical TranslatePress dictionary view
Strings from trp_dictionary_* with translation, status, and source flag.
Default TranslatePress Multilingual admin vs SleekView
Default TranslatePress admin
Front-end overlay editor is slow for bulk audits
No table view of all dictionary rows in WP admin
Filters reset between editor visits
Auto-translated drafts hard to spot across pages
No CSV export of trp_dictionary_* tables
SleekView
Dictionary as a table across every language pair
Saved views for missing, draft, or auto-translated rows
Inline edit translations directly in the row
Filter by source flag, language pair, or first-seen date
CSV export for translator handoffs
Features
What SleekView gives you for TranslatePress Multilingual
Dictionary in admin
Every trp_dictionary_* and trp_gettext_* row renders as a sortable table without opening the front-end overlay editor for each string.
Find missing strings
Save a view for empty translations or auto-translated drafts in any pair and clear the queue from inside the table.
Inline edits where context is clear
Translate clear one-liners directly in the row through the TranslatePress API. Visual-context strings still open in the overlay editor.
Audience
Who uses SleekView for TranslatePress Multilingual
Localization managers
Audit dictionary coverage by language pair without front-end browsing, with row counts pulled straight from trp_dictionary_*.
Translators
Work through missing entries from a clean table view sorted by first-seen date, instead of touring the site with the overlay editor.
Editors
Confirm a new page is fully translated by filtering the dictionary to source equals that page and watching every row turn published.
The bigger picture
Why dictionary tables deserve a real audit layer
TranslatePress's auto-capture is a double-edged sword. Every translatable string a visitor sees becomes a dictionary row, which is excellent for coverage and difficult for hygiene. Within a few months of go-live a typical site has fifteen to forty thousand entries spread across pair-specific tables, and the only way to find missing or draft strings is to browse the front end with the editor toolbar open.
That works for spot fixes and breaks for ensuring the new pricing page is fully translated before launch. Reading the dictionary tables directly closes that gap. A translator can sit down with a saved view of empty-cells-in-French sorted by first-seen date and clear three hundred entries in an afternoon.
A site owner can see how many strings are still drafts and decide whether to pull or ship. The visual editor is still the right tool for context-heavy work; SleekView is the right tool for the rest.
Questions
Common questions about SleekView for TranslatePress Multilingual
TranslatePress saves translations into its own custom dictionary tables, with one table per active source-target language pair. Theme and plugin strings live in separate trp_gettext_* tables. Slug translations use trp_slug_translations.
No. The visual editor is still the right tool for translations that depend on surrounding context, such as placement and tone. SleekView is for bulk audits, missing-string queues, and clear one-liners that do not need a rendered page.
Yes. Save a view that filters to empty translations in a chosen pair. The filter persists, so the next translation sweep loads the same scoped queue.
Yes. Pro add-ons like SEO Pack and Automatic Translation write to the same per-language dictionary tables, so SleekView surfaces them identically. Auto-translated rows show their machine source clearly labelled.
Yes. Any saved view exports to CSV with the visible columns. Translator briefs scope to the rows that need work instead of dumping the whole dictionary.
No. SleekView reads dictionary tables in WP admin only and paginates server-side. The front-end TranslatePress flow that swaps strings on every visitor request is untouched.
Yes. Filter to status draft from the automatic-translation flow, review the rows, and bulk-update status to published. The plugin's hooks fire as expected when SleekView writes through the documented API.
Yes. TranslatePress slug translations live in trp_slug_translations, and SleekView ships a separate view for them so URL-level translations are auditable alongside string content.
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
