This plugin is designed to allow a WordPress user to add an ISO 639-3 language code to in a custom field related to their post so that their posts can be organized by ISO 639-3 code. One advantage of this would be to list their WordPress install as a language resource with OLAC.
Known bugs and/or conflicts
version 0.1.3 None
version 0.1.2-beta plugin folder needs to be renamed to langauge_code this is corrected in version 0.1.3
0.1.4: IN PROGRESS
It would be nice to add the functionality to the plugin to allow an author to replace or insert any text field with the one auto suggesting language codes, by calling a function. It should probably have syntax or form after the order of: place
<?php do_action('plugin_name_hook'); ?>in the templates/widget/. The end result for the user would be that they could create a meta-data input from more than just the admin area (i.e. a from in another plugin, like a form creator, or the front end of WP.)
Need to Validate input against table (instead of writing straight to the DB, write to cache, validate and then to DB) e.g. what if someone types in ‘zzz’ and ‘zzz’ is not a language code?
Add multiple codes to a post dynamically e.g. (I have a data file with 2 languages connected to one post, but not every post.)
Translation file (A
.pofile This is a two fold issue Language names are different in different languages i.e. Deutsch, German, Allemand. This might be a table being developed by another part of the ISO 639 standard. Possibly, 639-6 See this wikipedia article http://en.wikipedia.org/wiki/ISO_639-6)
Add hook for disply in theme per key
Because each of the ISO 639-3 codes are stored in a custom field, and each custom field has two parts, a key and a value, It is necessary to be able to set the key as well as the value (and the default key). The Plug-in in its current state has only focused on adding the value part of the key-value pair. It is important for developers to know that a single post should be able to have more than one key with language codes in them. For example, if I have a post which is a linguistics exercise in phonology, then I might want to put the language of the instructions of the exercise in one key and the language code of the exercise data in another key.
An entirely different scenario is one where a post has two languages under one key. This is currently unaccounted for with the current state of the plug-in. E.g. If in the body of a post an author were to use two languages equally then they might want to use the same key to represent both languages.
- Promote at Weblog Tools Collection
- Promote Using Social Networking
- Promote On Your Own Blog
- The download location.
- A list of features.
- Contact or support information (or comments enabled)
- Auto detect and import of SIL’s tab file when SIL updates their tab file at: http://www.sil.org/ISO639-3/iso-639-3_20090210.tab.
Update notice to the user so that they know to update their plug-in every year when SIL updates their ISO changes. Or decide to follow a regular release cycle (at least annually) and maintenance with this plugin.
pursue use of ISO 639-3 in conjunction with the doublin core metadata standard
- Doublin Core metadata plugin
- Doublin Core metadata plugin
- Consider development beyond ISO 639-3 to ISO 639.
- What is ISO 639-3?
ISO 639-3 codes are codes for the representation of names of languages. ISO 639-3 attempts to provide as complete an enumeration of languages as possible, including living, extinct, ancient, and constructed languages, whether major or minor, written or unwritten. More information can be found at http://www.sil.org/iso639-3/.
- Who controls ISO 639-3?
The ISO does but, you can contact the registrar, SIL International.
- What are the plugin dependencies?
Everything you need to make this plugin work with wordpress ships with the plugin.
However in our code we have used the ISO 639-3 UTF-8 table provided by SIL International http://www.sil.org/ISO639-3/iso-639-3_20090210.tab This table is updated annualy.
We also have used and modified the jQuery autocomplete script made availible by PengoWorks.Com (http://www.pengoworks.com/workshop/jquery/autocomplete.htm “http://www.pengoworks.com/workshop/jquery/autocomplete.htm”)
0.1.3: CURRENT VERSION
- bug fix: changed the plugin folder name from language_code to language-code to follow WP Extend conventions. This also affected several paths to. js files.
- Promoted at the WordPress Plugin Database as 0.1.2 beta
The autocomplete seems to work better now. Can do accent/case insensitive searches.
- fixed bug for
MYSQL SELECTquery for searching (
TABLE language_codeto be
utf8_general_cito be accent/case insensitive for searching (
- specified for client browser to request
MYSQLto receive/send search in
utf8_general_cifor accent/case insensitive searching (
- fixed bug for
- Appache 2.2.11
- MySQL version: 5.1.30 (K) and 5.0.32 (H)
- PHP version: 5.2.8 (K) And 5.2.6 (H)
- WordPress Version: 2.7.1
- Language_Code Plugin version 0.1.2 Beta
- Database version: 1.0
- General working plug-in but some language’s ISO codes would not show up when typed in. e.g. typing in ‘gel’ did not bring up ‘Kag-Fer-Jiir-Koor-Ror-Us-Zuksun’ this was a big bug.
- Import ISO 639-3 to WP_ table Creation