xili-dictionary is a dictionary storable in custom post type (CPT) and terms (custom taxonomy) to create, update and translate .po files or .mo files of current theme folder and of current plugins.
- xili-dictionary is a plugin (compatible with plugin xili-language) to build a multilingual dictionary saved in the post tables of WordPress as CPT to build .mo files (used online by WP website), .po files (file assigned to a language and used by translator, text format of compiled .mo), and now .pot files. A .pot file (of theme or plugin) can be generated from sources w/o importing entries in dictionary. Files are read and saved on the right place (languages sub-folder) but can also be download on your desktop computer.
- With this dictionary, collecting terms from taxonomies (title, description), from bloginfos, from wp_locale, from current theme – international terms with
_e(), __() or _n() or _x(), _ex(), _nx(),...and other functions as in I10n.php – , it is possible to create and update .mo file in the current theme folder and current plugins.
- By importing .mo files, it is possible to regenerate readable .po files and enrich translation tables.
- xili-dictionary is full compatible with xili-language plugin and xili-tidy-tags plugin. Also compatible with xili re/un-attach media !
- xili-dictionary can be used w/o a multilingual plugin or with multilingual plugin based on taxonomy named ‘language’ (Polylang).
- As educational plateform in constant changing, xili-dictionary tries to use most of the WordPress Core functions and features (CPT, metabox, pointer, help, pomo libraries, …).
According some users, current versions can be stable with recent WP versions. BUT since 2 years, a new version is fully rewritten and tested in few websites. These new versions are available in Github and here in WP repository in tag Advanced View. Your feedback will be very valuable.
- code source renewed continiously with latest WP tools since WP 4.3
- readme rewritting
Version 2.12.5 (updated 2016-07-29)
see Changelog tab.
This releases are for theme’s creator or designer with some knowledges in i18n. Help are more and more included inside help tabs of dashboard and each screen.
The plugin post is frequently updated wiki.xiligroup.org
See also the WordPress plugins forum.
© 2009-2016 MS – dev.xiligroup.com
- Upload the folder containing
xili-dictionary.phpand language files to the
- Verify that your theme is international compatible – translatable terms like
_e('the term','mytheme')and no text hardcoded –
- Activate and visit the dictionary page in tools menu and docs here –
- To edit a msg, you can start from dictionary list or XD msg list using current WP admin UI library. Don’t forget to adapt UI with screen options and moving meta boxes.
More infos will be added progressively in a wiki here.
Why xili-dictionary is not included in xili-language ?
- because xili-dictionary is available for non multilingual site to manage theme and plugin translations.
- because it is possible to desactivate xili-dictionary after creation of .po .mo files used by WP, xili-language or other extensions.
Where can I see websites using this plugin ?
Twenty Fifteen 2015 – contains also tips and tricks about WordPress
Twenty Fourteen 2014 – contains also latest informations and documentions about xili-language trilogy
Twenty Thirteen 2013
Twenty Twelve 2012
Twenty Eleven 2011
Twenty Ten 2010
The reference website under renovation:
And as you can see in stats, thousand of sites use xili-language.
What is the difference with msgid and msgtr in .po file ?
The msgid line is equal to the term or sentence hardcoded in the theme functions like
_e() or __(). msgstr is the translation in the target language : by instance
fr_FR.pofor a french dictionary. (the compiled file is
fr_FR.mosaved in the theme folder.
The root language is in WordPress currently
en_US, but with xili-dictionary, it is possible to create a
en_US.mocontaining the only few terms that you want to adapt or modify.
Is xili-dictionary usable without xili-language to edit .po or .mo file ?
Yes and now automatically detected ! For example, to modify the results of a translation for your site with your words.
What about plural translations ?
Today works with .mo or .po with simple twin msgid msgstr couple of lines and themes with functions like
_e() or __()for localization AND
_n()which manage singular and plural terms like
msgid, msgid_plural, msgstr,...
What is a po file ?
It is a text file like this (here excerpt) with different types of msgid :
msgctxt "comments number" msgid "%" msgstr "%" msgid "Leave a reply" msgstr "Laisser une réponse" msgid "One thought on “%2$s”" msgid_plural "%1$s thoughts on “%2$s”" msgstr "Une réflexion au sujet de « %2$s »" msgstr "%1$s réflexions au sujet de « %2$s »" msgctxt "sentence" msgid "comment" msgid_plural "comments" msgstr "commentaire" msgstr "commentaires"
What happens if only the .mo is available ?
xili-dictionary is able to import a .mo of the target language and rebuild a .po editable in backend or a text editor. Example: if it_IT is in your language list, it_IT.mo can be imported, completed by webmaster and export as it_IT.po text file in languages sub-folder of the theme (as text backup).
What is the differences with poEdit application ?
Poedit is a standalone desktop application. Poedit offers the ways to translate apps and sites (that use gettext). This application is used by us to create localization of this and other plugins.
xili-dictionary is online and based on WP Core and essentially made for files used by WP (theme, plugin, custom terms of site…). For technicians, some advantages: possible to recover .mo files, to translate online items, to export .pot files, and more… It is also possible to import msgid present in new template default functions introduced in recent versions.
What about WP multisite (or network – former named WPMU) and the trilogy ?
Since WP 3.0, if multisite is activated, the trilogy is compatible and will include progressively some improvements dedicaded especially for WP network context.
Il n’y a aucun avis pour cette extension.
Contributeurs & développeurs
« xili-dictionary » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.Contributeurs
- verified with 4.5.3 – pretested with 4.6-rc1 – cleaning code continues…
2.12.3 (2015-11-04 2016-01-24)
- better role management, cleaning code continues…
2.12.2 (2015-09-28 )
- better Polylang compatibility
- improved msgid_exists – if contains slash
- ready with xili-language version 2.20.3+
2.12.0 (2015-06-28 ) – 2.12.1 (2015-07-05 )
- better labels in Writers and Origins taxonomies
- able to import parent sources if a child theme active
- writers displayed in list of msgs
- able to import keys of config.xml file (like in WPML)
- compatible with Polylang ‘language’ taxonomy
- datatables js updated to 1.10.7
- pre-test with WP 4.3-beta1
- link title added
- more terms from post-template.php of core
- core import process improved
- fixes import terms from comment-template.php and now try to add default translations (msgstr) for imported term (msgid).
- if you switch language of dashboard is other than in en_US, then the import process of sources msgid will try to import translations of chosen language.
- fixes in multisite mode (edit-tags screen)
- tested WP 4.2.2
- now able to import msgid from sources (theme, plugin) only in .pot file
- tested WP 4.2
- can import msgid of get_the_archive_title (since WP 4.1)
- improves adding context only after draft state
- now able to use flags available in Medias Library (if xili-language is active)
- Updated datatables js css
- tested WP 4.2-beta2
- fixes no context msgid creation after creation with context
- manages plugin language files in WP_LANG_DIR
- collects comment-template.php msgids
- better queries for WP 4.1 Dinah
2.9.2 (2014-12-16 17:00)
- fixes WPLANG (obsolete in WP4.0)
- fixes .po and .pot export in current child theme if files dont exists
- fixes js for file state of local- files in multisite install.
- Better import from local- mo file
- During deletion, if a msgid has more than one origin, the msgid is not deleted, only origin is unassigned.
- better message when creating or download or file writing,
- import from source files (current theme, plugins), a good way if no pot files delivered by authors,
- fixe uppercase content (BINARY),
- more local js for ui.
- can now create pot file,
- improvement in export, UI and texts.
- disable media button,
- subtitle of msg,
- formatted title (based on id).
- clean code
- fixes issue in download
- improve detection of existing msgid with context during manual creation. Need draft step to define context.
- able to save local-xx_XX (po or mo) in wp-content/languages/themes/ (WP_LANG_DIR)
- fixes issues when importing plural form.
- tested with WP 3.9-RC1
- fixes issues with pot file name and verify no msgstr when importing pot file.
- clean obsolete codes
- possible now to manage language files from plugins
- more embedded help
- possible now to download language files to computer for further works.
- limits scripts enqueuing to this plugin.
- WP3.8 improvements – fixes noun comment import,
- detect context when detecting duplicates
- fixes selector issue when importing pot file.
- tests WP 3.6 final
- add column type / origin in msgs list,
- add parent theme origin when import/export if child theme
- clean obsolete code lines
- fixes (capability)
- tests WP 3.6-beta3
- clean $wp_roles on deactivating
- able to import/export from parent languages subfolder if child theme active.
- tests 3.6 *
- improve import title for context of languages (no context for languages list) (XL 2.8.8+)
- Fixes origin in menu
- import titles of xili_language_list – the_category (xili_language 2.8.7)
- tested with WP 3.6 beta
- add infos and links in cat (removed from xl)
- import from sources : detects esc_html and esc_attr functions (I10n.php) and more.
- improved UI linking Categories (Taxonomies) and Translations in Edit Categories list,
- add feature to sort msgid by text,
- improved UI when editing msg,
- manage capabilities and option to add editing capability to role Editor.
- add support email form as in xili-language or xili-tidy-tags
- enable to import mo or po files of themes in languages folder (wp-content). So easy to create an adapted copy in theme languages sub-folder (since WP3.5)
- Tests WP 3.5.1 and XL 2.8.4, fixes
- add ajax functions for import and erase functions (big files, no freeze)
- fixes issues of 2.1 series (messages, import, conditions, and more…).
- 2.1.2 and 2.1.3 removed from repository
- list of untranslated msgs in edit msg screen.
- shortcut in side metabox to update .mo of current lang. See xili wiki
- fixes local-xx_XX import – new icons
- in multilingual website context, requires version 2.6 of xili-language.
- local datas saved in local-xx_XX .mo/po files.
- origin taxonomy used to manage one dictionary with multiple themes.
- see xili wiki
- 120417 – repository as current
- 120405 – pre-tests with WP 3.4: fixes metaboxes columns
- 120219 – new way of saving lines in CPT – new UI using WP library
- now msg lines full commented as in .po
- now translated lines (msgstr) attached to same taxonomy as xili-language
- compatible with theme and language files in sub-sub-folder.
- IMPORTANT – before upgrading from 1.4.4 to 2.0, export all the dictionary in .po files and empty the dictionary.
- 111221 – fixes
- between 0.9.3 and 1.4.4 see version 1.4.4 – 20120219
first public release (beta)
© 20160729 – MS – dev.xiligroup.com