Xili-dictionary v2.3: what's new ?

( being written and tested under WP 3.5rc2 )

xili-dictionary version 2.3 adds new visible (or not visible) features to improve importing and deleting process to avoid previous browser freeze when big files are imported or huge quantity of msg posts are erased inside WP database.

Contents

Importing

IMPORTANT NOTE : xili-dictionary is yet made to manage po, mo file of the current theme. Don't copy (big) files of WP core (present in wp-content/languages) ! In future release, it will be possible to work on plugin files...

Import settings screen before launching


[1] : The type of file to import (pre-selected by the calling button.

[2] : This option only available on WP Network install for SuperAdmin to choose the origin folder.

[3] : To import or not loca-xx_YY file previously made by xili-dictionary.

[4] : The language of the file (french will try to find fr_FR)

[5] : Option about comments included in PO file: if msgid exists in dictionary, you can decide, by example, to append the imported comment to the preexisting comment in db for this msgid.

[6] : This part is reserved for future uses to set the ajax loop when importing large file.

[7] : The button to start the importing processes loop indicates the name of the file. When clicked, a log window appears below.


After importing processes, go to the list of msgs and begin to translate. ;-)

Erasing

Erase all (or selected terms) of the dictionary. With this window, you can decide which msg to erase from database. (The files .mo and .po are not erased). Be aware and test on a non-production website to understand the processes.

Erasing settings screen before action

[1] : When checked, only msgs savable in local-xx_YY files, are erased. Only remain terms of theme himself.

[2] : Msg is the index of one entry in po or mo list. Here you decide what to erase, only the translation (msgstr) in one or all languages or both.

[3] : If you use taxonomy 'origin' in the msg list, here you select the terms belonging to one or more group.

[4] : This part is reserved for future uses to set the ajax loop when erasing quantity of terms.

[5] : The button to start the erasing processes loop indicates the name of the file. When clicked, a log window appears below.

After erasing processes, go to the list of msgs and see the results ;-) and reimport if necessary ;)

Parse and Scan source files (experimental)

preview of scanned files and terms ready to be imported


If you are developer of your theme or child theme, if you don't want to use poedit desktop software, if the theme is translation ready (with gettext functions) but does' not contain the wanted .po or .mo files, you can try to rebuilt them via xili-dictionary...

[1] : List of the theme's files scanned and (count of translatable terms found),

[2] : List of terms found,

[3] : Warning infos : Only use this possibility if no po, pot or mo file are provided by the theme maker. (this importer is experimental and only detect the I10n functions __( , _e( , _x( , _ex( , _n( and _nx( ).

[4] : If you agree, click and visit the list after to begin translation, create mo files (or po files for archiving or to send it to your devoted translator using a text editor ;-)

Other improvements

Some queries are improved using new features of WP_Query class of WordPress ( >3.4).

Better conditional controls in specific configurations.